The objective of this document is to describe the functioning of real time process. In the real time process the record from the external system is directly entered into UCM SDH (Source Data History) tables. The record is read from XML file and passed to the UCM source table and forwarded to the Siebel base table directly depending upon the survivorship rules. An output file which is a XML file is created for further reference.
Functional Description:
“UCM Server Party Package Workflow (File Transport) “is used in a real time process. This workflow receives the records from the external system in the form of a XML file. It also receives the operation name from this XML file. It can perform Insert, Update, Upsert, Delete and Query Operation. If the operation specified is “Insert” then it reads all the records from XML file and inserts the records one by one into UCM SDH table and then into the corresponding Siebel base table depending upon the survivorship rules. The workflow reads the XML file, executes the required action and sends back the response of the operation in the output file in the form of a XML again. This XML file also sends an error response to the external system incase of any errors encountered.
Technical Description:
UCM Server Party Package Workflow (File Transport)
This section describes the stepwise operation of the “UCM Server Party Package Workflow (File Transport)” workflow.
In real time scenario, “UCM Server Party Package Workflow (File Transport)” is used to execute the Insert, Update, Upsert, Delete and Query operation. The workflow reads the XML file which is nothing but the record detail sent by the external system and converts it into XML hierarchy, and converts that XML hierarchy into Property set. After that it executes the Operation specified in XML file. It can perform Insert, Update, Upsert, Delete and Query Operation. For Insert operation it inserts the record in corresponding UCM table and also in Siebel base table. It’s the inbound process and for outbound process it converts the output into property set, property set is converted into XML hierarchy. The output file is the XML file which is send back as a response of operation performed. This file can be sent back to the external system or can be stored at the specified location. The steps of the workflow are described in shot.
1. Start
2. Read from File:
Business service name: EAI HTTP Transport
Method name: Receive
Input Arguments:
FileName:
IsReceivingTextData:
Output Arguments:
Xml:
This step of workflow reads the XML file.
3. Convert to XML hierarchy:
Business service name: XML Hierarchy Converter
Method name: XMLDocToXMLHier
Input Arguments:
<Value>:
EscapeNames:
Output Arguments:
Core Req Prop:
This step converts the XMl file into Xml hierarchy.
4. Dispatch Message:
Business service name: UCM Dispatcher
Method name: DispatchMessage .
Input Arguments:
DispatcherMapName:
XMLEnvIntObjectName:
XMLHierarchy:
Output Arguments:
Disp Req Prop:
This step validates the incoming XML hierarchy. According to dispatching rules, it checks the integration object names. This also checks for the envelope, header, and fault sections of the message and identifies them.
4. Convert Request In:
Business service name: UCM Converter
Method name: XMLPropSetToPropSet .
Input Arguments:
XMLHierarchy
Output Arguments:
CIF System Prop
Tran Req Prop
This step converts the Xml hierarchy into Property set.
5. Transaction Manager:
Business service name: UCM Transaction Manager
Method name: Execute .
Input Arguments:
EnableRealtimeInsert
OnlyIOI
StatusObject
TurnOnCDMMatch
TurnOnDM
TurnOnSE
XMLHierarchy
Output Arguments:
Trans Resp Prop
Notification Req Prop
This step does tansaction in UCM table. This converter uses the hierarchy represented in the CIF integration object to perform the operation specified in XML file. The transaction manager translates XML command elements into Siebel eAI Adapter actions. If Input argument EnableRealtimeInsert is true then it performs the Operation in real time and inserts the record in corresponding UCM table after matching the records present in Siebel base table, and if it is false then it calls the UCM Contact Batch Data Management Workflow to execute the operation. We can also give the value “true” to TurnOnCDMMatch parameter for turning on the matching and “false” for turning off.
6. Convert Request Out:
Business service name: UCM Converter
Method name: PropSetToXMLPropSet .
Input Arguments:
CIFSystemContainer
FailSecurityHierarchy
NotificationHierarchy
XMLHierarchy
Output Arguments:
Conv Resp Prop
It converts the output into property set.
7. Decision point:
7.1. Yes:
Convert request out:
Business service name: UCM Publish/Subscribe Service
Method name: PublishMethod .
Input Arguments:
XMLHierarchy
Output Arguments:
7.2. No:
Convert to hierarchy:
Business service name: XML Hierarchy Converter
Method name: XMLHierToXMLDoc .
Input Arguments:
EscapeNames
XMLHierarchy
Output Arguments:
XMLHierarchy
It converts the property set into XML hierarchy.
8. Write to file:
Business service name: EAI File Transport
Method name Send .
Input Arguments:
<Value>
FileName
Output Arguments:
It creates an output file and keeps it at specified location.
9. End
Process Properties:
Following are the Process Properties that need to be defined for the workflow:
Name Value
- Enable Realtime Insert. False.
- Input File Name. This will contains the XML file Location.
- Realtime Pub Sub. True
- TurnOnCDMMatch. True
- Turn On Survivorship. True
- Turn On Data Management. True
- Output File Name This will contains the Location for the O/P file.