| Bookshelf Home | Contents | Index | Search | PDF | |
Transports and Interfaces: Siebel eBusiness Application Integration Volume III > EAI MSMQ Transport > Configuring EAI MSMQ Transport for Various Send and Receive Scenarios >
Receiving Inbound Messages with EAI MSMQ Transport
With the Siebel application as the receiver (inbound messaging), you design a workflow process that reads from the queue and converts the XML messages found there into Siebel message format. Then, the EAI Siebel Adapter updates the appropriate tables within the Siebel Database.
NOTE: EAI MSMQ Transport must run on the same machine where you have defined the receiving queue.
There are three methods for receiving messages for a Siebel application:
- Receive
- Receive and Execute Service (ReceiveDispatch)
- Receive, Execute, Send Response (ReceiveDispatchSend)
Receiving Messages from MSMQ
The following procedure describes how to set up your system to receive inbound messages from MSMQ.
To receive messages from MSMQ
- Access the Windows Computer Management tool.
- On Windows NT, choose Start > Programs > Windows NT 4.0 Option Pack > Microsoft Message Queue > Explorer.
- On Windows 2000, choose Start > Programs > Administrative Tools > Computer Management.
- Set up a queue to send messages to the Siebel application.
- Name the queue an easy-to-identify name, such as tosiebel.
- Create a message in the queue.
NOTE: In order to test this scenario adequately, you must have a partner application that can put a valid message for the Siebel application in the queue.
- From the application-level menu, choose View > Site Map > Business Process Administration > Workflow Processes.
- Set up a workflow for receiving a message from MSMQ as shown in the following figure:
NOTE: For details on Business Process Designer, see Siebel Business Process Designer Administration Guide.
- Create the following process properties in the Process Property applet:
- Set up the first step of the workflow process after Start to use the EAI MSMQ Transport with the Receive method. This step receives the incoming XML message, using the following input and output arguments:
- Set up the second step to use the XML Converter with the XMLToPropSet method to convert the XML message to a Siebel property set, using the following input and output arguments:
- Set up the third object to use the EAI Siebel Adapter with the Insert or Update method to update the Siebel Database, using the following input arguments:
NOTE: In order to test this scenario adequately, you must have a partner application that can put a valid message for the Siebel application in the queue.
- Save the workflow process and run a test using the Workflow Process Simulator.
Confirm that the message is removed from the queue using the MSMQ Explorer. In this example, if the message on the fromSiebel is valid, the Siebel Database should be updated with the message in the fromSiebel queue.
Receiving a Message from MSMQ and Acting on It
This procedure describes how to set up your system to receive an inbound message from MSMQ and perform an action based on that message within the Siebel application.
To receive and execute messages using EAI MSMQ Transport
- Access the Windows Computer Management tool.
- On Windows NT, choose Start > Programs > Windows NT 4.0 Option Pack > Microsoft Message Queue > Explorer.
- On Windows 2000, choose Start > Programs > Administrative Tools > Computer Management.
- Set up a queue to send messages to the Siebel application.
- Name the queue an easy-to-identify name, such as toSiebel.
- Create a message in the queue.
NOTE: In order to test this scenario adequately, you must have a partner application that can put a valid message for the Siebel application in the queue.
- From the application-level menu, choose View > Site Map > Business Process Administration > Workflow Processes.
- Set up a workflow process for receiving and dispatching a message from MSMQ as shown in the following figure:
NOTE: For details on Business Process Designer, see Siebel Business Process Designer Administration Guide.
- Create the following process properties in the Process Property applet:
- Set up the first step of the workflow process after Start to use the EAI MSMQ Transport with the ReceiveDispatch method. This step receives the incoming XML message, using the following input and output arguments:
- Set up the second step to use the XML Converter with the XMLToPropSet method to convert the XML message to a Siebel property set using the following input and output arguments:
- Set up the third object to use the EAI Siebel Adapter with the Insert or Update method to update the Siebel Database, using the following input arguments:
NOTE: In order to test this scenario adequately, you must have a partner application that can put a valid message for the Siebel application in the queue.
- Save the workflow process and run a test using the Workflow Process Simulator.
The contents of the output property set depend on the business service and method specified in the DispatchService and DispatchMethod arguments. Also, the Output Arguments applet should automatically populate and EndOfData should be set to True.
Receiving, Dispatching, and Sending MSMQ Messages
The following procedure shows you how to set up your system to receive an inbound message from MSMQ, perform an action within a Siebel application based on that message, and then send a synchronous response back to the external system.
To receive, dispatch, and send messages using EAI MSMQ Transport
- Access the Windows Computer Management tool.
- On Windows NT, choose Start > Programs > Windows NT 4.0 Option
Pack > Microsoft Message Queue > Explorer.- On Windows 2000, choose Start > Programs > Administrative Tools > Computer Management.
- Set up an MSMQ queue to receive messages from the Siebel application.
Give the queue an easy-to-identify name, such as fromSiebel.
- Set up another queue to send messages to the Siebel application.
- Name the queue an easy-to-identify name, such as toSiebel.
- Create a message in the queue.
NOTE: In order to test this scenario adequately, you must have a partner application that can put a valid message for the Siebel application in the queue.
- From the application-level menu, choose View > Site Map > Business Process Administration > Workflow Processes.
- Set up a workflow process for receiving and dispatching a message from MSMQ as shown in the following figure:
NOTE: For details on Business Process Designer, see Siebel Business Process Designer Administration Guide.
- Create the following process properties in the Process Property applet:
- Set up the first step of the workflow process after Start to use EAI MSMQ Transport with the ReceiveDispatchSend method to receive the incoming XML message, using the following input and output arguments:
NOTE: For illustration purposes, Workflow Utilities Echo method is used as dispatch service method. This could be changed to any dispatch service method as per your business requirements.
- Set up the second step to use the XML Converter with the XMLToPropSet method to convert the XML message to a Siebel property set using the following input and output arguments:
- Set up the third object to use the EAI Siebel Adapter with the Insert or Update method to update the Siebel Database, using the following input arguments:
NOTE: In order to test this scenario adequately, you must have a partner application that can put a valid message for the Siebel application in the queue.
- Save the workflow process and run a test using the Workflow Process Simulator.
The contents of the output property set depends on the business service and method specified in the DispatchService and DispatchMethod arguments. Confirm that the message is removed from the queue using the MSMQ Explorer. In this example, the Siebel Database should be updated with the message in the fromSiebel queue. Also, a response message will be in the queue specified by the MSMQRespQueueName and MSMQRespQueueMachineName arguments.
| Bookshelf Home | Contents | Index | Search | PDF | |
Transports and Interfaces: Siebel eBusiness Application Integration Volume III Published: 23 June 2003 |
