Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Administration   |   Topic List   |   Previous   |   Next   |   Contents

   Administering a BEA Tuxedo Application at Run Time

1. Use the LMID parameter to name the processor on which the server group(s) have been running. The alternate location must be the same for all server groups on the LMID.

2. In the RESOURCES section of the UBBCONFIG file, set the following parameters:

   • Set RESTART=Y for each server on the machine indicated by the LMID.

   • Specify the MIGRATE options.

3. Shut down all server groups and mark the servers in the groups as restartable by entering the following command.

   tmshutdown -R

4. Use the tmadmin(1) migratemach (migm) command to migrate all server groups from one machine to another when the primary machine must be shut down for maintenance or when the primary machine is no longer accessible. (The command takes one logical machine identifier as an argument.)

To migrate a machine when the alternate machine is accessible from the primary machine, complete the following procedure.

1. Shut down the MASTER machine by entering the following command on that machine.

   tmshutdown -R -1 primary_machine

2. On the MASTER machine, start a tmadmin session by entering the following command.

   tmadmin

3. At the tmadmin prompt, migrate the appropriate machine by entering the following command.

   migratemach primary_machine

4. If necessary, migrate the transaction log.

5. If necessary, migrate the application data.

To migrate a machine when the alternate machine is not accessible from the primary machine, switch the MASTER and BACKUP machines, if necessary.

1. On the alternate machine, start a tmadmin session by entering the following command.

   tmadmin

2. Request cleanup and restart of the primary machine that require these operations by entering the following command.

   pclean primary_machine

3. Transfer the appropriate server group to a configured alternate machine by entering the following command.

   migratemach primary_machine

4. Boot the newly migrated server group by entering the following command.

   boot -l alternate_machine

The following sample session shows how to migrate machines. In the first example, the alternate machine is accessible from the primary machine.

$ tmshutdown -R -l SITE1
Shutting down server processes...
Server ID = 1 Group ID = GROUP1 machine = SITE1: shutdown 
succeeded 1 process stopped.
$ tmadmin
tmadmin - Copyright © 1987-1990 AT&T; 1991-1993 USL. 
> migm SITE1
migm successfully completed
> q

In the second example, the alternate machine is not accessible from the primary machine.

$ tmadmin
tmadmin - Copyright © 1987-1990 AT&T; 1991-1993 USL.
>pclean SITE1
Cleaning the DBBL.
Pausing 10 seconds waiting for system to stabilize.
3 SITE1 servers removed from bulletin board
> migm SITE1
migm successfully completed.
> boot -l SITE1
Booting server processes ...
exec simpserv -A :
on SITE2 -- process id=22782 ... Started.
1 process started.
>q