This topic describes the outbound and inbound interactions.
Outbound support allows a client to make calls to the adapter to perform a specific operation in the Siebel Business Application. The client can requests a connection using a ConnectionFactory and a ConnectionSpec that specify the userName and password to be used for authentication. The client automatically creates an InteractionSpec that specifies a functionName that is a valid method of the business service. The business service is in the metadata of the incoming business object.
For Service Component Architecture clients, the functionality of the adapter is exposed through interfaces described by a WSDL. The outbound service description is an EISImportBinding Service Component Description Language (SCDL) artifact produced by the EMD, this is an import file. The values required at runtime are present in the import file, which specifies the functionName and the userName and password required.
Both mechanisms execute a request using the interaction of adapter. The resource adapter uses the input business object to determine the business service name and the InteractionSpec’s functionName to determine the method to invoke.
The resource adapter creates a copy of the input business object which is populated with results as the output business object. The resource adapter builds the required Siebel PropertySet based on the input business object and invokes the business service. The output Siebel PropertySet is then populated in the output business object. The output business object is returned to the WBIRecordImpl which is returned to the calling client.
For outbound support, the adapter supports methods on the generic business services, custom business services, and application services interfaces. In addition, there are built-in business services in the data object layer that the adapter supports.
Built-in business services supported by the adapter include:
Inbound interactions are supported by having a Siebel event component in which the Siebel business service name is specified and adapter polls the event component at regular intervals. These messages are propagated to Endpoints that register the events.
The event component lists the type of event, the corresponding business graph, and the status of the event. These values are retrieved by the resource adapter, then, the integration object represented by the event is retrieved. The integration object values are populated in the business graph, which is then dispatched to registered Endpoints.
Parent topic: Outbound and inbound events
Related concepts
Asynchronous event delivery
Components
Event triggering and processing