JavaOne-TS-3175-Building a Service With BPEL and the Java™ EE Platform-How Composite Applications and JBI Simplify SOA Development21 May 2006
Presentations, JavaOne, WS-BPEL, SOA-Blueprints
Presentation Slide Deck
Presented a technical session at JavaOne 2006 where we demonstrated how to build a SOA Composite Application using JBI, the Java EE Platform, and WS-BPEL.
|JavaOne 2006, Moscone Center, San Fransisco, CA.
|Hall E 134
|Date & Time
|Thursday, May 18, 2006, 1:30pm to 2:30pm
|Building a Service With BPEL and the Java™ EE Platform: How Composite Applications and JBI Simplify SOA Development
|Companies are using SOA to offer services that simplify and accelerate doing business with them. These services are typically implemented as a collaboration of new functionality with the functions of existing enterprise apps. The combination of BPEL to deal with asynchronous collaboration and Java™ Platform, Enterprise Edition (Java EE) components to implement the new business logic implements these services effectively. This session describes how Java EE platform developers can create composite applications of this form by using existing Java EE platform tools and app servers that support Java Business Integration (JBI).
|Core Enterprise, JAVA EE
|Gopalan Suresh Raj, Sun Microsystems Inc; Ron Ten-Hove, Sun Microsystems Inc; Peter Walker, Sun Microsystems Inc
Presentation Slide Deck
Insurance Claim Scenario
This was the scenario we presented at JavaOne 2006 in the session titled TS-3175: Building a Service With BPEL and the Java™ EE Platform: How Composite Applications and JBI Simplify SOA Development
It leverages the HTTP/SOAP Binding Component, the WS-BPEL Service Engine, and the Java EE service engine during runtime, and the NetBeans IDE during design-time. It shows how services deployed on these different JBI component containers can be orchestrated together to solve a business problem.
- WS-BPEL Service Engine
- HTTP/SOAP Binding Component
- Java EE Service Engine
A set of Enterprise JavaBeans exposed as WebServices.
A JBI Service Assembly consisting of the following service units
- BPEL Engine provider Service Unit consuming all the other provided services.
- HTTP SOAP binding consumer for servicing external requests.
Business Use case
The following is a typical Insurance Claim Scenario where a customer files a claim with the Insurer. On receiving the claim information, the Insurer invokes a webservice called the Claim Numberer to generate a unique claim number for the details submitted by the customer. On receiving the claim number information from the Claim Numberer, the Insurer passes the claim number on to the customer.
The Insurer now does a couple of things in parallel. The Insurer invokes an external web service called the BookValue service providing it the details of the claim to get the current book value of the car. Simultaneously, the Insurer also invokes an external web service called the Adjuster and passes the claim information submitted by the client along with associated claim number. The adjuster after doing his research, submits a repair value to repair the damage to the Insurer.
The Insurer now goes into a Repair-or-WriteOff scenario, where if the book value is greater than the repair value, the Insurer invokes a Finance web service to pay the repairer to repair the car. If the book value is NOT greater than the repair value, the Insurer invokes the Finance web service to pay the customer and write-off the car.
We demonstrated the Insurance Claim Scenario at JavaOne 2006 in the session entitled “TS-3175: Building a Service With BPEL and the Java™ EE Platform: How Composite Applications and JBI Simplify SOA Development“. It show-cased how to use the plethora of design time tools bundled in the Java EE Tools Bundle to create an Insurance Claim composite application and deploy them on to the JBI meta-container running on GlassFish that hosts a Java EE Service Engine, a WS-BPEL Service Engine and a HTTP/SOAP Binding Component. It also demonstrated how to debug the application using both the WS-BPEL debugger and the JPDA debugger dynamically switching between WS-BPEL and Java code.
Implementation using JBI
The above business case can be implemented based on SOA principles and the JBI specification using the Java EE Tools Bundle today. The EJB module consisting of all the EJB WebServices has to be deployed. The Service Assembly (composite application) which consists of all the Service Units has to be deployed.