Overview: Siebel Enterprise Application Integration > Siebel EAI Overview > About the Components of Siebel EAI >

Siebel EAI and Java/J2EE

Siebel Business Applications provide standards-based technologies that allow you to access J2EE components from Siebel applications and support the creation of Java/J2EE components to access Siebel objects.

For details on J2EE, see Transports and Interfaces: Siebel Enterprise Application Integration.

Accessing Java/J2EE Components from Siebel Applications

Siebel Business Applications provide three mechanisms for invoking Java/J2EE components (JSP, Servlets, or EJBs):

• Web Services
• The Outbound HTTP adapter
• Java Business Service

When interacting with J2EE components published as a Web Service, Siebel applications can consume the WSDL (Web Service Description Language) document describing the service and operations, and generate a proxy Business Service allowing the Siebel Business Application to invoke the Web Services just like a local object. When the Business Service is invoked, the Object Manager detects that the Business Service is a proxy to a Web Service and generates the appropriate SOAP (Simple Object Access Protocol) message and dispatches the request using a configured transport such as HTTP.

For more information on Web Services, see About Web Services.

Additionally, Siebel EAI allows you to interact with J2EE components using the Outbound HTTP transport adapter. You can use this when including external content within the Siebel user interface, or when the component you need to interact with does not support a Web Service (SOAP or WSDL) interface.

The Java Business Service allows the sending or receiving of messages though a JMS. The JMS Receiver server component, in fashion identical to the MQ Series Receiver component, allows the asynchronous receipt of messages, except you are using EAI JMS Business Service instead of EAI MQSeries Server Transport.

The Java Business Service is a business service that allows custom business services to be written in Java and accessed from the Siebel code.

The Java Business Service uses the Java Native Interface API provided by Java Virtual Machines (JVMs) and native code interaction. It is a widely used technology used for writing JDBC drivers.

Accessing Siebel Applications from Java/J2EE Components

Java/J2EE components can request information from Siebel applications using a variety of methods including:

• Siebel Java Data Bean
• Siebel Resource Adapter
• Web Services
• Java Message Service

Java Data Bean. The Java Data Bean is a collection of Java classes that allow developers to interact with a variety of Siebel objects such as business objects, business components, and so on. Using this interface, you can develop Java/J2EE components that interact with Siebel applications.

Siebel Resource Adapter. The Siebel Resource Adapter plays a central role in the integration and connectivity between Siebel applications and a Java application server. It serves as the point of contact between application components, application servers and enterprise information systems. A resource adapter, along with the other components, must communicate with each other based on well-defined contracts that are specified by the J2EE Connector Architecture.

Web Services. Web Services are emerging as an important technology for exposing application functionality independent of the underlying technology used to provide that functionality. Release 6.x introduced the notion of Business Services that could be invoked through XML over HTTP and MQSeries. This functionality is now the basis for supporting Web Services. Siebel Business Applications provide support for Simple Object Access Protocol (SOAP) and Web Services Definition Language (WSDL). These two standards provide the basis for Web Services and allow for interoperability between .NET, J2EE, and leading packaged applications such as Siebel Business Applications.

For more information on Web Services, see About Web Services.

Java Message Service. Enterprise messaging is recognized as a tool for building enterprise applications. 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 queuing 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.

For more details on the Java Message Service, see Transports and Interfaces: Siebel Enterprise Application Integration.