Previous | Next | Contents | Index | Navigation | Glossary | Library |
OEORPC_testsun = (DESCRIPTION
(ADDRESS = LISTENER_ADDRESS_testsun )
(CONNECT_DATA = (SID = OEORPC_testsun_SID )))
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.
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 |