Option
|
Description
|
---|---|
Name
|
Type a name for your IBM InfoSphere CDC instance. This name must be unique.
|
Server Port
|
Type the port number which IBM InfoSphere CDC uses for communication with client workstations running Management Console and other servers.
This port number cannot be used by other applications installed on the same server. You will use this port number when specifying access parameters for your datastore in the Access Manager perspective in Management Console. IBM InfoSphere CDC displays a default TCP/IP port of 11101. For more information, see your Management Console documentation.
If you install several instances on the same node, the port number for each instance must be unique.
|
Auto-Discovery Port
|
Select the box and type the UDP port number that is used for auto-discovery broadcasts sent from Access Server. For more information about auto-discovery, see your Management Console documentation.
|
Maximum Memory Allowed
|
Type the maximum amount of RAM you want to allocate for IBM InfoSphere CDC. You must allocate a minimum of 64 MB for each instance you configure. By default, there is 512 MB of RAM allocated for a 32 bit instance and 1024 MB of RAM allocated for a 64 bit instance.
|
Staging Store Disk Quota (GB)
|
Enter the maximum amount of disk space that will be utilized by the IBM InfoSphere CDC staging store on your source system. The default value is 100 GB and minimum value is 1 GB.
Specify 1 GB if you are creating an instance that will be used as a target of replication. This reduces the disk resources that IBM InfoSphere CDC requires on your target system.
|
Bit-Version
|
Select the bit-version of your database by selecting one of the following options:
▪32 bit
▪64 bit
These options are not enabled if you are installing IBM InfoSphere CDC on a 32-bit server.
|
Option
|
Description
|
---|---|
Local System account
|
Start IBM InfoSphere CDC services through the local system administrator account.
|
This account
|
Start IBM InfoSphere CDC services through the specified user account.
The account must be specified in the format <domain>\<user name>, where <domain> is the name of a domain in your environment, and <user name> is a valid login user name in the specified domain. If your computer is not part of a domain, you can specify <computer name>\<user name>.
In the Password and Confirm Password boxes, type the password currently associated with the selected Windows user account. If you change the password for the Windows user account after installing IBM InfoSphere CDC, you will have to use the Windows Services dialog to change the password currently set for each IBM InfoSphere CDC service.
|
Option
|
Description
|
---|---|
User name
|
Type the user name for the specified database.
|
Password
|
Type the password for the specified database.
|
Metadata Schema
|
Select the schema for the database that will be used for the IBM InfoSphere CDC metadata tables.
As a default, the user name entered above is used. You can specify any schema except those in use by other installed instances of IBM InfoSphere CDC for the given database. You must set up or decide on this schema as part of the installation prerequisites.
Make sure to use UPPERCASE letters for the metadata schema. By default, all the schema names (catalog names) in solidDB® are in uppercase.
|
Advanced
|
The Advanced button enables you to modify configuration parameters for the solidDB® JDBC driver. For more information about the JDBC driver parameters, see the solidDB® Programmer Guide.
Tip:
▪In HA setup, the parameter solid_tf_level is by default set to CONNECTION.
▪In SMA setup, the parameter solid_shared_memory is by default set to yes.
▪To enable use of operating-system-based external authentication, set this property:
solid_use_strong_encryption=yes
|
Option
|
Description
|
---|---|
Single server
|
Type the host name and port number for the specified solidDB® server.
|
Enable SMA
|
Select the check box if you are using solidDB® with shared memory access (SMA).
|
HA Configuration (HotStandby)
|
Type the host names and port numbers for the specified Primary and Secondary solidDB® servers.
|