The following sections provide procedures for upgrading your Oracle Tuxedo or Oracle WebLogic Enterprise application to Oracle Tuxedo 12c Release 2 (12.1.3) using simple and hot upgrade procedures:
Before you install the Oracle Tuxedo 12c Release 2 (12.1.3) 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 Oracle Tuxedo 12c Release 2 (12.1.3) Platform Data Sheets.
If you are installing Oracle Tuxedo 12c Release 2 (12.1.3) on a platform that contains an earlier release of Oracle Tuxedo software or the Oracle 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 Oracle Tuxedo 12c Release 2 (12.1.3) without having to shut down your enterprise:
You can add the Oracle Tuxedo 12c Release 2 (12.1.3) software to existing Oracle Tuxedo or Oracle WebLogic Enterprise domains without shutting down the existing applications, and you can add new Oracle Tuxedo 12c Release 2 (12.1.3) application servers to those domains without shutting down the existing applications. For instructions on performing a hot upgrade, see Performing a Hot Upgrade.
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 Oracle Tuxedo software is installed.
To avoid having to modify these files again, follow these steps:
RMfile to a temporary location. The
RMfile contains database vendor-specific settings that are used by commands such as
buildXAJS. It is located in the
tux_prod_diris the directory in which you installed the Oracle Tuxedo or Oracle WebLogic Enterprise software.
webgui.inifiles to a temporary location. These files contain customized initialization settings for the Oracle Tuxedo Administration Console server and GUI. The
tuxwsvr.inifile is located in the
/udataobjdirectory, and the
webgui.inifile is located in the
CATNAMESfile is located in the
jrly.configfiles are located in the
tux_prod_dirdirectory to a temporary location.
A simple upgrade consists of the following basic steps:
TLOG, make sure that no pending transaction logs are in them.
MASTERmachine by running the
TLOG, remove them.
For a Windows machine running Oracle WebLogic Enterprise or Oracle Tuxedo 12c Release 2 (12.1.3) or earlier software, perform the following additional steps before installing the Oracle Tuxedo 12c Release 2 (12.1.3) software to ensure that you are starting with a clean system.
procMGRservices. From the Start menu, click Start All Programs Administrative Tools Services. The Services window appears.
|Note:||The Oracle Tuxedo
|Note:||If you have both the C++ and Java components of WebLogic Enterprise 5.1 installed on your machine, you must remove the Java software before removing the C++ software.|
If you are upgrading from Tuxedo previous releases to Tuxedo 12c Release 2 (12.1.3), please note the following:
servopts -toption must be specified. The server may be a workstation listener (WSL) process (where the
servopts -toption allows interoperability for all of its workstation handler—WSH—processes), a domain gateway (GWTDOMAIN) process, or a system or application server process. For more information, see
GWTDOMAIN(5)in the Oracle Tuxedo File Formats, Data Descriptions, MIBs, And System Processes Reference.
If you have not upgraded to patch level 446, then you must set the
TM_GWT_OLDSECCHECK environment variable of the domain gateway in this Tuxedo 12c Release 2 (12.1.3). For more Oracle Tuxedo environment variable information, see
tuxenv(5) in the Oracle Tuxedo File Formats, Data Descriptions, MIBs, And System Processes Reference.
TPINITIALIZE(), you must set the
TM_CBL_IGNORE_CONTEXTenvironment variable to
“Y”when you run the COBOL application. For more Oracle Tuxedo environment variable information, see
tuxenv(5)in the Oracle Tuxedo File Formats, Data Descriptions, MIBs, And System Processes Reference.
tpreturn()API method throws an exception when an error is encountered. You need to change your existing code to invoke
tpreturn()API method in a try-catch block; otherwise, you will fail to successfully compile the code.
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.
Once you have finished migrating the
MASTER to Oracle Tuxedo 12c Release 2 (12.1.3) (via a hot upgrade), you will not be able to migrate it back to the acting backup until you have upgraded the backup to Oracle Tuxedo 12c Release 2 (12.1.3). 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 Oracle Tuxedo software on which it was running previously.
When you run
tmadmin(1) on an Oracle Tuxedo 12c Release 2 (12.1.3) machine with an old-release
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 (UNIX) directory.
During migration, keep in mind the following guidelines regarding the Oracle Tuxedo data storage areas:
TUXCONFIGfile is propagated automatically when the backup machine is run; therefore, you do not need to do anything.
BDMCONFIG) file, leave it as is.
To minimize downtime, Oracle recommends installing Oracle Tuxedo 12c Release 2 (12.1.3) on the
MASTER machine and backup
MASTER, 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 old-release clients and servers were created. In other words, both an old-release application and an Oracle Tuxedo 12c Release 2 (12.1.3) application should be available on each machine. This advice is not a requirement, but a recommendation.
The Oracle 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 Oracle Tuxedo are understood and supported with this release. However, such device lists originally created with Oracle 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.
If you already have
TLOG, make sure that no pending transaction logs are in them before shutting down the application, and keep in mind that removing the
TLOG (if they exist) after the application is shut down.
This section provides an overview of the tasks for a “hot upgrade.”
MASTERmachine and reboot the backup machine.
MASTERmachine running the old release to the backup
MASTERmachine running Oracle Tuxedo12c Release 2 (12.1.3).
For more information about hot upgrades, refer to the following section, 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 in Listing 4-1 to perform a hot upgrade for your application.
MACH1> tmshutdown -B MACH2 -l MACH2
Run tmconfig to reset the APPDIR, TUXCONFIG, TUXDIR for MACH2MACH2>
Kill tlisten processMACH2>
Load Tuxedo 12cR2 if it is not already loadedMACH2> cd $APPDIR2
MACH2> rm $TUXCONFIG2
MACH2> >UPGRADE #
Indicator that upgrade being doneMACH2>
Reset PATH, LD_LIBRARY_PATH, TUXCONFIG, APPDIRMACH2>
Rebuild clients and servers, create TLOGMACH2>
Start Tuxedo 12cR2 tlistenMACH1> >UPGRADE #
Indicator that upgrade being doneMACH1> tmboot -B MACH2 -l MACH2
MACH2> tmshutdown -B MACH1 -l MACH1
Run tmconfig to reset the APPDIR, TUXCONFIG, TUXDIR for MACH1MACH1>
Kill tlisten processMACH1>
Load Tuxedo 12cR2 if it is not already loadedMACH1> cd $APPDIR1
MACH1> rm $TUXCONFIG1
Reset PATH, LD_LIBRARY_PATH, TUXCONFIG, APPDIRMACH1>
Rebuild clients and servers, create TLOGMACH1>
Start Tuxedo 12cR2 tlistenMACH1> rm UPGRADE #
Remove indicator that upgrade being doneMACH2> rm UPGRADE #
Remove indicator that upgrade being doneMACH2> tmboot -B MACH1 -l MACH1
|Note:||If you are performing the upgrade illustrated in Listing 4-1 from a Windows platform, be sure to stop the Oracle Tuxedo
Now that you have successfully installed the Oracle Tuxedo software, you need to rebuild all application clients and servers that you want to execute on a system upgraded to Oracle Tuxedo 12c Release 2 (12.1.3).
|Notes:||Rebuild is mandatory when upgrading from a previous Oracle Tuxedo version to Oracle Tuxedo 12c Release 2 (12.1.3).|
|Note:||The TMS server must be rebuilt when upgrading a previous Oracle Tuxedo version to Oracle Tuxedo 12c Release 2 (12.1.3).|
You should also remove any old
TUXCONFIG files and reload them using the newly installed
If your Oracle Tuxedo system applications are distributed, the
MASTER and backup
MASTER machines must run the highest release of the Oracle 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 Oracle Tuxedo 12c Release 2 (12.1.3), Oracle 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 Oracle Tuxedo 12c Release 2 (12.1.3) only on Workstation clients, and you do not want to upgrade any of your Oracle Tuxedo system server machines to Oracle Tuxedo 12c Release 2 (12.1.3), you may do so. In other words, with any release level beginning with Oracle Tuxedo 6.5, Workstation clients may be intermixed freely in a configuration in which the
MASTER machines is running Oracle Tuxedo 6.5 or later.
This section provides supplementary installation instructions for customers using Oracle Jolt 12c Release 2 (12.1.3) with Oracle WebLogic Server 9.x, 10.x, or 12.1.x and Oracle Tuxedo 9.0, 9.1, 10.0, 10.3, 11.1.1.x, or 12.1.1. You can install the Jolt client personality software known as “Oracle Jolt for Oracle WebLogic Server” on an Oracle WebLogic Server 9.x, 10.x, or 12.1.x machine by copying the Jolt client personality software from an Oracle Tuxedo 12c Release 2 (12.1.3) machine to the target Oracle WebLogic Server machine. Of course, if the Oracle Tuxedo 12c Release 2 (12.1.3) machine and the target Oracle WebLogic Server machine are the same machine, you need only include the Jolt client library class files in your
CLASSPATH variable setting.
The “Oracle Jolt for Oracle WebLogic Server” client software consists of three JAR files:
joltwls.jar. Include these files in your
CLASSPATH variable setting.
For instructions on configuring the Jolt connection pool on Oracle WebLogic Server, see Using Oracle Jolt with Oracle WebLogic Server.