|
|
Hot Upgrade from Release 5.x, 6.1, or 6.2
During the upgrade, you must shut down the backup and master machines serially; the remainder of the configuration is unaffected.
Step 1: Hot Upgrade from Release 5.0 to Release 5.1
Note: This step is not necessary on any platforms other than SCO.
Now you have a configuration with the master running Release 5.1.
Step 2: Hot Upgrade from Release 5.1, 6.1, or 6.2 to Release 6.5
Preliminary Notes
This section is for customers running Release 5.1, 6.1, or 6.2.
Once you have finished migrating the master to Release 6.5 (via a hot upgrade), you will not be able to migrate it back to the acting backup until you have upgraded the backup to Release 6.5. In other words, migrating the master is an irreversible procedure; once you have completed it, you cannot change the master back to the release of the BEA Tuxedo system on which it was running previously.
When you are running tmadmin(1) on a Release 6.5 machine with a Release 5.1, 6.1, or 6.2 master, the UPGRADE file (as shown in Example) must reside in the current directory. To make sure that the files are in the current directory, run tmadmin from APPDIR.
During migration, keep in mind the following guidelines regarding the BEA Tuxedo data storage areas:
To minimize down time, we recommend installing Release 6.5 on the master and backup, and rebuilding all clients and servers in the directory on each machine that is defined by APPDIR, in parallel with the directory in which the Release 5.1, 6.1 or 6.2 clients and servers were created. (In other words, both a Release 5.1, 6.1 or 6.2 application and a Release 6.5 application should be available on each machine.) This is not a requirement, but a recommendation.
When migrating from Release 6.1 or 6.2, you must rebuild your clients and servers. Additionally, you must always rebuild if you are running a BEA Tuxedo application on an HP platform. The HP-UX shared library loader does not, by default, use the paths specified in the SHLIB_PATH environment variable when trying to locate the shared libraries needed by an executable at run time. The HP-UX shared library loader must be turned on. (This procedure is not necessary on any other platform supported by the BEA Tuxedo system.) As a result, once you have upgraded from Release 6.1 or 6.2 to Release 6.5, your application programs will not be able to find the Release 6.5 BEA Tuxedo libraries. These programs must be recompiled with the following setting.
CFLAGS=Wl,+s
This setting causes the compiler to pass the +s option to the link editor when the application is recompiled. It changes the program's default behavior during future upgrades.
Procedure
Example
Suppose you have the following on a UNIX platform:
Refer to the following instruction sequence to perform a hot upgrade for your application.
MACH1> tmshutdown -B MACH2 -l MACH2
MACH1> Run tmconfig to reset the APPDIR, TUXCONFIG, TUXDIR for MACH2
MACH2> Kill tlisten process
MACH2> Load System 6.5 if it is not already loaded
MACH2> cd $APPDIR2
MACH2> rm $TUXCONFIG2
MACH2> >UPGRADE # Indicator that upgrade being done
MACH2> Reset PATH, LD_LIBRARY_PATH, TUXCONFIG, APPDIR
MACH2> Rebuild clients and servers, create TLOG
MACH2> Start System 6.5 tlisten
MACH1> >UPGRADE # Indicator that upgrade being done
MACH1> tmboot -B MACH2 -l MACH2
MACH2> tmadmin
master
y
psr
q
MACH2> tmshutdown -B MACH1 -l MACH1
MACH2> Run tmconfig to reset the APPDIR, TUXCONFIG, TUXDIR for MACH1
MACH1> Kill tlisten process
MACH1> Load System 6.5 if it is not already loaded
MACH1> cd $APPDIR1
MACH1> rm $TUXCONFIG1
MACH1> Reset PATH, LD_LIBRARY_PATH, TUXCONFIG, APPDIR
MACH1> Rebuild clients and servers, create TLOG
MACH1> Start System 6.5 tlisten
MACH1> rm UPGRADE # Remove indicator that upgrade being done
MACH2> rm UPGRADE # Remove indicator that upgrade being done
MACH2> tmboot -B MACH1 -l MACH1
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|