|Bookshelf Home | Contents | Index | PDF|
As shown in Figure 5, Siebel eAI supports message-based integration with external applications where Siebel application is the initiator of the request or the receiver. The contents of the messages exchanged are called integration objects. Integration objects are defined in Siebel Tools.
The Java Message Service (JMS) is a standard Java API for accessing enterprise messaging systems. JMS is part of the Java 2 Platform, Enterprise Edition (J2EE). JMS supports the ability to asynchronously send and receive business data and events. JMS defines a common enterprise messaging API that is designed to be easily and efficiently supported by a wide range of enterprise messaging products. JMS supports both message queueing and publish-subscribe styles of messaging.
JMS is not a separate product. It is the specification of a common API for enterprise messaging. A JMS provider supplied by an enterprise messaging vendor is required to use it. Using the Java Business Service (JBS) feature, the JMS Transport is a feature that allows users to access third-party vendors' JMS providers. A JMS provider is a particular vendor's implementation of the JMS API. For example, IBM implements a JMS provider for their MQSeries product, and BEA implements a JMS provider for their Weblogic product.
|Overview: Siebel eBusiness Application Integration Volume l|