Navigator User Guide

10.5.5
- 10.5.6
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

Adding a Registration Group

A registration group is a named group of capture registrations that have the same source type and instance.

You must add a registration group before you can add capture registrations. You can add capture registrations immediately after defining the registration group or later.

On the

Resources

tab in the

Resource Explorer

, right-click

Registration Groups

and click

Add Registration Group

In the

Add Registration Group

dialog box, enter the following information:

Name: Enter a user-defined name for the registration group. This value can be an alphanumeric string of up to 16 characters in length. You cannot enter spaces or special characters.
Location: Select the location of the source from which you want to capture changes. This field applies to all source types except IDMS_L.

The location is a node name that is defined in a NODE statement in the dbmover.cfg configuration file on the PowerExchange Navigator system, or the value "local" for the local Windows system where the Navigator runs.

Default is
local
. Select
local
if the source is on the PowerExchange Navigator system.

For a remote Microsoft SQL Server source, specify the actual server name. Do not use a local alias to identify the server. PowerExchange does not support the use of local aliases when connecting to a remote server and creating SQL Server publications at registration creation.
Type: Select the data source type. Options are:

ADABAS
for Adabas files

AS4
for DB2 for i (i5/OS) tables

DATACOM
for CA Datacom/DB tables

DB2
for DB2 for z/OS tables

DB2UDB
for DB2 for Linux, UNIX, and Windows tables

IDMS_L
for IDMS tables to be registered for IDMS log-based CDC

IMS
for IMS databases

MSSql
for Microsoft SQL Server tables

For the PowerExchange Navigator to create capture registrations for Microsoft SQL Server sources, the license.key file on the PowerExchange Navigator system must contain a key that authorizes use of SQL Server CDC. Otherwise, when you try to add a capture registration for a SQL Server source, the PowerExchange Navigator fails with a license key error. This failure occurs even if the PowerExchange Listener is running with a license key that includes SQL Server CDC.

MySQL
for MySQL tables

ORACLE
for Oracle tables
PostgreSQL
for PostgreSQL tables

SAP HANA
for SAP HANA tables

VSAM
for VSAM ESDS, KSDS, RRDS, and VRRDS data sets
UserID: Enter a user ID that allows access to the source node that is specified in the
Location
field. This field applies to all source types except IDMS_L.

The type of user ID depends on the source type and PowerExchange security settings:

If the source is on an IBM i or z/OS system and PowerExchange security is enabled, enter an operating system user ID. PowerExchange security is enabled when the PowerExchange SECURITY statement in the DBMOVER member is set to (1,x) or 2.x).

For a DB2 for LUW, Microsoft SQL Server, MySQL, Oracle, PostgreSQL, or SAP HANA source, enter a valid database user ID, if required. For more information, see the SECURITY Statement in the
PowerExchange Reference Manual
.

If you use Microsoft NTLM and Active Directory authentication to control access to a Microsoft SQL Server source, enter the user ID in the format
domain\user_name
. Then in the
Password
field, enter a valid password for this user ID.

For a source on a supported Linux, UNIX, or Windows system, if you have enabled PowerExchange LDAP user authentication and, if applicable, disabled relational pass-through authentication, the user ID is the enterprise user name. For more information, see the
PowerExchange Reference Manual
.
Password: Enter a password for the specified user ID that allows access to the source node. This field applies to all source types except IDMS_L.

If the source is on an IBM i or z/OS system, you can enter a valid PowerExchange passphrase instead of a password. An IBM i passphrase can be from 9 to 31 characters in length. A z/OS passphrase can be from 9 to 128 characters in length. A passphrase can contain the following characters:

Uppercase and lowercase letters

The numbers 0 to 9

Spaces

The following special characters:

’ - ; # \ , . / ! % & * ( ) _ + { } : @ | < > ?

The first character is an apostrophe.

Passphrases cannot include single quotation marks (‘), double quotation marks (“), or currency symbols.

