Installing Management Console and Access Server (Version 10.2.

1) 2
System requirements for Access Server and Management Console 3
Hardware and software requirements 4
Network requirements 5
About Access Server 6
Installing Access Server 7
To install Access Server (Windows) 8
To perform a silent installation of Access Server (Windows) 9
To upgrade Access Server (Windows) 11
To uninstall Access Server (Windows) 12
To clean up a failed uninstallation of Access Server (Windows) 13
To install Access Server (UNIX and Linux) 14
To perform a silent installation of Access Server (UNIX and Linux) 15
To upgrade Access Server (UNIX and Linux) 17
To uninstall Access Server (UNIX and Linux) 18
To clean up a failed uninstallation of Access Server (UNIX and Linux) 19
To override the locale for the Access Server installation (UNIX and Linux) 20
After you install Access Server 21
Starting Access Server 22
To start Access Server (UNIX and Linux) 23
Creating an Access Server user account 24
To create an Access Server user account (UNIX and Linux) 25
Configuring firewall settings for outbound (static) ports 27
To configure static ports 31
About Management Console 32
Installing Management Console 33
To install Management Console 34
To perform a silent installation of Management Console 35
To uninstall Management Console 36
To clean up a failed uninstallation of Management Console 37
Commands 38
dmaccessserver-Starting Access Server 39
dmcreateuser-Adding a user account 40
dmshutdownserver-Shut down Access Server 43
Troubleshooting 44
Using the IBM Support Assistant (ISA DC) 45
To use ISA DC to collect data for a product problem (command line) 46
To use ISA DC to collect data for a product problem (GUI) 49
To use ISA DC to collect data for a question or an enhancement request (command line) 51
To use ISA DC to collect data for a question or an enhancement request (GUI) 53
Troubleshooting connection problems 54
Locating log files 55
Troubleshooting and contacting IBM Support 56
 IBM InfoSphere Change Data Capture, Version 10.2.1
System requirements for Access Server and
Management Console
Before you install Access Server and Management Console, ensure that the system
you choose meets the necessary operating system, hardware, software, disk and
memory requirements.
In this section, you will learn:

- Hardware and software requirements

- Network requirements

2
 IBM InfoSphere Change Data Capture, Version 10.2.1
System requirements for Access Server and
Management Console
Before you install Access Server and Management Console, ensure that the system
you choose meets the necessary operating system, hardware, software, disk and
memory requirements.
In this section, you will learn:

- Hardware and software requirements

- Network requirements

3
 IBM InfoSphere Change Data Capture, Version 10.2.1
Hardware and software requirements
Click the following links to view hardware and software requirements for
InfoSphere® CDC, Management Console, and Access Server:
Linux, UNIX, Windows and System i® replication engines: https://ibm.biz/BdxwE7
Mainframe replication engine: https://ibm.biz/BdxwXB

4
 IBM InfoSphere Change Data Capture, Version 10.2.1
Network requirements
Management Console requires a valid TCP/IP network so that it can communicate
with your installation of InfoSphere® CDC.

5
 IBM InfoSphere Change Data Capture, Version 10.2.1
About Access Server
Access Server is the server application that directs communications between
Management Console and replication engine processes.
If you want to use the CHCCLP simplified command line tool on a server other than
the one on which Management Console or Access Server are currently installed and
running, you can install copies of Access Server on any server from which you want
to issue commands; the additional installations of Access Server do not need to be
running for you to use the CHCCLP tool.
In this section, you will learn:

- Installing Access Server

6
 IBM InfoSphere Change Data Capture, Version 10.2.1
Installing Access Server
This section outlines how to install and uninstall Access Server.
See also:

- To install Access Server (Windows)

- To perform a silent installation of Access Server (Windows)
- To upgrade Access Server (Windows)
- To uninstall Access Server (Windows)
- To clean up a failed uninstallation of Access Server (Windows)
- To install Access Server (UNIX and Linux)
- To perform a silent installation of Access Server (UNIX and Linux)
- To upgrade Access Server (UNIX and Linux)
- To uninstall Access Server (UNIX and Linux)
- To clean up a failed uninstallation of Access Server (UNIX and Linux)
- To override the locale for the Access Server installation (UNIX and Linux)

7
 IBM InfoSphere Change Data Capture, Version 10.2.1
To install Access Server (Windows)
1. Double-click on the installation file.The IBM®InfoSphere® CDCAccess Server
installation wizard opens.
2. Click Next.
3. Read the license agreement and select I accept the terms in the license
agreement and then click Next.
4. Select the folder where you want to install Access Server and click Next.
5. Select the location for the product icons and click Next.
6. Specify the port number to communicate with Management Console and click
Next.
7. Enter the username and password for an Access Server account that will be used
to perform the following actions:
- Log in to Access Server from Management Console.
- Manage users and datastores in Management Console.
8. Review the installation summary and click Install.
9. Click Done to exit the installation.

Related tasks:
To uninstall Access Server (Windows)

8
 IBM InfoSphere Change Data Capture, Version 10.2.1
To perform a silent installation of Access Server
(Windows)
1. Copy the installation file for your platform from the CD-ROM or download it from
the IBM® Web site.
2. Generate your response file in one of two ways:
- Edit the following example response file for Access Server so that it is specific to
your environment:# Wed Sep 28 15:49:07 EDT 2011
# Replay feature output

# ---------------------

# This file was built by the Replay feature of InstallAnywhere.

# It contains variables that were set by Panels, Consoles or Custom Code.

#Has the license been accepted

#-----------------------------

LICENSE_ACCEPTED=TRUE

#Choose Install Folder

#---------------------

USER_INSTALL_DIR=C:\\Program Files\\IBM\\InfoSphere Change Data Capture\\Access Server

#Choose Shortcut Folder

#----------------------

USER_SHORTCUTS=C:\\Documents and Settings\\All Users\\Start Menu\\Programs\\IBM InfoSphere Change Data

Capture\\Access Server

#Choose Access Server Port

#-------------------------

as.port=10101

#Choose Access Server User Name

#------------------------------

access.username=Admin

#Choose Access Server Password

#-----------------------------

access.password=myPassword

- Record your own response file by running the following command:

<installation_executable_name> -r <response_file>where:
- <installation_executable_name> is the name of the Access Server installation
file.
- <response_file> is the name of the response file.

For example, cdcaccess-<version>-setup.exe -r ASResponseFile.txt

3. Silently install Access Server by running the following command:
<installation_executable_name> -i SILENT -f <response_file>
9
For example, cdcaccess-<version>-setup.bin -i SILENT -f ASResponseFile.txt

