Siebel Financial Services Connector for ACORD P&C and Surety Guide > Configuration Roadmap > Configuring the Workflow Process >
Configuring an Inbound Siebel Connector for ACORD XML
For an inbound message, one that originates in an external application, Figure 7 shows the structure of a workflow that receives a request and sends back a response. The example workflow is the ACORD Server Policy Package Workflow included in the sample workflows.
Figure 7. ACORD Server Policy Package Workflow
|
NOTE: The error handling conditions and business services on the right side of the diagram are necessary to handle any rare processing errors. The sample workflow provides information about how they are configured.
Adding Process Property Values
You need to create Process Property values for the workflow, to be used in later configurations. To create process properties
- Click the Process Properties tab.
- Enter the values shown in Table 27.
Table 27. Process Property Values for the Example Workflow
|
|
|
<Value> |
String |
<Value> |
ACORD Client Application Name |
String |
Siebel Financial Services |
ACORD Client Application Operation |
String |
Oracle |
ACORD Client Application Version |
String |
8.0 |
ACORD DOCTYPE |
String |
|
ACORD DispMap Integration Object Name |
String |
ACORDDispMap |
ACORD Envelope Integration Object Name |
String |
Newdefault |
ACORD Service Provider Name |
String |
Siebel Partner |
ACORD Signoff |
String |
FALSE |
Error Code |
String |
|
Error Message |
String |
|
IsClient |
String |
FALSE |
Object Id |
String |
|
PropSet Converter Out (Incoming) |
Hierarchy |
|
PropSet Converter Out (Outgoing) |
Hierarchy |
|
PropSet DTE Out (Incoming) |
Hierarchy |
|
PropSet DTE Out (Outgoing) |
Hierarchy |
|
PropSet Dispatcher Out (Incoming) |
Hierarchy |
|
PropSet TransMgr Out (Outgoing) |
Hierarchy |
|
PropSet XML Converter Out (Incoming) |
Hierarchy |
|
SiebelFINSOperation |
String |
|
SignonRsEcho |
Hierarchy |
|
XML Document Response |
String |
|
Configuring an XML Hierarchy Converter (Incoming)
The first connector component in the inbound sequence is a hierarchy converter. For information about Siebel hierarchy converters, see XML Reference: Siebel Enterprise Application Integration. To configure an XML hierarchy converter
- Name the hierarchy converter appropriately (it must be unique within the workflow).
- 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 ACORD XML Dispatcher.
- Set the input and output arguments, XML Hierarchy name, and XML document name.
The following are the input argument settings for the example hierarchy converter incoming configuration.
|
|
|
|
|
XML Document |
Process Property |
|
<Value> |
String |
The following are the output argument settings for the example hierarchy converter incoming configuration.
|
|
|
|
PropSet XML Converter Out (Incoming) |
Output Argument |
|
XML Hierarchy |
Configuring the FINS ACORD XML Dispatcher (Incoming)
The second connector component is the dispatcher. To configure the dispatcher
- Name the dispatcher appropriately (it must be unique within the workflow).
- Choose the type of business service from the multi-value group (MVG) window.
For this component, choose the FINS ACORD XML Dispatcher.
- Choose the method.
The example uses the Dispatch Message method.
- Set the input and output arguments.
The following are the input argument settings for the example dispatcher incoming configuration.
|
|
|
|
|
DispatcherMapName |
Process Property |
|
ACORD DispMap Integration Object Name |
String |
XMLEnvIntObjectName |
Process Property |
|
ACORD Envelope Integration Object Name |
String |
XML Property Set |
Process Property |
|
PropSet XML converter Out (Incoming) |
Hierarchy |
The following are the output argument settings for the example dispatcher incoming configuration.
|
|
|
|
PropSet Dispatcher Out (Incoming) |
Output Argument |
|
XML Property Set |
Configuring the FINS ACORD XML Converter (Incoming)
The third connector component is the converter. To configure the converter
- Name the converter appropriately (it must be unique within the workflow).
- Choose the type of business service from the multi-value group (MVG) window.
For this component, choose the FINS ACORD XML Converter.
- Choose the method.
The example uses XMLPropSetToPropSet, 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.
The following are the input argument settings for the example converter incoming configuration.
|
|
|
|
|
IsClient |
Process Property |
|
IsClient |
String |
XMLEnvIntObjectName |
Process Property |
|
ACORD Envelope Integration Object name |
String |
XML Property Set |
Process Property |
|
PropSet Dispatcher Out (Incoming) |
Hierarchy |
The following are the output argument settings for the example converter incoming configuration.
|
|
|
|
PropSet Converter Out (Incoming) |
Output Argument |
|
XML Property Set |
SignonRsEcho |
Output Argument |
|
SignonRsEcho |
Configuring the FINS ACORD XML Data Transformation Engine (Incoming)
The fourth connector component is the data transformation engine (DTE). To configure the DTE
- Name the DTE appropriately (it must be unique within the workflow).
- Choose the type of business service from the multi-value group (MVG) window.
For this component, choose the FINS ACORD XML 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.
The following are the input argument settings for the example DTE incoming configuration.
|
|
|
|
|
XML Property Set |
Process Property |
|
PropSet Converter Out (Incoming) |
Hierarchy |
The following are the output argument settings for the example DTE incoming configuration.
|
|
|
|
PropSet DTE Out (Incoming) |
Output Argument |
|
XML Property Set |
Configuring the FINS ACORD Transaction Manager
The fifth connector component is the transaction manager. To configure the transaction manager
- Name the transaction manager appropriately (it must be unique within the workflow).
- Choose the type of business service from the multi-value group (MVG) window.
For this component, choose the FINS ACORD XML 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.
The following are the input argument settings for the example transaction manager configuration. Notice that the data flow within the connector changes direction at this point from incoming to outgoing.
|
|
|
|
|
Only product Integration Object Instance |
Literal |
true |
|
|
Report Error in Message |
Literal |
true |
|
|
Rollback In Error |
Literal |
false |
|
|
SiebelFINSOperationOut |
Process Property |
|
Siebel FINS Operation |
String |
Status Object |
Literal |
true |
|
|
XML Property Set |
Process Property |
|
PropSet DTE Out (Incoming) |
Hierarchy |
The following are the output argument settings for the example transaction manager configuration.
|
|
|
|
PropSet TransMgr Out (Outgoing) |
Output Argument |
|
XML Property Set |
Configuring the FINS ACORD XML Data Transformation Engine (Outgoing)
The sixth connector component is the data transformation engine (DTE). To configure the DTE
- Name the DTE appropriately (it must be unique within the workflow).
- Choose the type of business service from the multi-value group (MVG) window.
For this component, choose the FINS ACORD XML DTE.
- Choose the method.
The example uses the Transform to External Hierarchy method because the data is moving from the Siebel internal system to an external system.
- Set the input and output arguments.
The following are the input argument settings for the example DTE outgoing configuration.
|
|
|
|
|
XML Property Set |
Process Property |
|
PropSet TransMgr Out (Outgoing) |
Hierarchy |
The following are the output argument settings for the example DTE outgoing configuration.
|
|
|
|
PropSet DTE Out (Outgoing) |
Output Argument |
|
XML Property Set |
Configuring the FINS ACORD XML Converter (Outgoing)
The seventh connector component is the converter. To configure the converter
- Name the converter appropriately (it must be unique within the workflow).
- Choose the type of business service from the multi-value group (MVG) window.
For this component, choose the FINS ACORD XML Converter.
- Choose the method.
The example uses PropSetToXMLPropSet because the converter is converting a property set from the DTE into a standard XML property set.
- Set the input and output arguments.
The following are the input argument settings for the example converter outgoing configuration.
|
|
|
|
|
Client Application Name |
Process Property |
|
ACORD Client Application Name |
String |
Client Application Organization |
Process Property |
|
ACORD Client Application Organization |
String |
Client Application Version |
Process Property |
|
ACORD Client Application Version |
String |
Is Client |
Process Property |
|
IsClient |
String |
Is Signoff |
Process Property |
|
ACORD Signoff |
String |
Service Provider Name |
Process Property |
|
ACORD Service Provider Name |
String |
SignonRsEcho |
Process Property |
|
SignonRsEcho |
Hierarchy |
XMLEnvIntObjectName |
Process Property |
|
ACORD Envelope Integration Object |
String |
XML Property Set |
Process Property |
|
PropSet DTE Out (Outgoing) |
Hierarchy |
The following are the output argument settings for the example converter outgoing configuration.
|
|
|
|
PropSet Converter Out (Outgoing) |
Output Argument |
|
XML Property Set |
Configuring an XML Hierarchy Converter (Outgoing)
The eighth connector component is a hierarchy converter. For information about Siebel hierarchy converters, see XML Reference: Siebel Enterprise Application Integration. To configure an XML hierarchy converter
- Name the hierarchy converter appropriately (it must be unique within the workflow).
- 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.
The following are the input argument settings for the example hierarchy converter outgoing configuration.
|
|
|
|
|
XML Header Text |
Process Property |
|
ACORD DOCTYPE |
String |
XML Hierarchy |
Process Property |
|
PropSet Converter Out (Outgoing) |
Hierarchy |
The following are the output argument settings for the example hierarchy converter outgoing configuration.
|
|
|
|
<Value> |
Output Argument |
|
XML Document |
This step completes the inbound workflow. The inbound ACORD XML connector can be used as the basis for any workflow that is used to receive an inbound request message.
|