On z/OS, the allowable characters in the IBM IRRPHREX exit do not affect the allowable characters in PowerExchange passphrases.

On z/OS, a valid RACF passphrase can be up to 100 characters in length. PowerExchange truncates passphrases longer than 100 characters when passing them to RACF for validation.

To use passphrases, ensure that the PowerExchange Listener runs with a security setting of SECURITY=(1,N) or higher in the DBMOVER member. For more information, see "SECURITY Statement" in the
PowerExchange Reference Manual
.

If you specify a user ID but omit the password or passphrase, when you open the registration group, the PowerExchange Navigator prompts you for a password in the
Missing Password
dialog box.
Source-specific fields: Depending on the source type that you entered in the
Type
field, some source-specific fields are displayed. The following table describes these fields by source type:

Source Type
Source-Specific Fields

ADABAS

In the
Collection Identifier
field, enter the instance name.

AS4 (DB2 for i)

In the
Collection Identifier
field, enter the instance name specified in the INST parameter of the AS4J CAPI_CONNECTION statement in the DBMOVER member of the dtllib/CFG file on the source system.

DATACOM

In the
MUF Name
field, enter the name of Multi-User Facility (MUF).

DB2 (DB2 for z/OS)

In the
Database Instance
box, enter the DB2 subsystem ID or the DB2 data-sharing group name.

DB2UDB (DB2 for Linux, UNIX, and Windows)

In the
Database
field, enter the name of the DB2 database.

IDMS_L

In the
Registration Location
list, select the location where the capture registrations will be stored. The location is a node name that is defined in a NODE statement in the dbmover.cfg configuration file on the PowerExchange Navigator system.

In the
UserID
and
Password
fields under the registration location, enter a user name and password that allow access to that location. If the registrations are on the z/OS system and PowerExchange security is enabled, enter an operating system user ID. PowerExchange security is enabled when the PowerExchange SECURITY statement in the DBMOVER member is set to (1,x) or 2.x).

In the
Source Map Location
list, select the location where the data maps for IDMS source tables are located.

In the
UserID
and
Password
fields under the source map location, enter a user name and password that allow access to that location. If the maps are on the z/OS system and PowerExchange security is enabled, enter an operating system user ID.

In the
Logsid
field, enter the value specified in the LOGSID statement in the DBMOVER configuration file on the source system.

IMS

In the
Recon Identifier
field, enter one of the following values:

For IMS synchronous CDC, enter the IMS subsystem ID.

For IMS log-based CDC, enter the value that is specified in the IMSID statement in the DBMOVER configuration member on the z/OS system where the RECON data sets are located.

MSSql

In the
Database Server
list, select the server where the SQL Server source is located. You can optionally append the SQL Server instance name and also a port number if you use a port other than the default port number of 1433. Use the following format:

server
[\instance_name
][,port_number
]

For example:
MSQL001\MSQLINST5,6983

If you include the instance name, the PowerExchange Navigator can use the SQL Server Browser, provided that it is active, to find a port for connecting to SQL Server if you did not specify the port or if you specified the port but the first connection attempt on that port failed.

If you do not use the default port and do not specify an instance or port number in this field, attempts to create capture registrations for source tables for this group will fail.

In the
Database Name
list, select or enter the name of a SQL Server publication database.

In the
Instance
field, optionally enter a unique user-defined identifier for the specified database server and database name combination. Maximum length is seven characters. This identifier is used to identify a set of registrations for the publication database. This identifier is also incorporated into the names of the extraction maps that are generated for capture registrations in the registration group. If you use the PowerExchange Logger for Linux, UNIX, and Windows, ensure that the instance identifier matches the DBID parameter value in the Logger configuration file. If you do not enter an
Instance
value, PowerExchange generates a unique instance identifier that is composed of all or part of the publication database name followed by a 3-digit number if a number is required to make the identifier unique.

