| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Using JBI Components: Java EE Service Engine as a Service Consumer |
|
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 Example Scenario
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
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 JAXB Wizard and Code-Seeder Pallete
Understanding the Database Binding Component
Using the Database Binding Component
Migrating From eTL to Sun Data Integrator
Designing Intelligent Event Processor (IEP) Projects
When a Java EE application needs to access an endpoint of a service provider deployed in the JBI runtime environment, the Java EE Service Engine communicates with the application server and the NMR in the JBI environment. In this case, the Java EE Service Engine normalizes the SOAP message that otherwise would have been used in the JAX-WS communication and sends it to the NMR. This normalized message is handled by a service that has been enabled by a service provider deployed in the JBI runtime environment. The following illustration depicts three JBI binding components acting as service providers, offering application-specific content to external clients.