Loan Demo and NetBeans SOA tools

This document is intended to illustrate NB 6.0 SOA functionality.

Use Case

Demonstrates a typical loan application:

1. Customer applies for a loan through a web application

2. Bank receives the applicant information

3. Bank sends the appropriate information to a credit company

4. The credit company processes the information and returns the status (and message):
   APPROVED or REJECTED (with explanation)

5. Bank notifies customer about the status of the loan.

6. Bank calculates loan approval percentage over a period of time.

7. Bank sends email to the Bank Manager if the loan is rejected (to aid w/ further decision making).

Talking Points About NetBeans Tools and the JBI Environment

Benefits of Using the NetBeans IDE SOA Module to Create and Orchestrate Web Services.

• Use the BPEL designer for visual authoring of the BPEL process (Business Process Execution Language)

• Use a Composite Application to deploy the business process to the JBI runtime

• Use the CASA editor to configure the deployed composite application.

• Use the WSDL Editor to create the web services used in the business process:
  SMTP Binding Component for sending mail
  XSLT Service Engine for data transformation

  IEP for processing events (to calculate loan approval percentage)

• From the Composite Application, you can generate Junit test cases that can easily be edited

• You can monitor event processing

• All without writing a single line of code!

JBI Environment

Open ESB 2.0 provides the JBI Environment, a standards-based environment wherein various data sources, protocols, and services can seamlessly interoperate.

The JBI runtime environment is available through the GlassFish Application Server runtime.

NetBeans IDE with SOA provides a rich set of JBI Binding Components and JBI Service Engines that are installed and deployed into the JBI Environment.

Composite Applications you build within the NetBeans IDE are deployed as Service Assemblies to the JBI Environment.

Each Service Assembly consists of a set Service Units (Web Services you create that, taken together, implement the Composite Application.)

Running the Demo

• Show the BPEL Designer and the Loan Application BPEL Process

• Deploy the EJB (external credit approval service)

• Deploy Composite Application

• Run Web Application (accept the default)

• Run Test Cases (run Reject twice and Approval twice)

• Show Event Processing (IEP) data tables

• Show email notification to the manager (Gmail inbox).

Talking About the Demo

We use NetBeans interactive tools to define the necessary web services.

We use the BPEL Designer to orchestrate the message exchange between the web services.

BPEL Designer also assigns values passed between web services, which are used to determine orchestration, and also for input and output to and from web services.

Demo Highlights

BPEL Designer – Open BPEL Designer and show partner links corresponding to web services defined by WSDL. Demonstrate the message exchange.

Deployment – Expand the Application Server runtime node, show the JBI runtime, Service Assemblies, and Service Units deployed to the JBI runtime. (Service Units are archive files that contain service artifacts to enable services.)

CASA Editor – The CASA Editor is a configuration tool that provides a view of the Service Units that have been deployed. (Show how Service Units listed in the Runtime Tab are modeled in CASA.) Show how CASA configures the bindings and illustrates message flow.

IEP – The IEP monitors and aggregates event processing data – loan information data that is changing in real time and provides the output data in table format. Open loan.iep and provide overview of designing event processing.

XSLT SE – The composite application uses the XSLT SE to transform HTML into a template that can be used to send notification emails using the SMTP Binding Component.