Invoking BPEL PM through the Java API, common pitfalls
Over the last weeks I worked with several people on the forums,
who tried to access Oracle BPEL PM through the Java API. Each of them got different exceptions - due to different enviroments/confgurations.
Previously I have written a couple of notes - describing most of these issues, all of them are linked from here - to have one place for looking up common pitfalls.
In general the are 2 usecases, each with a different shade of problems
- Accessng BPEL within the same VM
- Accessing BPEL from outside the vm (client)
- ClassNotFoundException: RMIContextFactory , also talking about getting no error message from the server [but no process instance is created] (all about the correct version of rmi libraries
- IOException: Disconnected / Connection refused
This usually happens when the rmi port, specified either in the context.properties, or in the hashtable is wrong.- BPEL PM Developer Install
rmiport: 23791
url: ormi://<host>:<rmiport>/orabpel
in this case the rmi connection is done directly through rmi - ORACLE BPEL PM installed in a midtier
opmnport: 6003
url: opmn:ormi://<host>:<opmnport>/OC4J_BPEL/orabpel
in the Application server case, the connection should be done through OPMN (the notification service) - as ports to the several oc4j instances get assigned at startup of the server, and could vary
- BPEL PM Developer Install
4 Comments:
Hi Clemens,
We had the same problems with the remote worklist service as you mention here. However, we have two more:
1. The updated payload is not seen in the bpel process after the task is completed and the TaskActionHandler returns. Bpel still sees the initial payload. We have solved it by copying the payload in the comment field and afterwards copy it into the payload-element. It is bit sneaky, but it works.
2. Have you tried to integrate a custom worklist app using the remonte WL API with OID/Portal by using the createContext(HttpServletRequest request) method? It probably will not work because portal is not setting the remote user for you, which is expected by this method..
Have you noticed these problems?
We have switched to the local WL API because it did not have the first problem. But it still has the second problem..
9:39 PM
Hi,
Small correction to midtier install URL syntax:
opmn:ormi://host:opmnport:OC4J_BPEL/orabpel
Regards,
Rajesh
11:57 PM
Small correction to midtier URL syntax:
opmn:ormi://host:opmnport/OC4J_BPEL/orabpel
Regards,
Rajesh
12:21 AM
what are you encountering? maybe I can help you - when you get me more details?!
10:08 PM
Post a Comment
<< Home