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.
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 12
c 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 on page 4‑6.
1.
|
Back up the RM file to a temporary location. The RM file contains database vendor-specific settings that are used by commands such as buildtms and buildXAJS. It is located in the tux_prod_dir/udataobj directory, where tux_prod_dir is the directory in which you installed the Oracle Tuxedo or Oracle WebLogic Enterprise software.
|
2.
|
Back up the tuxwsvr.ini and webgui.ini files to a temporary location. These files contain customized initialization settings for the Oracle Tuxedo Administration Console server and GUI. The tuxwsvr.ini file is located in the tux_prod_dir/udataobj directory, and the webgui.ini file is located in the tux_prod_dir/udataobj/webgui directory.
|
3.
|
Back up the CATNAMES, jrepository, and jrly.config files. The CATNAMES file is located in the tux_prod_dir/locale directory. The jrepository and jrly.config files are located in the tux_prod_dir/udataobj/jolt directory structure.
|
Note:
|
The Oracle Tuxedo procMGR service is called IPC Helper in Oracle Tuxedo 6.5 or Oracle WebLogic Enterprise 5.1.
|
•
|
In order to allow a Tuxedo 12c Release 2 (12.1.3) server to interoperate with Tuxedo 6.5 software, the Tuxedo 12 c Release 2 (12.1.3) server servopts -t option must be specified. The server may be a workstation listener (WSL) process (where the servopts -t option 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 your Tuxedo 6.5 COBOL program calls TPINITIALIZE(), you must set the TM_CBL_IGNORE_CONTEXT environment 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.
|
•
|
In this release, 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.
|
Once you have finished migrating the MASTER to Oracle Tuxedo 12
c 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 12
c 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 12
c Release 2 (12.1.3) machine with an old-release
MASTER, the
UPGRADE file shown in
Hot-Upgrade Example on page 4‑8 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.
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%/
$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 12
c Release 2 (12.1.3) application should be available on each machine.
This advice is not a requirement, but a recommendation.
If you already have DMTLOG and
TLOG, make sure that no pending transaction logs are in them before shutting down the application, and keep in mind that removing the
DMTLOG and
TLOG (if they exist) after the application is shut down.
•
|
The MODEL option in the configuration must be set to MP.
|
•
|
The MIGRATE option in the configuration must be set.
|
6.
|
Migrate the MASTER machine running the old release to the backup MASTER machine running Oracle Tuxedo12 c Release 2 (12.1.3).
|
•
|
A machine called MACH1 that is configured as the MASTER and that runs an old release
|
MACH1> tmshutdown -B MACH2 -l MACH2
MACH1> Run tmconfig to reset the APPDIR, TUXCONFIG, TUXDIR for MACH2
MACH2>
Kill tlisten process
MACH2>
Load Tuxedo 12cR2 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 Tuxedo 12cR2 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 Tuxedo 12cR2 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 Tuxedo 12cR2 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 Listing 4‑1 from a Windows platform, be sure to stop the Oracle Tuxedo procMGR (called IPC Helper in Oracle Tuxedo 6.5 or Oracle WebLogic Enterprise 5.1) service after stopping the tlisten process and to start the Oracle Tuxedo procMGR service before starting the tlisten process.
|
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 12
c Release 2 (12.1.3), Oracle Tuxedo 6.5 or later may still be used on other machines.
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 12
c Release 2 (12.1.3) machine to the target Oracle WebLogic Server machine. Of course, if the Oracle Tuxedo 12
c 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.