10.1.6 Configuring the Oracle Database Server for Oracle Connection Manager

Configuring the database server involves registering database information remotely with Oracle Connection Manager and, optionally, configuring the server for multiplexing.

Note:

If the database that you want to register with Oracle Connection Manager is located on a remote node, then you must configure the cman.ora parameter VALID_NODE_CHECKING_REGISTRATION to allow remote registration.

• Configuring Service Registration for Use with Oracle Connection Manager
  To enable the database server to communicate with Oracle Connection Manager, the tnsnames.ora file must include the service name entry, and the initialization parameter file (init.ora) must contain a descriptor that specifies the listening address of Oracle Connection Manager.
• Enabling Session Multiplexing for Oracle Connection Manager
  To enable Oracle Connection Manager to take advantage of session multiplexing, set the DISPATCHERS parameter in the initialization parameter file (init.ora) with the PROTOCOL and MULTIPLEX attributes.

10.1.6.1 Configuring Service Registration for Use with Oracle Connection Manager

To enable the database server to communicate with Oracle Connection Manager, the tnsnames.ora file must include the service name entry, and the initialization parameter file (init.ora) must contain a descriptor that specifies the listening address of Oracle Connection Manager.

The following procedure describes how to configure service registration:

1. Resolve the Oracle Connection Manager alias to a service name entry in the tnsnames.ora file as follows:

   cman_listener_address =
     (DESCRIPTION=
       (ADDRESS_LIST=
         (ADDRESS=(PROTOCL=tcp) (HOST=proxy_server_name)( PORT=1521))))
   

   For example, the alias listener_cman would be resolved to the following entry in the tnsnames.ora file:

   listener_cman=
    (DESCRIPTION=
     (ADDRESS_LIST=
      (ADDRESS=(PROTOCOL=tcp)(HOST=proxyserver1)(PORT=1521))))
   

2. Specify an alias for Oracle Connection Manager in the init.ora file as follows. This alias is the one specified in the tnsnames.ora file in step 1.

   REMOTE_LISTENER=cman_listener_address
   

   The alias must be specified because this address is TCP, port 1521 but it is not the default local listening address of TCP, port 1521 of the database server.

   For example, the alias for the Oracle Connection Manager listener running on host, proxyserver1, specified in step 1, might look like the following in the init.ora file:

   REMOTE_LISTENER=listener_cman
   

3. Configure REGISTRATION_INVITED_NODES in cman.ora if the database resides on a remote node. For example:

   (registration_invited_nodes=sales.us.example.com,10.245.129.60)

4. After the initialization parameter file is configured with the alias of Oracle Connection Manager, the Listener Registration (LREG) process can register database information with the Oracle Connection Manager listener. Use the following command to register the change:

   SQL> ALTER SYSTEM REGISTER

10.1.6.2 Enabling Session Multiplexing for Oracle Connection Manager

To enable Oracle Connection Manager to take advantage of session multiplexing, set the DISPATCHERS parameter in the initialization parameter file (init.ora) with the PROTOCOL and MULTIPLEX attributes.

For example:

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

The following table lists the parameters to set different levels of multiplexing:

Table 10-2 Session Multiplexing Parameters

Attribute	Description
PROTOCOL	The network protocol for which the dispatcher generates a listening endpoint.
MULTIPLEX	This parameter is used to enable session multiplexing, as follows: If 1, on, yes, true, or both is specified, then multiplexing is enabled for both incoming and outgoing network sessions. If in is specified, then multiplexing is enabled for incoming network sessions from the client. If out is specified, then multiplexing is enabled for outgoing network sessions. If 0, off, no, or false is specified, then multiplexing is disabled for both incoming and outgoing network sessions.