Monday, January 11, 2010

esb runtime and bpel in separate containers

If esb runtime and bpel are in separate containers, several issues may be encountered.

If opmnctl startall is used, esb container will most likely start before bpel container. If an External Service was created in esb which calls a BPEL process, the External Service will not show up under Web Services in em and the SOAP Endpoint URI will return 'No WebService Provider Found at this URL'. To resolve this, start BPEL fully before starting ESB runtime container.

In HA, if you start Node 1 completely and then start Node 2, you will notice that the Web Service is found in the ESB runtime container on node 2 but not on node 1 unless your HTTP Server is configured to not attempt to go over to the other container on node 1 to grab the wsdl from the BPEL container on node 1.

This can be done by making changes in opmn.xml which I will cover in a later post.

No comments:

Post a Comment