Creating Connection Manager configuration files

To configure a Connection Manager, you must create a configuration file, and then load the configuration file by running the oncmsm utility.
A Connection Manager configuration file consists of two parts:
  • The header, which contains Connection Manager parameters that are specific to the Connection Manager.
  • The body, which consists of one or more connection unit sections that contain parameters and attributes that are specific to the defined connection units.

The following steps apply to all connection-unit types:

  1. Create an ASCII text file in the $INFORMIXDIR/etc directory of the host the Connection Manager is installed on.
  2. On the first line of the file, specify the NAME parameter, followed by a name for the Connection Manager. Connection Manager names must be unique in the domain of the connection units that are managed. For example:
    NAME my_connection_manager_1
  3. Specify optional header parameters. For example:
    NAME my_connection_manager_1
    LOG 1
    LOGFILE $INFORMIXDIR/tmp/my_cm_1.log
  4. Create the body of the configuration file by specifying at least one connection unit type followed by the name of the connection unit, and then opening and closing braces. For example:
    NAME my_connection_manager_1
    LOG 1
    LOGFILE $INFORMIXDIR/tmp/my_cm_1.log
    
    CLUSTER my_cluster
    {
    }
  5. Set the connection unit's INFORMIXSERVER parameter to the sqlhosts file entries for connection-unit participants. For example:
    NAME my_connection_manager_1
    LOG 1
    LOGFILE $INFORMIXDIR/tmp/my_cm_1.log
    
    CLUSTER my_cluster
    {
        INFORMIXSERVER group_name
    }
  6. If the Connection Manager manages connection requests, specify SLA parameters, SLA names, and DBSERVER attributes. For example:
    NAME my_connection_manager_1
    LOG 1
    LOGFILE $INFORMIXDIR/tmp/my_cm_1.log
    
    CLUSTER my_cluster
    {
       INFORMIXSERVER group_name
       SLA sla_1 DBSERVERS=PRI
       SLA sla_2 DBSERVERS=HDR,SDS,RSS
    }
  7. Specify the FOC parameter and PRIORITY attribute. If the Connection Manager manages failover, specify the ORDER attribute, as well. For example:
    NAME my_connection_manager_1
    LOG 1
    LOGFILE $INFORMIXDIR/tmp/my_cm_1.log
    
    CLUSTER my_cluster
    {
       INFORMIXSERVER group_name
       SLA sla_1 DBSERVERS=PRI
       SLA sla_2 DBSERVERS=HDR,SDS,RSS
       FOC ORDER=ENABLED \
           PRIORITY=1
    }
  8. Specify optional SLA parameter attributes. For example:
    NAME my_connection_manager_1
    LOG 1
    LOGFILE $INFORMIXDIR/tmp/my_cm_1.log
    
    CLUSTER my_cluster
    {
       INFORMIXSERVER group_name
       SLA sla_1 DBSERVERS=PRI
       SLA sla_2 DBSERVERS=(HDR,SDS,RSS) \
                 POLICY=ROUNDROBIN
       FOC ORDER=ENABLED \
           PRIORITY=1
    }
  9. If the Connection Manager manages more than one connection unit, add the other connection units to the body of the configuration file. For example:
    NAME my_connection_manager_1
    LOG 1
    LOGFILE $INFORMIXDIR/tmp/my_cm_1.log
    
    CLUSTER my_cluster
    {
       INFORMIXSERVER group_name
       SLA sla_1 DBSERVERS=PRI
       SLA sla_2 DBSERVERS=(HDR,SDS,RSS) \
                 POLICY=ROUNDROBIN
       FOC ORDER=ENABLED \
           PRIORITY=1
    }
    
    CLUSTER my_cluster_2
    {
       INFORMIXSERVER group_name_2
       SLA sla_3 DBSERVERS=PRI
       SLA sla_4 DBSERVERS=(HDR,SDS) \
                 POLICY=ROUNDROBIN
       FOC ORDER=ENABLED \
           PRIORITY=1
    }

Copyright© 2019 HCL Technologies Limited