Create a new server for MySQL - Connect_CDC - aws_mainframe_modernization_service - connect_cdc_mimix_share - Latest

Name

Use alphanumeric characters to specify a unique server name for use in the model.

DBMS Type

Select MySQL from the dropdown list.

DBMS version

Server name

Specify the name of the server you want to model. Often, the value you enter here is the same as the host name of the system where MySQL is installed.

DBMS instance port

Specify the DMBMS instance port. The default value is 3306.

JDBC Driver

Driver Version

View the JDBC Driver version. This information is obtained each time a connection to the database is made (including a Test Connection).

DBMS logon IDs and DBMS logon password

• DBMS logon IDs—When you select rpuser as the DBMS logon ID, rpuser is the Default user and default Rep user. Note that both of these checkboxes are checked and grayed out.

• The Default user is what Connect CDC Director uses to connect to the server.

• The Rep user is what the kernel uses to connect to the server.

• DBMS logon password—You must enter a valid password for rpuser. If you do not, the install metabase process will fail. If you do not enter a password and leave the field blank, you will receive an error when you attempt to exit the Server Properties, Server dialog.

Metabase schema

Set to the owner of the metabase. It is the qualifier of the metabase tables, in the format qualifier.tablename. You cannot edit this field. This field is pre-filled with dbo.

Enable Prepared Statements

If selected, prepared statements are enabled for the entire database server. A prepared SQL statement is a statement in which the steps to parse, analyze, validate, and determine the access path are only done once, when the statement is first prepared. On subsequent executions of the statement, the database has this information stored in memory and can skip the initial preparation steps. After a statement is prepared, only the column values change from one execution of the statement to the next.

Each table can have as many as seven prepared statements: one for insert, up to five for update, and one for delete. The first time an insert, update, or delete is encountered, the statement is prepared, added to the cache, and is used to update the table. The statements are kept in the cache until removed.

Using prepared statements provides a significant performance improvement when the same SQL statement is executed over and over. However, in some cases data for unchanged columns will be captured and sent across the network.

Individual tables can disable prepared statements. This is useful for managing the size of the cache file.

Database limit

Displays the maximum size allowed by the database for open statements in the cache. The Specified limit, below, cannot exceed this value. The correct value is provided after you run a Test Connection. To do so, right-click the server name, then select Test Connection.

Specified limit

Enter the maximum size allowed for open statements in the cache. When the statement cache is full, the least recently used statement is removed from the cache, closed, and destroyed. If Journal batching is enabled, prior to removing the statement, pending batch updates are executed, If the statement that was removed is later referenced, a new prepared statement is created and added to the cache.

Remote Machine Name or IP

Select this checkbox if you are creating a new remote server for MySQL. Refer to Create a new remote MySQL. Specify the remote machine name or IP address. The remote machine name or IP address must be a valid machine name or IP address of the machine hosting the remote MySQL instance. The remote machine name (or IP address), and the Server name establish the connection with the remote server. This is a required field.

Model using metabase

Displays the name of the model. (Informational only)

Model version

Displays the version number, updated after each commit. (Informational only)

Metabase version

Displays the version of the metabase (for example, 40d). (Informational only)

GMT offset(minutes)

Displays the amount of time, in minutes, that local time differs from Greenwich Mean Time (GMT). For example, Boston is 300 minutes less than GMT. (Informational only)