[Top] [Prev] [Next] [Bottom]

Chapter 2 . Upgrading to BEA TUXEDO Release 6.4

Introduction

This chapter provides procedures for upgrading your BEA TUXEDO application to BEA TUXEDO Release 6.4.

Simple Upgrade

  1. Shut down the application.

  2. Update at least the master and backup machines to BEA TUXEDO Release 6.4.

  3. Reboot the application.

  4. Shut down and upgrade other machines as time permits.

Selecting a Hot Upgrade Procedure

Release 4.x and Release 6.x are defined as follows:

Hot Upgrade from Release 4.x

This section is for customers running Release 4.2.1 (or updates) or 4.2.2 (or updates). Interoperation of Release 6.4 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.

Step 1: Hot Upgrade from Release 4.2.x to Release 4.3

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

  2. Migrate the master to the backup.

  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.

Step 2: Hot Upgrade from Release 4.3 to Release 6.4

PRELIMINARY NOTES

Once you have finished migrating (via a hot upgrade) the master to Release 6.4, you will not be able to migrate it back to the acting backup until you have upgraded the backup to Release 6.4. (In other words, migrating the master is an irreversible procedure; once you've completed it, you cannot change the master back to the version of BEA TUXEDO it was running previously.)

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

When you are running tmadmin(1) on a Release 6.4 machine with a Release 4.3 master, the UPGRADE and UPGRADE42 files (see "EXAMPLE" below) must be in the current directory. (For example, you might simply run the tmadmin(1) command from APPDIR).

To minimize down time, we recommend installing Release 6.4 on the master and backup, and rebuilding all clients and servers in a new APPDIR, in parallel with 4.3. (That is, both a Release 4.3 and Release 6.4 application should be available on the machines to minimize down time.) This is not a requirement, but a recommendation.

PROCEDURE

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

  2. Shut down the configured backup.

  3. Reboot the configured backup, using Release 6.4.

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

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

  6. Using Release 6.4, re-boot the machine that you shut down in #5.

EXAMPLE

Suppose you have the following:

As you perform a hot upgrade for your application, the following input and output will be displayed on your screen. 

MACH1>	tmshutdown -B MACH2 -l MACH2
	MACH2>	kill tlisten process
 
	MACH2>	 load System 6.4 if not already loaded
 
	MACH2>	 ROOTDIR/APPDIR2 must be same as 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.4 tlisten
 
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.4 if not already loaded
 
MACH1> 	ROOTDIR/APPDIR1 must be same as 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.4 tlisten
 
	MACH2>	rm UPGRADE  # Remove indicator that upgrade being done
 
	MACH2>	rm UPGRADE42 # Remove indicator that upgrade being done
 
	MACH2>	 tmboot -B MACH1 -l MACH1

Hot Upgrade from Release 5.x or Release 6.x

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

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

  2. Migrate the master to the backup.

  3. Shut down the configured master.

  4. Upgrade the configured master machine to Release 4.1.

  5. If you are using an SCO platform, you must recompile and re-link application servers and clients. (Shared objects are not used in SCO platforms.)

    Note: This step is not necessary on any platforms other than SCO.

  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 5.1.

Step 2: Hot Upgrade from Release 5.1 or 6.x to Release 6.4

PRELIMINARY NOTES

This section is for customers running Release 5.1, Release 6.1, or Release 6.2.

Once you have finished migrating (via a hot upgrade) the master to Release 6.4, you will not be able to migrate it back to the acting backup until you have upgraded the backup to Release 6.4. (In other words, migrating the master is an irreversible procedure; once you've completed it, you cannot change the master back to the version of BEA TUXEDO it was running previously.)

When you are running tmadmin(1) on a Release 6.4 machine with a Release 5.1 or 6.x master, the UPGRADE file (see below) must be in the current directory. For example, you might simply run tmadmin(1) from APPDIR.

To minimize down time, we recommend that you install Release 6.4 on the master and backup, and rebuild all clients and servers in a new APPDIR, in parallel with 5.1 or 6.x. (That is, both a Release 5.1 or 6.x and Release 6.4 application should be available on the machines to minimize down time.) This is not a requirement, but a recommendation.

PROCEDURE

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

  2. Shut down the configured backup.

  3. Reboot the configured backup, using Release 6.4.

  4. Migrate the master running Release 5.1 or 6.x to the backup running Release 6.4.

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

  6. Using Release 6.4, re-boot the machine that you shut down in #5.

EXAMPLE

Suppose you have the following:

As you perform a hot upgrade for your application, the following input and output will be displayed on your screen. 

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.4 if 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.4 tlisten
 
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.4 if 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.4 tlisten
 
	MACH2>	rm UPGRADE  # Remove indictor that upgrade being done
 
	MACH2>	tmboot -B MACH1 -l MACH1
 





 
[Top] [Prev] [Next] [Bottom]