e-docs > Tuxedo > Installing the Tuxedo System > Upgrading the BEA Tuxedo System to Release 8.1 |
Installing the Tuxedo System |
Upgrading the BEA Tuxedo System to Release 8.1
The following sections provide procedures for upgrading your BEA Tuxedo or BEA WebLogic Enterprise application to BEA Tuxedo 8.1 using simple and hot upgrade procedures:
Preparing Your Machine for an Upgrade
Before you install the BEA Tuxedo 8.1 software on a machine, make sure that the required version of the operating system and the compiler have been installed. For operating system and compiler requirements for each supported platform, see BEA Tuxedo 8.1 Platform Data Sheets.
Selecting an Upgrade Procedure
If you are installing BEA Tuxedo 8.1 on a platform that contains an earlier release of BEA Tuxedo software or the BEA WebLogic Enterprise software, be sure to read the following procedures carefully.
If you can shut down your application for the upgrade, then shut down your application and perform a simple upgrade. For instructions on performing a simple upgrade, see Performing a Simple Upgrade. If you cannot shut down your application for the upgrade, you can perform a hot upgrade for any of the following software products to BEA Tuxedo 8.1 without having to shut down your enterprise:
You can add the BEA Tuxedo 8.1 software to existing BEA Tuxedo or BEA WebLogic Enterprise domains without shutting down the existing applications, and you can add new BEA Tuxedo 8.1 application servers to those domains without shutting down the existing applications. For instructions on performing a hot upgrade, see Performing a Hot Upgrade.
Backing Up Files
There are certain files that you need to back up prior to the installation and then restore after the installation is complete. Any modifications that you made to these files will be overwritten when the new BEA Tuxedo software is installed.
To avoid having to modify these files again, follow these steps:
Performing a Simple Upgrade
A simple upgrade consists of the following basic steps:
Performing Additional Upgrade Steps for Windows 2000
For a Windows 2000 machine running BEA WebLogic Enterprise or BEA Tuxedo 7.1 or earlier software, perform the following additional steps before installing the BEA Tuxedo 8.1 software to ensure that you are starting with a clean system.
Performing a Hot Upgrade
Before performing a hot upgrade, back up files as described in Backing Up Files.
During the hot upgrade, you must shut down the MASTER and backup MASTER machines serially. The remainder of the configuration is unaffected.
Pre-Upgrade Notes
Once you have finished migrating the MASTER to BEA Tuxedo 8.1 (via a hot upgrade), you will not be able to migrate it back to the acting backup until you have upgraded the backup to BEA Tuxedo 8.1. 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 software on which it was running previously.
When you run tmadmin(1) on a BEA Tuxedo 8.1 machine with an old-release MASTER, the UPGRADE file shown in Hot-Upgrade Example must reside in the current directory. To make sure that the files are in the current directory, you might, for example, run tmadmin from the Tuxedo application directory: %APPDIR% (Windows)/ $APPDIR (UNIX) directory.
During migration, keep in mind the following guidelines regarding the BEA Tuxedo data storage areas:
To minimize downtime, BEA recommends installing BEA Tuxedo 8.1 on the MASTER machine and backup MASTER, and rebuilding all clients and servers in the directory on each machine that is defined by %APPDIR%/ $APPDIR, in parallel with the directory in which the old-release clients and servers were created. In other words, both an old-release application and a BEA Tuxedo 8.1 application should be available on each machine. This advice is not a requirement, but a recommendation.
The BEA Tuxedo software supports device list path entries of up to 256 bytes in length (in previous releases the limit was 64 bytes in length.) Queue Spaces, TLOG files, and other configuration files originally created with an earlier version of BEA Tuxedo are understood and supported with this release. However, such device lists originally created with BEA Tuxedo 8.0 or earlier are restricted to 64-byte path names. Therefore, if the administrator wants to add a new extent using a path name greater than 64 bytes in length to a queue space in the future and such queue space is empty when the upgrade is performed, the administrator may want to create the queue space device list and the queue space at the time of the hot upgrade. Many applications need to preserve queue spaces across an upgrade and will not be able to recreate them. Furthermore, most applications will not need to add queue space extent in the future or will be able to do so using path names no longer than the ones they are currently using. This queue space recreation is completely optional and mentioned for completeness.
Hot-Upgrade Procedure
This section provides an overview of the tasks for a "hot upgrade."
For more information about hot upgrades, refer to the following section, Hot-Upgrade Example.
Hot-Upgrade Example
The following example describes a sample scenario for a hot upgrade and the sequence of steps to perform the hot upgrade.
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 8.1 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 8.1 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 8.1 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 8.1 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
Note: If you are performing the upgrade illustrated in the previous example on a Windows 2000 platform, be sure to stop the Tuxedo BEA procMGR (called IPC Helper in BEA Tuxedo 6.5 or BEA WebLogic Enterprise 5.1) service after stopping the tlisten process and to start the BEA procMGR service before starting the tlisten process.
Rebuilding an Application
Now that you have successfully installed the BEA Tuxedo software, you need to rebuild all application clients and servers that you want to execute on a system upgraded to BEA Tuxedo 8.1. You should also remove any old TUXCONFIG files and reload them using the newly installed tmloadcf(1).
If your BEA Tuxedo system applications are distributed, the MASTER and backup MASTER machines must run the highest release of the BEA Tuxedo software of any machines in the configuration. Other machines, including Workstation clients, may continue to use executables from an earlier release. For example, even if your MASTER and backup MASTER machines are running BEA Tuxedo 8.1, BEA Tuxedo 6.5 or later may still be used on other machines.
There is one important exception to the "highest release" rule. If you wish to install BEA Tuxedo 8.1 only on Workstation clients, and you do not want to upgrade any of your BEA Tuxedo system server machines to BEA Tuxedo 8.1, you may do so. In other words, with any release level beginning with BEA Tuxedo 6.5, Workstation clients may be intermixed freely in a configuration in which the MASTER machines is running BEA Tuxedo 6.5 or later.
Installing BEA Jolt 8.1 with BEA WebLogic Server
This section provides supplementary installation instructions for customers using BEA Jolt 8.1 with BEA WebLogic Server 6.0 or 7.0 and BEA Tuxedo 6.5, 7.1, 8.0, or 8.1. You can install the Jolt client personality software known as "BEA Jolt for BEA WebLogic Server" or "WebLogic Connectivity for BEA Tuxedo" on a BEA WebLogic Server 6.0 or 7.0 machine in one of two ways:
The following table describes how to use the first method to install the "BEA Jolt for BEA WebLogic Server" client software on a BEA WebLogic Server 7.0 machine.
On this platform . . . Complete this procedure . . . Windows UNIX The "BEA Jolt for BEA WebLogic Server" client software consists of three JAR files: jolt.jar, joltjse.jar, and joltwls.jar. Include these files in your CLASSPATH variable setting. For instructions on configuring the Jolt connection pool on BEA WebLogic Server, see Using BEA Jolt with BEA WebLogic Server.