Configuring Oracle Connection Manager on an Amazon EC2 instance - Amazon Relational Database Service

Configuring Oracle Connection Manager on an Amazon EC2 instance

Oracle Connection Manager (CMAN) is a proxy server that forwards connection requests to database servers or other proxy servers. You can use CMAN to configure the following:

Access control

You can create rules that filter out user-specified client requests and accept others.

Session multiplexing

You can funnel multiple client sessions through a network connection to a shared server destination.

Typically, CMAN resides on a host separate from the database server and client hosts. For more information, see Configuring Oracle Connection Manager in the Oracle Database documentation.

Supported versions and licensing options for CMAN

CMAN supports the Enterprise Edition of all versions of Oracle Database that Amazon RDS supports. For more information, see Oracle versions on Amazon RDS.

You can install Oracle Connection Manager on a separate host from the host where Oracle Database is installed. You don't need a separate license for the host that runs CMAN.

Requirements and limitations for CMAN

To provide a fully managed experience, Amazon RDS restricts access to the operating system. You can't modify database parameters that require operating system access. Thus, Amazon RDS doesn't support features of CMAN that require you to log in to the operating system.

Configuring CMAN

When you configure CMAN, you perform most of the work outside of your RDS for Oracle database.

Step 1: Configure CMAN on an Amazon EC2 instance in the same VPC as the RDS for Oracle instance

To learn how to set up CMAN, follow the detailed instructions in the blog post Configuring and using Oracle Connection Manager on Amazon EC2 for Amazon RDS for Oracle.

Step 2: Configure database parameters for CMAN

For CMAN features such as Traffic Director Mode and session multiplexing, set REMOTE_LISTENER parameter to the address of CMAN instance in a DB parameter group. Consider the following scenario:

  • The CMAN instance resides on a host with IP address 10.0.159.100 and uses port 1521.

  • The databases orcla, orclb, and orclc reside on separate RDS for Oracle DB instances.

The following table shows how to set the REMOTE_LISTENER value. The LOCAL_LISTENER value is set automatically by Amazon RDS.

DB instance name DB instance IP Local listener value (set automatically) Remote listener value (set by user)
orcla 10.0.159.200
( address= (protocol=tcp) (host=10.0.159.200) (port=1521) )
10.0.159.100:1521
orclb 10.0.159.300
( address= (protocol=tcp) (host=10.0.159.300) (port=1521) )
10.0.159.100:1521
orclc 10.0.159.400
( address= (protocol=tcp) (host=10.0.159.400) (port=1521) )
10.0.159.100:1521

Step 3: Associate your DB instance with the parameter group

Create or modify your DB instance to use the parameter group that you configured in Step 2: Configure database parameters for CMAN. For more information, see Associating a DB parameter group with a DB instance.