Transports and Interfaces: Siebel Enterprise Application Integration > 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 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. Review the configuration file to make sure that the parameters are set properly. Use named subsystems to dispatch to a workflow as described in Using Named Subsystems for Transport Parameters.

To configure SWE 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_lang]. Where lang is the three-letter language code for the language you are using, such as enu for U.S. English.
  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 in an English environment.

    [/eai_enu]
    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]://SiebelServer :SCBPort/EnterpriseName/XXXObjMgr_lang

    where:

    transport is TCPIP or http

    encryption is none or mscrypto

    compression is none or zlib

    SiebelServer is the name of your Siebel Server

    SCBPort is the listening port number for the SCBroker component (usually 2321)

    EnterpriseName is the name of your Siebel Enterprise Server

    XXXObjMgr_lang is the type of Application Object Manager for the Siebel Business Application you are installing and the language code used for this installation

    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 Application Object Manager specific to the Siebel Business Application you are installing.

    In the following example connect string, the Siebel Business Application installed is Siebel Sales, and the Application Object Manager is EAIObjMgr:

    ConnectString = siebel.TCPIP.None.None://server1:2321/siebelEnt/EAIObjMgr_enu

  4. Save and close the configuration file.
Transports and Interfaces: Siebel Enterprise Application Integration Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.