Transports and Interfaces: Siebel Enterprise Application Integration > EAI JMS Transport >

About the EAI JMS Transport Business Service

The EAI JMS Transport business service is an API for accessing enterprise messaging systems. It supports the ability to send and receive messages by way of Java Message Service (JMS) servers. JMS defines two messaging models: point-to-point (by way of JMS queues) and publish-and-subscribe (by way of JMS topics). Both are supported by the Siebel EAI JMS Transport.

JMS queues and topics are identified by their Java Naming and Directory Interface (JNDI) names. A JNDI naming service is required to use the EAI JMS Transport. It contains entries for the queues and topics used.

The API of the EAI JMS Transport is very similar to other Siebel messaging APIs such as the EAI MQSeries Server Transport and EAI MSMQ Transport.

The EAI JMS Transport is built using the Java Business Service and therefore inherits all the requirements of that business service. This includes the independent installation of a Java Virtual Machine (JVM) and the configuration of the Siebel application to identify and create the JVM.

Oracle supports integration, using the EAI JMS Transport, with any JMS provider that conforms to the JMS 1.02b or 1.1 standards. The EAI JMS Transport provides support for basic integration with both queues and topics with message types that are specified in About JMS Message Types.

Oracle does not support any vendor extensions to the JMS standard except where specified enhanced functionality is released and documented as part of a Siebel fix pack. The EAI JMS Transport provides basic JMS 1.02b functionality as described in this chapter, but the EAI JMS Transport does not provide access to more advanced capabilities detailed in the JMS 1.1 standard or for any functionality that is not described in the Siebel Bookshelf. For information on the JMS 1.0.2b and 1.1 standards, see:

http://www.oracle.com/technetwork/java/jms/index.html