Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide > Teller IFX Connector Roadmap >

Configuring the Workflow Process

The example in this section shows how to modify an existing workflow process to add an additional outbound Teller XML message. Keep the following distinctions between outbound and inbound in mind.

Outbound messages start in a Siebel client. The Siebel application sends an outgoing request to the external data source and receives an incoming response from the external data source. Usually, this is for a client's transaction.

Inbound messages start in an external data source. The Siebel application receives an incoming request from the external data source and sends an outgoing response to the external data source. Usually, this is for a server's transaction.

All Teller messages are outbound messages. You can configure the connector to handle inbound messages, but no inbound messages are configured out-of-the-box.

Whether outbound or inbound, the cycle consists of an outgoing and an incoming message (request and response). In an outbound message, the outgoing part of the cycle occurs first (request), and the incoming part occurs second (response). In an inbound message, the incoming part of the message occurs first (request) and the outgoing part occurs second (response).


 Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide 
 Published: 18 April 2003