10
 IBM InfoSphere Change Data Capture, Version 10.2.1
To upgrade Access Server (Windows)
1. Make a note of the location of the data folder for the existing Access Server for
use later. This will enable you to use your existing user, datastore, and
subscription settings after you upgrade.This folder is located in the following
locations:
- Windows XP—<installRoot>/data
- Windows 7, Windows 2008, Windows Vista—<drive>:\Users\<userName>
\AppData\Local\DataMirror\Access Server\data
2. Uninstall the existing Access Server.
3. Double-click on the installation file.The IBM®InfoSphere® CDCAccess Server
installation wizard opens.
4. Click Next.
5. Read the license agreement and select I accept the terms in the license
agreement and then click Next.
6. Select the folder where you want to install Access Server and click Next.
7. Select the location for the product icons and click Next.
8. Specify the port number to communicate with Management Console and click
Next.
9. Enter the username and password for an Access Server account that will be
used to perform the following actions:
- Log in to Access Server from Management Console.
- Manage users and datastores in Management Console.
10. Review the installation summary and click Install.
11. Click Done to exit the installation.
12. Copy the contents of the old DATA folder to the new location to enable you to
use the user, datastore and subscription settings it contains. Do NOT overwrite
the ID that you created in step 9.

Related tasks:
To uninstall Access Server (Windows)

11
 IBM InfoSphere Change Data Capture, Version 10.2.1
To uninstall Access Server (Windows)
1. Ensure that Access Server is not running.
2. Use the Windows Control Panel applet to remove Access Server.

Related tasks:
To install Access Server (Windows)
To clean up a failed uninstallation of Access Server (Windows)

12
 IBM InfoSphere Change Data Capture, Version 10.2.1
To clean up a failed uninstallation of Access Server
(Windows)
1. Back up your Access Serverdata directory.This directory is located in the
following locations:
- Windows XP—<installRoot>/data
- Windows 7, Windows 2008, Windows Vista—<drive>:\Users\<userName>
\AppData\Local\DataMirror\Access Server\data
This directory contains user and datastore profile information that you can use
after reinstalling Access Server.
2. Delete the Access Server installation directory. You can optionally delete all the
subdirectories within the installation directory, and retain your Windows user
application data directory.
3. Clean up the Zero G Registry file by removing the entries related to InfoSphere®
Change Data CaptureAccess Server. The registry file name and location are as
follows:
- Windows x86 processor—C:\Program Files\Zero G
Registry\.com.zerog.registry.xml
- Windows x86-64 processor—C:\Program Files(x86)\Zero G
Registry\.com.zerog.registry.xml
By default, these are hidden directories.
Notes:
- Ensure that you do not remove entries related to other products that you have
also installed on this machine.
- Note that the file name is preceded by a dot (that is, .com.zerog.registry.xml).

13
 IBM InfoSphere Change Data Capture, Version 10.2.1
To install Access Server (UNIX and Linux)
1. Log on to your UNIX or Linux machine with the account you are using for the
Access Server installation.
2. Copy the installation file for your platform from the CD-ROM or download it from
the IBM® Web site.
3. Make the installation program executable.
4. Start the installation with the following command:./<installation_binary_name>
where <installation_binary_name> is the name of the installation file.
5. Press Enter on the Introduction screen to display the license agreement. Follow
the instructions on the screen to navigate through the license agreement.
6. Enter 1 to accept the license agreement.
7. Specify the port number to communicate with Management Console and press
Enter.
8. Enter the absolute path to your installation directory or press Enter to accept the
default directory.The directory that you specify must be owned by the account
you are using for the installation. If the installation program cannot create the
directory, you are prompted to specify a different directory.
9. Review the installation summary and press Enter to start the installation.
10. Press Enter to exit the installation after the installation is complete.After you
have installed Access Server, you must complete both of the following tasks in
the order they are listed before you can log in to Management Console for the
first time:
- Start Access Server.
- Create an Access Server user account.

Related tasks:
To start Access Server (UNIX and Linux)
To create an Access Server user account (UNIX and Linux)
To override the locale for the Access Server installation (UNIX and Linux)

14
 IBM InfoSphere Change Data Capture, Version 10.2.1
To perform a silent installation of Access Server
(UNIX and Linux)
1. Log on to your UNIX or Linux machine with the account you are using for the
Access Server installation.
2. Copy the installation file for your platform from the CD-ROM or download it from
the IBM® Web site.
3. Make the installation program executable.
4. Generate your response file in one of two ways:
- Edit the following example response file for Access Server so that it is specific to
your environment:# Fri Oct 07 09:28:22 EDT 2011
# Replay feature output

# ---------------------

# This file was built by the Replay feature of InstallAnywhere.

# It contains variables that were set by Panels, Consoles or Custom Code.

#Has the license been accepted

#-----------------------------

LICENSE_ACCEPTED=TRUE

#Choose Access Server Port

#-------------------------

as.port=10101

#Choose Install Folder

#---------------------

USER_INSTALL_DIR=/opt/IBM/InfoSphereChangeDataCapture/AccessServer

- Record your own response file by running the following command:

<installation_executable_name> -r <response_file>where:
- <installation_executable_name> is the name of the Access Server installation
file.
- <response_file> is the name of the response file.

For example, cdcaccess-<version>-<operating_system>-<architecture>-

setup.bin -r ASResponseFile.txtNote: The Access Server supported operating
system-architecture combinations are aix-power, hpux-pa, solaris-sparc
, and linux-x86.

5. Silently install Access Server by running the following command:

<installation_executable_name> -i SILENT -f <response_file>
For example, cdcaccess-<version>-setup.bin -i SILENT -f ASResponseFile.txt

15
16
 IBM InfoSphere Change Data Capture, Version 10.2.1
To upgrade Access Server (UNIX and Linux)
1. Make a note of the location of the data folder for the existing Access Server for
use later. This folder is located in your <installRoot> directory. This will enable
you to use your existing user, datastore, and subscription settings after you
upgrade.
2. Uninstall the existing Access Server.
3. Log on to your UNIX or Linux machine with the account you are using for the
Access Server installation.
4. Copy the installation file for your platform from the CD-ROM or download it from
the IBM® Web site.
5. Make the installation program executable.
6. Start the installation with the following command:./<installation_binary_name>
where <installation_binary_name> is the name of the installation file.
7. Press Enter on the Introduction screen to display the license agreement. Follow
the instructions on the screen to navigate through the license agreement.
8. Enter 1 to accept the license agreement.
9. Specify the port number to communicate with Management Console and press
Enter.
10. Enter the absolute path to your installation directory or press Enter to accept the
default directory.The directory that you specify must be owned by the account
you are using for the installation. If the installation program cannot create the
directory, you are prompted to specify a different directory.
11. Review the installation summary and press Enter to start the installation.
12. Press Enter to exit the installation after the installation is complete.
13. Copy the contents of the old DATA folder to the new location to enable you to
use the user, datastore and subscription settings it contains. Do NOT overwrite
the ID that you created in step 10.After you have completed the installation, you
must then start Access Server.

