Transports and Interfaces: Siebel eBusiness Application Integration Volume III > EAI HTTP Transport > Using the EAI HTTP Transport for Inbound Integration >

Specifying HTTP Parameters for Inbound Integration

The EAI HTTP Transport is built into SWE. To use it, you first need to set certain configuration parameters for the virtual directory on the Web server. Your Siebel application installation includes a configuration file called eapps.cfg in the \bin subdirectory of your installation directory. This file is on the Web server side of your configuration, as opposed to on the Siebel Server side of your installation. You should review the configuration file to make sure that the parameters are set properly. Use named subsystems to dispatch to a workflow as described in the section Using Named Subsystems for Transport Parameters in EAI Transports and Interfaces Overview.

To configure the Siebel Web Engine to run the EAI HTTP Transport for inbound integration

  1. Open your eapps.cfg file in a text editor.
  2. Look for the section [/eai].
  3. Add the EnableExtServiceOnly configuration parameter or set it as follows, if it already exists, to enable the HTTP inbound transport. This example shown is for use with UNIX.

    4. [/eai]
    ConnectString = Connect String
    EnableExtServiceOnly = TRUE

    For the virtual directory, you need to set the ConnectString parameter. The syntax for the ConnectString is:

    ConnectString = siebel[.transport][.encryption][.compression]://gateway server {host|VIP}[:port]/enterprise name/object manager name[/server name]

    Where:

    transport = TCPIP or http.

    encryption = none or mscrypto.

    compression = none or zlib.

    gateway server = the name of your Siebel Gateway server. The default port for TCP/IP is 2320, and for HTTP it is 80.

    enterprise name = the name of your Siebel Enterprise Server.

    object manager name = the type of Object Manager for the Siebel eBusiness application you are installing.

    Siebel Server Name = the name of your Siebel Server.

    The following example shows the connect string using TCP/IP, with no encryption, no compression, and the server name and default port. In addition, you need to point to the Siebel Object Manager specific to the Siebel eBusiness application you are installing.

    In the example connect string, the Siebel eBusiness application installed is Siebel eSales, and the Siebel Object Manager is called eSalesObjMgr.

    ConnectString = siebel.TCPIP.none.none://gatewayhost:2320/siebel/eSalesObjMgr/Siebel Server name

  4. Save and close the configuration file.

Setting Configuration Parameters for Siebel Server

You must also set certain configuration parameters for whatever Siebel Server you are using. The server component you are running must be a Client Application Manager component. Set this in the configuration file for the server component of your choice, or use named subsystems.


 Transports and Interfaces: Siebel eBusiness Application Integration Volume III 
 Published: 23 June 2003