Transports and Interfaces: Siebel Enterprise Application Integration > EAI HTTP Transport >

EAI HTTP Transport for Inbound Messages

To use the EAI HTTP Transport, you complete two steps:

• Set up the business service for use in the workflow.
• Create the workflow.

Both steps are explained in this section.

This scenario assumes incoming XML. Your business requirements dictate if and how you need to adapt these steps to fit your needs.

To set up the business service

1. Start Siebel Tools, connecting to the server.
2. Find the business service named Workflow Process Manager.
3. Copy this record and rename the copy EAITEST.
4. In the Business Service User Props list, add a new record:
   1. Enter ProcessName in the Name column.
   2. Enter EAITEST in the Value column, as shown in the following illustration.
5. Compile a new .srf file and copy it to the SIEBEL_ROOT\Objects\lang_code directory.

   NOTE:  You can also deploy the business service to the run-time database to make it available. For more information, see Integration Platform Technologies: Siebel Enterprise Application Integration.

6. Restart the Siebel Server.
7. Verify that the EAI Object Manager has started.

After you set up the business service, you create a workflow to receive messages.

To create the new workflow to receive messages

1. In Siebel Tools, set up a new workflow as shown below and give it a unique name, such as EAITEST.

   NOTE:  For details on the Business Process Designer, see Siebel Business Process Framework: Workflow Guide.

2. Create the following process properties:

   Name	Data Type	Default String	In/Out	Description
   IncomingXML	Binary	<Value>	In/Out	By creating the IncomingXML process property, anything that is sent as data will be placed in this variable. This allows you to then perform a given action on that data. If the POST method was used, the data sent in the Body will be stored in this property. If the GET method was used, the data sent in the URL will be stored in this property.
   Account Message	Hierarchy	Not applicable	In/Out	This is hierarchy format of the incoming XML.
   <Value>	Binary	Not applicable	In/Out	Used to get the XML string that has been read or converted.
   Content-Type	String	text/html	Out	It indicates the content type of the response body. If you want to see the response in the same Web page then you must set the Default String parameter to text/html.

3. Set up the Incoming XML step to use the EAI XML Converter with the XMLDocToIntObjHier method. This step converts the message, using the following input and output arguments:

   Input Argument	Type	Property Name	Property Data Type
   <Value>	Process Property	IncomingXML	Hierarchy

   Property Name	Type	Output Argument
   Account Message	Output Argument	SiebelMessage

4. Set up the UpdateSiebel step to use the EAI Siebel Adapter with the Insert or the Update method and the following input and output arguments to update the Siebel Database.

   Input Argument	Type	Property Name	Property Data Type
   SiebelMessage	Process Property	Account Message	Hierarchy

   Property Name	Type	Value	Output Argument
   <Value>	Literal	<h1>Update Completed</h1>	Not applicable

   NOTE:  The HTTP response for inbound requests is determined by looking at the <Value> portion of the output property set. HTTP response headers can be set by setting properties on the output property set. If the process properties are set as In/Out (the default), the values will appear as HTTP headers on the HTTP response from the Siebel Server. Set each process property that you do not want as an HTTP header to In or None (the latter if the process property is only for use inside the workflow).

5. Save your workflow and test it using the Workflow Simulator.