Siebel Financial Services Connector for IFX XML Guide > Configuring FINS IFX XML > Process of Configuring the Workflow to Handle an IFX XML Request >

Configuring a Transport Mechanism

The fifth component is a transport mechanism. The example uses the HTTP transport. For information about transport mechanisms supported by Oracle, see Transports and Interfaces: Siebel Enterprise Application Integration.

This task is a step in Process of Configuring the Workflow to Handle an IFX XML Request.

To configure an HTTP transport

1. Name the transport component appropriately (it must be unique within the workflow).

   The example uses:

   • Name = Transport Manager
   • Type = Business Service
2. Choose the type of business service from the multi-value group (MVG) window.

   For this component, choose the IBC Transport Manager.

3. Choose the method.

   This example uses the Send and Receive method, so that the adapter will wait for a specified time for the external system to process the request and send a response.

4. Set the input and output arguments, including the Physical Queue Name, the Queue Manager Name, and the Message Text.

   Following are the input argument settings for the example HTTP transport configuration. Notice that the data flow within the connector changes direction at this point from outgoing to incoming.

   Input Argument	Type	Value	Property Name
   Message Text	Process Property		IFX Document Request
   Connect Info	Literal	http://IFXMiddleware/ Replace IFXMiddleware with a valid connection string from which you can obtain IFX service.
   HTTP User Agent Header Value	Literal	ifx Use all lower-case letters.

   Following are the output argument settings for the example HTTP transport configuration.

   Property Name	Type	Output Argument
   End of Data	Output Argument	End of Data
   IFX Document Response	Output Argument	Message Text
   Timed Out	Output Argument	Timed Out

This step completes the request portion of the workflow, and it begins the response portion of the workflow. The outbound Siebel Connector for IFX XML can be used as the basis for any workflow that is used to send an outbound request message and wait for a response message.

Alternative to the Transport Mechanism Business Service Step

If you do not have an IFX Service Provider, you can replace this business service step with two business service steps:

• A business service step that writes the IFX request document to a file.
• A business service step that reads the corresponding IFX response document from a file.

You may want to use this alternative during development, so that you can work without using an IFX server or middleware. Save all request and response message pairs into files to test all possibilities locally. Save a single IFX document in each file. The number of files depends on how many IFX documents you want to maintain.