Related tasks:
To uninstall Access Server (UNIX and Linux)

17
 IBM InfoSphere Change Data Capture, Version 10.2.1
To uninstall Access Server (UNIX and Linux)
1. Ensure that Access Server is not running.
2. Log on to your UNIX or Linux machine with the account you are using for the
Access Server uninstallation.
3. Navigate to the <Uninstall> folder for your current installation.
4. Run the following command :UninstallAccessServer
5. Follow the prompts to complete the uninstallation.

Related tasks:
To install Access Server (UNIX and Linux)
To clean up a failed uninstallation of Access Server (UNIX and Linux)

18
 IBM InfoSphere Change Data Capture, Version 10.2.1
To clean up a failed uninstallation of Access Server
(UNIX and Linux)
1. Back up your Access Serverdata directory.This directory is located in your
<installRoot> directory.
This directory contains user and datastore profile information that you can use
after reinstalling Access Server.
2. Delete the Access Server installation directory. You can optionally delete all the
subdirectories within the installation directory, and retain the data directory.
3. Clean up the Zero G Registry file by removing the entries related to InfoSphere®
Change Data CaptureAccess Server. The registry file name and location is
/var/.com.zerog.registry.xml.By default, the .com.zerog.registry.xml file is hidden.
Notes:
- Ensure that you do not remove entries related to other products that you have
also installed on this machine.
- Note that the file name is preceded by a dot (that is, .com.zerog.registry.xml).

19
 IBM InfoSphere Change Data Capture, Version 10.2.1
To override the locale for the Access Server
installation (UNIX and Linux)
1. Navigate to the directory that contains the installation file.
2. Start the installer with the following flags to override the locale of the installation:
- English—<file_name>.bin -l en
- Japanese—<file_name>.bin -l ja
- Korean—<file_name>.bin -l ko
- Simplified Chinese—<file_name>.bin -l zh_CN

where:
- <file_name> is the name of the installation file.

20
 IBM InfoSphere Change Data Capture, Version 10.2.1
After you install Access Server
After installing Access Server on a Linux or Unix platform, you must start Access
Server and create a user account. Also, if you are using a firewall or any other
security mechanism that requires fixed ports, then you need to configure firewall
settings.
In this section, you will learn:

- Starting Access Server

- Creating an Access Server user account
- Configuring firewall settings for outbound (static) ports

21
 IBM InfoSphere Change Data Capture, Version 10.2.1
Starting Access Server
If you have installed Access Server on a UNIX or Linux platform, then you can use
the dmaccessserver command to start Access Server from the command line. You
can locate this command from /bin directory of your installation. You must start
Access Server before you can log in to Management Console.
See also:

- To start Access Server (UNIX and Linux)

22
 IBM InfoSphere Change Data Capture, Version 10.2.1
To start Access Server (UNIX and Linux)
1. Navigate to the /bin directory in your Access Server installation directory.
2. Issue the following command from the command line:./dmaccessserver &

Related tasks:
To create an Access Server user account (UNIX and Linux)

Related reference:
dmaccessserver—Starting Access Server

23
 IBM InfoSphere Change Data Capture, Version 10.2.1
Creating an Access Server user account
If you have installed Access Server on a UNIX or Linux platform, then you must use
the dmcreateuser command to create a user account before you can log in to
Management Console.
You can use the same command to add additional users, or you can add additional
users in Management Console.
See also:

- To create an Access Server user account (UNIX and Linux)

24
 IBM InfoSphere Change Data Capture, Version 10.2.1
To create an Access Server user account (UNIX and
Linux)
1. Ensure that Access Server has been started.
2. Navigate to the \bin directory in your Access Server installation directory.
3. Run the following command at the command line:./dmcreateuser <user_name><full_name>
<description><password><role><manager><change_password><password_expiry>

where:
- <user_name> is the unique name for the user for which you want to create an
account.
- <full_name> is the full name of the user.
- <description> is a description about the user.
- <password> is the password you want the user to supply when logging into
Management Console. If you have enabled complex passwords, then you must
specify a password that meets the requirements.
- <role> is the role you want to assign to the user. Enable one of the following
values:
- SYSADMIN—Specifies that a user assigned to this role is a system
administrator and can perform all available operations in Management Console
. Only users that require full operational access to the Monitoring and
Configuration perspectives should be assigned to this role. System
administrators can also modify system parameters to calibrate their replication
environment
- ADMIN—Specifies that a user assigned to this role is an Administrator and can
perform all available operations in Management Console, but cannot modify
system parameters. Users assigned to this role can access both the Monitoring
and Configuration perspectives.
- OPERATOR—Specifies that a user assigned to this role is an Operator and
only has access to the Monitoring perspective in Management Console.
- MONITOR—Specifies that a user assigned to this role is a Monitor and only
has access to the Monitoring perspective in Management Console.
- <manager> indicates that a user assigned the role of SYSADMIN also has
privileges to manage datastores and user accounts in the Access Manager
perspective of Management Console. If you want to enable this privilege for a
system administrator, then specify a value of TRUE. Otherwise, specify a value
FALSE. You must enable this privilege with a value of TRUE if you are creating
a user account for the UNIX or Linux platforms that will allow you to log in to
Management Console for the first time after the installation.
- <change_password> indicates that you want the user to change their password
when logging into Management Console for the first time. If you want the user to
change the password, specify a value of TRUE. Otherwise, if you want the user
to login using the same password you have assigned to them, then specify a
value of FALSE.
- <password_expiry> indicates that you want to override any existing password
expiry policies set in Management Console so that the password never expires.
If you want to override an existing password expiry policy, specify a value of
25
 TRUE. Otherwise, if you want the password to expire, then specify a value of
FALSE.

Related tasks:
To start Access Server (UNIX and Linux)

Related reference:
dmcreateuser—Adding a user account

26
 IBM InfoSphere Change Data Capture, Version 10.2.1
Configuring firewall settings for outbound (static)
ports
If your network uses a firewall or other security mechanism that requires static ports
for communication, then you must specify the ports that other computers can use to
communicate with Access Server services.
Note: In addition to a network firewall, you might have personal firewall software
installed and enabled on client machines. This firewall may cause a problem when
connecting to Management Console from Access Server. To calculate the number
of Access Server ports to open, use this formula: number of ports to open = 2 *
(number of users + (number of users * number of datastores) + number of
datastores) where a datastore refers to an InfoSphere® CDC instance.

