Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Search   |   PDF Files   |   Contact   |
eLink Adapter into WebLogic Enterprise CORBA Doc Home   |   BEA eLink Adapter into WebLogic Enterprise CORBA User Guide   |   Previous Topic   |   Next Topic   |   Contents   |   Index

This section contains the following topics:

• Running the eLink Adapter for CORBA

• Shutting Down the eLink Adapter for CORBA

Once all configuration prerequisites have been completed successfully, you can bring up the eLink Adapter into WebLogic Enterprise CORBA using the tmboot command. Only the administrator who created the TUXCONFIG file can execute tmboot.

The adapter is generally booted from the machine designated as MASTER in the RESOURCES section of the UBBCONFIG file or the BACKUP acting as MASTER. For the tmboot command to find executables, eLink Platform system processes, such as the BBL, must be located in the $TUXDIR/bin directory. Application servers should be in the directory defined by the APPDIR variable, as specified in the configuration file.

When booting the eLink Adapter for CORBA, the tmboot command uses the CLOPT parameter from the UBBCONFIG file. Application servers are booted in the order specified by the SEQUENCE parameter, if SEQUENCE is not specified, servers are rebooted in the order in which they appear in the configuration file. The command line should look something like the following when using the tmboot command.

$ tmboot [-g grpname] [-o seqeunce] [-s] [-A] [-y]

The tmboot command uses the following options:

-g grpname

Boots all application servers in groups using this grpname parameter.

-o sequence

Boots all servers in the order shown in the SEQUENCE parameter.

-s server-name

Boots an individual server.

-A

Boots all administrative servers for machines listed in the MACHINES section. This option ensures that the DBBL, BBL, and BRIDGE processes are started in the proper order.

-y

Provides an automatic "yes" response to the prompt that asks whether all administrative and application servers should be booted. This prompt is displayed only if no options that limit the scope of the command (-g grpname, for example) are specified.

Use the tmshutdown command to shut down all or part of a BEA eLink Platform application. The rules for running this command are similar to those for running tmboot.

When the entire application is shut down, tmshutdown removes the interprocess communication (IPC) resources associated with the BEA eLink Platform system. The options used by tmboot for partial booting (-A, -g, -I, -S, -s, -l, -M, -B) are supported in tmshutdown.

The tmshutdown command does not shut down the administrative server BBL on a machine to which clients are attached. You can use the -c option to override this feature. You need this option for occassions when you must bring down a machine immediately and you cannot contact clients.

Only the administrator who has written the TUXCONFIG file can execute tmshutdown. The application can be shut down only from the machine designated as MASTER in the configuration file. When the BACKUP acts as MASTER, it is considered to be the MASTER for shutdown purposes.

The order in which application servers are shut down is the reverse of the order specified by the SEQUENCE parameter for them, or the reverse order in which they are listed in the configuration file. If some servers have SEQUENCE numbers and others do not, the unnumbered servers are the first to be shut down, followed by the application servers with SEQUENCE numbers (in reverse order). Finally, administrative servers are shut down.

When an application is shut down, all the IPC resources allocated by the BEA eLink Platform system are removed. The tmshutdown command does not remove IPC resources allocated by the DBMS.