Siebel Financial Services Connector for IFX XML Guide > Configuring FINS IFX XML > Process of Configuring the Workflow to Handle an IFX XML Request >
Configuring the Siebel Connector for IFX XML Response
The response portion of the cycle is the partner to the outgoing portion in an outbound cycle. This task is a step in Process of Configuring the Workflow to Handle an IFX XML Request. Configuring an XML Hierarchy Converter
The first connector component in the response sequence is a hierarchy converter. For information about Siebel hierarchy converters, see Siebel Business Process Framework: Workflow Guide. To configure an XML hierarchy converter
- Name the hierarchy converter appropriately (it must be unique within the workflow).
- Name = Incoming Hierarchy Converter
- Type = Business Service
- Choose the type of business service from the multi-value group (MVG) window.
For this component, choose the XML Hierarchy Converter.
- Choose the method.
This example uses the XML Document to XML Hierarchy method because, for an incoming message, the conversion is from an XML document to an XML hierarchy that can be used by the FINS IFX XML Dispatcher.
- Set the input and output arguments, XML Hierarchy name, and XML document name.
Following are the input argument settings for the example hierarchy converter incoming configuration.
|
|
|
|
XML Document |
Process Property |
|
IFX Document Response |
Following are the output argument settings for the example hierarchy converter incoming configuration.
|
|
|
|
PropSet Out Incoming Hierarchy Converter |
Output Argument |
|
XML Hierarchy |
Configuring the FINS IFX XML Dispatcher
The second connector component in the response sequence is the dispatcher. To configure the dispatcher
- Name the dispatcher appropriately (it must be unique within the workflow).
The example uses:
- Name = Incoming Dispatcher
- Type = Business Service
- Choose the type of business service from the multi-value group (MVG) window.
For this component, choose the FINS IFX Tutorial Dispatcher.
- Choose the method.
The example uses the Dispatch Message method.
- Set the input and output arguments.
Following are the input argument settings for the example dispatcher incoming configuration.
|
|
|
|
DispatcherMapName |
Literal |
FINS IFX Tutorial DispMap |
|
XMLEnvIntObjectName |
Literal |
FINS IFX Tutorial Envelope |
|
XML Property Set |
Process Property |
|
PropSet Out Incoming Hierarchy Converter |
Following are the output argument settings for the example dispatcher incoming configuration.
|
|
|
|
PropSet Out Incoming Dispatcher |
Output Argument |
|
XML Property Set |
Configuring the FINS IFX XML Converter
The third response component is the converter. To configure the converter
- Name the converter appropriately (it must be unique within the workflow).
The example uses:
- Name = Incoming Converter
- Type = Business Service
- Choose the type of business service from the multi-value group (MVG) window.
For this component, choose the FINS IFX Tutorial Converter.
- Choose the method.
The example uses the XMLPropSetToPropSet method, because the converter is converting an XML property set from the dispatcher into a Siebel-hierarchy-based property set.
- Set the input and output arguments.
Following are the input argument settings for the example converter incoming configuration.
|
|
|
|
Enable Data Formatting |
Literal |
True |
|
IFX Application Business Service Name |
Literal |
FINS IFX XML Extension |
|
XMLEnvIntObjectName |
Literal |
FINS IFX Tutorial Envelope |
|
XML Property Set |
Process Property |
|
PropSet Out Incoming Dispatcher |
Following are the output argument settings for the example converter incoming configuration.
|
|
|
|
PropSet Out Incoming Converter |
Output Argument |
|
XML Property Set |
Configuring the FINS IFX XML Data Transformation Engine
The fourth response component is the data transformation engine (DTE). To configure the DTE
- Name the DTE appropriately (it must be unique within the workflow).
The example uses:
- Name = Incoming DTE
- Type = Business Service
- Choose the type of business service from the multi-value group (MVG) window.
For this component, choose the FINS IFX Tutorial DTE.
- Choose the method.
The example uses the Transform to Siebel Hierarchy method because the data is moving from an external system to a Siebel internal system.
- Set the input and output arguments.
Following are the input argument settings for the example DTE response configuration.
|
|
|
|
XML Property Set |
Process Property |
|
PropSet Out Incoming Converter |
Following are the input argument settings for the example DTE response configuration.
|
|
|
|
PropSet Out Incoming DTE |
Output Argument |
|
XML Property Set |
Configuring the FINS IFX Transaction Manager
The fifth response component is the transaction manager. To configure the transaction manager
- Name the transaction manager appropriately (it must be unique within the workflow).
The example uses:
- Name = Incoming Transaction Manager
- Type = Business Service
- Choose the type of business service from the multi-value group (MVG) window.
For this component, choose the FINS IFX Tutorial Transaction Manager.
- Choose the method.
The example uses the Execute Transaction method because the data is being received from the external data source and must be delivered to the Siebel application.
- Establish the input and output arguments.
Following are the input argument settings for the example transaction manager configuration.
|
|
|
|
XML Property Set |
Process Property |
|
PropSet Out Incoming DTE |
Following are the input argument settings for the example transaction manager configuration.
|
|
|
|
PropSet Out Incoming TransMgr |
Output Argument |
|
XML Property Set |
This step completes the outbound connector sequence.
|