The following figure highlights the ports you can configure for Management Console
and Access Server components. You can configure static port numbers for all or
some of these ports, depending on your network requirements.

27
The labels in the figure above correspond to the following groups of ports:
- 1—Communication from Management Console to the Access Server service. You
specify this port when you install Access Server and when you log in to
Management Console. The default port is 10101 and you can set this value in
Management Console.
28
- 2—Communication from Access Server back to Management Console for monitor
updates.
- 3—Communication from Management Console to the Access Server service, per
datastore (that is, per InfoSphere CDC instance). This requires two ports for each
InfoSphere CDC instance.
- 4—Communication from the Access Server service to the datastore, listen
process. This is established for each Management Console connection.
- 5—Communication from the Access Server service to the datastore, monitor
process. This is a shared connection between all Management Console
connections on the same datastore. This requires two ports for each datastore.
You must also configure your routers and firewalls to allow communication through
the configured ports. For more information, contact your network administrator.
Management Console requires:
- One input and output port to the Access Server.
- One input port from the Access Server
- One input and output port per datastore (regardless of whether you connect to the
datastore)

The Access Server requires:

- One input and output port per datastore, per installation of Management Console
- Two input and output ports, per datastore

Additionally, you can have more than one datastore, or more than one installation of
Management Console; for example:
- One installation of Management Console and one datastore
- One installation of Management Console and two datastores
- Two installations of Management Console and one datastore
- Two installations of Management Console and two datastores

Example: calculating ports required

To help determine the number of ports required, take a scenario where there are ten
concurrent users and three datastores.
To calculate the number of Access Server ports to open, use this formula: number of
ports to open = 2 * (number of users + (number of users * number of datastores) +
number of datastores) where a datastore refers to an InfoSphere CDC instance.
Using the previously mentioned scenario of ten concurrent users and three
datastores, the number of Access Server ports required is 86. Here is the
breakdown of the calculation, following the order in the figure above illustrating the
ports you can configure for Management Console and Access Server components:
- Number of concurrent users that will log into Access Server = 10
- One port per user to connect to and deliver unsolicited message = 10
- Number of possible concurrent connections from Management Console to connect
to datastores); that is, 10 users * 3 datastores = 10 * 3
- Number of possible concurrent connections to datastore, listen process; that is, 10
users * 3 datastores)
- Two ports required to connect to each datastore, monitor process = 2 * 3
Therefore, 10 + 10 + (10 *3) + (10 *3) + (2 *3) = 86
To calculate the number of ports to open Management Console, use this formula:
29
number of ports to open = 2 + number of datastores
Using the previously mentioned scenario of ten concurrent users and three
datastores, the number of ports required is 5 for each Management Console. This is
the breakdown of the calculation for each Management Console:
- Connection to Access Server = 1
- Connection for unsolicited updates from Access Server = 1
- One port for each connection to a datastore, listen process = 1 * 3
Therefore, 1 + 1 + (1 *3) = 5

See also:

- To configure static ports

30
 IBM InfoSphere Change Data Capture, Version 10.2.1
To configure static ports
1. Open the dmaccessserver.vmargs file in a text editor. This file is located in the
conf directory in your Access Server installation directory.
2. Replace the entry in this file with the following text:-jar lib/server.jar
local_port:<first_port> local_port_count:
<number_available_ports><Access_Server_listener_port>
where:
- <first_port> is the first port in the range that you want the Access Server
service to use when sending messages or establishing connections.
- <number_available_ports> is the number of ports you want to reserve for
this use.To calculate the number of Access Server ports to open, use this
formula: number of ports to open = 2 * (number of users + (number of users *
number of datastores) + number of datastores) where a datastore refers to an
InfoSphere® CDC instance.
- <Access_Server_listener_port> is the port number that Access Server
listens on and is set during the Access Server installation. You do not have to
specify a value here if you are using the default port number of 10101.

For example, if the number of available ports for communication is 500 and you
want Access Server to listen for connections on port 10101, then the entry would
be as follows: -jar lib/server.jar local_port:10102 local_port_count:500 10101
This enables Access Server to listen for connections on port 10101 and restricts
it to using ports in the range of 10102 to 10601.
These changes will take effect after you restart the Access Server service.

Related concepts:
Configuring firewall settings for outbound (static) ports

31
 IBM InfoSphere Change Data Capture, Version 10.2.1
About Management Console
Management Console is an administration application that allows you to configure
and monitor replication. Management Console allows you to manage replication on
various servers, specify replication parameters, and initiate refresh and mirroring
operations from a client workstation. After defining the data that will be replicated
and starting replication, you can close Management Console on the client
workstation without affecting data replication activities between source and target
servers.
Management Console includes an event log and a monitoring tool. The event log
allows you to examine generated InfoSphere® CDC event messages. The
monitoring tool allows you to continuously monitor replication operations and
latency. Diagrams depicting components of your replication configuration are
constructed through direct manipulation of graphical objects. The monitor in
Management Console is intended for time-critical working environments that require
continuous analysis of data movement.
In this section, you will learn:

- Installing Management Console

32
 IBM InfoSphere Change Data Capture, Version 10.2.1
Installing Management Console
This section outlines how to install and uninstall Management Console.
See also:

- To install Management Console

- To perform a silent installation of Management Console
- To uninstall Management Console
- To clean up a failed uninstallation of Management Console

33
 IBM InfoSphere Change Data Capture, Version 10.2.1
To install Management Console
1. Double-click on the installation file. The IBM®InfoSphere® CDCManagement
Console installation wizard opens.
2. Click Next.
3. Accept the terms of the license agreement by selecting I accept the terms in the
license agreement and click Next.
4. Select the folder where you want to install Management Console and click Next.
5. Select the location for the product icons and click Next.
6. Review the installation summary and click Install.
7. Click Done to exit the installation.

Related tasks:
To uninstall Management Console

34
 IBM InfoSphere Change Data Capture, Version 10.2.1
To perform a silent installation of Management
Console
1. Copy the installation file for your platform from the CD-ROM or download it from
the IBM® Web site.
2. Generate your response file in one of two ways:
- Edit the following example response file for Management Console so that it is
specific to your environment:# Tue Apr 05 13:59:28 EDT 2011
# Replay feature output

# ---------------------

# This file was built by the Replay feature of InstallAnywhere.

# It contains variables that were set by Panels, Consoles or Custom Code.

#Has the license been accepted

