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

How to Use EAI HTTP Transport to Receive Documents from BizTalk


This section describes how to set up and use EAI HTTP Transport for receiving documents from BizTalk over HTTP.

NOTE:  BizTalk Siebel HTTP Inbound Transport has been redesigned and implemented as an HTTP-based Application Integration Component (AIC) for the Siebel 7.5 release. This new HTTP-based AIC combines the functionality of the 7.0.x ASP application and the HTTP COM utility.

There are two high-level steps to this procedure:

Configuring Siebel Server

You need to set up EAI HTTP Transport for inbound processing in order to receive documents from BizTalk over HTTP. There are three tasks involved with configuring the Siebel Server for Inbound HTTP communication with BizTalk. These three steps include:

  • Enabling the EAI Component group on the Siebel Server
  • Setting up Siebel eAI
  • Setting up the Siebel Web Engine

For details on each of these steps, see EAI HTTP Transport.

Setting Up HTTP-Based AIC to Run on BizTalk Server

This section explains how to set up the required components for running the HTTP-based AIC Inbound Transport on the BizTalk Server machine. Although the AIC can run either on the Siebel Server machine or on the BizTalk Server machine, it is recommended that you run the AIC on the BizTalk Server machine locally for ease of configuration. If you would like to run the AIC on the Siebel Server, see Setting Up the AIC Inbound Transport to Run Remotely on the Siebel Server.

NOTE:  The HTTP-based AIC does not require ActiveX Data Controls.

Checklist

q

Copy the HTTP-based AIC Dynamic Link Library (DLL) from the Siebel Server machine to the BizTalk Server machine.

For details, see To copy HTTP-based AIC DLL from Siebel Server to BizTalk Server Machine.

q

Register the Siebel AIC on the BizTalk Server machine (one-time operation).

For details, see To register AIC as a COM+ Server Application on the BizTalk Server machine.

q

Copy the required Siebel HTTP AIC Active Server Pages (ASP) to the BizTalk Server machine.

For details, see To copy the required Siebel HTTP AIC Active Server Pages (ASP) to the BizTalk Server machine.

To copy HTTP-based AIC DLL from Siebel Server to BizTalk Server Machine

  • Copy the sscaeibh.dll file from SIEBSRVR_ROOT\eaiconn\bts\http\ on the Siebel Server to a newly created directory, such as c:\AIC on the BizTalk Machine.

To copy the required Siebel HTTP AIC Active Server Pages (ASP) to the BizTalk Server machine

  • Copy the Siebel_BizTalkHTTPAIC_1_post.asp page and the Siebel_Biz TalkHTTPAIC_1.asp page from Siebel Machine:

    SIEBSRVR_ROOT\eaiconn\bts\scripts

    to BizTalk Machine:

    BizTalk installation directory\MessagingManager\pipeline

Receiving Messages from BizTalk Using the HTTP Inbound Transport

This section explains how you use the BizTalk interface to receive XML documents using the Siebel HTTP Inbound transport. The activities associated with the inbound communication from BizTalk occur in the BizTalk Messaging Manager. For information on using this BizTalk application, consult the Microsoft BizTalk Server documentation.

Checklist

q

Set up the Siebel HTTP Inbound Transport.

For details, see How to Use EAI HTTP Transport to Receive Documents from BizTalk.

q

Set up the EAI HTTP Transport Named Subsystem and the HTTP Receive function to receive and process incoming XML documents.

For details, see EAI HTTP Transport Named Subsystems.

q

Set up the organization, port, and channel (collectively known as BizTalk configuration objects) for use with the HTTP Inbound Transport.

For details, see To set up BizTalk configuration objects for HTTP inbound below.

To set up BizTalk configuration objects for HTTP inbound

  1. Run the BizTalk Server Messaging Manager on the BizTalk Server machine.
    1. Set up a Home Organization for Siebel applications, such as Siebel Sales.
    2. Set up a Siebel Trading Partner to be the Destination Organization, such as Oracle.
    3. Create new document specification for the XDR document definition stored in WebDav.
  2. Set up a new BizTalk Server port to send the document to the Siebel application with the Primary Transport of Application Integration Component, Siebel.BizTalkHTTPAIC.
    1. Using BizTalk Messaging Manager, create a new port named Siebel HTTP AIC Port.
    2. Specify the primary transport type to be Application Integration Component.
    3. Specify the Component Name to be the AIC component name, Siebel.BizTalkHTTPAIC.
    4. Save your work.

      When you have finished setting up this port, BizTalk is configured to deliver messages to Siebel BizTalk AIC.

  3. Set up a new channel for the port created in Step d, such as Siebel HTTP AIC Channel.

    After you have specified HTTP AIC as the primary transport for document interchange with Siebel information, you need to supply BizTalk with configuration data specific to Siebel HTTP AIC. You do so by creating a new channel. For more information on setting up ports and channels, see Microsoft BizTalk Server documentation.

    This configuration data is passed to the Siebel HTTP AIC component through the BizTalk Server. One of the configuration items that is passed to the Siebel HTTP AIC component is the name of the HTTP Service you defined within Siebel application. HTTP AIC dynamically invokes the HTTP Service within the Siebel application and passes the XML document to the HTTP Service through the Siebel Web Engine.

    You can optionally create maps using BizTalk Mapper if data transformation is required for the documents received by the Siebel application from the external application. For information on the mapping capabilities of BizTalk, see Microsoft BizTalk Server online documentation.

    1. Configure the Advanced properties in the final Channel Configuration page.
    2. Provide the input parameters as required by the EAI HTTP Transport:

      Web Server is the server where SWE is running (format is defined as webserver:Port), Source is the new HTTP Service you previously created, and the user name and password to connect to the Siebel Server.

  4. Configure a File Receive Function from BizTalk Server Administration to poll a file location and deliver to the channel configured in Step 2.

    NOTE:  This example uses File Transport to receive documents from trading partners for the sake of illustration. In your actual business situations, a trading partner can deliver messages to a Siebel application over any supported transport.

    1. Open BizTalk Server Administration, expand Microsoft BizTalk Server, and expand the server group to which you want to add the File receive function.
    2. Select Receive Functions.
    3. Choose Action > New > File Receive Function and provide the following information.
      • Name. The name of the File receive function, such as Siebel HTTP AIC.
      • Comment. Add a brief description (optional).
      • Server. Server on which the receive function runs.
      • Polling Location. Enter c:\http.

        NOTE:  This is the location where your trading partner delivers the XML documents for the Siebel application so the channel can pick it up from there and send it to the Siebel application for processing.

      • File Types To Poll For. Type the extension of the files that BizTalk Server receives. In this case, type *.xml.
    4. Click the Advanced tab and enter a Channel Name, such as Siebel HTTP AIC Channel.
  5. Click OK to finish.

    NOTE:  If there are any errors while sending the document to the Siebel Server, they are written to the Application Event log with details.

Transports and Interfaces: Siebel eBusiness Application Integration Volume III