Inbound ASI

An inbound ASI defines an interface for services provided by Oracle. External applications use this type of ASI to invoke Siebel-provided services.

An external application makes an inbound request that the inbound dispatcher receives. Based on the information in the ASI, the dispatcher invokes one of several services to pass its data to the Siebel application—either a data synchronization service, other business services, or a workflow process. For further details about data synchronization services, see ASI Data Synchronization Services. For more information about business services and workflows, see Business Processes and Rules: Siebel Enterprise Application Integration.

The dispatcher determines which service to invoke, according to the ASI configuration and transport protocols. The ASI determines whether the service request is a request-response operation (a response containing the status of the operation or the data retrieved) or a one-way request (where no response is required). ASIs are configured to have the same input and output argument (Siebel Message), and always return a response unless you change the ASI argument. External applications can use inbound ASIs, which can be exposed as a Web service, XML, or Java. The following image shows these processes.