#-----------------------------

LICENSE_ACCEPTED=TRUE

#Choose Install Folder

#---------------------

USER_INSTALL_DIR=C:\\Program Files\\IBM\\InfoSphere Change Data Capture\\Management Console

#Choose Shortcut Folder

#----------------------

USER_SHORTCUTS=C:\\ProgramData\\Microsoft\\Windows\\Start Menu\\Programs\\IBM InfoSphere Change Data

Capture\\Management Console

- Record your own response file by running the following command:

<installation_executable_name> -r <response_file>where:
- <installation_executable_name> is the name of the Management Console
installation file.
- <response_file> is the name of the response file.

For example, cdcmc-<version>-setup.exe -r MCResponseFile.txt

3. Silently install Management Console by running the following command:
<installation_executable_name> -i SILENT -f <response_file>
For example, cdcmc-<version>-setup.exe -i SILENT -f MCResponseFile.txt

35
 IBM InfoSphere Change Data Capture, Version 10.2.1
To uninstall Management Console
Use the Windows Control Panel applet to remove Management Console.

Related tasks:
To install Management Console
To clean up a failed uninstallation of Management Console

36
 IBM InfoSphere Change Data Capture, Version 10.2.1
To clean up a failed uninstallation of Management
Console
1. Delete any files remaining in the Management Console installation folder.
2. Clean up the Zero G Registry file by removing the entries related to InfoSphere®
Change Data CaptureManagement Console. The registry file name and location
are as follows:
- Windows x86 processor—C:\Program Files\Zero G
Registry\.com.zerog.registry.xml
- Windows x86-64 processor—C:\Program Files(x86)\Zero G
Registry\.com.zerog.registry.xml
By default, these are hidden directories.
Notes:
- Ensure that you do not remove entries related to other products that you have
also installed on this machine.
- Note that the file name is preceded by a dot (that is, .com.zerog.registry.xml).

37
 IBM InfoSphere Change Data Capture, Version 10.2.1
Commands
This section includes the commands necessary for the installation of Access Server.
For more information on other Access Server commands, see Commands for
Access Server.
In this section, you will learn:

- dmaccessserver—Starting Access Server

- dmcreateuser—Adding a user account
- dmshutdownserver—Shut down Access Server

38
 IBM InfoSphere Change Data Capture, Version 10.2.1
dmaccessserver—Starting Access Server
Use this command to start Access Server services for Windows and to start Access
Server processes for UNIX and Linux.
Note: To stop Access Server, use the kill command to stop the dmaccessserver
process.

Syntax
DMACCESSSERVER

Parameters
None.

39
 IBM InfoSphere Change Data Capture, Version 10.2.1
dmcreateuser—Adding a user account
Use this command to add a new user. Adding a user account is necessary to
provide users with the ability to log in to Management Console.

Syntax
DMCREATEUSER username fullname description password role manager changePassword

passwordNeverExpires [-accessserver hostname port adminuser adminpassword]

Parameters
- username
- Specifies the unique name for the user you want to create an account for.
- fullname
- Specifies the full name of the user.
- description
- Specifies a description about the user.
- password
- Specifies the password you want the user to supply when logging into
Management Console. If you have enabled complex passwords, then you must
specify a password that meets the requirements.
- role
- Specifies the role you want to assign to the user. Enable one of the following
values:
- SYSADMIN—Specifies that a user assigned to this role is working in a system
administrator account and can perform all available operations in
Management Console. Only users that require full operational access to the
Monitoring and Configuration perspectives should be assigned to this role.
System administrators can also modify system parameters to calibrate their
replication environment.
- ADMIN—Specifies that a user assigned to this role is working in an
Administrator account and can perform all available operations in
Management Console, but cannot modify system parameters. Users assigned
to this role can access both the Monitoring and Configuration perspectives.
- OPERATOR—Specifies a that user assigned to this role is working in an
Operator account and has access to both the Monitoring and Configuration
perspectives. Operators can add, import and export projects, but they cannot
create new subscriptions. Users assigned to the Operator role can start, stop,
and monitor replication activities. They can also view the tables selected for
refresh and start a refresh on a subscription. Operators can view notifications
sent by subscriptions or datastores. However, users assigned to this role
cannot configure replication and select or remove tables from a refresh.
- MONITOR—Specifies that a user assigned to this role is working in a
Monitoring account and only has access to the Monitoring perspective in
Management Console. Users assigned to the Monitor role can view the event
log, view statistics, and view table mappings. Monitors can view the replication
state and status of a subscription and can view latency threshold information.
However, users assigned to this role cannot start or stop replication, configure
replication, refresh tables, or view notifications sent by subscriptions and
40
 datastores.
- manager
- Specifies that a user assigned the role of SYSADMIN also has privileges to
manage datastores and user accounts in the Access Manager perspective of
Management Console. If you want to enable this privilege for a system
administrator, then specify a value of TRUE. Otherwise, specify a value FALSE.
Note: You must enable this privilege with a value of TRUE if you are creating a
user account for the UNIX or Linux platforms that will allow you to log in to
Management Console for the first time after the installation.
- changePassword
- Specifies you want the user to change their password when logging into
Management Console for the first time. If you want the user to change the
password, specify a value of TRUE. Otherwise, if you want the user to login
using the same password you have assigned to them, then specify a value of
FALSE.
- passwordNeverExpires
- Specifies that you want to override any existing password expiry policies set in
Management Console so that the password never expires. If you want to
override an existing password expiry policy, specify a value of TRUE.
Otherwise, if you want the password to expire, then specify a value of FALSE.
- -accessserver hostname port adminuser adminpassword
- The following parameters are optional and are only required if you are running
this command remotely from the system where you have installed Access
Server. The -accessserver parameter indicates that you want to connect to a
remote installation of Access Server. It indicates that you want to run this
command for an installation of Access Server that is physically remote from the
Access Server installation where you are running this command.
- -accessserver
- Specify -accessserver. This parameter indicates that you want to connect
to a remote installation of Access Server.
- hostname
- The fully qualified host name of the remote system where Access Server is
installed.
- adminuser
- A user with system administrator (SYSADMIN) privileges (see the role
parameter above) and the ability to manage users and datastores (see the
manager parameter above).
- adminpassword
- The password for the specified SYSADMIN user.

Related tasks:
To create an Access Server user account (UNIX and Linux)

41
42
 IBM InfoSphere Change Data Capture, Version 10.2.1
dmshutdownserver—Shut down Access Server
Use this command to shut down the Access Server service for Windows and shut
down the Access Server process for UNIX and Linux.

