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 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
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 features of theJava EE Service Engine are:
Java EE service units - Using Java EE service units, end users can deploy and manage a composite application as a single entity: a JBI service assembly.
Transactions support - Enables Java EE web services and JBI services to participate in a single transaction. For example, a BPEL process can call an EJB bean that updates a database, all in the same transaction.
Security support - Enables separate JBI components to make use of a single authentication mechanism. In practice, a user signs on once, and the JBI system propagates the security credentials to the various JBI components as needed.
Code upgrade to JAX-WS 2.1
Endpoint enabling through jbi.xml
Support for RPC/Literal style operations
Direct invocation of endpoints
Packaging Java EE applications as part of the composite application
Cluster support - Enables you to deploy a Java EE service unit to an application server cluster. When the JBI service assembly is deployed to the cluster, the Java EE service units are also deployed to each server instance in the cluster.
Message properties propagation — This new feature supports propagation and reception of Normalized message properties. This feature allows additional properties to be propagated between Java EE components and JBI components. Propagation and reception of these message properties is handled by the Java EE Service Engine. For example, a web service client can pass additional message properties while invoking a JBI endpoint (for example, BPEL endpoints). The endpoint can use these properties and also send back additional properties to the client.
For more information on the Java EE Service Engine Features, see the article Bridging Java EE Web Services and JBI Components.