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   |   Installation   |   Topic List   |   Previous   |   Next   |   Contents

   Installing the BEA Tuxedo System

This section is for customers running Release 4.2.1 (or updates) or 4.2.2 (or updates). Interoperation of Release 6.5 with Release 4.2 is not supported.

During the upgrade, you must shut down the backup and master machines serially; the remainder of the configuration is unaffected.

1. Make sure your environment is set up as follows:

   • The configuration must include a backup machine.

   • The MODEL option must be set to MP.

   • The MIGRATE option must be set.

2. Migrate the master to the backup machine.

3. Shut down the configured master.

4. Upgrade the configured master machine to Release 4.3.

5. Relink all application servers and clients.

6. Reboot the configured master.

7. Once the configured master is up, migrate the master control.

Now you have a configuration with the master running Release 4.3.

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've completed it, you cannot change the master back to the release of the BEA Tuxedo system it was running previously.)

Dynamic reconfiguration (which is available during upgrades from Release 5) is not available when you are running a Release 6.5 master and one or more Release 4.3 nodes. The lack of dynamic reconfiguration means:

• Administrative activities will be restricted until the full application has been upgraded.

• The values of TUXDIR and APPDIR cannot be changed during a hot upgrade. Therefore you must move the files in the directory defined by the ROOTDIR environment variable to a new location, and install the corresponding files for the new release in that directory. In Release 6.5, the path name for this directory is set with the TUXDIR variable. Similarly, you must move the files in the directory defined by APPDIR to a new location and install the corresponding Release 6.5 files in that directory.

  On a UNIX platform, you may simplify these tasks by using symbolic links. For example, you might use the path name /usr/tuxedo as a symbolic link that points to /usr/tuxedo43 and later /usr/tuxedo65.

When you run tmadmin(1) on a Release 6.5 machine with a Release 4.3 master, the UPGRADE and UPGRADE42 files (as shown in Example) must reside in the current directory. To make sure that the files are in the current directory, you might, for example, run tmadmin(1)from APPDIR.

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 4.3 clients and servers were created. (In other words, both a Release 4.3 application and a Release 6.5 application should be available on each machine.) This is not a requirement, but a recommendation.

1. Make sure your environment is set up to comply with the following requirements:

   • The configuration must include a backup machine.

   • The MODEL option must be set to MP.

   • The MIGRATE option must be set.

   • MAXGROUPS must be set to 100 and the value of MAXSERVERS must match that of MAXQUEUES in the configuration.

2. Shut down the backup machine.

3. Reboot the backup machine, using Release 6.5.

4. Migrate the master running Release 4.3 to the backup running Release 6.5.

5. Shut down the machine that is now acting as the backup.

6. Using Release 6.5, reboot the machine that you shut down in Step 5.

Suppose you have the following on a UNIX platform:

• A machine called MACH1 that is initially configured as the master and that runs Release 4.3

  • A corresponding application directory called $APPDIR1

  • A corresponding configuration file called $TUXCONFIG1

• A machine called MACH2 that is configured as the backup

  • A corresponding application directory called $APPDIR2

  • A corresponding configuration file called $TUXCONFIG2

Refer to the following instruction sequence to perform a hot upgrade for your application.

MACH1> tmshutdown -B MACH2 -l MACH2
 
       MACH2> Kill tlisten process
 
       MACH2> Load System 6.5 if it is not already loaded
 
       MACH2> ROOTDIR/APPDIR2 must be the same as the 4.3 directories
 
       MACH2> cd $APPDIR2
 
       MACH2> rm $TUXCONFIG2
 
       MACH2> >UPGRADE    # Indicator that upgrade being done
 
       MACH2> >UPGRADE42  # Indicator that upgrade done from 4.3
 
       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
 
MACH1> Kill tlisten process
 
MACH1> Load System 6.5 if it is not already loaded
 
MACH1> ROOTDIR/APPDIR1 must be the same as the 4.3 directories
 
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> rm UPGRADE42 # Remove indicator that upgrade being done
 
       MACH2> tmboot -B MACH1 -l MACH1

 

Copyright © 2000 BEA Systems, Inc. All rights reserved. Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.