Previous  Next          Contents  Index  Navigation  Glossary  Library

Establishing a Network Connection

This section discusses how the Oracle Order Entry Release 10SC client establishes a connection with the Oracle Order Entry Transaction Manager. There are three sources of information that Oracle Order Entry uses: SQL*Net configuration files (tnsnames.ora and listener.ora) and the profile OE: Transaction Manager. See: Oracle Order Entry/Shipping Profile Options.

SQL*Net and OE: Transaction Manager Profile Definition

As noted in the Oracle Order Entry Transaction Manager Installation Guide, you must define new entries in your network definition for the Listener and the Order Entry Transaction Manager and modify the following components in the Listener and Oracle Entry Transaction Manager definitions. Although the Order Entry Trasaction Manager is an executable, not a database, the network needs it to be registered as if it were a database. Please note that italicized names followed by each entry are fictitious names used only for the examples in this section.

Listener Definition:

Database Definition (for the Order Entry Transaction Manager):

The above SQL*Net configuration translates into the following entries in the Network Configuration files.

tnsnames.ora:

OEORPC_testsun  = (DESCRIPTION
				(ADDRESS = LISTENER_ADDRESS_testsun )
				(CONNECT_DATA = (SID = 
				OEORPC_testsun_SID )))

listener.ora:

LISTENER_OEORPC_testsun =(ADDRESS = LISTENER_ADDRESS_testsun)
SID_LIST_LISTENER_OEORPC_testsun = 
				(SID_DESC = 
				(SID_NAME = OEORPC_testsun_SID )
				(PROGRAM = OEORPC)
				(ORACLE_HOME = OE_TOP_PATH )
				(ENVS = OEORPC_ENVS ))

The final step in configuring the Oracle Order Entry Transaction Manager is to set the profile OE: Transaction Manager at the site level to the name of the Transaction Manager, or OEORPC_testsun in our example.

Connections between the client and the Transaction Manager

Footnotes:

1. Client finds the proper entry in the tnsnames.ora file by looking up the value in the OE: Transaction Manager profile, which stores the name of the Oracle Order Entry Transaction Manager.

2. Once the tnsnames.ora entry is found, the client knows where on the network the listener is waiting. Once it contacts the listener, it passes to the listener the SID of the Transaction Manager, which is defined in the tnsnames.ora file.

3. The listener may be waiting for connection requests for more than one database or other services. It determines the database or service to which the client is requesting connection by matching the client's Transaction Manager SID to the SID_NAME in the listener's SID_DESC list. Once the SID_NAME and SID_DESC are determined, the listener uses the other parameters defined in that SID_DESC, such as PROGRAM, ENVS, and ORACLE_HOME, to spawn the appropriate process with the correct environment.

         Previous  Next          Contents  Index  Navigation  Glossary  Library