| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Java CAPS Java EE Service Engine User's Guide Java CAPS Documentation |
| 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 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
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
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
|