Plain JMS API

Use to directly interact with EDN JMS topics. This is typically a J2SE client with raw JMS access.

The remote client must configure JNDI properties to point to the SOA server.

• Oracle WebLogic Server JMS

• AQ JMS

The advantages are:

• Supports the standard JMS API, meaning you can use many JMS software tools.

The disadvantages are:

• Service level degradation.

• Requires manual discovery of mapped JMS and configuration of JNDI.

• Requires extra coding, including handling of the internal EDN event structure, filter translation, subject propagation, transaction, error handling, and so on.

EDN API - EdnJmsConnection

For a J2SE client, such as Oracle Event Processing. This option provides all standard publish and subscribe options.

The remote client must perform the following tasks:

• Configure JNDI properties to point to the SOA server.

• Invoke the EDN helper method findRelevantBEConnFactory to return an appropriate connection factory. This enables you to use a JMS connection for publishing and subscribing to events.

• Oracle WebLogic Server JMS

• AQ JMS

The advantages are:

• No client JNDI configuration or JMS adapter deployment

• Handles JMS mapping, conversion, and translation.

The disadvantages are:

• Based on the plain JMS connection factory and topic.

For information about the JMS adapter, see the "Oracle JCA Adapter for JMS" chapter of Understanding Technology Adapters.