This user-defined instance identifier is useful in migration scenarios. If you need to migrate change capture from one environment to another, such as from test to production, and you do not
define an instance identifier, PowerExchange uses a generated instance identifier in the new environment. The generated instance identifier might be different from the one in the original environment. To avoid having to update the extraction map names in PowerCenter workflows and edit the DBID parameter value for the PowerExchange Logger, enter an instance identifier that matches the instance identifier in the original environment when creating registrations for the new environment.

In this migration scenario, ensure that the paths in CAPT_PATH and CAPT_XTRA statements in the dbmover.cfg configuration file are unique in the original environment and new environment.

MySQL

In the
Database Server
field, enter the server name or IP address of the MySQL server where the source database is located. If the MySQL server is on the local host where the Navigator runs, you can enter
localhost
. Optionally, you can append the port number if you use a port other than the default port of 3306. Use the following format:

server[,port_number]

For example:
"localhost,3400"

In the
Instance
field, optionally enter a unique user-defined identifier for the MySQL server that you specified in the
Database Server
field. Maximum length is seven characters. This identifier is used to identify a set of registrations for tables in the database on the MySQL server. This identifier is also incorporated into the names of the extraction maps that are generated for capture registrations in the registration group. If you use the PowerExchange Logger for Linux, UNIX, and Windows, ensure that this instance identifier matches the DBID parameter value in the Logger configuration file. If you do not enter an
Instance
value, PowerExchange generates a unique instance identifier that consists of first four characters of the database server name followed by a three-digit number if a number is required to make the identifier unique.

ORACLE

In the
Collection Identifier
field, enter the Oracle instance identifier specified in the ORACLEID statement in the DBMOVER configuration file on the source system.

PostgreSQL

In the
Database Server
list, select the server where the PostgreSQL source is located. You can optionally append a port number if you use a port other than the default port number of 5432. Use the following format:

server[,port_number]

For example:
PGSL001,6983

If the server does not use the default port and you do not specify a port number in this field, attempts to create capture registrations for this registration group will fail.

In the
Database Name
list, select the name of the PostgreSQL source database on the specified server.

In the
Instance
field, optionally enter a unique user-defined identifier for the specified database server and database name combination. Maximum length is seven characters. This identifier is used to identify a set of registrations for the database. This identifier is also incorporated into the names of the extraction maps that are generated for capture registrations in the registration group. If you use the PowerExchange Logger for Linux, UNIX, and Windows, ensure that the instance identifier matches the DBID parameter value in the Logger configuration file. If you do not enter this value, PowerExchange generates a unique instance identifier that is composed of the first four characters of the database server name followed by a 3-digit number if a number is required to make the identifier unique.

SAP HANA

In the
Database Server
list, select the server where the SAP HANA source is located. You can optionally append a port number if you use a port other than the default port number 39015. Use the following format:

server[:port_number]

For example:
saphana:30015

If the server does not use the default port and you do not specify a port number in this field, attempts to create capture registrations for this registration group will fail.

In the
Database Name
list, select the name of the SAP HANA source database on the specified server.

In the
Instance
field, optionally enter a unique user-defined identifier for the specified database server and database name combination. Maximum length is seven characters. This identifier is used to identify a set of registrations for the database. This identifier is also incorporated into the names of the extraction maps that are generated for capture registrations in the registration group. If you use the PowerExchange Logger for Linux, UNIX, and Windows, ensure that the instance identifier matches the DBID parameter value in the Logger configuration file. If you do not enter this value, PowerExchange generates a unique instance identifier that is composed of the first four characters of the database server name followed by a 3-digit number if a number is required to make the identifier unique.

Click
DDL
to create and save the pklog.sql file, which contains DDL for creating the PKLOG and PROCESSED tables for the source tables registered under the registration group. The PKLOG table contains metadata about captured DML changes, and the PROCESSED table contains the maximum sequence number (SCN) for the most recent change data capture cycle. You can generate this file after the registration group is created by right-clicking the registration group and selecting DDL.

VSAM