Syntax
DMSHUTDOWNSERVER [- accessserver hostname host port number adminuser name adminpassword value]

Parameters
- hostname host
- Specifies the hostname where Access Server is installed.
- port number
- Specifies the port number used to connect to Access Server.
- adminuser name
- Specifies the username that will be used to log on to Access Server.
- adminpassword value
- Specifies the password for the username that will be used to log on to Access
Server.

43
 IBM InfoSphere Change Data Capture, Version 10.2.1
Troubleshooting
If you encounter issues while running InfoSphere® CDC, you have a number of
options for tracking and troubleshooting issues to help with problem resolution.
There are three methods that you can use in InfoSphere CDC for tracking and
troubleshooting issues:
- Data Collection with the IBM® Support Assistant (ISA DC)
- Management Console Support Assistant
- The dmsupportinfo command, which is executed on the replication engine
If you are trying to troubleshoot issues with InfoSphere CDC version 10.2 or later on
Linux, UNIX and Windows operating systems, you should use the ISA DC tool
unless otherwise instructed by IBM Technical Support.
In this section, you will learn:

- Using the IBM Support Assistant (ISA DC)

- Troubleshooting connection problems
- Locating log files
In addition to the Management Console event log, InfoSphere CDC produces
other logs to help troubleshoot replication errors, and the installation process also
produces log files.
- Troubleshooting and contacting IBM Support

44
 IBM InfoSphere Change Data Capture, Version 10.2.1
Using the IBM Support Assistant (ISA DC)
You can use the IBM® Support Assistant Data Collection tool (ISA DC) to collect
InfoSphere® CDC data to provide to IBM Technical Support to assist you in
troubleshooting issues with InfoSphere CDC, to request a product enhancement or
to ask a question about InfoSphere CDC.
ISA DC can be used with InfoSphere CDC replication engines that are version 10.2
or later, except InfoSphere CDC for z/OS®.
The ISA DC tool is included in the InfoSphere CDC installation process, and does
not require configuration. The executable files are located in the isa folder in the
InfoSphere CDC directory. Simply run the isadc.bat, isadc.sh or index.html file, as
appropriate, to launch the tool.
Prerequisites and considerations for using ISA DC
The following prerequisite must be satisfied on the machine on which ISA DC will be
run, in order to successfully use the tool:
- IBM JRE/JDK version 1.6 or later
The following issues should be taken into consideration before you attempt to use
ISA DC:
- ISA DC cannot be run remotely. It must be run on the machine where the instance
is configured.
- ISA DC cannot be used to collect data from InfoSphere CDC for z/OS.
- If InfoSphere CDC is installed but you have not configured an instance or are
unable to configure an instance, ISA DC can still be used to collect minimal data to
assist IBM Technical Support in resolving the issue.
See also:

- To use ISA DC to collect data for a product problem (command line)

- To use ISA DC to collect data for a product problem (GUI)
- To use ISA DC to collect data for a question or an enhancement request
(command line)
- To use ISA DC to collect data for a question or an enhancement request (GUI)

45
 IBM InfoSphere Change Data Capture, Version 10.2.1
To use ISA DC to collect data for a product problem
(command line)
1. Launch the IBM® Support Assistant.Run the isadc.bat or isadc.sh file, located in
the isa\isadc folder in the root directory of the InfoSphere® CDC instance.
2. Enter 1 to accept the license agreement and press Enter.After the license
agreement has been accepted, it will not be shown again.
3. Provide a file name and press Enter.The name provided will be given to the .zip
file containing the data collection results.
If you do not want to assign a name to the data collection results, press Enter
and a default name will be used.
4. Enter 1 to confirm your chosen file name and press Enter to continue.
5. Enter 1 to run the InfoSphere Change Data CaptureSupport Assistant Data
Collector and press Enter.The Welcome page is displayed.
6. Read the Welcome page information and enter 1 to proceed. Press Enter.
7. Enter 1 to collect data for a product problem and press Enter.
8. Enter 1 to process your input and continue collecting data. Press Enter.If you
want to cancel the collection, enter 2 and press Enter.
If you want to go back and change your input for the previous step, enter 3 and
press Enter.
9. Select the name of the InfoSphere CDC instance for which data will be collected.
If you have multiple instances of InfoSphere CDC configured, you will be asked
to select which instance for which you want to collect. Enter the corresponding
number for the instance name and press Enter.
If you have a single InfoSphere CDC instance configured, it will be selected
automatically and this step will be skipped.
Even if you do not have an instance configured, ISA DC will still collect what
data is available. If no instance is configured, you can skip to Step 14.
10. Enter 1 to process your input and continue collecting data. Press Enter.If you
want to cancel the collection, enter 2 and press Enter.
If you want to go back and change your input for the previous step, enter 3 and
press Enter.
11. If your selected instance is not running, you will be alerted by ISA DC. As only
minimal data is available if the instance is stopped, it is preferable that the
instance be running during data collection.Try to start your instance. When the
instance is running, enter 1 and press Enter.
If you cannot start your instance and want to continue the data collection
process, enter 2 and press Enter.
12. Enter 1 to process your input and continue collecting data. Press Enter.If you
want to cancel the collection, enter 2 and press Enter.
If you want to go back and change your input for the previous step, enter 3 and
press Enter.
13. If the instance is running, you will be asked for information regarding when the
problem occurred.
A. Enter the date and time when you think the problem began and press Enter.
This information must be entered in the following format: yyyy-mm-dd
hh:mm:ss
46
 B. Enter 1 to process your input and continue collecting data. Press Enter.If you
