Configuring Db2 for LUW workspace data connections
During workspace creation, under Connection Type, click Db2 for LUW.
Connecting to the source database
In the Source Settings section, you provide the connection information for the source database.
Providing the connection details
To provide the connection details for the source database:
In the Server field, provide the server where the database is located.
In the Database field, provide the name of the database.
In the Port field, provide the port to use to connect to the database.
In the Username field, provide the username for the account to use to connect to the database.
In the Password field, provide the password for the specified username.
To test the connection to the source data, click Test Source Connection.
Ensuring encryption of source database authentication
The Enable SSL/TLS setting indicates whether to encrypt source database authentication.
By default, it is in the on position. We strongly recommend that you do not turn off this setting.
Trusting the server certificate
To indicate that Tonic Structural should trust the server certificate, toggle Trust Server Certificate to the on position.
Connecting through an SSH bastion
For additional security, to connect through an SSH bastion :
Toggle Enable SSH Tunnel to the on position.
In the SSH Host field, provide the host for the SSH bastion.
In the SSH Port field, provide the port for the SSH bastion.
In the SSH User field, provide the name of the user to use to connect to the SSH bastion.
If you do not use a private key, then in the SSH Passphrase field, provide the passphrase to use for authentication.
If you do use a private key, then in the SSH Private Key field, provide the private key. If the private key uses a passphrase, then in the SSH Passphrase field, provide the passphrase for the private key.
Blocking data generation on all schema changes
By default, data generation is not blocked as long as schema changes do not conflict with your workspace configuration.
To block data generation when there are any schema changes, regardless of whether they conflict with your workspace configuration, toggle Block data generation on schema changes to the on position.
Connecting to the destination database
Note that you must create the destination database with the full schema before you run data generation.
Copying the connection and authentication details from the source database
If the destination database is in the same location as the source database, then you can copy the connection and authentication details from the source database.
To copy the connection and authentication details from the source database:
Click Copy Settings from Source.
In the Password field, provide the password.
To test the connection to the destination database, click Test Destination Connection.
Providing the connection details
To provide the connection details for the destination database:
In the Server field, provide the server where the database is located.
In the Database field, provide the name of the database.
In the Port field, provide the port to use to connect to the database.
In the Username field, provide the username for the account to use to connect to the database.
In the Password field, provide the password for the specified username.
To test the connection to the destination database, click Test Destination Connection.
Ensuring encryption of destination database authentication
The Enable SSL/TLS setting indicates whether to encrypt destination database authentication.
By default, the toggle is in the on position. We strongly recommend that you do not turn off this setting.
Trusting the server certificate
To indicate that Structural should trust the server certificate, toggle Trust Server Certificate to the on position.
Connecting through an SSH bastion
For additional security, to connect through an SSH bastion :
Toggle Enable SSH Tunnel to the on position.
In the SSH Host field, provide the host for the SSH bastion.
In the SSH Port field, provide the port for the SSH bastion.
In the SSH User field, provide the name of the user to use to connect to the SSH bastion.
If you do not use a private key, then in the SSH Passphrase field, provide the passphrase to use for authentication.
If you do use a private key, then in the SSH Private Key field, provide the private key. If the private key uses a passphrase, then in the SSH Passphrase field, provide the passphrase for the private key.
Last updated