Siebel Financial Services Connector for IFX XML Guide > Configuring FINS IFX XML > Process of Configuring the Workflow to Handle an IFX XML Request >
Creating a Workflow for the IFX XML Request Message
The following procedures show how to construct a converter to handle a request message. This task is a step in Process of Configuring the Workflow to Handle an IFX XML Request. To construct a converter to handle a request message
- In Siebel Tools, select the Workflow Process object type in the Object Explorer.
- In the Object List Editor, right-click and then choose New Record.
- Enter the following values:
- Click anywhere outside the new row or move outside of the row with the UP or DOWN arrow keys.
Siebel Tools saves the new object.
- Right-click the new record, and then choose Edit Workflow Process.
- Create a workflow with the required components. Figure 5 shows the structure of the finished workflow.
For complete details about using this working space, and information about workflow processes in general, see Siebel Business Process Framework: Workflow Guide.
Figure 5. IFX Add Payment Outbound Workflow
|
Adding Process Property Values
You need to create Process Property values for the workflow, to be used in later configurations. To create process properties
- In the Process Properties view, enter the values shown in the following table.
|
|
End of Data |
String |
IFX Document Request |
String |
IFX Document Response |
String |
OP Outgoing TransMgr |
String |
PropSet Out Incoming Converter |
Hierarchy |
PropSet Out Incoming DTE |
Hierarchy |
PropSet Out Incoming Dispatcher |
Hierarchy |
PropSet Out Incoming Hierarchy Converter |
Hierarchy |
PropSet Out Incoming TransMgr |
Hierarchy |
PropSet Out Outgoing Converter |
Hierarchy |
PropSet Out Outgoing DTE |
Hierarchy |
PropSet Out Outgoing TransMgr |
Hierarchy |
SearchSpec |
String |
SearchSpec%1 |
String |
Timed Out |
String |
Configuring the Wait Step
The Wait step can be configured to perform an action after the workflow is initiated. When the action is taken, the remaining steps will then be performed. In this example, the Wait step is configured to retrieve the Row_ID of the current record. To configure the Wait step
- Double click the Wait step of FINS IFX Tutorial Outbound Connector workflow.
- In the Wait applet, enter the following value:
- Name = Get Current Payment Id
- Leave the Input Arguments applet empty (that is, with no records).
- Add output arguments in the Output Arguments applet (shown in the table below), and then click the Return to Designer button.
|
|
|
|
SearchSpec |
Literal |
[FIN Service Request Payment Request.Payment Id]=%1 |
|
Search Spec%1 |
Expression |
[Id] |
Fin Service Request Payment Request |
Configuring the FINS IFX XML Transaction Manager
The first outbound component is the transaction manager. To configure the transaction manager
- Name the transaction manager appropriately (it must be unique within the workflow), and select the type.
The example uses:
- Name = Outgoing 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 Outbound method because the data is being sent out from the Siebel data source.
- Establish the input and output arguments.
As for all Siebel business services, create a new record (CTRL+N) for a new argument. Select from the available input arguments, and type in any that do not appear in the list. Add all required arguments first, then go on to any optional arguments. See Siebel Connector for IFX XML for input and output specifications.
When you have finished setting the input and output arguments, click the Return to Designer button.
Following are the input argument settings for the example transaction manager configuration.
|
|
|
|
DispatcherMapName |
Literal |
FINS IFX Tutorial DispMap |
|
IXMLMapPath |
Literal |
IFX/PaySvcRs/PmtAddRs |
|
PrimaryRowId |
Process Property |
|
Object Id |
SiebelFINSOperationOut |
Literal |
SAQuery |
|
SiebelFINSRespIntObjName |
Literal |
FINS IFX Tutorial Payment Add Internal IntgObj |
|
SearchSpec |
Process Property |
|
SearchSpec |
SearchSpec%1 |
Process Property |
|
SearchSpec%1 |
Following are the output argument settings for the example transaction manager configuration.
|
|
|
|
PropSet Out Outgoing Transmgr |
Output Argument |
|
XML Hierarchy |
Configuring the FINS IFX XML Data Transformation Engine
The second 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 = Outgoing 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 External Hierarchy method because the data is moving from a Siebel internal system to an external system.
- Set the input and output arguments.
These arguments include the DTE map name, created during the configuration of the internal and external integration objects.
Following are the input argument settings for the example DTE configuration.
|
|
|
|
XML Property Set |
Process Property |
|
PropSet Outgoing TransMgr |
Following are the input argument settings for the example DTE configuration.
|
|
|
|
PropSet Out Outgoing DTE |
Output Argument |
|
XML Property Set |
Configuring the FINS IFX XML Converter
The third component is the converter. To configure the converter
- Name the converter appropriately (it must be unique within the workflow).
The example uses:
- Name = Outgoing 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 PropSetToXMLPropSet method because the converter is converting a property set from the DTE into a standard XML property set.
- Set the input and output arguments.
Following are the input argument settings for the example converter configuration.
|
|
|
|
Client Application Name |
Literal |
Siebel FINS Application |
|
Client Application Organization |
Literal |
Siebel FINS |
|
Client Application Version |
Literal |
7.0 |
|
Date Output Format |
Literal |
YYYY-MM-DD |
|
Enable Data Formatting |
Literal |
true |
|
IFX Application Business Service Name |
Literal |
FINS IFX XML Extension |
|
Is Client |
Literal |
true |
|
Is Log Out |
Literal |
true |
|
Service Provider Name |
Literal |
Partner IFX Middleware |
|
XMLEnvIntObjectName |
Literal |
FINS IFX Tutorial Envelope |
|
XML Property Set |
Process Property |
|
PropSet Out Outgoing DTE |
Following are the output argument settings for the example converter configuration.
|
|
|
|
PropSet Converter |
Output Argument |
|
XML Property Set |
Configuring an XML Hierarchy Converter
The fourth component 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).
The example uses:
- Name = Outgoing 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 Hierarchy to XML Document method because, for an outgoing message, the final conversion is from an XML hierarchy to an XML document that can be accepted by any XML-compliant converter at the external location.
- Set the input and output arguments, XML Hierarchy name, and XML document name.
Following are the input argument settings for the example hierarchy converter configuration.
|
|
|
|
Escape Name |
Literal |
false |
|
XML Header Text |
Literal |
<!DOCTYPE IFX SYSTEM "http://IFXWebSite/IFX101.dtd"> Replace IFXWebSite with a valid connection string that connects to the IFX101.dtd. |
|
XML Hierarchy |
Process Property |
|
PropSet Out Outgoing Converter |
Following are the output argument settings for the example hierarchy converter configuration.
|
|
|
|
IFX Document Request |
Output Argument |
|
XML Document |
|