Adding a subscription

Before you can start replicating data, you need to add a subscription. When adding a new subscription, you can organize your subscription into a project and select the datastores you want to use as the source and target of data during replication activities. How you decide to set up the datastores in your subscriptions depends on your replication requirements.

About this task

When creating your subscriptions, be aware that all subscriptions that come from the same source datastore must have a unique name and all subscriptions that go to the same target datastore must have a unique Source ID. The source ID is automatically generated based on truncating the subscription name to 8 characters. If you attempt to create a subscription with a duplicate Source ID, an error will result and the subscription will not be created. If this occurs, you must open the Advanced Settings dialog and give the subscription a unique Source ID.

Procedure

  1. Click Configuration > Subscriptions.
  2. Right-click on a project and select Subscription > New Subscription.
  3. Enter the name of the new subscription in the Name box.

    All subscriptions that come from the same source datastore must have a unique name and all subscriptions that go to the same target datastore must have a unique Source ID. The source ID is automatically generated based on truncating the subscription name to 8 characters. If you attempt to create a subscription with a duplicate Source ID, an error will result and the subscription will not be created. If this occurs, click Advanced Settings and give the subscription a unique Source ID.

  4. Enter the description of the new subscription in the Description box.
  5. If you want to include the new subscription in a project, select a project from the Project list or click New Project to create a new project.

    If you do not select a project, Management Console places the new subscription into the Default Project.

  6. Select the source datastore from the Source list.
  7. Select the target datastore from the Target list.
    Note: To create a subscription that publishes to a queue from InfoSphere® Classic CDC for z/OS®, select the same datastore as both the source and target for the subscription.
  8. If you selected <External> from the Target datastore list, click Details to supply the required connection information.
  9. If you want to specify advanced settings for the subscription, click Advanced Settings. Modify the following properties and click OK, then click OK again.

    On the General tab, the following properties can be set:

    Source ID
    Specify the source ID for the new subscription.
    TCP Host
    Specify the TCP host that your source datastore will use to recognize the target datastore when the computer where CDC Replication is installed has multiple network cards. This is useful if you want to specify a host that is different from the host that you specified in the Access Manager perspective. The default option is Auto-select, which will automatically select the network card that can communicate with the target datastore. The host that you specified in the Access Manager perspective also appears by default as well as any alias that you configured in the Datastore Properties dialog box.
    Firewall Port
    Specify a port number for the new subscription.
    Mark subscription as persistent
    Enable if you want to specify that the subscription is persistent. This feature is only enabled for subscriptions whose datastores support the functionality. A persistent subscription restarts automatically after a recoverable error occurs. By default, a persistent subscription restarts only after a recoverable error when the instance is restarted. To allow a persistent subscription to restart after a subscription stops without the instance stopping and restarting, set the system property mirror_auto_restart_interval_seconds to a non-zero value. See the documentation for this parameter under the "System parameters" > "General product system parameters" section for your CDC Replication engine.
    Select the datastore to handle the transferable work
    Specify where transferable work will be performed, in order to minimize impact on the source or target datastore.
    Minimize network load
    Specify whether to minimize the network load where possible, even if it may result in increased replication latency. This option is only available when both the source and target datastores support the functionality.

    On the Propagation Control tab, the following properties can be set:

    Propagation Control
    Click Add and select the source ID for any subscription for which you want to prevent data from being replicated to the target.

    On the Communication Protocol tab, you can specify the communications protocol that will be used by the source datastore to communicate with the target datastore

    Do not replicate data received from any subscriptions
    Enable if you want to prevent replication from all subscriptions.
    TCP/IP
    Specifies that TCP/IP will be used exclusively as the communication protocol.
    JMS
    Specifies that either TCP/IP or JMS message queues will be used as the communication protocol.
  10. Click OK.

What to do next

After you click OK, you will be asked if you want to map the source tables for the subscription. Click Yes to map tables or No to close the dialog and continue. If you do not want to be asked this question again in the future, enable the checkbox on the dialog.