Siebel Adapter 6.0 SP3 | webMethods Siebel Adapter Documentation | webMethods Siebel Adapter Installation and User’s Documentation | Overview of the Adapter | webMethods-to-Siebel Communication | Invoke Business Component Method Services | Invoke Business Component Method Service Run-Time Processing
 
Invoke Business Component Method Service Run-Time Processing
The following diagram illustrates how the Siebel Adapter processes an Invoke Business Component Method service at run time.
Step
Description
1
A flow or Java service, typically invoked by an Integration Server client, initiates the Business Service service on the Integration Server. The client passes the required input information to the service.
You configure the Business Service service and the wrapping flow or Java service using Designer.
2
The adapter service retrieves a connection from the service's associated connection pool.
You configure and enable the adapter connection using the IIntegration Server Administrator. Adapter connections contain attributes that help the adapter connect to the Siebel application. For more information about connection pooling, see Connection Pooling.
3
The Object Manager invokes the business component method specified in the Invoke Business Component Method service, using Siebel's Business Object Interface (BOI) API to process the invocation.
4
If the operation is successful, the Object Manager passes the result to the Invoke Business Component Method service, which returns the result to the client. The output is a string field named Status, which contains the output generated by the method that is invoked.
If the operation is unsuccessful, the Object Manager returns an error to the adapter, which passes the exception to the Integration Server logs. For more information about how the adapter handles exceptions, see Logging and Exception Handling.