Transports and Interfaces: Siebel eBusiness Application Integration Volume III > Interfacing with Microsoft BizTalk Server > Connecting to BizTalk Using HTTP >

Siebel HTTP Outbound Transport

BizTalk Server uses the Microsoft Internet Information Server (IIS) and Active Server Pages (ASP) to receive documents over HTTP. The ASP file uses BizTalk Interchange Submit( ) and SubmitSync( ) methods to send documents to BizTalk Server.

To create a virtual directory for HTTP Outbound

1. Create a new directory for the ASP file.

   The directory should be on the Web Server where you would be sending your outbound XML documents from the Siebel application. This is usually the BizTalk machine.

2. Create a new virtual directory on IIS using the new directory you created. Name the directory, for example, BizTalkReceive.

NOTE:  The virtual directory can be on either the Siebel Server or the BizTalk Server. If the Internet Information Server is on the Siebel Server machine, you need to register the BizTalk Server Interchange Application to the Siebel Server. If IIS is on the BizTalk Server, you do not need to register Interchange application, because it is already a part of the BizTalk Server installation. See your Microsoft Internet Information Server (IIS) documentation for details on setting up virtual directories.

To copy the ASP files to the new HTTP Outbound directory

• Copy the ASP file SiebelBizTalkOutHTTP.asp from:

  SIEBSRVR_ROOT\eaiconn\BTS\SCRIPTS

  to the new directory you just created, for example:

  c:\BizTalkReceive\

Sending Messages to BizTalk Using the Siebel HTTP Outbound Transport

This section explains how to use the Siebel BizTalk interface to send an XML document to BizTalk Server over HTTP Outbound transport.

To set up BizTalk configuration objects for HTTP Outbound

1. On the BizTalk Server machine, access the BizTalk Messaging Manager.
2. Set up your home organization as Siebel and set up applications for the home organization.

   NOTE:  For each BizTalk-specific step, see Microsoft BizTalk Server documentation for the details.

3. Create a new organization and name it as is appropriate. For example, if your trading partner is Oracle, enter Oracle.
4. Create a document definition for previously-created document specification from WebDAV and name it, for example, Siebel Order. See To import schema into BizTalk Server to save it as a BizTalk document specification.
5. Create a messaging port to your trading partner.
   1. In the Destination Organization window select the organization, such as Oracle. Click Browse under Primary Transport.
   2. Select the appropriate transport for your trading partner.
   3. Complete the remaining pages as needed and click Finish to complete.
6. Create a new channel for the port created in Step 5.
   1. Create a new channel "From an Application" such as Siebel To Oracle Channel.Click Next.
   2. Select the appropriate inbound document definition, such as Siebel Order.
   3. Select appropriate outbound document definition for your trading partner, such as Oracle Order.
   4. Select an appropriate map, if necessary.
   5. Complete other pages as required and select Finish to complete.
7. Modify SiebelBizTalkOutHTTP.asp to specify the Channel name you configured in Step 6.
   1. Search for sChannel in the file.
   2. Remove the comment designator from this statement:

   sChannel = Channel Name you just created

To create the Siebel workflow for HTTP Outbound

1. From the Site Map choose Administration - Business Process > Workflow Processes.
2. Create a new workflow process as shown below to send a message to BizTalk.

   NOTE:  For information on how to set up Siebel Workflow, see Siebel Business Process Designer Administration Guide.

3. Set up the process properties for your workflow as follows:

   Name	Data Type	Value
   OrderMessage	Hierarchy	-
   <Value>	String	-
   Object Id	String	record # for an order

4. Set up the first step after Start to use the EAI Siebel Adapter with the Query method to query the order from Siebel Database, using the following input and output arguments:

   Input Arguments	Type	Value	Property Name	Process Property Type
   Output Integration Object Name	Literal	Sample Order	-	-
   Object Id	Process Property	-	Object Id	String

   Property Name	Type	Value	Output Argument
   OrderMessage	Output Argument	-	Siebel Message

5. Set up the second step to use the EAI XML Converter with the Integration Object Hierarchy to XML Document method and the following input and output arguments to convert the order object to XML document:

   Input Arguments	Type	Value	Property Name	Property Data Type
   Siebel Message	Process Property	-	Order Message	Hierarchy

   Property Name	Type	Value	Output Argument
   <Value>	Output Argument	-	XML Document

6. Set up the last step to use the EAI HTTP Transport with the Send or the SendReceive method and the following input arguments.

   Input Arguments	Type	Value	Property Name	Property Data Type
   Message Text	Process Property	-	<Value>	String
   Request Method	Literal	POST	-	-
   Request URL Template	Literal	The URL to which the document will be posted—for example, http://WebServer/virtual directory name/SiebelBizTalkOutHTTP.asp where: WebServer is the name of your Web server and virtual directory name is the virtual directory you set up in To create a virtual directory for HTTP Outbound, such as BizTalkReceive.	-	-

   NOTE:  You may require asynchronous or synchronous communication, using Send and SendReceive respectively, depending on your unique situation.

7. Save your workflow process and test it using the Workflow Process Simulator.