Using JBI Components: Scenario Message Flow

Configuring JBI Components

Administering JBI Components for Java CAPS

Using the Java EE Service Engine in a Project

About the Java EE Service Engine

Java EE Service Engine Features

Java EE Service Engine Limitations

Java EE Service Engine Use Case Scenarios

Java EE Service Engine as Service Provider and Service Consumer

Java EE Service Engine as a Service Provider

Java EE Service Engine as a Service Consumer

Java EE Service Engine Example Scenario

Scenario Message Flow

NetBeans Tooling Support for the Java EE Service Engine

Software Requirements and Installation

Configuring and Starting the Java EE Service Engine

To Start the Java EE Service Engine from the GlassFish V2 Application Server

To Start the Java EE Service Engine from the Admin Console

To Start the Java EE Service Engine Using Command Line Interface

Installing Java EE Service Engine Using Command Line Interface

Other Operations Using the Command Line Interface

Administering the Java EE Service Engine

To View the General Properties

Java EE Service Engine Log Management

Java EE Service Engine Deployment Articrafts

Using the Java EE Service Engine to Create a Composite Application

Using the BPEL Designer and Service Engine

Using the HTTP Binding Component

Processing an Order in a Purchase Order System

Designing Custom Encoders

Using the XSLT Editor

XSLT Designer: Simple Transformation Tutorial

Using the File Binding Component

Using the File Binding Component in a Project

Using the JMS Binding Component

Understanding the FTP Binding Component

Using the FTP Binding Component in a Project

Understanding the LDAP Binding Component

Using the LDAP Binding Component in a Project

Using the JMS JCA Wizard

Using the JAXB Wizard and Code-Seeder Pallete

Understanding the Database Binding Component

Using the Database Binding Component

Using the WSDL Editor

Migrating From eTL to Sun Data Integrator

Designing Intelligent Event Processor (IEP) Projects

Designing Data Integrator Projects

Using the Sun Data Mashup Engine

Scenario Message Flow

The example scenario message flow works as follows:

The client application, acting as a web service, sends a message to a message queue.
The message is picked up by a message driven bean (MDB).
Upon receiving the message, the MDB contacts the NMR using the Java EE Service Engine, for the service endpoint that is exposed by the BPEL process.
When the MDB executes, the BPEL application that is hosted by the BPEL service engine, contacts the NMR to find its partner services.
In the example, only one partner service, the stateless session bean (JSR 109 web service) is hosted in the same Application Server JVM instance. The JSR 109 web service's is enabled in the NMR by the Java EE Service Engine when the stateless session bean is deployed.
The stateless session bean then uses Java EE persistence APIs to access the database.