Define a server for Enterprise Replication

Prerequisite tasks

The list displays the tasks that you must complete before you can define a server for ER by using the IBM® OpenAdmin Tool (OAT) for Informix®.

1. Prepare the network environment for the server.
   1. Set up the hosts files.
      • In the hosts file of the new node, identify the IP address and system name of each server in the ER domain.
      • In the hosts files of the other servers in the domain, identify the IP address and system name for the new node.
   2. Set up the services files.
      • In the services file of the new node, identify the port number and service name of each server in the ER domain.
      • In the services files of the other servers in the domain, identify the port number and service name for the new node.
   3. Set up the trusted environment.

      Set up a trust relationship for all users in the hosts.equiv file in the $INFORMIXDIR/etc directory, or for specific users in .rhosts files in their home directory.

2. Update the SQLHOSTS file for the server. If you are adding the server to an existing ER domain, also update the SQLHOSTS files for the other servers in that ER domain.
   1. Set up the server groups.

      Each server in the ER domain must be a member of a server group that has a unique ID. The server group identifies the server in the ER domain.

   2. Verify that any existing servers in the ER domain contain the server group information for the new node.

      If you are adding the server to an existing domain, update the SQLHOSTS information about all root and nonroot servers in the domain.

      For hierarchical routing topologies, root and nonroot nodes must include information for all the servers. Each leaf node must include information only for itself and its parent node.

   3. Set the network encryption by setting the encryption configuration parameters.
   4. Check the connection security option.
   5. Test the network environment.

      If you are making the server a new node in an existing ER domain, verify the network connection and test the trusted environment.

3. Optional: Create the ATS (Aborted Transactions Spooling) and RIS (Row Information Spooling) directories for the server.

   The ATS and RIS files contain information about failed transactions and aborted rows. You can repair data after replication has failed by using ATS and RIS files.

4. Verify that the server is up and running. For Informix 12.10, the server can be a stand-alone server or a primary server in a cluster. For Informix versions prior to 12.10, the server must be a stand-alone server, not part of a high availability cluster. For Informix versions prior to 12.10, OAT cannot define a server for ER if it is part of a high availability cluster. You can define a server that is part of a high availability cluster by using the cdr command-line utility.

Step 1: Select a server

The list displays servers in the current OAT group that are not already in the current ER domain. Select the server to define for ER from the list.

Add a server to the list

If the server does not appear in the list because it is not part of the current OAT group, click Add a server to the list, and enter the connection information for the server. The server is added to the current OAT group, added to the list, and automatically selected.

To select a server in a different OAT group, log on to the OAT group for that server and start the Define Server wizard again.