Grid
Use these pages to view information about the servers in a grid and the service level agreements associated with the grid.
Prerequisite: 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 or
later.
A grid is one type of connection unit that is managed by a Connection Manager.
- Server List
- Use this page to view information about servers
in the connection unit.
- Server Group
- The name of the database server group.
- Type
- The type of the server in the grid.
- Source
- A server from which an authorized user can run grid commands. Grid commands are propagated to all other servers in the grid.
- Member
- A server in the grid that is not a source server.
- Server Group Members
- The servers that are members of the database server group.
- SLA
- Use this page to view information about the service
level agreements (SLAs).
- SLA
- The name of the SLA. An SLA is the contract between specified client applications and their service providers, in this case, the Informix database servers. Based on service level agreements, the Connection Manager connects the client applications to the appropriate servers.
- Servers
- The servers in the SLA listed in order of connection preference with the first server listed having the highest connection priority. For example, the list g_one,g_two,g_three indicates that the client is connected first to server g_one. If server g_one is not available, the client is connected to server g_two. If server g_two is not available, the client is connected to server g_three. When a group of servers is in parenthesis, all the servers have the same connection priority. For example, the following list gives each server equal priority: (g_one,g_two,g_three).
- Service Port
- The port number associated with the SLA.
- Mode
- The mode that the Connection Manager uses to redirect client requests.
- Redirect
- The Connection Manager redirects client connection requests to the appropriate server. The Connection Manager returns the appropriate server node, IP address, and port number to the client application (depending on the SLA definition). The client application connects to the server using the IP address and port number that the Connection Manager provides.
- Proxy
- The Connection Manager functions as a proxy server when clients connect to database servers from outside a firewall. The Connection Manager actively routes all client communications to and from the database servers.
- Latency, Failure, and Workload
- The weight of each of the factors in the
connection policy: the lowest latency, the fewest apply failures,
and the least workload. The default is an equal weight for each factor.
The Connection Manager determines which server to connect with a client
application based on these factors when the quality of data is monitored.
When the quality of data is not monitored, the Connection Manager
routes client connections based on the workload only. The option to monitor the quality of data is enabled
on the page with the Modify Server action.
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 or Replicates page with the Check or Sync Data action.