Installing SOA 10g ( – Fusion Middleware


This is my first post under Fusion Middleware technology. In this post we will see how to install SOA and carry out the basic validation (sanity check) for the installed components.

Pre-Installation Steps

You can download SOA software from OTN. This software version available for download is Once we install SOA, we will upgrade the same to using patchset. SOA patch set can be downloaded from metalink. The patchset checkin number is 7272722.

Before starting the SOA installation we need to do some pre-installation task. Every SOA suite installation needs a database (Oracle). Also we need to create 3 schemas in that database before we proceed with runInstaller of SOA suite.

Please carry out a installation of Oracle database server software and create a simple database. Also you need to have database version 10g R2 ( for SOA installation.

Once the database is created you need to run shell script. This script will be present in the software dump downloaded from OTN.

After unzipping the software in a directory, you can navigate to the following location


Here you will find running this script, make sure that you set ORACLE_HOME and ORACLE_SID of the database you have installed. If the database is not installed on the same host, then you need to login to the server where database is installed and then run this script.

Run this script as shown below. You need to provide hostname, port # and database SID of the database you have installed.

-bash-3.00$ sh
Integration Repository Creation Assistant (IRCA)
(c) Copyright 2006 Oracle Corporation. All rights reserved.

Enter database “host port serviceName” [localhost 1521 orcl]: rws60066rems 1618  obieebam
Enter sys password:
Enter sys password: Running IRCA for all product(s):
connection=”rws60066rems 1618  obieebam”, , orabpelUser=ORABPEL, esbUser=ORAESB, orawsmUser=ORAWSM

Validating database …
Validating database character set …
WARNING: The target database character set is WE8ISO8859P1
For multi-byte support, the AL32UTF8 character set is recommended.

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:
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
/tmp/irca2008-12-31_01-54-01AM.log for any error or other information.

Also while running the script you need to provide password for sys, orabpel, oraesb and orawsm. It will set the password for orabpel, oraesb and orawsm.

Once this is down, you can start with the installation task of installing SOA.

Installation Step

From the SOA software dump, start the runInstaller using following command.

-bash-3.00$ ./runInstaller -invPtrLoc $HOME/oraInst.loc


Screen 1) Advanced Installation (For more option and flexibility go for Advanced installation)


Screen 2) Provide the path for inventory location


Screen 3) select “J2EE Server, Web Server and SOA Suite” for complete installation.


Screen 4) Verifying the system requirements


Screen 5) Database connection Information – You need to provide the connection information for the database you have installed before starting the SOA installation


Screen 6) Database Schema Passwords – Provide the database schema passwords for ORABPEL, ORAESB and ORAWSM. These will be same as what provided while running script in  pre-installation step.


Screen 7) You can provide the file staticports.ini for custom ports, or you can accept the default ports.


Screen 8) Administration Settings – Provide the name for AS Instance and OC4J instance. You also need to set the password for administrator.


Screen 9) Cluster Topology Configuration – This is requrired for advanced installation in case if we have to configure a standby or a load balancing site. For this installation we are ignoring this step.


Screen 10) This screen will show the installation summary. You can click on Install.


At the end of installation it will ask you to run as a root user. After you run, you can click on OK on that dialog box. Configuration assistants will start, which will install all the components.

SOA gets installed in $HOME/product/ direcory

Following are the different URLs that will be available

Enterprise Service Bus :

Enterprise Manger :

BPEL Console :

Worklist Application :

OWSM Control :

Where 7777 is your HTTP port.

This version for SOA is Now we need to upgrade the same to Following are the steps for the same.

Upgrading the SOA to

Download and unzip the patch 7272722. After unziping you will get Disk1 and Disk2.

Before running runInstaller you need to carryout some pre-installation task.

Pre-Installation Step

Step 1) From the base directory where the patch was unziped, navigate to following directory

cd /base_dir/Disk1/install/soa_schema_upgrade/bpel/scripts

and run script upgrade_10131_10134_oracle.sql by connecting to SOA database as orabpel user

Step 2) From the base directory where the patch was unziped, navigate to following directory

cd /base_dir/Disk1/install/soa_schema_upgrade/esb/sql/oracle

and run script upgrade_10133_10134_oracle.sql by connecting to SOA database as oraesb user

Installation Task

Go to Disk1 and start the runInstaller.

./runInstaller  -invPtrLoc $HOME/oraInst.loc


Screen 1) Make sure you select the correct ORACLE_HOME here. This should be your SOA Oracle Home.


Screen 2) Provide the oc4jadmin password you selected during SOA installation


Installer will shutdown the SOA services. Click on OK and wait for some time.


Screen 3) After shutting down all services, you will see the summary screen. Click on Install.

At the end of installation it will ask you to run as a root user. Once that is done, it will start with configuration assistants.


After the installation you can bring up all the services. This completed SOA installation.

Hope this helps !!


Forms Runtime Diagnostics – Oracle Apps 11i

Many times we face issue with the form and we have to carry out the debugging at runtime as we give input to the form. This kind of situations can be handeled easily using FRD (Forms Runtime Diagnostics). This feature is available in 11i as well as in R12. In this post we will see how to enable the diagnostics and view the trace files in Oracle Apps 11i. You can also check one of my old post about generating forms trace files in Oracle E-Business Suite R12.

The following method applies to 11.5.10 and above.

Step 1) Check the value of “ICX:Forms launcher” profile option.

Current value set for this profile in my environment is :

Step 2) Append the ICX:Forms launcher profile value with the “Forms Runtime Diagnostics (FRD)” variables. Following are the different variables available in FRD

  • record=all
  • config=debug
  • log=<logfile path>

So the new “ICX: Forms Launcher” profile value will become :

Step 3) Close the forms and then go to the home page and open the form you want to work upon. No need to bounce the forms services.

Once you open the form you will see the dialog as shown below


Also you will be able to see the trace file at the location given by variable “log=” In my case the trace file is present in /tmp directory.

The content of the trace file is as shown below


Forms Runtime Performance/Diagnostics Collection
File Name: /tmp/avdeo_frd.log
Process ID: 29403
Client IP:
Forms 6.0 (Forms Runtime) Version (Production)
PL/SQL Version (Production)
Oracle Virtual Graphics System Version (Production)
Oracle Multimedia Version (Production)
Oracle Tools Integration Version (Production)
Oracle Tools Common Area Version
Oracle CORE Version – Production

TSE Startup Time : 1230616643390353000
TSE Handshake Duration  : 1230616643393408000
# C

Opened file: /slot/ems1978/appmgr/hz1mq100appl/fnd/11.5.0/forms/US/FNDSCSGN.fmx

ON-LOGON Trigger Fired:

State Delta:
GEOMETRY   100,250:4000,400



If you don’t give the variable “log=” in “ICX:Forms Launcher” profile option then the trace file will be located in $FORMS60_TRACE_PATH location.

Hope this helps !!