want to cancel the collection, enter 2 and press Enter.
If you want to go back and change your input for the previous step, enter 3
and press Enter.
C. Determine the period of time for which the data will be collected and press
Enter.The amount specified will be applied as a before value and an after
value to the date and time specified previously. For example, if you select 1
Day as the time period, data will be collect for 24 hours before the specified
date and time and for the 24 hours after the specified date and time.
D. Enter 1 to process your input and continue collecting data. Press Enter.If you
want to cancel the collection, enter 2 and press Enter.
If you want to go back and change your input for the previous step, enter 3
and press Enter.
14. Select the method to transfer the data collection archive file and press Enter.
Choose one of the following options:
- Send using secure transfer to IBM Support (HTTPS)—Sends the .zip file to
IBM Support using a secure protocol.
- Send using FTP to IBM Support (unencrypted)—Sends the .zip file to IBM
Support using an unencrypted protocol.
- Send using FTP to another location (unencrypted)—Sends the .zip file to a
recipient of your choice, using an unencrypted protocol.
- End the collection without sending—Ends the data collection and creates
the .zip file, but does not transfer it.
15. Enter 1 to process your input and continue collecting data. Press Enter.If you
want to cancel the collection, enter 2 and press Enter.
If you want to go back and change your input for the previous step, enter 3 and
press Enter.
16. If you chose to end the collection without sending the output, ISA DC will notify
your when the .zip file has been successfully created. Enter 1 and press Enter to
exit the application.
17. If you chose to transfer the file using HTTPS, follow these steps:
A. If you want to receive a confirmation email when the upload was successful,
enter an email address and press Enter. If you do not want to receive
confirmation, press Enter to continue.
B. Enter 1 to process your input and continue collecting data. Press Enter.If you
want to cancel the collection, enter 2 and press Enter.
If you want to go back and change your input for the previous step, enter 3
and press Enter.
C. Enter the PMR number that was given to you by IBM Technical Support and
press Enter. Ensure that the PMR number follows the required naming
convention of PMRNumber.BranchNumber.CountryCode. If an unknown
PMR number is entered, you will be asked to correct the PMR number and
re-send the data.
D. Enter 1 to process your input and continue collecting data. Press Enter.If you
want to cancel the collection, enter 2 and press Enter.
If you want to go back and change your input for the previous step, enter 3
and press Enter.
47
18. If you chose to transfer the file to IBM Technical Support using unencrypted
FTP, follow these steps:
A. Enter the PMR number that was given to you by IBM Technical Support and
press Enter. Ensure that the PMR number follows the required naming
convention of PMRNumber.BranchNumber.CountryCode. If an unknown PMR
number is entered, you will be asked to correct the PMR number and re-send
the data.
B. Enter 1 to process your input and continue collecting data. Press Enter.If you
want to cancel the collection, enter 2 and press Enter.
If you want to go back and change your input for the previous step, enter 3
and press Enter.
19. If you chose to transfer the file using unencrypted FTP, follow these steps:
A. Enter the FTP host name and press Enter.
B. Enter the user name and press Enter.
C. Enter the password for the user name and press Enter.
D. Enter the path for the directory on the FTP server and press Enter.
E. Enter 1 to process your input and continue collecting data. Press Enter.If you
want to cancel the collection, enter 2 and press Enter.
If you want to go back and change your input for the previous step, enter 3
and press Enter.
20. When you receive notice that the operation has completed successfully, enter 1
and press Enter to exit the application.

48
 IBM InfoSphere Change Data Capture, Version 10.2.1
To use ISA DC to collect data for a product problem
(GUI)
1. Launch the IBM® Support Assistant.Run the index.html file, located in the
isa\isadc folder in the root directory of the InfoSphere® CDC instance.
2. Read the license agreement and click OK to accept it.After the license
agreement has been accepted, it will not be shown again.
3. Click Start.The Welcome screen opens.
4. Click OK.
5. Select A product problem from the drop down box.
6. Click OK.
7. Select the name of an InfoSphere CDC instance from the drop down list and
click OK.If you have multiple instances of InfoSphere CDC configured, you will
be asked to select which instance for which you want to collect.
If you have a single InfoSphere CDC instance configured, it will be selected
automatically and this step will be skipped.
8. If your selected instance is not running, you will be alerted by ISA DC. As only
minimal data is available if the instance is stopped, it is preferable that the
instance be running during data collection.Try to start your instance. When the
instance is running, select Yes, I have started the instance from the drop down
box and click OK.
If you cannot start your instance and want to continue the data collection
process, select No, continue with minimal data collection from the drop down
box and click OK.
9. If the instance is running, you will be asked for information regarding when the
problem occurred. Enter the date and time when you think the problem began
and click OK.This information must be entered in the following format: yyyy-mm-
dd hh:mm:ss.
10. Determine the period of time for which the data will be collected and click OK.
Choose one of the following values:
- 6 hours
- 12 hours
- 1 Day
- 2 Days
- 7 Days
The amount specified will be applied as a before value and an after value to the
date and time specified previously. For example, if you select 1 Day as the time
period, data will be collect for 24 hours before the specified date and time and
for the 24 hours after the specified date and time.
11. If you chose to end the collection without sending the output, select Do not
transfer data to IBM. ISA DC will notify you when the .zip file has been
successfully created.
12. If you want to transfer the data to IBM using a secure transfer (HTTPS), select
the Transfer to IBM option.
A. Choose the HTTPS transfer type option.
B. Enter the PMR number that was given to you by IBM Technical Support.
Ensure that the PMR number follows the required naming convention of
PMRNumber.BranchNumber.CountryCode. If an unknown PMR number is
49
 entered, you will be asked to correct the PMR number and re-send the data.
C. Enter your email address.
D. Click Transfer.
13. If you want to transfer the data to IBM using unencrypted FTP, select the
Transfer to IBM option.
A. Choose the FTP transfer type option.
B. Enter the PMR number that was given to you by IBM Technical Support.
Ensure that the PMR number follows the required naming convention of
PMRNumber.BranchNumber.CountryCode. If an unknown PMR number is
entered, you will be asked to correct the PMR number and re-send the data.
C. Click Transfer.
14. If you choose to send the data to a location other than IBM using unencrypted
FTP, click Transfer to another server via FTP
A. Enter the email address or IP address of the recipient in the Hotmail/IP
Address field.
B. Enter the user name.
C. Enter the password.
D. Enter the path for the directory on the FTP server.
E. Click Transfer.
15. When you receive notice that the operation has completed successfully, click
Browse directory if you want to see the file you created or click Start New
Collection to collect more data.To exit the application, close your browser tab or
window.

50
 IBM InfoSphere Change Data Capture, Version 10.2.1
