10 Configuring Oracle Connection Manager

10.1.1 Configuring the cman.ora file for the Oracle Connection Manager Host

You configure the computer that hosts Oracle Connection Manager by setting parameters in the cman.ora file. This file resides on the computer that hosts Oracle Connection Manager, and is located in the ORACLE_HOME/network/admin directory. Oracle Connection Manager will not start if the cman.ora file does not exist. This file includes the following components:

• Listening endpoint

• Access control rule list

• Parameter list

Each Oracle Connection Manager configuration is encapsulated within a single name-value (NV) string, which consists of the preceding components.

One computer can host any number of Oracle Connection Managers, each with its own entry in the cman.ora file. When defining more than one Oracle Connection Manager in the file, you can assign a default by giving only one a fully qualified host name.

You make changes to the cman.ora file manually. You can specify multiple rules for both client and Oracle Connection Manager Control utility (CMCTL) connections. The following guidelines apply when making changes:

• You must enter at least one rule for client connections and one rule for CMCTL connections. Omitting a rule results in the rejection of all connections for the rule type omitted.

• Oracle Connection Manager does not support wildcards for partial IP addresses. If you use a wildcard, then use it in place of a full IP address. The IP address of the client may be, for example, (SRC=*).

• Oracle Connection Manager supports only the /nn notation for subnet addresses. In Example 10-1, in the first rule, /27 represents a subnet mask that comprises 27 left-most bits. Only the first 27 bits in the client's IP address are compared with the IP address in the rule.

To set parameters in the cman.ora file, do the following:

1. Navigate to the cman.ora file in the ORACLE_HOME/network/admin directory.

2. Open the cman.ora file with a text editor.

   Example 10-1 shows a cman.ora file that contains a configuration entry for an Oracle Connection Manager called CMAN1.

   Example 10-1 Sample cman.ora File

   CMAN1=
     (CONFIGURATION=
       (ADDRESS=(PROTOCOL=tcp)(HOST=proxysvr)(PORT=1521))
       (RULE_LIST=
         (RULE=(SRC=192.168.2.32/27)(DST=sales-server)(SRV=*)(ACT=accept)
           (ACTION_LIST=(AUT=on)(MCT=120)(MIT=30)))
         (RULE=(SRC=192.168.2.32)(DST=proxysvr)(SRV=cmon)(ACT=accept)))
       (PARAMETER_LIST=
         (MAX_GATEWAY_PROCESSES=8)
         (MIN_GATEWAY_PROCESSSES=3)))
          
   

3. Configure the listening endpoint (ADDRESS).

   The listening endpoint specifies the protocol address for the Oracle Connection Manager listener. CMON, the Oracle Connection Manager monitoring process, uses this address to register information about gateway processes with the listener. The database uses the address to register service information at the Oracle Connection Manager node.

   The Oracle Connection Manager listener always listens on the TCP/IP protocol.

   (ADDRESS=(PROTOCOL=tcp)(HOST=proxysvr)(PORT=1521))
   

   Note:

   Oracle Connection Manager can connect to the database using protocols such as TCP/IP (version 4 and version 6). The protocol TCPS is not supported.

4. Configure the access control rule list (RULE_LIST).

   The access control rule list specifies which connections are accepted, rejected, or dropped by the listener. Example 10-1 shows the following rules:

   • In the first rule in the example, the following parameters are set:

     • src=192.168.2.32/27 is for client connections. It designates the IP address of the client, or source.

     • DST=sales-server designates the destination host name. The parameter ACT specifies the action, that is, accept, reject, or drop. The parameter ACTION_LIST sets attributes for a connection if it is accepted, enabling you to override default parameter settings on a connection-by-connection basis.

   • In the second rule, the following parameters are set:

     • SRC=192.168.2.32 and DST=proxysvr represent the same server, indicating that Oracle Connection Manager and CMCTL must reside on the same computer.

     See Also:

     "Enabling Access Control"

5. Configure the parameter list (PARAMETER_LIST).

   The parameter list sets attributes for an Oracle Connection Manager. Parameters take the following forms:

   • If global, then it applies to all Oracle Connection Manager connections unless a rule-level parameter overrides it. To change a global parameter default setting, enter it into the PARAMETER_LIST with an allowable value.

   • If a rule-level parameter is enabled in the ACTION_LIST section of the RULE_LIST, then it applies only to connections specified by the rule. It overrides its global counterpart.

(RULE_LIST=
  (RULE=(SRC=client1-pc)(DST=sales-server)(SRV=sales.us.example.com)(ACT=reject))
  (RULE=(SRC=192.168.2.45)(DST=192.168.2.200)(SRV=db1)(ACT=accept)))

10.1.2 Configuring Clients for Oracle Connection Manager

To route clients to the database server through Oracle Connection Manager, configure the tnsnames.ora file with a connect descriptor that specifies the protocol address of Oracle Connection Manager. This address enables clients to connect to the Oracle Connection Manager computer. The connect descriptor looks similar to the following:

sales=
  (DESCRIPTION=
    (ADDRESS=
      (PROTOCOL=tcp)
      (HOST=cman-pc)
      (PORT=1521))
    (CONNECT_DATA=
      (SERVICE_NAME=example.com)))

To configure a protocol address for Oracle Connection Manager, do the following:

1. Start Oracle Net Manager.

   See Also:

   "Using Oracle Net Manager to Configure Oracle Net Services"

2. In the navigator pane, select Service Naming from Directory or Local menus.

3. Click the plus sign (+) on the toolbar, or select Create from the Edit menu.

   The Welcome page of the Net Service Name wizard appears.

4. Enter a name in the Net Service Name field.

5. Click Next.

   The Protocol page appears.

6. Select the TCP/IP protocol for Oracle Connection Manager.

7. Click Next.

   The Protocol Settings page appears.

8. Specify the Oracle Connection Manager port and protocol. The default port number for Oracle Connection Manager is 1521, and the protocol is TCP/IP.

   See Also:

   Oracle Database Net Services Reference for protocol parameter settings

9. Click Next.

   The Service page appears.

10. Enter a service name in the Service Name field, and then select the connection type.

    See Also:

    "About Connect Descriptors" for additional information about setting the service name string

11. Click Next.

    Note:

    Do not click Test, because a connection cannot be tested at this point.

12. Click Finish to save your configuration and dismiss the Net Service Name wizard.

    The new net service name and the Oracle Connection Manager protocol address is added to the Service Naming folder.

10.1.3 Configuring the Oracle Database Server for Oracle Connection Manager

Configuring the database server is a two-part process that involves registering database information remotely with Oracle Connection Manager and, optionally, configuring the server for multiplexing.

This section contains the following topics:

• Configuring Service Registration

• Enabling Session Multiplexing

DISPATCHERS="(PROTOCOL=tcp)(MULTIPLEX=on)"