« The Trials of Application Deplyment | Main | ORMI Providor URLs »

Calling BPEL EJBs from AS 10.1.3

Calling BPEL from App Server 10.1.3


I've been sick the last week and I haven't been up to concentrating much so I decided to upgrade some of the software on my system, nice brainless activity.  I upgraded my database to 10.1.0.4, my BPEL to production 10.1.2.0.2, my main JDeveloper installation to 10.1.3 and then expected it all to work together.


I was running some benchmarks and to get throughput I moved my dehydration store to 10.1.0.4, and it worked seamlessly.  I then started using a 10.1.3 OC4J instance to call web services in BPEL.  Again worked flawlessly.  By now I thought I could walk on water so I started amending the benchmark code to modify BPEL domain settings on the fly.


Now I'd gone too far.  BPEL complained about receiving ORMI 1.3 requests instead of 1.1 and refused to play ball.  So thats a long introduciton to what this entry is about, calling BPEL from a 10.1.3 app server instance.


Patching the Backward


Turns out that my friend Paolo Ramasso in Italy had raised a bug about this 12 months ago and there is now a patch number 4676768 for App Server 10.1.2 to allow it to inter-operate with 10.1.3.  I couldn't apply this patch directly as it only works against a full J2EE app server install, not against the OC4J standalone that is used by the developer install of BPEL.  To make it work with the standalone version you need to take the RMIConnection.class from the patch and use it to replace the class in the OC4J.jar file in the standalone OC4J.  The easiest way to do this is to



  1. Shutdown BPEL developer OC4J

  2. Download and unzip the patch.

  3. Open a command prompt and change to the 4676768filesj2eehomeoc4j.jar directory in the patch.

  4. Execute the update jar command to update the OC4J.jar "jar uf %BPEL_DEVELOPER_HOME%\ntegration\orabpel\system\appserver\oc4j\home\oc4j.jar *"

  5. Start BPEL developer OC4J

Everything should now inter-operate fine, at least it does with mine.  Of course all this hand patching is not needed when running BPEL in a full App Server instance


Next time I will talk about changing BPEL domain setting on the fly, which is of course where I started all this hand patching in the first place!

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About This Entry

This page contains a single entry from the blog posted on March 9, 2006 10:34 AM.

The previous post in this blog was The Trials of Application Deplyment.

The next post in this blog is ORMI Providor URLs.

Many more can be found on the main index page or by looking through the archives.

Powered by
Movable Type and Oracle