To use ISA DC to collect data for a question or an
enhancement request (command line)
1. Launch the IBM® Support Assistant.Run the isadc.bat or isadc.sh file, located in
the isa\isadc folder in the root directory of the InfoSphere® CDC instance.
2. Enter 1 to accept the license agreement and press Enter.After the license
agreement has been accepted, it will not be shown again.
3. Provide a file name and press Enter.The name provided will be given to the .zip
file containing the data collection results.
If you do not want to assign a name to the data collection results, press Enter
and a default name will be used.
4. Enter 1 to confirm your chosen file name and press Enter to continue.
5. Enter 1 to run the InfoSphere Change Data CaptureSupport Assistant Data
Collector and press Enter.The Welcome page is displayed.
6. Read the Welcome page information and enter 1 to proceed. Press Enter.
7. Enter 2 to collect data for a question or an enhancement request and press
Enter.
8. Enter 1 to process your input and continue collecting data. Press Enter.If you
want to cancel the collection, enter 2 and press Enter.
If you want to go back and change your input for the previous step, enter 3 and
press Enter.
9. Select the method to transfer the data collection archive file and press Enter.
Choose one of the following options:
- Send using secure transfer to IBM Support (HTTPS)—Sends the .zip file to
IBM Support using a secure protocol.
- Send using FTP to IBM Support (unencrypted)—Sends the .zip file to IBM
Support using an unencrypted protocol.
- Send using FTP to another location (unencrypted)—Sends the .zip file to a
recipient of your choice, using an unencrypted protocol.
- End the collection without sending—Ends the data collection and creates
the .zip file, but does not transfer it.
10. Enter 1 to process your input and continue collecting data. Press Enter.If you
want to cancel the collection, enter 2 and press Enter.
If you want to go back and change your input for the previous step, enter 3 and
press Enter.
11. If you chose to end the collection without sending the output, ISA DC will notify
your when the .zip file has been successfully created. Enter 1 and press Enter to
exit the application.
12. If you chose to transfer the file using HTTPS, follow these steps:
A. If you want to receive a confirmation email when the upload was successful,
enter an email address and press Enter. If you do not want to receive
confirmation, press Enter to continue.
B. Enter 1 to process your input and continue collecting data. Press Enter.If you
want to cancel the collection, enter 2 and press Enter.
If you want to go back and change your input for the previous step, enter 3
and press Enter.
C. Enter the PMR number that was given to you by IBM Technical Support and
press Enter. Ensure that the PMR number follows the required naming
51
 convention of PMRNumber.BranchNumber.CountryCode. If an unknown
PMR number is entered, you will be asked to correct the PMR number and
re-send the data.
D. Enter 1 to process your input and continue collecting data. Press Enter.If you
want to cancel the collection, enter 2 and press Enter.
If you want to go back and change your input for the previous step, enter 3
and press Enter.
13. If you chose to transfer the file to IBM Technical Support using unencrypted
FTP, follow these steps:
A. Enter the PMR number that was given to you by IBM Technical Support and
press Enter. Ensure that the PMR number follows the required naming
convention of PMRNumber.BranchNumber.CountryCode. If an unknown PMR
number is entered, you will be asked to correct the PMR number and re-send
the data.
B. Enter 1 to process your input and continue collecting data. Press Enter.If you
want to cancel the collection, enter 2 and press Enter.
If you want to go back and change your input for the previous step, enter 3
and press Enter.
14. If you chose to transfer the file using unencrypted FTP, follow these steps:
A. Enter the FTP host name and press Enter.
B. Enter the user name and press Enter.
C. Enter the password for the user name and press Enter.
D. Enter the path for the directory on the FTP server and press Enter.
E. Enter 1 to process your input and continue collecting data. Press Enter.If you
want to cancel the collection, enter 2 and press Enter.
If you want to go back and change your input for the previous step, enter 3
and press Enter.
15. When you receive notice that the operation has completed successfully, enter 1
and press Enter to exit the application.

52
 IBM InfoSphere Change Data Capture, Version 10.2.1
To use ISA DC to collect data for a question or an
enhancement request (GUI)
1. Launch the IBM® Support Assistant.Run the index.html file, located in the
isa\isadc folder in the root directory of the InfoSphere® CDC instance.
2. Read the license agreement and click OK to accept it.After the license
agreement has been accepted, it will not be shown again.
3. Click Start.The Welcome screen opens.
4. Click OK.
5. Select A question or enhancement request from the drop down box.
6. Click OK.
7. If you chose to end the collection without sending the output, select Do not
transfer data to IBM. ISA DC will notify you when the .zip file has been
successfully created.
8. If you want to transfer the data to IBM using a secure transfer (HTTPS), select
the Transfer to IBM option.
A. Choose the HTTPS transfer type option.
B. Enter the PMR number that was given to you by IBM Technical Support.
Ensure that the PMR number follows the required naming convention of
PMRNumber.BranchNumber.CountryCode. If an unknown PMR number is
entered, you will be asked to correct the PMR number and re-send the data.
C. Enter your email address.
D. Click Transfer.
9. If you want to transfer the data to IBM using unencrypted FTP, select the
Transfer to IBM option.
A. Choose the FTP transfer type option.
B. Enter the PMR number that was given to you by IBM Technical Support.
Ensure that the PMR number follows the required naming convention of
PMRNumber.BranchNumber.CountryCode. If an unknown PMR number is
entered, you will be asked to correct the PMR number and re-send the data.
C. Click Transfer.
10. If you choose to send the data to a location other than IBM using unencrypted
FTP, click Transfer to another server via FTP
A. Enter the email address or IP address of the recipient in the Hotmail/IP
Address field.
B. Enter the user name.
C. Enter the password.
D. Enter the path for the directory on the FTP server.
E. Click Transfer.
11. When you receive notice that the operation has completed successfully, click
Browse directory if you want to see the file you created or click Start New
Collection to collect more data.To exit the application, close your browser tab or
window.

53
 IBM InfoSphere Change Data Capture, Version 10.2.1
Troubleshooting connection problems
If you have problems connection to Access Server or a datastore (that is, an
InfoSphere® CDC installation), refer to this checklist.
Failing to connect to Access Server
- Verify your network firewall configuration between your Management Console and
Access Server machines.
- Ensure that you have configured static ports properly on both Management
Console and Access Server.

Failing to connect to a datastore

- Verify your network firewall configuration between your Management Console and
Access Server machines.Access Server connects to Management Console so this
may lead to a datastore connection problem.
- Ensure that you have configured static ports properly on both Management
Console and Access Server.
- If the Management Console machine is configured with a personal firewall, ensure
that it is properly configured to allow connections to Management Console from
Access Server. Typically, the resolution is to add Management Console to your list
of software exemptions in the personal firewall software. However, depending on
your personal firewall, this may differ. Consult your personal firewall documentation
for any connection conflicts or problems.

Related tasks:
To configure static ports

54
 IBM InfoSphere Change Data Capture, Version 10.2.1
Locating log files
In addition to the Management Console event log, InfoSphere® CDC produces
other logs to help troubleshoot replication errors, and the installation process also
produces log files.
Review the log files in the <CDC_installation directory>\Uninstall\Logs directory
if you encounter any errors during the installation of InfoSphere CDC, Management
Console, or Access Server.

55
 IBM InfoSphere Change Data Capture, Version 10.2.1
Troubleshooting and contacting IBM Support
The following support page contains the latest troubleshooting information and
details on how to open a service request with IBM® Support:
- http://www.ibm.com/software/data/infosphere/support/change-data-capture/

For contact information in your region:

- http://www.ibm.com/planetwide/

56