Siebel Communications Guide > Defining Integration Workflows for Siebel Communications >

Sample Integration Workflow: CUT Receive Account Data

This section examines a receive-type sample workflow process to help you understand how the workflow process is set up.

This sample workflow process, shown in Figure 20, receives an XML string from an IBM MQSeries queue and updates the Account instance in the Siebel database.

Figure 20.  CUT Receive Account Data Workflow Process

CUT Receive Account Data Workflow Properties

You should set workflow process properties when you need a property to be true for the entire workflow. For example, as shown in the following procedure, the CUT Receive Account Data workflow process has five properties. The Error Message, Error Code, Object Id, and Siebel Operation Object Id properties are included in each workflow process by default. The Account XML property defines the MQSeries message as XML recognizable by Siebel eBusiness applications.

The CUT Receive Account Data workflow process has these additional properties:

• Account Message. Contains the object in its Siebel Communications hierarchical format when converted. It must be in this format before it can be inserted or updated in Siebel Communications.
• Account XML. Specifies the Siebel object that has been converted to XML.
• Process Instance Id. Specifies the process instance and is automatically populated when a process is executed and persistence is enabled.

CUT Receive Account Data Workflow Steps

CUT Receive Account Data Workflow includes the steps described in this section.

Receive Account Update Step

The Receive method of the EAI MQSeries Server Transport retrieves the inbound message from the Account physical queue. This queue is named in the Physical Queue Name argument.

In this case, the output from the receive step is put into the Account XML process property. The assumption is that the inbound message is already in XML format.

Convert to Internal Step

The next step, Convert to Internal, uses the XML Document to Integration Object Hierarchy method of the EAI XML Converter to convert the inbound message to the Siebel business object format.

The output argument from this step is stored in the Account Message process property, in the Siebel Message format.

Update Account Step

The last step before End uses the Insert or Update method of the Siebel EAI Adapter to perform the updating task. The Siebel EAI Adapter checks the Siebel database for an Account record that matches the current instance of Account in the Account Message property.

If an Account record matching the current instance does not appear in the database, the Siebel EAI Adapter inserts the record into the database.

If an Account record in the database matches the current instance, the adapter updates the record with the instance.