A Upgrade Path for SOA Suite 10.1.3.3 on WebSphere 6.1.0.15 Installation

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

1. Stop the SOAServer server.

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:

   Disk1\install\soa_schema_upgrade\bpel\scripts\upgrade_10133_10134_oracle.sql

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

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

4. Apply Opatch for Oracle SOA Suite 10.1.3.4 on WebSphere 6.1.0.15.

   Refer to Step 6: Apply Opatch for Oracle SOA Suite 10.1.3.4 on WebSphere 6.1.0.15 for more information on applying the opatch.

5. Modify the installation properties in the WAS_SOA10134_Installables\upgrade.properties file.

   Refer to Step 4 of Step 7: Install and Configure IBM WebSphere Application Server Version 6.1.0.15 section.

   Modify the following values as per the environment. Sample values are mentioned below:

   • CELL_NAME=[hostName]Cell01

   • NODE_NAME=[hostName]Node01

   • PROFILE_NAME=AppSrv01

   • SERVER_NAME=SOAServer

   • WAS_HOME=C:/Progra~1/WebSphere/AppServer

   • DMGR_HOST=[DMGR_HOSTNAME]

   • DMGR_SOAP_CONNECTOR_PORT=[DMGR_PORT]

   • SOA_HOME=C:/product/10.1.3.1/OracleAS_5

   See Also:

   Refer to Step 4 in (UNKNOWN STEP NUMBER) Installation and Configuration section for more details.

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

6. Run the following script from WAS_SOA10134_Installables folder at the operating system command prompt:

   For...	Run...
   Windows XP	upgradeSOA.bat -secure
   Linux	upgradeSOA.sh -secure

   
   

   This script upgrades the existing Oracle SOA Server. 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 <SOA_HOME>/WebSphere/10.1.3.3/backup/${DATE_DIR}/.

   Note:

   The J2C Connection Factories that existed before the upgrade will no longer be available after the upgrade. The corresponding resouces.xml are backed up in the directory mentioned above. These will have to be recreated by the user after the upgrade. Refer to Configuring J2C Connection Factories for Adapters in WebSphere.

   The configuration scripts mentioned in the table execute in two parts:

   The first part creates all the artifacts required for the SOAServer such as DataSources, ConnectionFactories, and Shared-Libraries on the WebSphere Application Server. (On Linux environments, this part needs to be executed as a 'root' user.) The second part of the script modifies configuration values under SOA_HOME. (On Linux environments, this part needs to be executed as a 'non-root' user.)

   After you execute the script, this script prompts you to enter the WebSphere username and password. If the authentication is successful, then the Deployment Manager artifacts will be installed/configured into WebSphere application server.

   Note:

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

   • While running the upgradeSOA.bat or upgradeSOA.sh file, set the environment variable WAS_HOME to the WAS folder. For example, C:\WAS in Microsoft Windows or /opt/IBM/WebSphere in Linux.

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

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

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

   • The above scripts can be run without the "-secure" option, if security is disabled in the WebSphere environment.

   • On Linux environments, the above script needs to be executed as a 'root' user. Also, the script will prompt for the SOA username while executing the second phase of the configuration.