Wednesday, January 6, 2010

Installation of Oracle SOA on Weblogic 9.2: Part 2

As discussed in my last post (Steps to install Oracle SOA on Weblogic 9.2: Part 1) we will be moving ahead with the following topics in the second part of the above mentioned post.:

- Installation of Weblogic server 9.2 MP3
- Configuring Oracle SOA suite on Weblogic 9.2 MP3
- Installation of latest MLR patch
- Verification of Installation

4. Installation of Weblogic server 9.2 MP3

Many of the apps DBAs/SOA admins might not be familiar with Weblogic Application server.Weblogic was originally owned by BEA which was later acquired by Oracle. Post BEA acquisition Oracle has brought up its products on Weblogic. The latest Oracle Fusion Middleware 11g uses Weblogic as its Application server. As this is not the right post to talk much about Weblogic I will be coming up with exclusive Weblogic administration posts later.

Installation of Weblogic server 9.2 MP 3 is quite simple and straight. Please refer to the oracle install document for Weblogic 9.2:

All the install related documents can be obtained from the below link:

The installer provides you with two alternatives for installation ie COMPLETE and CUSTOM. You can choose COMPLETE type of installation.

In case you face issues or require the screen shots please let me know. I will be sending the screen shots via mail.

5. Configure SOA on Weblogic:

- Application of Hotpluggability patch on SOA for Weblogic:

Before configuring SOA to run on Weblogic a patch numbered 7337034(HOTPLUG: SOASUITE ON WEBLOGIC 9.2 - CHANGES FOR HOTPLUGGABILITY) needs to be applied on the SOA home. This step is mandatory and should not be skipped. In order to apply the patch please follow the below steps:

1. On the OS level issue the command export OPATCH_PLATFORM_ID=0.This environment variable if not set leads to failure in patch application.This is one of the mandatory prerequisites of the patch.
2. Stop the SOA application using opmnctl stopall
3. Apply the patch by navigating into the unzipped patch directory and issuing the command $ORACLE_HOME/OPatch/opatch apply.(Note: ORACLE_HOME should be set to the SOA Home or the directory path where you have installed SOA Application.
4. Check if the patch was applied successfully by the issuing $ORACLE_HOME/OPatch/opatch lsinventory.

- Creation of new directory structures inside BEA_HOME:

Create the following directory structures under the BEA_HOME.These directories will hold the domain related files for the SOA domain to be created in forthcoming steps:


(Note: user_projects directory may not be present and you have to create it)

- Edit the file

In order to configure SOA on Weblogic we need to run certain scripts. All these scripts and associated templates and files are provided by Oracle via a patch.The patch number is 7490612 and it can be downloaded from metalink.

The Oracle install guide for SOA with Weblogic 9.2 does not provide the number for this patch and refers to it as The zip file is originally named

Download the patch file on to any location (on the same server hosting Weblogic and SOA application) and unzip it. On unzipping the file you would get Weblogic_SOA10134 folder. Inside this folder you would get the Weblogic_SOA10134_Base folder which contains all the required templates, files, scripts etc, required to configure SOA on Weblogic.

1. Edit the file present inside Weblogic_SOA10134_Base directory. Let me describe the properties you would have to edit in the file:

# BEA_HOME is the path where Bea home directory exist.

(Dont get confused with BEA_HOME with WEBLOGIC_HOME. Both are different. BEA_HOME is the directory where multiple BEA products like Weblogic server, portal, Aqualogic etc can be installed. On the other hand Weblogic Home refers to the directory containing weblogic specific files ie $BEA_HOME/weblogic92)


# WL_HOME is the path where Weblogic is exist (usually it should be under bea home directory)

WL_HOME= /u01/bea /weblogic92

# JAVA_HOME is the path of jrockit folder inside your bea directory

( Do not mention jdk150_12 in place of jrockit_150_12 as both directories exist in BEA_HOME.Weblogic 9.2 uses jrockit_150_12)

JAVA_HOME/u01/bea /weblogic92/jrockit_150_12

# Set this property to 'YES' if you wish to create SOA Server in the new domain "SOADomain" In our case we set it to yes as we don’t have any pre existing Weblogic domains.


The domain home will contain all the files and folders related to the new SOA domain formed. We will discuss about Weblogic domains in our forth coming posts.


EXISTING_DOMAIN_NAME is the name of the existing domain where you wish to create SOA Server as a managed server

This property value should be set only when you set the CREATE_NEW_DOMAIN as NO.Hence in our case its useless as we are going to create a new domain.


ADMIN_SERVER_PORT is the port where the existing domain's Admin Server is runningThis property value should be set only when you se CREATE_NEW_DOMAIN as NO. So again its of no use for us.


NEW_ADMIN_SERVER_PORT is the port where you wish to run the Admin Server of the SOA domain to be created newly:


SOA_SERVER_NAME is the name of the managed server on which SOA application will run.This managed server will be a part of the new SOA domain formed by us and will be managed by the SO domain’s admin server.

SOA_SERVER_PORT is the PORT where OracleSOAServer (Managed server) will be running


APPS_HOME is the path where you wish to copy your applications and adapters that are required for OracleSOAServer


# SOA_HOME is the path where Oracle SOA Suite is Installed


# DB_URL is the url to connect to ORABPEL,ORAESB and ORAWSM schemas


#DB_BPEL_PASSWORD is the password for ORABPEL schema in database

#DB_ESB_PASSWORD is the password for ORAESB schema in database

#DB_OWSM_PASSWORD is the password for ORAWSM schema in database

#PROXY_HOST is set to true if any proxy server is existing and running.Set this to false else you would get an error during AIA installation.We will discuss in our future posts.


Comment the following:

Keep these parameters as they are:


-Set the environment variables:

Once you are done with editing the file, save and exit from the vi editor. Set the environment variables as mentioned below. If not set the configuration script wont work:

Make the following entries to the bash_profile of the user owning the SOA/Weblogic application:

export ORACLE_HOME=/u01/soa_home

export WL_HOME=/u01/bea/weblogic92
export BEA_HOME=/u01/bea
export JAVA_HOME=/u01/bea/jdk150_12


WL_HOME is the directory inside BEA_HOME where Weblogic server is installed

BEA_HOME is the directory under which all the BEA products are installed

JAVA_HOME is the jdk directories present under BEA_HOME.Dont specify the jRockit directory.

Once you are done with this export the bash by issuing the command . ./bash_profile

- Run the script:

Once you modify the file and set the required environment variables go to the Weblogic_SOA10134/Weblogic_SOA10134_Base directory and run script.

Note : Weblogic_SOA10134 directory is the directory obtained after unzipping patch#

The script does the following:

1. Creates a new Weblogic Domain named SOAdomain(Name depends on what you specify in the file)

2. Creates a managed server under the newly created domain called OracleSOAserver.(Name depends on what you specify in the file)

3. Deploys Oracle SOA server on the managed server OracleSOAserver
4. Creates and configures the required files for admin server of the new SOAdomain in order to start/stop/manage managed server OracleSOAserver.

Note: The script in between asks you for a username and password for the new domain ie SOAdomain.Provide the account details and do remember it/store it.

The script must display “BUILD SUCCESSFUL” message indicating the successful integration of SOA with Weblogic.

Once this is done you can go ahead and shut doun the oc4j processes which are no longer required.This can be done using ./opmnctl stopall command.

- Start the node manager:

The node manager process ini Weblogic is responsible for managing managed servers on behalf of the domains admin server. When you start the node manager, it creates a mapping to the SOA domain, which enables you to start and stop OracleSOA server managed server remotely using admin console.

In order to start the node manager run the script present in the $WEBLOGIC_HOME/server/bin directory.Run the script as a background process because if you don’t do so it getts killed once you close the os session from which you ran it.This can be done by the following command:

$WEBLOGIC_HOME/server/bin/ &

The node manager sh should start without any errors displaying all its domains mappings. Though it runs fine for me on Linux 4.On Linux 5.4 we facec some issue as mentioned below:

Issue: weblogic.nodemanager.common.ConfigException: Native version is enabled but node manager native library could not be loaded


+ CLASSPATH=/u01/bea/patch_weblogic923/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/u01/apps/oracle/product/bea/WLI92/jrockit_150_12/lib/tools.jar:/u01/apps/oracle/product/bea/WLI92/weblogic92/server/lib/weblogic_sp.jar:/u01/apps/oracle/product/bea/WLI92/weblogic92/server/lib/weblogic.jar:/u01/apps/oracle/product/bea/WLI92/weblogic92/server/lib/webservices.jar::/u01/apps/oracle/product/bea/WLI92
+ export CLASSPATH
+ export PATH
+ cd /u01/apps/oracle/product/bea/WLI92/weblogic92/common/nodemanager
+ set -x
+ '[' '' '!=' '' ']'
+ '[' '' '!=' '' ']'
+ /u01/bea/jrockit_150_12/bin/java -jrockit -Xms128m -Xmx256m -Xverify:none -Dweblogic.nodemanager.javaHome=/u01/apps/oracle/product/bea/WLI92/jrockit_150_12 weblogic.NodeManager -v

weblogic.nodemanager.common.ConfigException: Native version is enabled but node manager native library could not be loaded
at weblogic.nodemanager.server.NMServerConfig.initProcessControl(

+ set +x

This issue occurred while trying to start the node manager after script was run successfully during the Weblogic integration phase.


Go to $WL_HOME/common/nodemanager

Check for file

If not present make one by referring to past installations on appsnet.

Just modify the NativeVersionEnabled property to false in file, that will solve the pb. If you dont have a property in file add one.

Sample file:

#Wed Sep 16 13:40:21 IST 2009
DomainsFileEnabled=true ListenAddress=

- Start weblogic server:

$BEA_HOME/user_projects/SOADomain/bin/ &

The server on starting must display “Server started in running mode”

- Start the managed server:

1. Login to Weblogic admin screen [APPLICATION_HOSTNAME]:8001/console

2. Enter username/password as the one you gave during running the script.

3. Click on Environments->Servers->OracleSOAserver

4. Cick on control tab

5. Click on start to start the server. The server should take some 3 minutes to start.

- Verification of URLs:

Verify the BPEL, ESB & OWSM Url’s


You can login using the same admin passwords used for Weblogic.

- Apply MLR#8 Patch:

Once your SOA on Weblogic instance is up and running you can apply the latest MLR patch available.In my case I applied MLR 8 patch.The application process is pretty simple and can be done using the readme guide.Do perform the pre and post steps mentioned in thye readme of the patch.

Hence here we complete the post. Our Oracle SOA on Weblogic 9.2 MP3 MLR#8 instance is ready for use. The same instance will now be used for AIA 2.4 installation. I will be writing about the AIA 2.4 Installation on SOA with Weblogic in my forthcoming posts.

Please let me know if this post was helpful and what other technologies would you like to hear about.

Signing off…Happy Learning…
Why try fitting in when I am born to stand apart….

Installation of Oracle SOA on Weblogic 9.2: Part 1

Oracle SOA suite installer has been traditionally available with Oracle Application Server. Post BEA acquisition Oracle has been trying to run most of its products on Weblogic and SOA suite 10g is no different. I will be writing about all the steps and related issues for installing Oracle SOA with Weblogic 9.2.

We will start with single server installation. In the coming forth posts I will be talking about Oracle SOA on Weblogic High Availability/Clustered installations. Though the install guide for Oracle SOA/ Weblogic 9.2 is available ,the guide does not mention certain patch numbers and steps. I would try to jot down all those missing steps too. Also I will be discussing some issues we faced during installation.

In order to install Oracle SOA suite on Weblogic 9.2 MP3 we basically need to follow the below steps:

1. Creation of SOA related schemas on Database
2. Installation of Oracle SOA Suite Basic for OC4J
3. Upgrade of Oracle SOA suite to version
4. Installation of Weblogic server 9.2 MP3
5. Configuring Oracle SOA suite on Weblogic 9.2 MP3
6. Installation of latest MLR patch
7. Verification of Installation

Let me discuss all these steps in detail:

1. Creation of SOA related schemas on Database.

The database used by SOA suite is also known as Dehydration store. The database stores schemas related to SOA suite. The major schemas stored are orabpel, oraesb, orabpel etc. In case of AIA Foundation pack installation the database would also store the aia schema.

- In order to install SOA suite a 10g R2 database needs to be in place.(For other versions check the certification matrix on metalink).

- Install the database and make sure you configure the listener. The listener should be up and running without issues and so should be the database.

- You should have details like hostname for the Database, Database listener port and Database SID

- Create a user with dba privileges or else you can use the sys user. In case you are using sys user make sure you procure the password from the DBAs

- Once you are ready with all the database related prerequisites as mentioned above its time to create the SOA related schemas in the database.

- For this we need to run the file that is provided along with the SOA installer itself.

- The file can be found in /install/soa_schemas/irca/ location where is the directory you get after unzipping the SOA Installer that you have downloaded from oracle site.

- Go to the /install/soa_schemas/irca/ loacation and run the schema creation script ./

- The installer would prompt for DB info like hostname for the Database, Database listener port ,Database SID, user with DBA priviledges and its password.Enter the required info and proceed.

- The script then would create the orabpel/oraesb/orawsm schemas and also would prompt you to assign the passwords for the schemas formed. Make sure you remember/store the passwords for future use. That’s very important!

- Now the Database configuration is complete and you are ready to start SOA installation.

- Sample irca script run:

[soauser@myappserver irca]$ pwd
[soauser@myserver irca]$./
Integration Repository Creation Assistant (IRCA)
(c) Copyright 2006 Oracle Corporation. All rights reserved.

Enter database "host port serviceName" [localhost 1521 orcl]: 1525 aia
Enter sys password:
Running IRCA for all product(s):
connection=" 1525 aia", , orabpelUser=ORABPEL, esbUser=ORAESB, orawsmUser=ORAWSM

Validating database ...
Validating database character set ...

Running prerequisite checks for ORABPEL ...
Enter password for ORABPEL:
Loading ORABPEL schema (this may take a few minutes) ...

Running prerequisite checks for ORAESB ...
Enter password for ORAESB:
Loading ORAESB schema (this may take a few minutes) ...

Running prerequisite checks for ORAWSM ...
Enter password for ORAWSM:
Loading ORAWSM schema (this may take a few minutes) ...

INFO: ORABPEL schema contains 225 valid objects.

INFO: ORAESB schema contains 180 valid objects.

INFO: ORAWSM schema contains 90 valid objects.

IRCA completed.
Please check for any ERROR message above and also check the log file
irca2009-10-08_01-56-29PM.log for any error or other information.

- ORABPEL : xxxxxx
- ORAESB : xxxxxx
- ORAWSM : xxxxxx

- Incase you need to change/reset the SOA schema password please follow the below link:

- In case you need to re install the SOA suite again on the same DB, make sure you re run the script again. This will overwrite the existing SOA schemas and form new ones.

2. Installation of Oracle SOA Suite Basic for OC4J:

Now we are ready to start the installation of Oracle SOA Suite Basic for OC4J. For newbies this term can be quite confusing. Let me explain

Oracle SOA Suite comes with two install options Basic and advanced.

We have to choose the Basic Install option which is a mandatory requirement if you intend to install SOA on Weblogic Application Server.


The following components are installed during the Basic Installation

1. Oracle Containers for J2EE
This component provides a complete Java 2 Enterprise Edition (J2EE) environment for developing Java applications.

2. Oracle SOA Suite
This component provides Oracle SOA Suite, which enables services to be created, managed, and orchestrated into composite applications and business processes. Oracle SOA Suite includes Oracle BPEL Process Manager, Oracle Enterprise Service Bus (ESB), Oracle Web Services Manager (OWSM), and Oracle Business Rules.

3. Oracle Enterprise Manager 10g Application Server Control
This component is used for Web-based management of Oracle Application Server.

4. Oracle Process Manager and Notification Server
This component provides process control and monitoring for Oracle Application Server instances and their components.

5. OC4J Java Single Sign-On
This component allows users to log in to all SSO-based applications with a single username and password.

Installation of SOA suite:

The installations of SOA suite is pretty straight and for instructions please refer to the install guide from Oracle. Make sure you choose the basic install.

Common issues during SOA suite Install:

On some platforms like Linux 5.4 one might encounter problems like prerequisite check failed. In order to resolve this proceed with following steps:

1. Run the pre-check manually
./runInstaller -executeSysPrereqs

2.Run the installer in ignore Warnings mode because of the Linux OS version – 5.4 is not known by the installer.
./runInstaller –ignoreSysPrereqs

Validation of Installed SOA:

Once you have successfully installed SOA suite Basic you can check the following urls:

Enterprise Manager Console: http://:8888/em
BPEL Console: http://:8888/BPELConsole
ESB Console : http://:8888/esb

- Here is the hostname of the machine where you have installed SOA application. For eg:
- 8888 is the default port used by SOA suite.

Once you are done with all these steps its time to upgrade the SOA to version.

3. Upgrade of Oracle SOA suite to version

Upgrade of SOA suite can be done by application of patch # 7272722.This patch is applied through Oracle Universal Installer (GUI).The process consists of two steps:

1. Upgrade of SOA schemas in the database:
Before applying the upgrade patch make sure you upgrade the BPEL and ESB schemas present in the database. This can be done using SQL scripts provided along with the 7272722 upgrade patch.

1. Shutdown the SOA application (Go to $SOA_HOME/opmn/bin directory and issue the command ./opmnctl stopall)

2. Login to the database as orabpel user and run the script <7272722_Upgrade_Patch>/Disk1/install/soa_schema_upgrade/bpel/scripts/upgrade_10131_10134_oracle.sql

3. Now logout of the database

4. Login to the database as oraesb user and execute the sql script <7272722_Upgrade_Patch>/Disk1/install/soa_schema_upgrade/esb/sql/oracle/ upgrade_10133_10134_oracle.sql

5. Schema upgrade is complete.

6. If you miss this step and upgrade the SOA application you will not be able to access the BPEL screen. If you have such an issue simply shut down the SOA application and run the upgrade scripts as mentioned above. Restart the application and check the logins.

2. Upgrade the SOA Application by applying patch 7272722

Application of upgrade patch is quite straight forward. Please refer to the readme provided with the patch. In case you require the screen shots please mail me for it.

Here we complete our session on Steps to install Oracle SOA on Weblogic 9.2: Part 1 . In the next part we will be covering important topics like

- Installation of Weblogic server 9.2 MP3
- Configuring Oracle SOA suite on Weblogic 9.2 MP3
- Installation of latest MLR patch
- Verification of Installation

Stay tuned….and Happy Learning :-)


Why try fitting in when Iam born to stand apart...!!!