Defining sqlhosts information for connection management

You must define sqlhosts network-connectivity information for client applications that connect to Connection Managers, Connection Managers that connect to database servers, and database servers that are part of a Connection Manager connection unit.

If Connection Managers or clients are installed on hosts where database servers are not installed, you must create a sqlhosts file on each host.

Entries in an sqlhosts file can specify connection information for the following connection-unit components:
  • Database servers
  • Aliases for database servers that are using secure ports
  • Connection Manager service-level agreements (SLAs)
  • Groups that can contain database servers, database-server aliases, or SLAs.

All database servers that a Connection Manager connects to must be listed in the sqlhosts file that the Connection Manager uses. If the Connection Manager is monitoring a high-availability cluster, the sqlhosts file the Connection Manager uses must contain entries for all cluster servers.

  1. Create entries in each database server's host sqlhosts file.
    You can modify one sqlhosts file, and then distribute it to the hosts of other database servers.
  2. Create entries in each Connection Manager's host sqlhosts file.
    You can create one sqlhosts file, and then distribute it to the hosts of other Connection Managers.
  3. Create entries in each client application's host sqlhosts file.
    You can create one sqlhosts file, and then distribute it to the hosts of other client applications.
  4. If a host has multiple database servers that are installed on it, if the sqlhosts file is in a directory other than $INFORMIXDIR/etc, or if you are using a network-connectivity file other than $INFORMIXDIR/etc/sqlhosts, set the host's INFORMIXSQLHOSTS environment variable to the location of the sqlhosts file.
If sqlhosts file entries use the s=6 option to define secure ports, use the information in the sqlhosts file to create a password file.