BPEL WSM End Point Callback Pbm

Question

There is an issue during the BPEL Web Service call using WSM endpoint.
This is what my situvation is
1. I have BPEL Process (Process B) registered in WSM.
2. I have other BPEL process(Process A) which calls the above process(Process B) using the WSM endpoint instead of the standard orabpel endpoint.
I get the following error
<Faulthttp://schemas.xmlsoap.org/soap/envelope/>
<faultcode>env:Server</faultcode>
<faultstring>java.lang.NullPointerException</faultstring>
</Fault>
In the opmn log I see the following exception
<2007-08-14 17:06:15,687> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::doShortCut> Parner Property optShortCut
07/08/14 17:06:16 ----------------- __callback Caught Exception class com.collaxa.cube.CubeException
<2007-08-14 17:06:16,593> <DEBUG> <default.collaxa.cube.engine> <bpel.testbpelprocess.BPEL_BIN$$BPELC_BpInv4::perform> error thrown
ORABPEL-00000
Exception not handled by the Collaxa Cube system.
An unhandled exception has been thrown in the Collaxa Cube system. The exception reported is: "java.lang.NullPointerException
at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.populateOutMsgParts(WSIFOperation_JaxRpc.java:1338)
at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.buildResponseMessages(WSIFOperation_JaxRpc.java:1259)
at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeOperation(WSIFOperation_JaxRpc.java:1784)
at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeRequestResponseOperation(WSIFOperation_JaxRpc.java:1460)
at
etc
At the same time I could not find Process A instance in bpel console while I see Process B instance and it was invoked correctly. Does anybody know the cause of this.
The same process were working fine with standard endpoint. This happens only when the endpoint is WSM, after some research in the documentation I found that WSM listener port need to be configured as a callback port for BPEL. To me it looks like WSM is running in the same port as BPEL, I am not sure where I can find the WSM port. If anybody has any idea please share.
Thanks,
Chitra

Answer 1

First get your WSM configured properly and test that it is communicating to your far endpoint. There is a 'Test Page' capability to actually make invocations on the target. Once that works you should be able to access the gateway WSDL (I'm assuming that's what you're configuring) via a browser. Then its simply a matter of apply that WSDL URL to your client partner link.
The WSM quick start guide is pretty helpful. Check that out if you haven't done so.