In the
Collection Identifier
field, enter the instance name.
Add Registration: Select this option to add capture registrations to the group. Clear this option to add only the registration group.

By default, this option is selected.

Source Type	Source-Specific Fields
ADABAS	In the Collection Identifier field, enter the instance name.
AS4 (DB2 for i)	In the Collection Identifier field, enter the instance name specified in the INST parameter of the AS4J CAPI_CONNECTION statement in the DBMOVER member of the `dtllib`/CFG file on the source system.
DATACOM	In the MUF Name field, enter the name of Multi-User Facility (MUF).
DB2 (DB2 for z/OS)	In the Database Instance box, enter the DB2 subsystem ID or the DB2 data-sharing group name.
DB2UDB (DB2 for Linux, UNIX, and Windows)	In the Database field, enter the name of the DB2 database.
IDMS_L	In the Registration Location list, select the location where the capture registrations will be stored. The location is a node name that is defined in a NODE statement in the dbmover.cfg configuration file on the PowerExchange Navigator system. In the UserID and Password fields under the registration location, enter a user name and password that allow access to that location. If the registrations are on the z/OS system and PowerExchange security is enabled, enter an operating system user ID. PowerExchange security is enabled when the PowerExchange SECURITY statement in the DBMOVER member is set to (1,`x`) or 2.`x`). In the Source Map Location list, select the location where the data maps for IDMS source tables are located. In the UserID and Password fields under the source map location, enter a user name and password that allow access to that location. If the maps are on the z/OS system and PowerExchange security is enabled, enter an operating system user ID. In the Logsid field, enter the value specified in the LOGSID statement in the DBMOVER configuration file on the source system.
IMS	In the Recon Identifier field, enter one of the following values: For IMS synchronous CDC, enter the IMS subsystem ID. For IMS log-based CDC, enter the value that is specified in the IMSID statement in the DBMOVER configuration member on the z/OS system where the RECON data sets are located.
MSSql	In the Database Server list, select the server where the SQL Server source is located. You can optionally append the SQL Server instance name and also a port number if you use a port other than the default port number of 1433. Use the following format: server [\instance_name ][,port_number ] For example: MSQL001\MSQLINST5,6983 If you include the instance name, the PowerExchange Navigator can use the SQL Server Browser, provided that it is active, to find a port for connecting to SQL Server if you did not specify the port or if you specified the port but the first connection attempt on that port failed. If you do not use the default port and do not specify an instance or port number in this field, attempts to create capture registrations for source tables for this group will fail. In the Database Name list, select or enter the name of a SQL Server publication database. In the Instance field, optionally enter a unique user-defined identifier for the specified database server and database name combination. Maximum length is seven characters. This identifier is used to identify a set of registrations for the publication database. This identifier is also incorporated into the names of the extraction maps that are generated for capture registrations in the registration group. If you use the PowerExchange Logger for Linux, UNIX, and Windows, ensure that the instance identifier matches the DBID parameter value in the Logger configuration file. If you do not enter an Instance value, PowerExchange generates a unique instance identifier that is composed of all or part of the publication database name followed by a 3-digit number if a number is required to make the identifier unique. This user-defined instance identifier is useful in migration scenarios. If you need to migrate change capture from one environment to another, such as from test to production, and you do not define an instance identifier, PowerExchange uses a generated instance identifier in the new environment. The generated instance identifier might be different from the one in the original environment. To avoid having to update the extraction map names in PowerCenter workflows and edit the DBID parameter value for the PowerExchange Logger, enter an instance identifier that matches the instance identifier in the original environment when creating registrations for the new environment. In this migration scenario, ensure that the paths in CAPT_PATH and CAPT_XTRA statements in the dbmover.cfg configuration file are unique in the original environment and new environment.
MySQL	In the Database Server field, enter the server name or IP address of the MySQL server where the source database is located. If the MySQL server is on the local host where the Navigator runs, you can enter localhost . Optionally, you can append the port number if you use a port other than the default port of 3306. Use the following format: `server`[,`port_number`] For example: "localhost,3400" In the Instance field, optionally enter a unique user-defined identifier for the MySQL server that you specified in the Database Server field. Maximum length is seven characters. This identifier is used to identify a set of registrations for tables in the database on the MySQL server. This identifier is also incorporated into the names of the extraction maps that are generated for capture registrations in the registration group. If you use the PowerExchange Logger for Linux, UNIX, and Windows, ensure that this instance identifier matches the DBID parameter value in the Logger configuration file. If you do not enter an Instance value, PowerExchange generates a unique instance identifier that consists of first four characters of the database server name followed by a three-digit number if a number is required to make the identifier unique.
ORACLE	In the Collection Identifier field, enter the Oracle instance identifier specified in the ORACLEID statement in the DBMOVER configuration file on the source system.
PostgreSQL	In the Database Server list, select the server where the PostgreSQL source is located. You can optionally append a port number if you use a port other than the default port number of 5432. Use the following format: `server`[,`port_number`] For example: PGSL001,6983 If the server does not use the default port and you do not specify a port number in this field, attempts to create capture registrations for this registration group will fail. In the Database Name list, select the name of the PostgreSQL source database on the specified server. In the Instance field, optionally enter a unique user-defined identifier for the specified database server and database name combination. Maximum length is seven characters. This identifier is used to identify a set of registrations for the database. This identifier is also incorporated into the names of the extraction maps that are generated for capture registrations in the registration group. If you use the PowerExchange Logger for Linux, UNIX, and Windows, ensure that the instance identifier matches the DBID parameter value in the Logger configuration file. If you do not enter this value, PowerExchange generates a unique instance identifier that is composed of the first four characters of the database server name followed by a 3-digit number if a number is required to make the identifier unique.
SAP HANA	In the Database Server list, select the server where the SAP HANA source is located. You can optionally append a port number if you use a port other than the default port number 39015. Use the following format: `server`[:`port_number`] For example: saphana:30015 If the server does not use the default port and you do not specify a port number in this field, attempts to create capture registrations for this registration group will fail. In the Database Name list, select the name of the SAP HANA source database on the specified server. In the Instance field, optionally enter a unique user-defined identifier for the specified database server and database name combination. Maximum length is seven characters. This identifier is used to identify a set of registrations for the database. This identifier is also incorporated into the names of the extraction maps that are generated for capture registrations in the registration group. If you use the PowerExchange Logger for Linux, UNIX, and Windows, ensure that the instance identifier matches the DBID parameter value in the Logger configuration file. If you do not enter this value, PowerExchange generates a unique instance identifier that is composed of the first four characters of the database server name followed by a 3-digit number if a number is required to make the identifier unique. Click DDL to create and save the pklog.sql file, which contains DDL for creating the PKLOG and PROCESSED tables for the source tables registered under the registration group. The PKLOG table contains metadata about captured DML changes, and the PROCESSED table contains the maximum sequence number (SCN) for the most recent change data capture cycle. You can generate this file after the registration group is created by right-clicking the registration group and selecting DDL.
VSAM	In the Collection Identifier field, enter the instance name.

Add capture registrations to the group or complete the registration group definition, as follows:

If you selected the

Add Registration

option, click

and proceed to Adding a Capture Registration.

If you cleared the

Add Registration

option, click

Finish

. The

Registration Group

tab in the

Resource Inspector

displays the properties for the registration group. Additionally, if the PowerExchange Listener on the source system is running, the

Registration Group

tab in the

Resource Explorer

displays any existing capture registrations for the source instance associated with the registration group.

Registration Groups and Capture Registrations

Registration Groups

Adding a Capture Registration

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal

0 COMMENTS

We’d like to hear from you! Log in to comment.

Rename Saved Search

Table of Contents

Navigator User Guide

Navigator User Guide

Adding a Registration Group

Adding a Registration Group