Category Archives: SOA

out of Space for Code Cache for Adapters

If you are facing issues like ‘Out of Space for Code Cache for Adapters’ in Jdeveloper then you must do this changes as discussed in this forum post

Set – JVM Options : XX:ReservedCodeCacheSize=128m in

SOA suite installation white paper

Soa Suite installation white paper is available for download here

installing soa-suite in linux64

Recently I got the following issue while installing Soa Suite

in linux64.

I tried the solution specified here but it was not working and it keeps giving the error

[xxx@indl144224 linux64]$ ./runInstaller -jreLoc /scratch/software/mw_local/FMWTOOLS_MAIN_GENERIC_101104.0028.2/xxx/mw_home_standalone/jrockit_160_20_D1.1.0-18/Starting Oracle Universal Installer...
Checking if CPU speed is above 300 MHz.    Actual 2327 MHz    Passed
Checking Temp space: must be greater than 150 MB.   Actual 2481 MB    Passed
Checking swap space: must be greater than 500 MB.   Actual 8273 MB    Passed
Checking monitor: must be configured to display at least 256 colors.    Actual 16777216    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2011-01-19_04-21-22PM. Please wait ...
[xxx@indl144224 linux64]$ java.lang.UnsatisfiedLinkError: Can't load library: /tmp/OraInstall2011-01-19_04-21-22PM/oui/lib/linux64/
at java.lang.ClassLoader.loadLibrary(
at java.lang.Runtime.load0(
at java.lang.System.load(
at oracle.sysman.oii.oiip.osd.unix.OiipuUnixOps.loadNativeLib(
at oracle.sysman.oii.oiip.osd.unix.OiipuUnixOps.<clinit>(
at oracle.sysman.oii.oiip.oiipg.OiipgEnvironment.ssgetCurrentGroupOfUserux(
at oracle.sysman.oii.oiix.OiixEnvironmentOps.ssgetCurrentGroupOfUserux(

So i tried the following thing and it worked

[xxxn@indl144224 linux64]$ linux32 bash
bash-3.2$ pwd
bash-3.2$ cd ..
bash-3.2$ lsaix  hpia64  hpunix  linux  linux64  solaris  win32  win64
bash-3.2$ cd linux
bash-3.2$ ./runInstaller -jreloc /scratch/software/mw_local/FMWTOOLS_MAIN_GENERIC_101104.0028.2/xxx/mw_home_standalone/jrockit_160_20_D1.1.0-18/

SOA – a quick view

What is SOA?

SOA is standard based method of system development and integration

What are the benefits?

  • Reusability
  • Integration
  • Interoperability
  • Agile development
  • Scalability
  • Cost Efficient

What are all the ways to implement services?

  • Point to point approach
  • Vendor specific implementation
  • Web services
  • SCA-style implementation

What are Services?

  • Building blocks of SOA
  • Interface and message structure definitions
  • Standard protocol for interoperability

What are SOA standards?

What is SCA [Service Component Architecture]?

SCA provides a programming model for building applications using SOA

What are the difference between SOA and SCA?

  • SOA is an approach or implementation style and SCA uses SOA to build a composite application
  • SOA is architectural style but SCA is assembly model and defines/design

What are the elements of SCA?

What is SDO [Service Data Object]?

  • Representation of data source in XML format and specifes methods to create, delete and modify data
  • Simplify and unify the way in which applications handles the data

What is EDN [Event Driven Network]?

  • To handle asynchronous messaging arising from a business event
  • Supports publish and subscribe model
  • Aligns with Event driven Architecture [EDA]

Quick look at the mediator component

What is Oracle Mediator Component?

Mediator is the load balancer which can route, filter, validate and transform data from the service providers to external references

  • Route: determines the service component to which the message has to be sent
  • Validate: validate the incoming payload information
  • Filter: Filters the payload for specific information before routing it to the specific component
  • Transformation: Transforms data from one xsd format to another using XSL Mapper

the code specific to mediator in the composite.xml will be like

<component name="ConversionMediator">
<implementation.mediator src="ConversionMediator.mplan"/>

Mediator component in the design view consist of

Name: Name of the mediator component

WSDL Url: the service provider URL

Port Type: The port on which the request message is sent

Resequence Level: Whether the sequencing of the incoming message will be taken care commonly[Operation] or for each component [component]

Priority: priority set for parallel routing rule

validate XSD: validate the schema for the incoming message

Callouts: specifies java classes for extra logic in programmatic way


Standard -> the incoming message will be sequence based on the sequence id

Best Effort -> sequencing based on the best possible way

FIFO ->  sequencing of message based on the time of the arrival of the message

Static Routing:

routing rule based on static information

Filter -> content based or header based routing

Transform -> using xsl mapper file

validate -> using schematron file

Assign -> assign header,payload values of the message from source to target

sequential -> rule executed one after the other

Parallel -> rule executed in parallel. Priorities are given to the parallel rule

Dynamic Routing:

routing rule based on external rule which keeps changing based on the invocation context

Fault Handling: This is handled in composite or at the component[mediator] level by specifying fault policies

Event Handling: A mediator can subscribe or publish an event

Soa Suite 11gR1 ( installation guide for Windows

The complete Soa suite installation guide is uploaded here

Complete fusion middleware documents are available at

System requirements and specifications


  • Processor
  • Operating System
  • Disk Space
  • Physical Memory
  • Browser
  • JDK

Complete requirments are available at

Download the files

All software can be downloaded from the Fusion Middleware 11gR1 PS2 download page (also known as the FMW download page)

Installation procedure [RCU version]

  1. Oracle DB (OracleXE Univ)
  2. Weblogic Server 10.3
  3. Repository Creation Utility for DB schema
  4. Soa Suite
  5. Soa Suite patchset installer for
  6. Jdeveloper
  7. Soa Extension (Oracle SOA Composite Editor)
  8. Weblogic domain creation

If you face any problem in creating the DB schema using RCU then please download the RCU and follow this installation process. Also you will face some issues in creating the Weblogic db schema for soa_infra during weblogic domain creation

  1. Oracle DB (OracleXE Univ)
  2. Weblogic Server 10.3
  3. Repository Creation Utility for DB schema
  4. Soa Suite
  5. Jdeveloper
  6. Soa Extension (Oracle SOA Composite Editor)
  7. Weblogic domain creation (domain creation will fail for soa_infra stating a version problem if you have used RCU
  1. Soa Suite patchset installer for




WebLogic Server



Repository Creation Utility


If repository tool is creating some kind of problem while creating DB schema then please use RCU of [if you are using then please refer to section X for the installation order]


SOA Suite & Patch

You have to have Soa Suite installed in your system before installing the patchset installer BPM)




SOA Extension for JDeveloper

You can install the extensions directly from inside JDeveloper through the “Help -> Check for Updates” menu option which is the recommended way install extensions. If you can’t connect to the Internet from your JDeveloper, you can directly download JDeveloper extensions from this page, and point the Check for Updates wizard to the local file you have downloaded.

Note: for other extensions please refer

Setting up the database

Run the following commands to increase the process limits (Only for Oracle XE)

sqlplus sys/welcome1@XE as sysdba
SQL> show parameter session
SQL> show parameter processes
SQL> alter system reset sessions scope=spfile sid='*';
SQL> alter system set processes=200 scope=spfile;
SQL> shutdown immediate
SQL> startup
SQL> show parameter session
SQL> show parameter processes

Weblogic Domain Creation

refer this link

Server URLS

The link for the Weblogic console

http://localhost:7001/console (login with weblogic/welcome1)

The link for the EM console

http://localhost:7001/em (login with weblogic/welcome1)

The link for the SOA worklist app


The link for B2B


The link for BAM (must use IE browser)


Starting the servers

Go to the domain directory and type startWebLogic.cmd

D:\Oracle\Middleware\user_projects\domains\soa_infra_domain> startWebLogic.cmd

On the same command line press ctrl+c or goto the bin directory of the domain folder and type stopWebLogic.cmd

D:\Oracle\Middleware\user_projects\domains\soa_infra_domai\bin> stopWebLogic.cmd

D:\Oracle\Middleware\user_projects\domains\soa_infra_domain\bin> stopManagedWebLogic.cmd so_server1

Unable to deploy EJB: ejb_ob_engine_wls.jar from ejb_ob_engine_wls.jar

If your soa server is up but your soa_infra is down then search for the following error in

weblogic.application.ModuleException: Exception preparing module: EJBModule(ejb_ob_engine_wls.jar)

Unable to deploy EJB: ejb_ob_engine_wls.jar from ejb_ob_engine_wls.jar:

There are 1 nested errors: JDT compilation error! The method getMBeanAttribute(String, String) is undefined for the type FacadeFinderBean_4vacyo_Intf The method getNumberOfCompositeInstancesByPartitions(String[]) is undefined for the type FacadeFinderBean_4vacyo_Intf The method listComposites() is undefined for the type FacadeFinderBean_4vacyo_Intf The method invokeMBeanOperation(String, String, String[], Object[]) is undefined for the type FacadeFinderBean_4vacyo_Intf The method setMBeanAttribute(String, String, Object) is undefined for the type FacadeFinderBean_4vacyo_Intf The method getNumberOfFaultedCompositeInstancesByPartitions(String[]) is undefined for the type FacadeFinderBean_4vacyo_Intf
 at weblogic.ejb.container.ejbc.CompilerForJDT.compile(
 at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(
 at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(
 at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(
 at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(
 at weblogic.ejb.container.deployer.EJBDeployer.compileJar(
 at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(
 at weblogic.ejb.container.deployer.EJBDeployer.prepare(
 at weblogic.ejb.container.deployer.EJBModule.prepare(

Then install the SOA patchset installer ( on top of your existing SOA suite

BINDING.JCA-12563 resolution

If you ever face issues like

BINDING.JCA-12563 Exception occurred when binding was invoked. Exception occurred during invocation of JCA binding: “JCA Binding execute of Reference operation ‘Write’ failed due to: Input Source null. Input Source null. Input Source is null. “. The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
then there is a problem in the xml transformation in the mediator to write the file
Look if the transformation information in the mediator is proper.
Check if the transformation exist in the first place.


I got this error yesterday when I tried to deploy a dummy soa composite

Error Message: {}remoteFault
Fault ID    default/Project1!3.0*ad3d0394-9602-4482-9429-fc45d624bb5b/ProcessHello/3-BpInv0-BpSeq0.3-3
Fault Time    Sep 3, 2010 1:07:55 PM
Non Recoverable System Fault :
<bpelFault><faultType> <message>0</message></faultType>
<remoteFault xmlns="">
<part name="summary">
<part name="detail"><detail>null</detail></part>
<part name="code"><code>null</code></part>

for the above error the solution is the deploy the soa composite along with the deployment plan

right-click the composite and click on generate

when u deploy the soa composite you will have to select the
‘Use the SOA configuration option’ and locate the file

The sample config plan will be like

<?xml version="1.0" encoding="UTF-8"?>
<SOAConfigPlan xmlns:jca="" xmlns:wsp="" xmlns:orawsp="" xmlns:edl="" xmlns="">
 <composite name="Project1">
 <!--Add search and replace rules for the import section of a composite
 <service name="orderprocessor_client_ep">
 <binding type="ws">
 <attribute name="port">
 <binding type="ws">
 <attribute name="port">
 <!--Add search and replace rules for the component properties
 For components and service/reference bindings, you can add policy references.
 <component name="*">
 <wsp:PolicyReference orawsp:category="management" orawsp:status="enabled" URI="oracle/log_policy"/>
 <component name="OrderProcessor">
 <property name="activationAgent.LoadData.className">
 <property name="activationAgent.LoadData.portType">
 <reference name="StoreFrontService">
 <binding type="ws"/>
 <!--To configure monitor.config:
 <property name="enabled"><replace>true</replace></property>
 <property name="dataObjectsFolder"><searchReplace><search>mydev</search><replace>myproduction</replace></searchReplace></property>

 sample properties to configure for adapter:

 To add search and replace rules for wsdls, xsd and jca files
 <wsdlAndSchema name="OrderProcessor.wsdl|StoreFront.wsdl|xsd/BPELProcess1.xsd|xsd/OrderProcessor.xsd|xsd/singleString.xsd|xsd/StoreFront.xsd|xsd/StoreFrontProcessor.xsd">