Connect CDC now uses the Service Name instead of the unique Oracle system identifier (SID) to connect to Oracle. When you configure an Oracle Server in Director you must specify the Service Name in the Server name field.
|
Capture tab |
|
|---|---|
|
Parameter |
Description |
|
Capture Info |
|
|
Server |
The name of the z/OS server that hosts capture agent. Often, the value you enter here is the same as the location name of the system where DB2 subsystem is installed. |
|
Port |
The port assigned on the z/OS server to accept CDC Capture requests. |
|
Agent |
The name of the CDC Capture Agent installed on z/OS. After entering the server and port information, choose “Refresh” to automatically fill in the names of any active Capture Agents names on the z/OS server. |
|
Private key path |
Name and path of the private key file used to authenticate Capture connections with the Capture daemon running on z/OS. |
|
JCL Info |
|
|
Job card |
The JCL Job statement, which schedules CDC extract jobs on z/OS. |
|
Job Lib |
The JCL DD statement identifying the LOADLIB path where DMXDC is installed on the z/OS system required to run the JCL job. z/OS only searches public libraries if none are set in Job Lib. |
|
ISPF Lib |
Path to DMXCDC ISPF libraries. |
The value you specify in the Server name field is used for connections to Oracle by the kernel components and client utilities such as MonCon and the Director.
To make these connections, Connect CDC uses the Oracle thin JDBC driver with the Service Name as follows:
url=jdbc:oracle:thin:@//HOST:PORT/SERVICE_NAMEUsing the Service Name provides the following benefits:
-
You can specify multiple Service Names
-
The same Service Name can be specified for multiple Oracle instances
-
Allows for client application transparency
-
Oracle recommended connection method