Updating a source definition for Data Gate

Connect to a data source to give Data Gate access to the original data in Db2 for z/OS. You define a data source when you create (provision) an instance for the first time. This data source can be changed later .

Before you begin

Important: If the source database changes, the newly configured Db2 for z/OS subsystem must have activated a valid Db2 Connect license (see Activating the Db2 Connect Unlimited license on a Db2 for z/OS subsystem).

Procedure

  1. Make sure that the Cloud Pak for Data perspective is selected. If necessary, click Perspective icon to change the perspective.
  2. Under My instances, click the name of the instance that you want to edit.

The details page of the instance is displayed. For example:

Instance details

  1. Click Open instance.
  2. You can now change the values under the headings Source database, Log reader, TLS certificate, and Data gate pairing name.
    For a description of the fields and controls, see the steps 24 through 30 in Creating a service instance for Data Gate from the web client.

    All fields marked with an asterisk (*) are required fields. These fields must contain valid values for the Continue button to be enabled.

  3. Click Continue.
    The Select tables tab is in front.
  4. Select schemas and tables for your changed data source.
    See the steps 34 and 35 in Creating a service instance for Data Gate from the web client for a description of the fields and controls.
  5. Click Continue.
    The Finish tab is in front, and you see a summary of your settings. For a description of the items on the Finish page, see the steps 36 and 37 in Creating a service instance for Data Gate from the web client.
  6. Click the Finish button at the bottom of the page when ready.
    Important: The configuration process might take several minutes to complete. Do not close the Configure page during that time.

Understanding Side Effects When Updating Source Database Connection Information

Updating the source database connection information in Data Gate can have different impacts on your existing configuration. This section explains the effects of modifying various connection parameters.

Important: Some connection changes will cause you to lose all previously loaded tables and require you to start from scratch.

Impact Summary

Parameter Type What You Change What Happens Impact on Your Data What You Need to Do
Source Database Connection AND Log Reader Connection In Source database: Host, Secure DDF port, Location. In Log reader: Host, Secure DDF port. Pairing is dropped and recreated. ALL loaded tables are LOST. Replication state is RESET. Table configurations are REMOVED. Re-add all tables, reload all data, reconfigure replication.
Authentication Credentials Username, Password, TLS certificate, Keystore/Truststore passwords. Pairing is retained. Loaded tables are PRESERVED. Replication continues. No data loss. No action required (connection updates automatically).
Note: Log reader connection parameters only apply if you selected Use different connection information for the log reader during configuration. Therefore, Host and Secure DDF port appear in two sections: Source database section and Log reader section.
CAUTION:
Changing ANY of these fields (in either section) will cause table loss.

Detailed Scenarios

Scenario 1: Changing Source Database Connection

  • Trigger: Changing Host, Secure DDF port, or Location in the Source database section.
  • Effect: All table selections are removed, and pairing is dropped and recreated.
  • Example: Updating host from db2host1.example.com to db2host2.example.com results in losing all loaded tables and requiring re-adding and reloading tables.

Scenario 2: Changing Log Reader Connection

  • Trigger: Changing Host or Secure DDF port in the Log reader section (only if using different connection information for the log reader).
  • Effect: All table selections are removed, and pairing is dropped and recreated.
  • Example: Updating Log reader host from db2host1.example.com to db2host2.example.com results in losing all loaded tables and requiring re-adding and reloading tables.

Scenario 3: Changing Credentials Only

  • Trigger: Changing Username or Password in either Source database or Log reader section.
  • Effect: Pairing is retained, and all table selections are preserved.
  • Example: Updating a user's password results in retaining all loaded tables and continuing replication normally. No action required.

Scenario 4: Updating TLS Certificate

  • Trigger: Uploading a new TLS certificate or changing Keystore/Truststore passwords.
  • Effect: Pairing is retained, and all table selections are preserved.
  • Example: Updating a certificate from certificate1.p12 to certificate2.p12 results in retaining all loaded tables and continuing replication normally. No action required.