Add rule to oracle connection manager

Oracle 11.2.0.4 on Linux.
I need to add a rule in my oracle connection manager.
Now I do not use rule:
(rule_list=
(rule=
(src=*)(dst=*)(srv=*)(act=accept)
(action_list=(aut=off)(moct=0)(mct=0)(mit=0)(conn_stats=on))
I can add a rule like this:
(rule_list=
(rule=
(src=*)(dst=dbxx-int.dbc.cineca.it)(srv=service_name1_ext)(act=accept)
(src=*)(dst=dbxx-int.dbc.cineca.it)(srv=service_name2_ext)(act=accept)
(action_list=(aut=off)(moct=0)(mct=0)(mit=0)(conn_stats=on))
Since my two service_name end with ext can I use a single rule like this:
I can add a rule like this:
(rule_list=
(rule=
(src=*)(dst=dbxx-int.dbc.cineca.it)(srv=*_ext)(act=accept)
(action_list=(aut=off)(moct=0)(mct=0)(mit=0)(conn_stats=on))

this forum is commonly used to connect from Oracle databases to foreign databases using Oracle's gateway product. A connection manager can't be used here. You might ask that question in the generic database forum:
General Questions
but in my opinion you should log a service request to get assiatance.
- Klaus

Similar Messages

Oracle Connection Manager

Hi,
i'm having a problem configuring Oracle Connection Manager. It does start the instance of connection manager
Summary of my environment is
10g Application server and infrastructure machine OS: Windows 2003
9i Database Server: Windows 2003
Client : Java Applet
JDBC driver type : THIN
Installed: 10g Infra first and then 10g midiier(portal and wireless) in seperate oracle homes on the same machine. Eveything is up and running as i was able to login seperately in infra and midtier enterprise managers.
Final Goal : Trying to connect to an Oracle 9i database on a differnt machine than the appserver using an applet, thin drivers and Oracle Connection Manager
Problem : Connection manager instance not started however cmanADMIn service started.
CMCTL:CMAN_oracle9-app> administer cmanOracleAS
Current instance cmanOracleAS is not yet started
Connections refer to (address=(protocol=tcp)(host=10.10.1.101)(port=1610)).
The command completed successfully.
CMCTL:cmanOracleAS> startup
Service Oracleoracle_infraCMAdmincmanOracleAS already running.
TNS-04012: Unable to start Oracle Connection Manager instance.
CMCTL:cmanOracleAS>
Steps done to configure Oracle Connection manager
1. Copied 4 .exe (CMADMIN, CMCTL,CMGW,CMMIGR) files to bin folder of Appserver or midtier's main ORACLE_HOME/BIN folder.
2) created a cman.ora file and copied in appservers /NETWORK/ADMIN directory
3) On cammand prompt type CMCTL...ADMINISTER cman_OracleAS where cman_OracleAS is the name of cman instance used in cman.ora file.
My cman.ora file is as follows
# Copyright (c) 2001,2002, Oracle Corporation. All rights reserved.
# NAME
# cman.ora
# DESCRIPTION
# Sample CMAN configuration file that the user can modify for their
# own use.
# NOTES
# 1. Change <fqhost> to your fully qualified hostname
# 2. Change <lsnport> to the listening port number
# 3. Change <logdir> and <trcdir> to your log and trace directories
# MODIFIED (MM/DD/YYYY)
# asankrut 10/05/2002 - Added Rule List Specifications
# asankrut 06/11/2002 - Modified to add new parameters; added comments.
# asankrut 12/31/2001 - Creation.
# CMAN Alias
cmanOracleAS =
(configuration=
# Listening address of the cman
(address=(protocol=tcp)(host=appserver_name)(port=1610))
# Configuration parameters of this CMAN
(parameter_list =
# Need authentication for connection?
# Valid values: boolean values for on/off
(aso_authentication_filter=off)
# Connection statistics need to be collected?
# Valid values: boolean values for on/off
(connection_statistics=yes)
# Log files would be created in the directory specified here
(log_directory=D:\GAV\OracleAS10\NETWORK\log)
# Logging would be in done at this level
# Valid values: OFF | USER | ADMIN | SUPPORT
(log_level=ADMIN)
# Maximum number of connections per gateway
# Valid values: Any positive number (Practically limited by few 1000s)
(max_connections=256)
# Idle timeout value in seconds
# Valid values: Any positive number
(idle_timeout=0)
# Inbound connect timeout in seconds
# Valid values: Any positive number
(inbound_connect_timeout=0)
# Session timout in seconds
# Valid values: Any positive number
(session_timeout=0)
# Outbound connect timeout in seconds
# Valid values: Any positive number
(outbound_connect_timeout=0)
# Maximum number of gateways that can be started
# Valid values: Any positive number (Practically limited by
# system resources)
(max_gateway_processes=16)
# Minimum number of gateways that must be present at any time
# Valid values: Any positive number (Practically limited by
# system resources)
# max_gateway_processes > min_gateway_processes
(min_gateway_processes=2)
# Remote administration allowed?
# Valid Values: Boolean values for on/off
(remote_admin=on)
# Trace files would be created in the directory specified here
(trace_directory=D:\GAV\OracleAS10\NETWORK\trace)
# Trace done at this level
# Valid values: OFF | USER | ADMIN | SUPPORT
(trace_level=ADMIN)
# Is timestamp needed with tracing?
# Valid values: Boolean values for on/off
(trace_timestamp=on)
# Length of the trace file in kB
# Valid values: Any positive number (Limited practically)
(trace_filelen=1000)
# No. of trace files to be created when using cyclic tracing
# Valid values: Any positive number
(trace_fileno=1)
# Maximum number of CMCTL sessions that can exist simultaneously
# Valid values: Any positive number
(max_cmctl_sessions=4)
# Event logging: event groups that need to be logged
(event_group=init_and_term,memory_ops)
# Rule list
# Rule Specification:
# src = Source of connection; '*' for 'ANY'
# dst = Destination of connection; '*' for 'ANY'
# srv = Service of connection; '*' for 'ANY'
# act = Action: 'accept', 'reject' or 'drop'
# Action List Specification:
# aut = aso_authentication_filter
# moct = outbound_connect_timeout
# mct = session_timeout
# mit = idle_timeout
# conn_stats = connect_statistics
(rule_list=
(rule=
(src=*)(dst=databaseIP)(srv=*)(act=accept)
(action_list=(aut=off)(moct=0)(mct=0)(mit=0)(conn_stats=on))
(rule=
(src=appserverIP)(dst=127.0.0.1)(srv=cmon)(act=accept)
Please help
Thanks
Atul Jain
[email protected]

Forgot to mention that
cmanOracleAS.log file i.e connection manger log file is as follows.
It says does not currently know of service 'cmon' but i have the rule which
allows cmctl to conect locally with 127.0.0.1 .
TNSLSNR for 32-bit Windows: Version 10.1.0.3.0 - Production on 17-MAR-2005
12:17:53
Copyright (c) 1991, 2004, Oracle. All rights reserved.
System parameter file is D:\GAV\oracle_infra\network\admin\sqlnet.ora
Command-line specified parameter file is D:\GAV\oracle_infra\network\admin\
cman.ora
Log messages written to D:\GAV\OracleAS10\NETWORK\log\cmanoracleas1_924.log
Trace information written to D:\GAV\OracleAS10\NETWORK\trace\
cmanoracleas1_924.trc
Trace level is currently 6
Started with pid=332
Running in PROXY mode
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.10.1.101)
(PORT=1610)))
TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
17-MAR-2005 12:22:07 * (connect_data=(service_name=cmon)(pid=ctl)) *
(ADDRESS=(PROTOCOL=tcp)(HOST=10.10.1.101)(PORT=4589)) * establish * cmon *
12514
TNS-12514: TNS:listener does not currently know of service requested in
connect descriptor
17-MAR-2005 12:22:10 * (connect_data=(service_name=cmon)(pid=ctl)) *
(ADDRESS=(PROTOCOL=tcp)(HOST=10.10.1.101)(PORT=4596)) * establish * cmon *
12514
TNS-12514: TNS:listener does not currently know of service requested in
connect descriptor
17-MAR-2005 12:23:31 * (connect_data=(service_name=cmon)(pid=ctl)) *
(ADDRESS=(PROTOCOL=tcp)(HOST=10.10.1.101)(PORT=4782)) * establish * cmon *
12514
Thanks
Atul jain

TNS-04012: Unable to start Oracle Connection Manager instance.

Hi,
I've tried to configure Connection Manager but i fails on:
TNS-04012: Unable to start Oracle Connection Manager instance
This is my configuration (I've removed as much as possible to remove possible errors):
CMAN1=(CONFIGURATION=
(ADDRESS=(PROTOCOL=tcp)(HOST=<hostname>)(PORT=1522))
(RULE_LIST=
(RULE=(SRC=*)(DST=<IP>)(SRV=*)(ACT=accept))))
CMCTL> administer CMAN1
Current instance CMAN1 is not yet started
Connections refer to (ADDRESS=(PROTOCOL=tcp)(HOST=<hostname>)(PORT=1522)).
The command completed successfully.
CMCTL:CMAN1> startup
TNS-04012: Unable to start Oracle Connection Manager instance.I've reviewed following notes without getting any closer (298916.1 and 733421.1)
I can't see any errors in any of the following possible issues:
* The max_connections value must not exceed 1024. Maximum acceptable value is 1024
* The max_gateway_processes value must not exceed 64. Maximum acceptable value is 64
* The trace_directory and log_directory values must be valid
* The trace_level and log_level values do not support numeric values 6,10 and 16
* Duplicate sections
* Misspelled parameter names or parameter values
* Host values that are not resolvable
* Rule list must allow the local address of the machine where cman is installed
* A specfic address in SRC or DST for a rule in the rule list must be resolvable(Try ip address range as a workaround and see the enhancement request 6125025)
* Windows: Ensure the ORA_DBA group is present and O/S user starting CMAN is in the group
* Windows: Ensure any firewall is not blocking Oracle from using Network
All help are appreciated!
Cheers

933746 wrote:
Osama_mustafa wrote:
Refer to
Troubleshooting Guide: TNS-04012: Unable to Start Oracle Connection Manager Instance [ID 733421.1]Hi,
As I've stated in my post I've reviewed this post without any help.I would suggest you read the provided doc [ 733421.1] more thoroughly.... the answer is there.

Certificates in lieu of Oracle connection Manager for our Applets -- Help!!

I support an application named IDEA out of New York. The IDEA application is an INTRANET application for use within our company Firewall.
Currently, the IDEA application's front end resides on a Windows 2000 Server running IIS 5 and JRun 3.0. The back-end runs on Oracle 8.1.7 database on a UNIX Database Hosting Utility (DHU). Our applets communicate with the back-end database using Oracle Connection Manager that is installed on the Web Host.
We are trying to migrate to the DWeb environment (Linux cluster). The linux cluster is running Apache Tomcat. We have been told that installing Oracle connection manager is not a viable solution (our company does not support it). Because of this our applets cannot communicate with our database. Below is a brief description of this limitation and also the work-around.
====================================================================================================================================================
Connecting to the Database through the Applet
The most common task of an applet using the JDBC driver is to connect to and query a database. Because of applet security restrictions, unless particular steps are taken an applet can open TCP/IP sockets only to the host from which it was downloaded (this is the host on which the Web server is running). This means that without these steps, your applet can connect only to a database that is running on the same host as the Web server.
If your database and Web server are running on the same host, then there is no issue and no special steps are required. You can connect to the database as you would from an application.
As with connecting from an application, there are two ways in which you can specify the connection information to the driver. You can provide it in the form of host:port:sid or in the form of a TNS keyword-value syntax.
For example, if the database to which you want to connect resides on host prodHost, at port 1521, and SID ORCL, and you want to connect with user name scott with password tiger, then use either of the two following connect strings:
using host:port:sid syntax:
String connString="jdbc:oracle:thin:@prodHost:1521:ORCL";
conn = DriverManager.getConnection(connString, "scott", "tiger");
using TNS keyword-value syntax:
String connString = "jdbc:oracle:thin:@(description=(address_list=
(address=(protocol=tcp)(port=1521)(host=prodHost)))
(connect_data=(sid=ORCL)))";
conn = DriverManager.getConnection(connString, "scott", "tiger");
If you use the TNS keyword-value pair to specify the connection information to the JDBC Thin driver, then you must declare the protocol as TCP.
However, a Web server and an Oracle database server both require many resources; you seldom find both servers running on the same machine. Usually, your applet connects to a database on a host other than the one on which the Web server runs. There are two possible ways in which you can work around the security restriction:
You can connect to the database by using the Oracle8 Connection Manager.
or:
You can use a signed applet to connect to the database directly.
These options are discussed in the next section, "Connecting to a Database on a Different Host Than the Web Server".
Connecting to a Database on a Different Host Than the Web Server
If you are connecting to a database on a host other than the one on which the Web server is running, then you must overcome applet security restrictions. You can do this by using either the Oracle8 Connection Manager or signed applets. ====================================================================================================================================================
It was suggested that we implement signed applets (it is our only alternative at this time). This is where, hopefully, you can help me. We are unfamiliar with using certificates and signing applets. We need to obtain certificates that will allow our applets to connect to our oracle database on the DHU. What kind of certificates do we use? Are their coding examples of how to use these certificates? We have a CA within our company but they cannot tell us what kind of certificates we need. How many certificates do we need? Do we install any certificates on the backend database server? Any information would be greatly appreciated. We are basically trying to get our applet to work outside the sandbox by establishing a connection to the database server.Thanks in advance for your time.

or:
You can use a signed applet to connect to the database directly.
These options are discussed in the next section, "Connecting to a Database on a Different Host Than the Web Server".
If you want to connect to the database from the applet there is a third option.
Since this is an intranet application you have control over the desktops using this
application. In our company the jre ignores signed applets (as it should) because
it gives control to the user to run potentially harmfull applets from the Internet.
The way to dish out special privileges to applets is the policy, put a policy file on
you intranet and have the jre use it by specifying its URL in the java.security.
Here is some more info about security configuration of the jre:
http://forum.java.sun.com/thread.jspa?threadID=646161&tstart=45
reply 3
We use Oracle jinitiator to run Oracle forms but I am not involved in that project
and do not know a lot about it. It does perform quite good though.

Certificates in lieu of Oracle connection Manager for our Applets

I support an application named IDEA out of New York. The IDEA application is an INTRANET application for use within our company Firewall.
Currently, the IDEA application's front end resides on a Windows 2000 Server running IIS 5 and JRun 3.0. The back-end runs on Oracle 8.1.7 database on a UNIX Database Hosting Utility (DHU). Our applets communicate with the back-end database using Oracle Connection Manager that is installed on the Web Host.
We are trying to migrate to the DWeb environment (Linux cluster). The linux cluster is running Apache Tomcat. We have been told that installing Oracle connection manager is not a viable solution (our company does not support it). Because of this our applets cannot communicate with our database. Below is a brief description of this limitation and also the work-around.
====================================================================================================================================================
[i][i][i]Connecting to the Database through the Applet
The most common task of an applet using the JDBC driver is to connect to and query a database. Because of applet security restrictions, unless particular steps are taken an applet can open TCP/IP sockets only to the host from which it was downloaded (this is the host on which the Web server is running). This means that without these steps, your applet can connect only to a database that is running on the same host as the Web server.
If your database and Web server are running on the same host, then there is no issue and no special steps are required. You can connect to the database as you would from an application.
As with connecting from an application, there are two ways in which you can specify the connection information to the driver. You can provide it in the form of host:port:sid or in the form of a TNS keyword-value syntax.
For example, if the database to which you want to connect resides on host prodHost, at port 1521, and SID ORCL, and you want to connect with user name scott with password tiger, then use either of the two following connect strings:
using host:port:sid syntax:
String connString="jdbc:oracle:thin:@prodHost:1521:ORCL";
conn = DriverManager.getConnection(connString, "scott", "tiger");
using TNS keyword-value syntax:
String connString = "jdbc:oracle:thin:@(description=(address_list=
(address=(protocol=tcp)(port=1521)(host=prodHost)))
(connect_data=(sid=ORCL)))";
conn = DriverManager.getConnection(connString, "scott", "tiger");
If you use the TNS keyword-value pair to specify the connection information to the JDBC Thin driver, then you must declare the protocol as TCP.
However, a Web server and an Oracle database server both require many resources; you seldom find both servers running on the same machine. Usually, your applet connects to a database on a host other than the one on which the Web server runs. There are two possible ways in which you can work around the security restriction:
You can connect to the database by using the Oracle8 Connection Manager.
or:
You can use a signed applet to connect to the database directly.
These options are discussed in the next section, "Connecting to a Database on a Different Host Than the Web Server".
Connecting to a Database on a Different Host Than the Web Server
If you are connecting to a database on a host other than the one on which the Web server is running, then you must overcome applet security restrictions. You can do this by using either the Oracle8 Connection Manager or signed applets. ====================================================================================================================================================
It was suggested that we implement signed applets (it is our only alternative at this time). This is where, hopefully, you can help me. We are unfamiliar with using certificates and signing applets. We need to obtain certificates that will allow our applets to connect to our oracle database on the DHU. What kind of certificates do we use? Are their coding examples of how to use these certificates? We have a CA within our company but they cannot tell us what kind of certificates we need. How many certificates do we need? Do we install any certificates on the backend database server? Any information would be greatly appreciated. We are basically trying to get our applet to work outside the sandbox by establishing a connection to the database server.
Thanks in advance for your time.

Eston,
Have you searched SUN's java Web site? Maybe this article will help:
http://java.sun.com/developer/technicalArticles/Security/Signed/index.html
Good Luck,
Avi.

How to install oracle connection manager on solaris 10

I have installed oracle application server 10.1.2 on solaris 10. How do i install oracle connection manager utility.
My end goal is to use applets/jdbc.
Thanks

Thank you Zettabyte!!
Folks, network printers should NOT BE configured like this:
lpadmin -p somequeue -s someprinter
that creates a remote style queue and puts all the I/O and processing capability on the basic LPD listener present on network printer interfaces. This will cause problems down the road, not to mention that you cannot control access, get any logging, filter content, or control banner pages.
Network printers should use any software (or PPD file) supplied by the vendor over the basic lpadmin/netstandard config.
You can install CUPS, but Oracle won't support it until it's part of the OS (S11, apparently).
The "System Administration Guide: Solaris Printing" is highly recommended for those administering printers on Solaris.

DataDirect and Oracle Connection Manager

Quick Question - Has anyone made the Plumtree Portal running on Oracle using the built in DataDirect drivers work with an infrastructure that uses Oracle Connection Manager (OCM).
Due to security and performance reasons, using Oracle Connection Manager is needed to communicate accross firewalls.
Ive already followed up with DataDirect, they dont support it currently. Plumtree Support doesnt seem to think it will work (im guessing there right).
If anyones got any insight, it be appreciated.
-DM

please send configuration file of cman.ora, listener.ora

Monitor oracle connection manager (cman) in grid control

How to montior oracle connection manager listener/instace in Grid Control. When I installed grid agent on the box where oracle connection manager running, agent is not able to discover the oracle connection manager instance. Is it possible to montior this via Grid Control?

please send configuration file of cman.ora, listener.ora

How Oracle Connection Manager Works

as this image
http://www7.0zz0.com/2013/04/30/08/747223164.gif

So each user has a connection reserved while he/she is online. X number of online users need x number of connections. It is resource consuming. Javamail connection pool is to solve this kind of problem, I believe. No, I'm afraid that's not true.
First, the JavaMail connection pool is for IMAP connections only, and it only applies to a
single user.
IMAP connections are extremely stateful, and that state is represented in the JavaMail API.
It's extremely difficult to share a single connection between multiple users.
The simplest approach is to assume that each user has one folder open at a time, and each
open folder requires a separate connection. You should time out connections after some
short period of inactivity; typical IMAP servers will time out the connection after 30 minutes.

NET8 CONNECTION MANAGER 설치와 설정방법

제품 : SQL*NET
작성날짜 : 2003-01-15
NET8 CONNECTION MANAGER 설치와 설정방법
=======================================
Purpose
Oracle Connection Manager(v3.0.x)의 설치와 설정 방법을
알아 보고 시작시켜 봅니다.
V3.0.x은 Oracle8 Enterprise Edition에 같이 들어 있으며
Oracle8의 일부는 아닙니다.
1. 설치 방법
2. 설정 방법
3. 시작 하기 (Windows NT)
Explanation
1. 설치 방법
다음 세가지의 실행 파일이 설치 됩니다.
CMGW, CMADMIN, CMCTL (Unix 와 VMS)
CMGW80, CMADM80, CMCTL80(desktop Oracle8에서)
CMGW, CMADMIN, CMCTL(desktop Oracle8i에서)
CMGW/CMGW80
이 것은 Connection Manager의 hub와 같은 역할을 하는
gateway process입니다.
CMGW의 기능은 다음과 같습니다.
- CMADMIN를 등록합니다.
- SQL*Net 2.x와 NET 8.x에서 오는 접속 요청에 대해 대기합니다.
기본적으로 1610 port를 사용합니다.
- NET 8.x listeners에 접속 요청을 발생 시킵니다.
- client와 server사이의 data를 전달합니다.
- CMCTL/CMCTL80에 의해 발생되는 요청에 응답합니다.
CMADMIN/CMADM80
Connection Manager의 모든 관리적인 문제들을 처리하는 multi-threaded
process입니다.
SQL*Net 2.x 와 NET 8.x clients들을 위해
Oracle Names Server에 있는 주소정보를 유지하는 기능을 합니다.
- CMGW/CMGW80 등록 작업을 합니다.
- local Oracle Names Server를 찾습니다.
- 하나이상의 db instance를 서비스하는 모든 listener들을 관리합니다.
- CMGW/CMGW80 와 listener에 대한 주소 정보를 등록합니다.
- 네트워크와 Names Server의 수정된 정보를 감시합니다.
- CMCTL/CMCTL80의 요청에 응답합니다.
CMGW, CMADMIN/CMGW80, 와 CMADM80 의 서로간의 정보전달은 IPC를 통해
이루어 집니다.
CMAN은 주기적으로 Names Server의 바뀐 정보를 cache에 반영합니다.
CMCTL/CMCTL80
CMADM/CMADM80 와 CMGW/CMGW80 를 관리하는 일을 합니다.
현재 제공되는 명령은 start, stop, status, 그리고 version 입니다.
CMCTL START [CMAN | CM | ADM]
이 명령은 Connection Manager 또는 그 구성요소를 시작 시킵니다.
- 인자가 없는 경우 또는 CMAN을 준 경우는 gateway 와
administration process를 시작시킵니다.
- CM 을 주면 gateway process 만 시작됩니다.
- ADM 을 주면 administration process 만 시작됩니다.
CMCTL STOP [CM]
Connection Manager process들을 중지 시킵니다.
- 인자가 없는 경우 또는 CM 을 준 경우 gateway 와
administration process 모두를 중지시킵니다.
gateway process가 중단될 경우 administration process는 자동으로
중단됩니다.
현재 진행중인 접속이 있는 경우 CMAN 는 중지될 수 없습니다.
CMCTL STATUS [CMAN | CM | ADM]
이 명령은 Connection Manager의 요소들의 상태를 보여줍니다.
- 인자가 없거나 CMAN이나 CM일 경우 gateway process의 상태를 보여 줍니다.
- ADM은 administration process의 상태를 보여 줍니다.
CMCTL VERSION
이 명령은 control utility의 버젼을 보여 줍니다.
CMGW/CMGW80 와 CMADM/CMADM80의 버젼은 status명령으로 볼 수 있습니다.
2. 설정 방법
client들은 tnsnames.ora 이나 Oracle Names Server 가 필요합니다.
Connection Manager는 cman.ora 가 필요하며 server는 init.ora에 MTS설정이
필요합니다.
client설정
tnsnames.ora파일의 예 입니다.
EXAMPLE=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=SERVER.US.ORACLE.COM)
(PORT=1521)
(CONNECT_DATA=
(SID=ORCL)
하나의 protocol로 Connection Manager를 사용하는 tnsnames.ora파일 예입니다.
EXAMPLE_CMAN=
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=CMAN.US.ORACLE.COM)
(PORT=1610)
(ADDRESS=
(PROTOCOL=TCP)
(HOST=SERVER.US.ORACLE.COM)
(PORT=1521)
(CONNECT_DATA=
(SID=ORCL)
(SOURCE_ROUTE=YES)
ADDRESS_LIST가 path입니다.
첫번째 주소가 CMAN에 접속하는 정보이고, 두번째 주소가 서버에
접속할때 CMAN에 의해 사용되는 주소입니다.
필요하다면 ADDRESS_LIST 안에 여러개의 CMAN 의 주소를 설정할
수 있습니다. CMAN은 기본적으로 라우터처럼 동작합니다.
접속 요청을 다음 hop으로 지정합니다.
여러개의 protocol로 Connection Manager를 사용하는
tnsnames.ora파일 예입니다.
EXAMPLE_CMAN=
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=
(PROTOCOL=SPX)
(SERVICE=CMAN)
(ADDRESS=
(PROTOCOL=TCP)
(HOST=SERVER.US.ORACLE.COM)
(PORT=1521)
(CONNECT_DATA=
(SID=ORCL)
(SOURCE_ROUTE=YES)
위의 예에서 CMAN에 접속하기 위해서 client는 SPX를 사용하고
server에 접속하기 위해서 CMAN은 TCP/IP를 사용하게 됩니다.
Oracle7에서 소개된 Oracle Multi-Protocol Interchange (MPI)과
같은 기능을 합니다.
만일 서버까지 가는데 한개 이상의 router가 있는 경우
SQL*Net 2.3에서 소개된 DESCRIPTION_LIST를 사용할 수 있습니다.
다음은 DESCRIPTION_LIST를 사용한 tnsnames.ora 파일의 예 입니다.
EXAMPLE_ROUTES=
(DESCRIPTION_LIST=
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=CMAN1.US.ORACLE.COM)
(PORT=1610)
(ADDRESS=
(PROTOCOL=TCP)
(HOST=SERVER.US.ORACLE.COM)
(PORT=1521)
(CONNECT_DATA=
(SID=ORCL)
(SOURCE_ROUTE=YES)
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=CMAN2.US.ORACLE.COM)
(PORT=1610)
(ADDRESS=
(PROTOCOL=TCP)
(HOST=SERVER.US.ORACLE.COM)
(PORT=1521)
(CONNECT_DATA=
(SID=ORCL)
(SOURCE_ROUTE=YES)
만일 Oracle Names Server를 사용하면 Connection Manager는 자동으로
CMAN을 위한 주소를 Names Server에 있는 기존의 주소에 추가하게 됩니다.
SQLNET.ORA파일에 다음과 같은 parater를 설정할 수 있습니다.
USE_CMAN = [TRUE | FALSE]
- TRUE 라고 설정하면 CMAN이 무작위로 뽑은 간접적인 경로를 이용해
client를 접속시킵니다. ( 적어도 하나의 CMAN address가 있는
address list)
- TRUE 그리고 description에 간접 경로가 없는 경우에는 무작위로 뽑은
경로가 사용됩니다.
- FALSE 이거나 설정이 안된 경우 무작위로 뽑힌 경로가 사용됩니다.
Connection Manager 설정
CMAN 은 한개의 파일(CMAN.ORA)로 설정된다.
CMAN.ORA 파일은 다음 세개의 부분으로 구성된다.
1) CMAN - Connection Manager를 위한 listening주소를 포함한다.
2) CMAN_PROFILE - CMAN 설정 parameter들을 포함한다.
3) CMAN_RULES - 접속 요청에 대한 필터링에 관련된 규칙을 포함한다.
CMAN=
(ADDRESS_LIST=
(ADDRESS=
(PROTOCOL=SPX)
(SERVICE=CMAN)
(ADDRESS=
(PROTOCOL=TCP)
(HOST=CMAN.US.ORACLE.COM)
(PORT=1610)
이 CMAN의 예에서는 SPX 와 TCP/IP 두개의 주소에서 listening하고 있습니다.
CMAN 은 CMAN이 실행되는 장비에서 oracle이 지원하는 모든 protocol에 대해
listen할 수 있습니다.
CMAN_PROFILE=
(PARAMETER_LIST=
(MAXIMUM_RELAYS=64)
(LOG_LEVEL=0)
(TRACING=YES)
(RELAY_STATISTICS=YES)
(SHOW_TNS_INFO=NO)
(USE_ASYNC_CALL=YES)
(AUTHENTICATION_LEVEL=0)
각 parameter들에 대한 정의 :
MAXIMUM_RELAYS = n
- 허용되는 최대 동시 접속수
- 기본값 8
- 최대값 1024
LOG_LEVEL = n
- CMAN에 의해 수행되는 logging의 level설정
- 기본값 0 ( logging이 안됨 )
- 0에서부터 4까지의 값을 설정할 수 있음
TRACING = [YES | NO]
- YES로 설정하면 CMAN은 파일에 tracing을 한다.
- 기본값 NO
주의: trace파일을 읽기위새허는 Oracle Trace를 사용하면 됩니다.
RELAY_STATISTICS = [YES | NO]
- YES는 I/O활동에 대한 통계정보를 저장하게 합니다.
예를 들어 :
     - IN bytes 수
     - OUT bytes 수
     - IN packets 수
     - OUT packets 수
- 기본값 NO
SHOW_TNS_INFO = [YES | NO]
- Yes로 설정하면 log 파일에 TNS events를 포함하게 합니다.
- 기본값 NO
USE_ASYNC_CALL = [YES | NO]
- YES로 설정하면 CMAN 접속을 실행하고 받아들이고 대답하는 과정에서
모든 비동기적인 기능을 사용할 수 있게 합니다.
- 기본값 NO
주의: CMAN은 out-of-band breaks를 지원합니다.
CMAN은 그것을 서버로 전달합니다.
AUTHENTICATION_LEVEL = [0 | 1]
- 1로 설정하게 되면 CMAN은 Secure Network Services를 사용하지 않은
접속 요청은 거절하게 됩니다
Secure Network Services은 Advanced Networking Option의 일부입니다.
- 기본값은 0 입니다.
즉 Secure Network Services가 필요없다는 뜻입니다.
CMAN_RULES=
(RULE_LIST=
(RULE=
(SRC = shost)
(DST = dhost)
(SRV = services)
(ACT = accept | reject)
CMAN_RULES에 정의된 parameter들:
- shost 는 client에서 session을 요청한 source hostname 이거나
IP address입니다.
- dhost 는 서버쪽의 hostname 이거나 IP address 입니다.
- services 는 SID 이름입니다.
- ACT: 위 세개의 parameter들의 값을 근거로한 들어오는 접속요청에
대한 승인이나 거절입니다.
주의: wild-card는 'x'입니다. IP address (d.d.d.d)인 경우에
각 'd'는 wild-card character인 'x'로 교체될 수 있습니다.
RULE_LIST내에 여러 RULE들이 정의될 수 있습니다.
여러 rule들 중에 처음에 맞는 rule이 그 요청에 적용됩니다.
CMAN_RULES이 존재하는 경우 Connection Manager는 규칙에 허용되지 않은
것들은 모두 허락되지 않게 합니다.
만일 CMAN_RULES이 정의되지 않았다면 모든것이 허용됩니다.
Connection Manager의 제한
만일 connection path에 사용된 Connection Manager가 한개 이상이라면 (1개
이상의 hop이라면), tnsnames.ora를 직접 설정해야 하며 Oracle Names Server
를 사용할 수 없습니다.
TCP/IP network에서만 Connection Manager는 접근 통제(CMAN_RULES)를 할 수
있습니다.
Oracle Multi-Protocol Interchange (MPI) 과의 호환성
client와 server사이에 단 하나의 MPI만 있다면, MPI를
Connection Manager로 교체하십시요.
client와 server사이에 여러개의 MPI가 있다면,
tnsnames.ora를 수정해서 MPI들을 Connection Manager들로
교체하십시요.
SQL*Net V2.x client와의 호환성
Connection Manager를 SQL*Net 2.x clients과 Oracle 8사이의
중심이나 접속 필터로 사용하기 위해서는 다음과 같은 일을
해야 합니다.
1) Connection Manager를 설치하고 설정합니다..
2) SQL*Net v2.x client들을 Connection Manager를 MPI처럼 사용
하도록 설정 합니다.
Server 설정
===========
NET8의 새로운 기능을 이용하기 위해서는 Connection Manager를 설정
해야 하며 서버를 Multi-Threaded Server (MTS)로 설정해야 합니다.
MTS parameter들은 각 instance의 INIT.ORA파일에 설정합니다.
NET8 MTS를 위한 parameter들은 SQL*Net 2과 다르지 않습니다.
다음 Connection Pooling 과 Multiplexing 기능을 사용할때
MTS_DISPATCHERS parameter의 경우만 제외하면 말입니다.
MTS_DISPATCHERS parameter:
     MTS_DISPATCHERS ="(PROTOCOL=TCP)(POOL=NO)(MULT=ON)"
이 예에서 TCP/IP를 위해 dispatcher들을 설정하고 Connection Pooling
기능을 사용하지 못하게 하고, Multiplexing를 가능하게 합니다.
만일 Connection Pooling 과 Multiplexing 를 사용하지 않을 거라면
SQL*Net 2.x용으로 정의된 MTS parameter들을 사용하실 수 있습니다.
좀더 자세한 내용은 MTS관련 문서를 참조 하시기 바랍니다.
Connection Manager를 사용하는 경우, INIT.ORA에 새로운 parameter를
설정해야 합니다. Connection Manager는 한개 이상의 physical connection
을 만들기 때문에 instance의 dispatcher가 허용할 client sessions의 최대값을
알아야 합니다. SESSIONS라는 parameter가 이 값을 설정합니다.
이 값은 'LSNRCTL SERVICES' 명령으로 볼 수 있습니다.
3. 시작 하기 (Windows NT)
Oracle Names server 환경에서 :
- command line utility 사용하기
1. 작업 표시줄에서 시작->실행
열기: x:\CMCTL80.exe (8i에서는 CMCTL.exe)
OK<click>
2. CMCTL> start CMAN <enter>
- Windows NT 제어판 사용하기
1. 제어판>SERVICES <double click>
2. 다음을 찾아 시작 시킵니다.
(주의: 순서대로 시작시켜야 합니다.)
OracleCMAdminService80 <click start>
OracleCMANService80 <click start>
NON-Oracle Names server 환경에서 :
- command line utility 사용하기
1. 작업 표시줄에서 시작->실행
열기: x:\CMCTL80.exe (8i에서는 CMCTL.exe)
OK<click>
2. CMCTL> start CM <enter>
- Windows NT 제어판 사용하기
1. 제어판>SERVICES <double click>
2. 다음을 찾아 시작 시킵니다.
(주의: 순서대로 시작시켜야 합니다.)
OracleCMANService80 <click start>
Reference Ducumment
---------------------

Hi
You must install the Connection Manager, available on the Oracle8 distribution media, onto the Web server host. You can find the installation instructions in the Net8 Administrator's Guide.
On the Web server host, create a CMAN.ORA file in the [ORACLE_HOME]/NET8/ADMIN directory. The options you can declare in a CMAN.ORA file include firewall and connection pooling support
Here is an example of a very simple CMAN.ORA file. Replace <web-server-host> with the name of your Web server host. The fourth line in the file indicates that the connection manager is listening on port 1610. You must use this port number in your connect string for JDBC.
cman = (ADDRESS_LIST =
(ADDRESS = (PROTOCOL=TCP)
(HOST=<web-server-host>)
(PORT=1610)))
cman_profile = (parameter_list =
(MAXIMUM_RELAYS=512)
(LOG_LEVEL=1)
(TRACING=YES)
(RELAY_STATISTICS=YES)
(SHOW_TNS_INFO=YES)
(USE_ASYNC_CALL=YES)
(AUTHENTICATION_LEVEL=0)
Ariel G.

Troubleshooting Connection Manager

Hey, I try to setup the oracle connection manager.
I installed the Connection via the universal installer
Then I created a cman.ora in $TNS_ADMIN with following content:
cman1 =
(CONFIGURATION=
(ADDRESS=(PROTOCOL=tcp)(HOST=172.17.12.143)(PORT=1521))
(RULE_LIST=
(RULE=
(SRC=*)(DST=*)(SRV=*)(ACT=accept)
(ACTION_LIST=(aut=off)(moct=0)(mct=0)(mit=0)(conn_stats=on))
(RULE=(SRC=sles11-rac)(DST=127.0.0.1)(SRV=*)(ACT=accept))
I also edited the tnsnames.ora :
cman1 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 172.17.12.143)(PORT = 1521))
Then I start the connection manager:
CMCTL> administer cman1
Current instance cman1 is not yet started
Connections refer to (ADDRESS=(PROTOCOL=tcp)(HOST=172.17.12.143)(PORT=1521)).
The command completed successfully.
CMCTL:cman1> startup
TNS-04012: Unable to start Oracle Connection Manager instance.
CMCTL:cman1>
Where is the mistake ???

I may found the answer, might be stupid but anyway
http://marist89.blogspot.com/2005/07/futzing-with-10g-connection-manager.html
I don´t have a listener configured. There is NOTHING in the oracle documentation which is saying that a listener is needed.
I thought cman would cover this listening process as well.
I will try it now
Edited by: Christian on 09.07.2010 14:23
Yeah, is working now. Just installed the Oracle Net Tools and configured the listener
+1
Thanks for this note. This was frustrating. I didn't find much on this error on the net or support, so pasting it again here:
(EVENT=Failed to start listener process)(REASON=)(OPN=65)(NS1=12545)(NS2=12560)(NT1=515)(NT2=2)
The only reference I found to needing the listener was in the CMAN architecture doc. I'm guessing the listener is supposed to be auto-installed with CMAN. Maybe it's an OUI bug? I'm on Solaris SPARC 64bit. Anyway, for anyone else, make sure the Oracle Net Listener is selected as well as Oracle Connection Manager when installing using the client software bundle. In the default install I went through, it wasn't sufficient to have a DB listener installed in a separate ORACLE_HOME on the same host. The listener software had to be in the same ORACLE_HOME as CMAN software. Also, I didn't have to configure the listener installed with CMAN. When CMAN is started, it starts a tnslsnr process, but I didn't have to setup a listener.ora. Port 1521 is already taken on this host by another listener yet the CMAN version still started??
Side note. Tried modifying an existing EE server installation. There is a CMAN option available that wasn't selected. Observed error: OUI-10150 ... setting s_dlgCfgNamingLabelSIDnull ... That's when I found the note in the docs and on Metalink that CMAN is supposed to be installed from the client software package in 11.2.
JP
Edited by: user10311101 on Jul 20, 2010 10:16 AM

Source Routing - Connection Manager

Hi,
I need some help understanding the following source routing function of Connection Manager. The book says:
"Source routing is used with Connection Manager. CM servers as a proxy server for Oracle Net traffic, enabling Oracle Net traffic to be routed securely though a firewall. Oracle Net treats the addresses as a list of relays, connecting to the first address that then requesting to be passed from the first to the second until the destination is reached. It differs from failover and load balancing in that all addresses are used each time a connection is made".
I do understand it is possible to configure CM in such a way that it can act as a firewall, accepting and rejecting connections based on certain criteria. What I do not understand is the second part where the addresses are treated as a list of relays. Why would something like this be necessary and how could that be configured in CM.
Any help would be greatly appreciated....
Thanks in advance.

Hi,
Oracle connection manager enables greater resource utilization for increased scalability,
multiprotocol connectivity and secure network acces control.
Example tnsnames.ora:
     CMExample.world =
     (DESCRIPTION=
     (ADDRESS_LIST=
     (ADDRESS=
     (PROTOCOL=tcp)
          (PORT=1610)
               (HOST=CM_SERVER)
     (ADDRESS=
          (PROTOCOL=tcp)
               (PORT=1521)
               (HOST=LSNR_SERVER)
(CONNECT_DATA=
          (SID=ORCL)
(SOURCE_ROUTE=yes)
Example cman.ora:
     cman = (ADDRESS_LIST=
(ADDRESS=(PROTOCOL=tcp)(HOST=h)(PORT=1610))
(ADDRESS=(PROTOCOL=tcp)(HOST=h)(PORT=1620))
     cman_profile = (parameter_list=
(MAXIMUM_RELAYS=1024)
(LOG_LEVEL=1)
(TRACING=no)
(RELAY_STATISTICS=yes)
(SHOW_TNS_INFO=yes)
(USE_ASYNC_CALL=yes)
(AUTHENTICATION_LEVEL=1)
Configuring CM for Network Acces Control(Firewall support):
Example:
cman = (ADDRESS_LIST=
(ADDRESS=(PROTOCOL=tcp)(HOST=h)(PORT=1610))
(ADDRESS=(PROTOCOL=tcp)(HOST=h)(PORT=1620))
cman_rules = (rule_list=
(rule=(src=spcstn)(dst=x)(srv=x)(act=accept))
"For more information Note:126079.1"

Connection manager documentation

I'm having trouble finding some good documentation on Oracle Connection Manager, can anybody point me in the right direction.
I'm looking in to how it might be used to proxy SQLnet in order to satisfy firewall requirements, and I'm at the stage of what does it do and what are the hardware and pre-requisite requirements, rather than needing in depth configuration info at the moment.
Thanks in advance.

You can find information on Net Services Administrator's Guide

Connection Manager in 11.1.2

Hi ,
I am new to smart view version 11.1.2. I have to add new URL in connection manager. Can somebody help me to do this. I opened shared connections, and searching for action panel to add the URL for HFM. I don't see anything to add the url. "Do i need to search in Private coinnections"?. Can somebody Help on this.
Thanks in advance
Mo
Edited by: user10926115 on Mar 28, 2011 12:08 PM

Hi Mo,
Hyperion Ribbon -> Connect -> Smart View Data Source Manager (opens, usually on right)
Set Connection Type to 'Independent Provider Connections'
Click the "+", select 'URL Provider'
(Add Connection Dialog opens)
Select 'Hyperion Provider'
Then enter your URL in the Location: text field, usually http://<HFMServerName>/hfmofficeprovider/hfmofficeprovider.aspx
Regards,
Robb Salzmann

Connection manager

Hello,
I'm trying to set a test envirinment to learn Oracle Connection Manager. I've read appropriate chapters in Net documentation and a forum thread:
Re: Configuration of Connection Manager
But there are still things that I can't work on.
I have two machines, database on one of them and client on the other. It's database 10g, client on WinXP, database on Linux.
Where should I install connection manager? on Linux or Windows, maybe any?
If it was a production environment, what would be the best solution?
Thanks in advance,
Aliq

Hello again,
thank you both for help. Unfortunately it still doesn't work :/
Since I couldn't get the install files for Windows (I didn't have cman installed there) I decided to change:
database on WinXP, so listener there too (listening on 1521, database is called "test" and it's open). Hostname = hostB
client and cman on Linux. Hostname = hostA
My cman.ora looks like this:
cman_ora(
configuration=
(address=(protocol=tcp)(host=hostA)(port=1610))
(rule_list=(src=*)(DST=hostB)(srv=*)(act=accept))
(rule_list=(src=*)(DST=hostA)(srv=*)(act=accept))
(PARAMETER_LIST=
(LOG_DIRECTORY=/u01/app/oracle/product/10.2.0/db_1/network/admin/log)
(LOG_LEVEL=ADMIN)
cman.ora:
testcman=
(description=
(SOURCE_ROUTE=YES)
(ADDRESS=(PROTOCOL=TCP)(HOST=hostA)(port=1610))
(ADDRESS=(PROTOCOL=TCP)(HOST=hostB)(port=1521))
(CONNECT_DATA =
(SERVER=DEDICATED)
(SERVICE_NAME=test)
Then I do (on Linux -> client/cman)
$cmctl
cmctl> administer
Current instance CMAN_ora is not yet started
Connections refer to
(description=
(SOURCE_ROUTE=YES)
(ADDRESS=(PROTOCOL=TCP)(HOST=hostA)(port=1610))
(ADDRESS=(PROTOCOL=TCP)(HOST=hostB)(port=1521))
(CONNECT_DATA =
(SERVER=DEDICATED)
(SERVICE_NAME=test)
The command completed successfully.
cmctl:CMAN_ora>startup
TNS-04012: Unable to start Oracle Connection Manager instance
Aliq
Message was edited by:
user547746
Message was edited by:
user547746

Add rule to oracle connection manager

Similar Messages

Maybe you are looking for