1. Overview: Siebel Enterprise Application Integration
  2. Access to a Java or J2EE Component from a Siebel Application

Access to a Java or J2EE Component from a Siebel Application

Siebel Business Applications provide three mechanisms to start Java and J2EE components:

  • Web Services

  • The Outbound HTTP adapter

  • Java Business Service

When interacting with a J2EE component that is published as a Web Service, a Siebel application can use the Web Service Description Language (WSDL) document that describes the service and operations, then generate a proxy Business Service that allows the Siebel Business Application to call the Web Service just like it does with a local object. When the Business Service is called:

  1. The Object Manager detects that the Business Service is a proxy to a Web Service

  2. The appropriate Simple Object Access Protocol (SOAP) message is generated

  3. The request is dispatched by 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 technique when you include external content within the Siebel user interface, or when the component you must interact with does not support a SOAP or WSDL interface.

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

  • Allows a message to be sent or received though a JMS. The JMS Receiver server component, which is similar to the MQ Series Receiver component, allows for asynchronous receipt of messages, except you use the EAI JMS Business Service instead of the EAI MQSeries Server Transport.

  • Uses the Java Native Interface API that is provided by Java Virtual Machines (JVM) and native code interaction. It is a widely used technology that is used for writing JDBC drivers.