| Oracle® Fusion Middleware Application Adapter for Siebel User's Guide for Oracle WebLogic Server 11g Release 1 (11.1.1.4.0) E17056-04 |
|
 Previous |
 Next |
| Oracle® Fusion Middleware Application Adapter for Siebel User's Guide for Oracle WebLogic Server 11g Release 1 (11.1.1.4.0) E17056-04 |
|
Previous |
Next |
When using Siebel XML to integrate with Siebel Integration Objects, the interface uses a Siebel Workflow.
|
Note: This appendix is intended as a supplement to the documentation designed for Oracle Application Adapter for Siebel user and is not intended as a substitute for Siebel documentation. For complete and up-to-date information on Siebel Workflow and policy topics, see the Siebel Bookshelf for your Siebel system. |
This appendix contains the following topics:
A Siebel Workflow is defined within Siebel to emit or to receive Siebel XML. In either case, emitting or receiving is handled by Siebel transport services for MQSeries, File, or HTTP. The following topics describe the use and creation of workflows that employ the supported transport services.
A Siebel Workflow is a series of Siebel Business Services linked together to accomplish a business task. You create workflows using the Siebel Client Workflow Administration screens. Workflows are invoked through one of the following methods:
The following topic briefly describes how to invoke the workflow through a policy condition.
|
See Also: Siebel Bookshelf documentation for more information on policy and other methods. |
A workflow policy is defined by a set of conditions that performs a set of defined actions. A Siebel workflow policy consists of:
Conditions that define circumstances, based on changes in the state of a Siebel database.
Actions that define steps taken when conditions are fulfilled.
Creating a policy to invoke a workflow as an action involves the following steps:
Define an action to be executed after a policy is triggered. Use the Run Integration Process program.
Create a policy by setting conditions and selecting appropriate policy groups and actions.
Activate the policy by choosing an activation date.
Run the Generate Triggers server task from Server Administration windows to set the conditions to be monitored.
Start the Workflow Monitor agent after editing with the appropriate policy group (to which your policy belongs) to evaluate whether to perform an action.
Start the Workflow Action Agent server task from Server Administration windows to perform the action.
When a Siebel Workflow is triggered based on a Siebel policy, run-time, or script (eScript or Siebel VB) event, the result is the generation of a Siebel XML document that is placed on one of the Siebel transports. For example, when you add a new account in the Siebel Call Center application, you can design and configure a workflow to be triggered on the account transaction. You can design the workflow to extract the data for the new record, convert it to Siebel XML, and then, place it on an MQSeries message queue.
In this example, the Siebel Workflow process executes the following series of Siebel Business Services:
Calls the Siebel EAI Siebel Adapter that queries for the newly updated account record and places the data in its original internal structure into memory.
Calls the Siebel EAI XML Converter that converts the data into an XML message.
Calls the Siebel EAI MQSeries Transport that places the newly created XML message into the appropriate MQSeries message queue
After the message is placed in the message queue, it is retrieved by Oracle Application Adapter for Siebel 6.3 and higher. The following Workflow sequence illustrates the previous steps, as shown in Figure A-1.
Figure A-1 How to Create a Siebel Workflow That Exports Siebel Update Data
A Siebel Workflow that is triggered by an external event begins by receiving a Siebel XML document placed on one of its transports. The result might be the update of a Siebel record using the XML as input, for example, when a new account is added in another CRM system but also must be updated in the Siebel Call Center application. You can design and configure a Workflow to receive or listen on an MQSeries message queue. Upon receipt of the XML message, the Workflow processes the transaction into the Siebel system to update the record.
In this example, upon receipt of the Siebel XML message in the message queue, the Siebel MQSeries Receiver server task initiates a Siebel Workflow process, which in turn executes a series of Siebel Business Services as follows:
Calls the Siebel EAI XML Converter, which converts the XML message into Siebel internal format.
Calls the Siebel EAI Siebel Adapter, which applies the newly updated account record based on the methods defined in its service.
The following is a sample of the Workflow process, as shown in Figure A-2.
The following topics include procedures for creating Siebel Workflows in the Siebel Workflow Administration window.
The following procedure is an example of a Siebel Workflow illustrated in the Siebel Workflow Administration window. The Workflow was designed for exporting Siebel Account record information using the MQSeries transport.
The following is a Siebel Workflow Administration window, as shown in Figure A-3.
Figure A-3 Siebel Workflow Administration Window
The following procedure describes how to create a Siebel Workflow that generates Siebel XML when an Account record is updated in the Siebel Call Center application. The Workflow is then placed on an MQSeries message queue.
To create a Siebel Workflow:
In the Process Properties tab of the Workflow Process window, define the Account message and Account XML process properties.
The Account message contains Siebel Account data in hierarchical format.Account XML specifies the Siebel Account data that the workflow has converted to XML.
The following window is displayed, showing the Process Properties tab active, as shown in Figure A-4.
Figure A-4 Process Properties Tab of the Workflow Process Window
Use the Siebel Workflow Administration windows to create a Workflow.
Define an EAI Siebel Adapter Business Service step to receive an instance of Account data and call it Get New Account.
The Business Service obtains the Account information from Siebel using the Query method.
Output from this Business Service is generated in hierarchical format, as shown in Figure A-5.
Figure A-5 Output From Business Service Generated From a Hierachical Format
Define an EAI XML Converter Business Service step and call it Convert to XML.
It is defined to receive the Account data from the EAI Siebel Adapter Business Service in hierarchical format and convert it to XML format, as shown in Figure A-6.
Figure A-6 EAI XML Converter Business Service
Define an EAI MQSeries server transport Business Service step and call it Send to Q, as shown in Figure A-7.
It is defined to receive the Account data from the EAI XML Converter Business Service in Siebel XML format and send the Account XML to MQSeries using the Send method.
Figure A-7 EAI MQ Series Server Transport Business Server Send to Q
The following procedure is an example of a Siebel Workflow illustrated in the Siebel Workflow Administration window. The Workflow was designed for exporting Siebel Account record information using the File transport.
The following window is displayed with the Process Designer tab active, as shown in Figure A-8.
Figure A-8 Siebel Workflow Administration Window
This procedure describes how to create a Siebel Workflow that generates Siebel XML when an Account record is updated in the Siebel Call Center application and then places Siebel XML on the file system.
To create a Siebel Workflow:
Figure A-9 Process Properties Tab of the Workflow Process Window
On the Process Properties tab of the Workflow Process window, define the Account message and Account XML process properties, as shown in Figure A-9.
Account message contains the Siebel Account data in hierarchical format.
Account XML specifies which Siebel Account data the Workflow converted to XML.
Use the Siebel Workflow Administration windows to create a Workflow.
As shown in Figure A-10, the following is an example of a Siebel Workflow Administration window.
Figure A-10 Siebel Workflow Administration Window
Define an EAI Siebel Adapter Business Service step to receive an instance of Account data and call it Get New Account.
The Business Service obtains the Account information from Siebel using the Query method.
Output from this Business Service is generated in hierarchical format.
Figure A-11 Creation of an EAI XML Converter
As shown in Figure A-11, define an EAI XML Converter Business Service step and call it Convert Account Data to XML.
This Business Service is defined to receive the Account data from the EAI Siebel Adapter Business Service in hierarchical format and convert it to XML format.
Figure A-12 File Transport for the EAI XML Converter Business Service
As shown in Figure A-12, define an EAI File Transport Business Service step and call it Send Account Data.
This Business Service is defined to receive the Account data from the EAI XML Converter Business Service in Siebel XML format and send the Account XML to the file system in a specified directory using the Send method.
The following procedure is an example of a Siebel Workflow illustrated in the Siebel Workflow Administration window. The Workflow was designed for exporting Siebel Account record information using the HTTP transport.
This procedure describes how to create a Siebel Workflow that generates Siebel XML when an Account record is updated in the Siebel Call Center application.
To create a Siebel Workflow:
Figure A-13 Process Properties Tab of the Siebel Workflow Process Window
As shown in Figure A-13, in the Process Properties tab of the Workflow Process window, define the Account message and Account XML process properties.
Account message contains the Siebel Account data in hierarchical format.
Account XML specifies the Siebel Account data that the Workflow has converted to XML.
Use the Siebel Workflow Administration windows to create a Workflow.
Figure A-14 Siebel Workflow Administration Window
As shown in Figure A-14, define an EAI Siebel Adapter Business Service step to receive an instance of Account data and call it Get New Account.
The Business Service obtains the Account information from Siebel using the Query method.
Output from this Business Service is generated in hierarchical format.
Define an EAI XML Converter Business Service step and call it Convert to XML.
This Business Service is defined to receive the Account data from the EAI Siebel Adapter Business Service in hierarchical format and convert it to XML format.
Figure A-15 EAI XML Converter Business Converter Business Service
Define an EAI HTTP Transport Business Service step and call it Send - HTTP, as shown in Figure A-15.
This Business Service is defined to receive the Account data from the EAI XML Converter Business Service in Siebel XML format and send the Account XML to HTTP using the Send method.
The following procedure is an example of a Siebel Workflow illustrated in the Siebel Workflow Administration window. The Workflow was designed for importing Siebel Account record information through the MQSeries Transport.
Figure A-16 shows a sample Siebel Workflow Administration window.
Figure A-16 Siebel Workflow Administration Window
This procedure describes how to create a Siebel Workflow that generates Siebel XML when an Account record is updated in the Siebel Call Center application.
To create a Siebel Workflow:
Figure A-17 Process Properties Tab of the Siebel Workflow Process Window
In the Process Properties tab of the Workflow Process window, define the Account message and Account XML process properties, as shown in Figure A-17.
Account message contains the Siebel Account data in hierarchical format.
Account XML specifies the Siebel Account data that the Workflow converted to XML.
Figure A-18 Creation of an EAI MQ Series Server Transport Business Service
Define an EAI MQSeries Server Transport Business Service step and call it Receive, as shown in Figure A-18.
The Business Service is defined to receive the Account data from the MQSeries message queue.
The EAI MQSeries Server Transport Business Service receives the Account data in Siebel XML format and sends it to the EAI XML Converter Business Service.
Figure A-19 Configuration of an EAI XML Converter Business Service
Define an EAI XML Converter Business Service step and call it Get XML from MQ & Convert to XML, as shown in Figure A-19.
This Business Service is defined to receive the Account data from the EAI MQSeries Server Transport Business Service in XML format and convert it to hierarchical format.
Figure A-20 Update Account Configuration for the EAI XML Converter that Uses MQ Series Transport
Define an EAI Siebel Adapter Business Service step and call it Update Account, as shown in Figure A-20.
This Business Service is defined to receive from the EAI XML Converter Business Service the instance of Account data in hierarchical format.
The Business Service applies the Account information into Siebel using the Insert or Update method.
The following procedure is an example of a Siebel Workflow illustrated in the Siebel Workflow Administration window. The workflow was designed for importing Siebel Account record information through the File transport
This procedure describes how to create a Siebel Workflow that generates Siebel XML when an Account record is updated in the Siebel Call Center application and then places Siebel XML on the file system.
The following is a Siebel Workflow Administration window with the Process Designer tab active, as shown in Figure A-21.
Figure A-21 Siebel Workflow Admininstration Window
To create a Siebel Workflow:
Figure A-22 Process Properties Tab of the Workflow Process Window
In the Process Properties tab of the Workflow Process window, define the Account message and Account XML process properties, as shown in Figure A-22.
Account message contains the Siebel Account data in hierarchical format.
Account XML specifies the Siebel Account data that the workflow converted to XML.
Figure A-23 EAI File Transport Business Service Step
Define an EAI FileTransport Business Service step and call it Receive Account Data, as shown in Figure A-23.
The Business Service is defined to receive the Account data from the file system.
The EAI File Transport Business Service receives the Account data in Siebel XML format and sends it to the EAI XML Converter Business Service.
Figure A-24 EAI XML Converter Business Service Step
Define an EAI XML Converter Business Service step and call it Convert from XML, as shown in Figure A-24.
This Business Service is defined to receive the Account data from the EAI File Transport Business Service in XML format and convert it to hierarchical format.
Figure A-25 Creation of the EAI Adapter Business Service Step Called Update
Define an EAI Siebel Adapter Business Service step and call it Update or Insert New Account, as shown in Figure A-25.
This Business Service is defined to receive from the EAI XML Converter Business Service the instance of Account data in hierarchical format.
The Business Service applies the Account information into Siebel using the Insert or Update method.
The following procedure is an example of a Siebel workflow illustrated in the Siebel Workflow Administration window, as shown in Figure A-26. The Workflow was designed for importing Siebel Account record information through the HTTP transport, as shown in .
Figure A-26 Siebel Workflow Administration Window
The following procedure describes how to create a Siebel Workflow that generates Siebel XML when an Account record is updated in the Siebel Call Center application and then places Siebel XML on the file system.
To create a Siebel Workflow:
Figure A-27 Process Properties Tab of the Workflow Process Window
In the Process Properties tab of the Workflow Process window, define the Account message and Account XML process properties, as shown in Figure A-27.
Account message contains the Siebel Account data in hierarchical format.
Account XML specifies the Siebel Account data that the workflow converted to XML.
Figure A-28 EAI XML Converter Business Service Step
Define an EAI XML Converter Business Service step and call it XML to Property Set, as shown in Figure A-28.
The Business Service is defined to receive the Account data from the EAI HTTP Transport Business Service in XML format and convert it to hierarchical format.
Figure A-29 EAI Adapter Business Service Update Step
Define an EAI Siebel Adapter Business Service step and call it Update Siebel, as shown in Figure A-29.
The Business Service is defined to receive from the EAI XML Converter Business Service the instance of Account data in hierarchical format.
The Business Service applies the Account information into Siebel using the Insert or Update method.
|
 Copyright © 2009, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|