Verify that the PowerExchange installations on the source system, PowerExchange Logger for Linux, UNIX, and Windows system, and PowerExchange Navigator system use a PowerExchange version that VSAM CDC Connector supports. Also verify that the logging of change records to a remote PowerExchange Logger for Linux, UNIX, and Windows is properly configured. Test your configuration by verifying that PowerExchange is able to capture change records from VSAM sources and log the records to remote PowerExchange Logger for Linux, UNIX, and Windows log files.

In PowerExchange Navigator, check that an active PowerExchange capture registration and extraction map exists for each source. The extraction map name must begin with "d" for default, which indicates the default extraction map that PowerExchange generates.

If your site uses TLS or SSL security, verify that valid certificates are available for the source and target servers and that the PWX_CONFIG environment variable points to the dbmover configuration file that includes the SSL configuration for the PowerExchange Listener. For more information about configuring TLS or SSL security, see the

PowerExchange Reference Manual

.

If you localize PowerExchange messages in Japanese, before you start the Secure Agent, create a copy of the PowerExchange dbmover_ja.cfg file. Then set the PWX_CONFIG environment variable to point to the copy. For more information about the dbmover_ja.cfg configuration file, see the

PowerExchange Reference Manual

.

Create the target tables and materialize them with data, if materialized target tables do not already exist. When users are ready to run mapping tasks the first time, they should start the tasks close to the time when the initial materialization of the target tables occurred to avoid missing changes.

From the

Add-On Connectors

page of Administrator, add the VSAM CDC Connector if it has not already been added.

Download the Secure Agent. The Secure Agent can then download the VSAM CDC Connector components and PowerExchangeClient packages based on your licensing. The download also creates a Secure Agent group that contains a Secure Agent as the runtime environment. You can add another Secure Agent to the group. You must have at least one runtime environment in each organization so that users in the organization can run tasks.

In Administrator, configure user roles if the predefined roles are not sufficient. Then assign one or more roles to each user or user group. The roles must provide the privileges that the users require to perform all of their tasks. Usually, the organization administrator configures user roles.

If you do not want users to run scheduled mapping tasks during a certain period, define a blackout period for all schedules on the

Schedules

page in Administrator.