register ESB hosted WS in jbpm-bpel console as Partner Servi

[langeto]

I'm using two server installations, one JBoss ESB 4.2.1 GA and one JBoss AS 4.2.1 GA with a JBPM-BPEL 1.1.GA.

Registering a WS (that resides on JBoss ESB server installation) as Partner Service on the JBoss AS installation using the jbpm-bpel console works as expected.
I'm using the URL pointing to the WSDL document. The jbpm-bpel console lists the base location, the target namespace and the service in Partner Service Catalog. (A BPEL-process is now able to use the service).

If I provide an ESB configuration with an HTTP-Gateway for this WS (according to quickstarts sample webservice-producer) I'm able to call the service from a client using gateway URL (tested with soapUI and WS endpoint http://myhost:18765) but there is no WSDL and I can't register this gateway URL as Partner Service in jbpm-bpel console.

Is it possible to use the gateway 'endpoint' as WS endpoint? How do I have to configure the Partner Service for the BPEL process?

Thanks, Torsten

[marklittle]

Just to let you know that for BPEL we are only supporting ActiveEndpoints at this stage.

[burrsutter]

Have you tried the contract.war?

http://localhost/contract

look for the service, click on the link and get the WSDL?

In any case, the WSDL through/mediated the ESB is virtually the same as the WSDL directly to the JBossWS endpoint aside from the port number.

Burr

[langeto]

Exploring the 'contract' web application I found the URL to register Partner Service under JBPM-BPEL but it is not the JBossWS endpoint with a different port number.
I've registered the service using

http://myhost:8080/contract/contract.jsp?serviceCat=MyServiceCategory&serviceName=MyWSTESTService&protocol=http

(without ...'?wsdl').

@Mark
Is this an undocumented/not supported feature? Subject to change?

Thanks, Torsten

[marklittle]

What do you mean "undocumented"? Support for only ActiveEndpoints BPEL is well documented in the ESB.

[burrsutter]

We have never tested the mediation of a jBPM-BPEL Endpoint via the ESB. Only regular JBossWS endpoints and integration with Active Endpoints BPEL have been tested.

Can you list the steps taken to verify that the WS endpoint (jBPM-BPEL I assume) is available?

You should see it originally under http://localhost/jbossws
If you can find it there then you can setup the jboss-esb.xml like you would in webservice_producer.

Do spend some time figuring out how the webservice_bpel works with AE (and the other WS examples work), then you might be able to extract the knowledge you need to be successful here.

[langeto]

First of all: Our test application is running!

To ensure that we have defined a legal scenario (without ActiveEndpoints) I would like to clarify our approach.

We have installed two server instances:
- one JBoss AS 4.2.1 GA with a JBPM-BPEL 1.1.GA. (server instance A)
- one JBoss ESB 4.2.1 GA (server instance B)

Then we have deployed a WS on B and provided a jboss-esb.xml configuration via *.esb deployment (based on webservice-producer example).

After that we have defined and registered a BPEL process on A that uses the 'plain' WS on B. (The WS was registered as Partner Service in jbpm-bpel console on A using 'http://myhost:8080/testWS/TestWS?wsdl').
The BPEL process is running and calls the WS directly.

In the next step we tried to connect to the ESB mediated WS. (The WS was registered as Partner Service in jbpm-bpel console on A using 'http://myhost:8080/contract/contract.jsp?serviceCat=MyServiceCategory&serviceName=MyWSTESTService&protocol=http')
The BPEL process is running and calls the actions defined in jboss-esb.xml (print-before, JBossWSAdapter that calls TestWS and print-after).

Question:
Is the definition of the Partner Service in JBPM-BPEL using following base location 'http://myhost:8080/contract/contract.jsp?serviceCat=MyServiceCategory&serviceName=MyWSTESTService&protocol=http'
the recommended approach?

Torsten