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 Siebel Web Server Extension (SWSE). To use it, you 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 Siebel Web Server Extension (SWSE) installation directory, on the Web server computer. 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 SWSE to run the EAI HTTP Transport for inbound integration

  1. Open the 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 a U.S. English environment.

    [/eai_enu]
    ConnectString = Connect String
    EnableExtServiceOnly = TRUE

    Also set the ConnectString parameter, whose syntax 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 specific Siebel Application Object Manager you are using and the language code used for this component

    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 indicate the specific Siebel Application Object Manager for the application you are running.

    In the following example connect string, the Siebel Application Object Manager is EAIObjMgr_enu:

    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 © 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices.