Communicating through the JBI Bridge from BPEL to a JCD
By jason on Jul 22, 2008
One of the features of JavaCAPS 6 is the ability to communicate between the new JBI-based applications and the Repository-based projects of the JavaCAPS 5.x technology. This allows reuse of existing projects and the ability to make use of the 5.x architecture while it continues to provide functionality that is not yet available in the new technology.
This example shows how to communicate from the JBI-compliant BPEL 2.0 engine of OpenESB and JavaCAPS to a repository-based JCD. Though the principle is the same for communicating from any JBI-compliant composite application to a JCD.
The starting point for this example is the OpenESB introduction tutorial. This example also assumes that you are familiar with the JBI-based technology of OpenESB and the repository-based projects of JavaCAPS. If you are not yet familiar with the JBI-based technology, you should definitely start with the aforementioned tutorial.
The first step in the tutorial creates a simple BPEL process, which is exposed using a SOAP Binding Component Service Unit, and then deployed in a Composite Application (a Service Assembly in JBI speak).
The second step shows how to invoke an EJB Service from that BPEL process. But what if you wanted to implement that functionality in a JCD? You might do this for 2 reasons:
- You already have the functionality implemented in a JCD and you want to reuse it
- That step may consist of considerable mapping logic and it will be easier to implement it using the graphical mapper of JCD collaborations rather than writing the java manually.
The following movie shows how to:
- create a JCD using XSD OTDs
- build it in a repository-based project
- include that project as a Service Unit in a JBI Service Assembly (Composite Application)
- test the process and jcd
(This item is also located on the Grok JavaCAPS wiki)