A Upgrade Path for SOA Suite 10.1.3.3 on WebLogic 9.2 Installation

The steps to be followed to upgrade a SOA Suite 10.1.3.3 on WebLogic 9.2 installation to 10.1.3.4 are as follows:

1. Stop the managed servers and admin servers in the SOA domain.

2. Apply SOA Suite Patchset 10.1.3.4 on the existing SOA Suite 10.1.3.3 installation (SOA_HOME).

   Refer to Step 5: Apply SOA Suite Patchset 10.1.3.4 of the Installation and Configuration section.

3. Upgrade SOA Schemas to 10.1.3.4.

   Run the 10.1.3.4 SOA Schema upgrade scripts for orabpel/oraesb schemas that are available in the SOA Suite 10.1.3.3 Patchset Installation pack.

   Execute the following SQL script against ORBPEL schema to upgrade the ORABPEL schema:

   install\soa_schema_upgrade\bpel\scripts\upgrade_10133_10134_oracle.sql

   Execute the following SQL script against ORAESB schema to upgrade the ORAESB schema:

   install\soa_schema_upgrade\esb\sql\oracle\upgrade_10133_10134_oracle.sql

4. Apply Patch for Oracle SOA Suite 10.1.3.4 on WebLogic 9.2.

   Refer to Step 6: Apply Patch for Oracle SOA Suite 10.1.3.4 on WebLogic 9.2 for more information on applying the patch.

5. Modify the installation properties in the Weblogic_SOA10134_Base\SOADomain.properties file.

   Refer to Step 3 of Step 7: Install and Configure WebLogic Server Version 9.2 section.

   Choose the following values to retain the existing domain which contains SOA Suite 10.1.3.3 on WebLogic 9.2

   • CREATE_NEW_DOMAIN = NO

   • DOMAIN_HOME: path of the existing domain's parent directory

   • EXISTING_DOMAIN_NAME: name of the existing domain used for SOA Suite 10.1.3.3

   • ADMIN_SERVER_PORT: port where the existing domain's admin server is running

   Enter appropriate values for other properties in the SOADomain.properties file.

6. Start the Admin server in the SOA Domain.

7. Run the following script from Weblogic_SOA10134_Base folder at the operating system command prompt:

   For...	Run...
   Windows XP	upgrade.bat
   Linux	upgrade.sh

   
   

   This script upgrades the existing domain, which contains the admin server (AdminServer) and Oracle SOA Server managed server (oracleSOAServer). The SOA applications are redeployed and adapter binaries are upgraded to 10.1.3.4. Also, the old SOA applications and adapters will be backed up under <APPS_HOME>/soaApps_backup/<date>.

   Note:

   • This script will prompt for the password of the default 'weblogic' user at the commad prompt.

   • While running the upgrade.bat or upgrade.sh file, set the environment variable BEA_HOME to the bea folder. For example, C:\bea in Microsoft Windows or /home/userfolder/bea in Linux.

   • Based on the BEA_HOME variable value, the setup script assumes the jdk folder name to be jdk150_06 and appends this value to BEA_HOME, sets it to the JAVA_HOME variable, and checks for the path existence in the file structure. For example, JAVA_HOME=BEA_HOME/jdk150_06.

     If JAVA_HOME path does not exist, then setup file throws a message asking to set JAVA_HOME before running the setup file.

   • Based on the BEA_HOME variable value, the setup file assumes the WebLogic folder name is weblogic92 and appends this value to BEA_HOME, sets it to the variable WL_HOME, and checks for the path existence in the file structure. For example, WL_HOME=BEA_HOME\weblogic92.

     If WL_HOME path does not exist, then setup file throws a message asking to set WL_HOME before running the setup file.

   • Setting WL_HOME as environment variable sets the variable WL_JAR_PATH, which contains the following value: WL_HOME\server\lib\weblogic.jar.

     The WL_JAR_PATH is used to load the WebLogic ant task class weblogic.ant.taskdefs.management.WLSTTask. The setup script assumes that weblogic.jar is available at the WL_HOME\server\lib folder.