1. Overview: Siebel Enterprise Application Integration
  2. Types of ASI Interfaces

Types of ASI Interfaces

An ASI is either an inbound ASI and or an outbound ASI.

Inbound ASI

The following image illustrates how an inbound ASI is used to accept data into a Siebel application from an external system by using Siebel workflow processes, Siebel business services, and Siebel data synchronization services through the Siebel Object Manager.


Inbound ASI. In this image, External Application connects by one-way arrows to SOAP 1.1/XML, HTTP, MQ, MSMQ, Integration Server Adapter and Java, which in turn connect by arrows to Service Invocation Layer and Siebel Business Process which are grouped together. Administration Screen connects by arrow to Service Invocation Layer and also by arrow labelled Publish to WSDL 1.0 (Service Definition) DTD/XSD (Interface Definition.) An arrow labelled Import connects WSDL 1.0 (Service Definition) DTD/XSD (Interface Definition) to External Application.

Outbound ASI

The following figure illustrates how an Outbound ASI is used to send data that is based on a UI event or a trigger in a Siebel workflow process.


Outbound ASI. In this image, Siebel Business Process, Siebel UI Event, and Service Invocation Layer are grouped together. Service Invocation Layer connects by arrow to (SOAP 1.1/XML, HTTP, MQ, MSMQ), Integration Server Adapter, and Java, all of which in turn connect by arrow to External Application. External Application connects by arrow labelled Publish to WSDL 1.1 (Siebel Server Definition), which in turn connects by arrow labelled Import to Administration Screen. Administration Screen connects to Service Invocation Layer.