Modify Server
Use this page to modify an Enterprise Replication (ER) server. Change the ATS directory or RIS directory, the idle timeout, or the type of some of the participants on the server. Enable monitoring the quality of replicated data.
ER node options
- ATS directory
- Disable ATS file generation, or specify the directory in which
to generate the ATS files.
- Disable ATS file generation
- Do not generate ATS files on this server.
- Generate the ATS files in the temporary directory
- Store the ATS files in the /tmp directory on UNIX systems and in the %INFORMIXDIR%\tmp directory on Windows systems.
- Generate the ATS files in this directory
- Enter the complete path for an existing directory in which to store the ATS files.
- RIS directory
- Disable RIS file generation, or specify the directory in which
to generate the RIS files.
- Disable RIS file generation
- Do not generate RIS files on this server.
- Generate the RIS files in the temporary directory
- Store the RIS files in the /tmp directory on UNIX systems and in the %INFORMIXDIR%\tmp directory on Windows systems.
- Generate the RIS files in this directory
- Enter the complete path for an existing directory in which to store the RIS files.
- ATS and RIS file format
- Specify the format for the ATS and RIS files.
- Text
- Generate text files that ER can process to repair failed transactions. (Default)
- XML
- Generate XML files that you can use if you write your own custom repair scripts.
- Both
- Generate text files and XML files.
- Idle timeout (minutes)
- Specify the amount of time that the connection between the server and the other servers in the ER domain can be idle before the server disconnects. Select On and enter the time in minutes. Entering 0 (zero) minutes or leaving the field blank is the same as selecting Off.
Change the type of participants on this server
Change the type of the participants on the server in replicates whose conflict resolution rule is ignore.
- Participant type
- Specify the participant type:
- No change
- The participant type is not changed.
- Primary
- The participants both send and receive replicated data.
- Receive-only
- The participants only receive data from primary participants.
When you click Save, the page displays the options that you selected and the results of the action.
Monitor the quality of data
When the quality of data is monitored, the Connection Manager can route client connections to the replication servers based on the transaction latency, the number of apply failures, and the workload. When the quality of data is not monitored, the Connection Manager can route client connections based on the workload only. This option requires IBM® Informix® 11.70.For the Connection Manager, the OpenAdmin Tool (OAT) for Informix requires IBM Informix 11.70.xC3 and the Connection Manager that is packaged with Informix 11.70.xC3 or later, or with IBM Informix Client Software Development Kit (Client SDK) 3.70.xC3
- Enable monitoring the quality of replicated data
- Monitor the quality of replicated data for the replication servers in the grid or replicate set that this server is a member of and define this server as the master server for data quality. To configure the Connection Manger to route client connections based on the quality of data, create a service level agreement (SLA) on the pages.
When the quality of data is monitored, the failed transactions on the replication servers are counted. When you synchronize data, you can reset the failed transaction count on the replication servers or you can continue with the current count. To maintain accurate information about the quality of data, reset the count when you synchronize the data. The failed transaction count is reset on the Replicates page with the Check or Sync Data action. or