Previous  Next          Contents  Index  Navigation  Glossary  Library

Standalone Mode

Normally, the Oracle Order Entry Transaction Manager runs in the INHERIT mode, where the listener spawns a Transaction Manager process whenever it receives a request from the clients. A connection is then established between the client and the spawned Transaction Manager process, and the listener returns to the waiting state to process the other client requests for connection.

The Transaction Manager can also run in STANDALONE mode. In this mode, the Transaction Manager process, not the listener, waits for the client request and then establishes an immediate connection with the client. As a result, only one client can make a connection with the Transaction Manager running in the STANDALONE mode, whereas multiple clients could make connections in the INHERIT mode. Furthermore, unlike in the INHERIT mode where the Transaction Manager inherits only the environment variables defined in the listener.ora file, the Transaction Manager running in the STANDALONE mode inherits all the environment variable from Application Server where it was launched. Such characteristics make STANDALONE mode the ideal environment for running the diagnostics on the Transaction Manager. See: Generating a Diagnostics File.

Configuration of the Order Entry Transaction Manager in Standalone Mode:

Because most platforms, including UNIX, do not allow more than one process to use the same network address, use Network Manager to define a new entry for the Transaction Manager in both the client and the server tnsnames.ora file with a different network address than the listener's. No modification is needed for the listener.ora file because the STANDALONE Transaction Manager does not use the listener process. This allows you to run both the STANDALONE mode and the INHERIT mode Transaction Manager at the same time. An example tnsnames.ora file would now include two entries for the Transaction Manager:

### EXISTING ENTRY FOR THE LISTENER MODE ###
OEORPC_testsun = 	(DESCRIPTION 
				(ADDRESS =	(PROTOCOL=tcp)
						(HOST=testsun)
						(PORT=1527))
				(CONNECT_DATA=(SID=OEORPC_testsun)))

### NEW ENTRY FOR THE STANDALONE MODE ###
OEORPC_testsun_sa = (DESCRIPTION 
				(ADDRESS =	(PROTOCOL=tcp)
					(HOST=testsun)
					(PORT=1528))
				(CONNECT_DATA=(SID=OEORPC_testsun_sa)))

Note that the new entry for the standalone mode must be added to both the client and server tnsnames.ora files. Furthermore, an OE: Transaction Manager profile must be defined at a level other than the site level; we recommend the user level. When the user launches the Applications, s/he must sign on with the user name for which OE: Transaction Manager has been defined at the user level; this client session would then connect to the STANDALONE mode Transaction Manager. See: Oracle Order Entry/Shipping Profile Options.

Running the Order Entry Transaction Manager in STANDALONE mode:

Before running the Transaction Manager in the standalone mode, set the following environment variables to the same values from the release 10.6 environment: FDWHOAMI, GWYUID, FNDNAM. Optionally, you can define the environment variables OERPCDBG and OEDBGFILE to set the debugging level and specify debugging file name, respectively. See: Generating a Diagnostics File.

The command to startup the standalone Transaction Manager server is:

$OE_TOP/$APPLBIN/OEORPC mode=standalone server=<Transaction Mgr Name>

The Server parameter should be set to the Oracle Order Entry Transaction Manager name defined in the Network Manager when you were installing and setting up the Transaction Manager. In our example, type the following to run in standalone mode. 

$OE_TOP/$APPLBIN/OEORPC mode=standalone server=OEORPC_testsun_sa

         Previous  Next          Contents  Index  Navigation  Glossary  Library