Step 2: Select the ER domain and set the node options
Specify the ER domain, the node type, and the node options for the server.
This information about the new node appears at the top of the page.
- Server that you are defining for ER. The name of the server that you selected.
- ER group. The server group for the server. The server group is identified in the SQLHOSTS information about the server when you prepare the network environment.
Specify the ER domain
- To make the server a node in an existing ER domain:
- Select Add the server as a new node to an existing ER domain.
- Select a server to synchronize the ER domain configuration from
the list.
The list shows the servers in the SQLHOSTS information of new node. The SQLHOSTS information is verified when you prepare the network environment for the server, before you run the wizard.
When you add a server to an existing ER domain, you must synchronize the global catalog in the new node with an existing server in the domain.
For hierarchical routing topologies, if you define the new node as a nonroot or leaf node, ER also uses this synchronization server as the parent of the new node.
- To make the server the first node in a new domain, select Create a new ER domain.
Specify the ER node type
- If you make the server the first node in a new domain, it is a root node and the other options are not available.
- If you add the server to an existing ER domain, specify the node type. Choose the node type that corresponds to the way that you have set up the SQLHOSTS information for this node.
The node type depends on the topology that you created when you prepared the network environment for the server. The ER topology describes the connections that the ER servers make to interact with each other.
- In a fully connected topology, all the nodes are root nodes.
- In hierarchical routing topologies:
- A root node can connect with any other root node and its child nodes.
- A nonroot node can connect with its parent node and one or more child nodes.
- A leaf node can connect only with its parent node.
Specify the ER node options (optional)
ATS directory
- 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: 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:
- To generate text files that ER can process during a repair operation, select Text.
- To generate XML files that you can use if you write your own custom repair scripts, select XML.
- To generate text files and XML files, select Both.
Idle timeout
Set the number of minutes that the connection between the new node and the other servers in the ER domain can be idle before the new node disconnects.
Select On and enter the time in minutes, or select Off for no timeout.
Entering 0 (zero) minutes is the same as selecting Off.