Skip Navigation Links | |
Exit Print View | |
Oracle Java CAPS Java EE Service Engine User's Guide Java CAPS Documentation |
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
Configuring and Starting the Java EE Service Engine
To Start the Java EE Service Engine from the NetBeans IDE
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
The following example shows how the Java EE Service Engine can be used in a business integration.
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.