| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Using JBI Components: Java EE Service Engine Use Case Scenarios |
|
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 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
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
JBI components are typically used to handle high-level business operations. The Java EE Service Engine becomes necessary in situations where complex Java EE-based business logic needs to communicate with JBI components. In these situations, the Java EE Service Engine facilitates the transfer of data between components. Some examples of this data exchange include:
BPEL Service Engine calling an Enterprise Java Bean (EJB) web service
Message-driven bean (MDB) or servlet calling a BPEL process
EJB web service called through a JMS transport using the JMS Binding Component
Java EE components calling web services using the FTP Binding Component
Java EE components making web service calls through SMTP transport using the SMTP Binding Component