Model remote journals in the Connect CDC Director - Connect_CDC - connect_cdc_mimix_share - Latest

Connect CDC Advanced User Guide

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (MIMIX Share)
Version
Latest
Language
English
Product name
Connect CDC
Title
Connect CDC Advanced User Guide
Copyright
2024
First publish date
2003
Last edition
2024-07-19
Last publish date
2024-07-19T23:30:25.334335

Use the following procedure to model remote journals in the Connect CDC Director. Refer to the Connect CDC Getting Started Guide for the Connect CDC Director navigation details and field definitions.

  1. Use the Server Properties dialog to create an i5 server. This is the i5 server that contains the remote journal.

    Note: Multiple System i5 Change Selectors can be used to process the same journal.
  2. Use the Refresh Available Tables dialog to refresh available tables from the remote journal i5 server that you wish to replicate.

  3. Select Table1 for distribution.

    After distribution, the following displays. The “[UNKNOWN]” labeling indicates that the table is not journalled, as expected.

  4. Use the Process Definition Properties dialog to create the CS process.

    1. Right-click on the iSeries server to display a pop-up menu.

    2. Choose New Process>DB2 Change Selector to create the CS.

    The Process Definition Properties (Basic tab) dialog displays.

    In the example below, the Change Selector Process “rmtjrnl” is created manually.

  5. Use the Process Definition Properties (Advanced tab) dialog to add the remote journal (MIKEG/QSQJRN).

  6. From the Journal drop-down list select the remote journal to be used by the CS. This links the CS process to the remote journal. Note that you must manually validate that this is the correct remote journal, since Connect CDC will not be able to perform the validation. Refer to Changes to the Connect CDC Director.

  7. Click OK.

  8. Commit the Model.

  9. Open the Model in MonCon. See Connect CDC MonCon.

  10. Start the request.