Professional Documents
Culture Documents
and BPEL
In SOA 10G, it is a good practice to have BPEL and ESB co-located at the same JVM. Doing so will not
only improves performance but also allows JTA global transaction propagates between the two. However,
these advantages will not be fully materialized, or even will totally disappear, if wrong protocols was
chosen when these two components call each other.
You should get the actual value of __esb_{partnerlink}_{porttype} from the ESB's WSDL file
http://xxx:7777/esb/wsil/AIASystem/EBS/SalesOrderOrchastrationEBS?wsdl
<bpelsuitcase>
<bpelprocess id="BPElProcess1" src="BPElProcess1.bpel">
<partnerlinkbindings>
<partnerlinkbinding name="client">
<property name="wsdlLocation">BPElProcess1.wsdl</property>
</partnerlinkbinding>
</partnerlinkbindings>
<configurations>
<property name="InvocationMode">local</property>
</configurations>
</bpelprocess>
</bpelsuitcase>
Step 4. ESB to BPEL communication uses "oc4jinstancename" property defined in "antorabpel.properties" to determine the instance name of the current oc4j node. This is required for
successful lookup of BPEL delivery service. In clustered environment this property takes a different
meaning (it is used for group name) and cannot be used as "oc4jinstancename" so another property
called "local.oc4jinstancename" should be defined to specify the local oc4j instance name, for the lookup
to function correctly.
Step 5: Restart the server (required for step 1 above). Setting the global JNDI attribute to true flattens the
JNDI tree. This means that any J2EE application can access any JNDI object in the container without
providing credentials. This may increase security
Posted by Francis Ip at 12:02 PM
Email ThisBlogThis!Share to TwitterShare to Facebook
2 comments:
1.
Francis IpJanuary 11, 2012 at 2:18 PM
I have just updated the the "ESB -> BPEL" portion of this blog. The changes are:
1.
Some
design
time
consideration
2. Settings in ant-orabpel.properties.
Reply
2.
HussainiJanuary 25, 2012 at 5:25 PM
Thanks Francis for the blog. As rest of the world is on 11g, I think a similar note would be helpful to
them
as
well...
Ok, coming back to my comment, I knew about this except EJB local invocation. Thanks. In the
BPEL to ESB call, if we use preffered port it is creating problems in dynamic parterlink execution.
Often the call goes to design time specified end point. It used to work prior to SOA 10.1.3.4
Reply