Overview
MySQL is the open-source relational database now owned by Oracle. In an enterprise estate it is rarely the system of record for finance or HR, and it is very often the back end of everything else: internal web applications, wikis and portals, open-source monitoring and ticketing platforms, and the embedded database inside network, storage and security appliances. When a team says “the data is in the app’s database”, on a Linux estate it is frequently a MySQL instance they mean.
The ReadyWorks connector connects directly to a MySQL server over the network using the mysql.php driver and a username and password. A job carries a SQL statement in its Data Selection field, ReadyWorks runs that statement, and the result set is written to the destination staging table with one column per selected column. There is no intermediate file and no export step.
This matters when the data you need has no API in front of it. An application that tracks licences, seat assignments or approvals in its own tables can be read directly, joined to device and identity data in the data fabric, and used to drive the same workflows as any API-sourced feed. Because the job runs arbitrary SQL, you can shape the extract at the source with joins and a WHERE clause instead of staging the whole table and filtering later.
The connector is inbound only. It reads query results and writes staging tables, and it issues no writes to the source database.
NOTE: Give ReadyWorks a dedicated database account with read access only to the tables it needs. The job runs whatever SQL the Data Selection field contains, under whatever privileges that account holds.
Connector Properties
Authentication Methods
One method ships: a direct network connection with a database username and password.
NOTE: The connection form has no field for TLS, certificate verification or a CA bundle. Place the ReadyWorks server and the MySQL server on a network path you trust, or front the connection with a tunnel.
Method 1: Username / Password (MYSQL_user)
Connect to a MySQL Server
Username / Password connects to the MySQL server named in Source Server on the port given in Source Server Port (the default is 3306), authenticates with the supplied credentials, and selects the database named in Source DB Name. All five fields are required. The password is stored encrypted.
Connection Configuration Fields (5)
No authentication recipe is stored. The driver script authenticates natively using the fields above.
Inbound Job Fields Enabled (13)
These are the job-level settings exposed for a MySQL extract. Data Selection holds the SQL statement.
Inbound Job Templates (1)
One inbound template ships as a worked example. It arrives disabled and carries a placeholder query, so it is a pattern to copy rather than a job to enable.
Job Template Configuration
Settings
Job Parameters and Enumeration
MySQL Table Data
Data Selection: SELECT * FROM {tablename}
Outbound Job Templates (0)
This connector ships no outbound templates and does not support outbound jobs.