Bookshelf Home | Contents | Index | PDF     

Transports and Interfaces: Siebel Enterprise Application Integration > EAI HTTP Transport > Using the EAI HTTP Transport for Inbound Integration >

Using the EAI HTTP Transport in Sessionless Mode

Using the EAI HTTP Transport in sessionless mode allows you to use one URL to perform Login, Request, and Logoff in a single HTTP request. This mode does not use session cookies because there is no login session between the HTTP requests. The disadvantage of this mode is the overhead incurred by the Application Object Manager needing to log in with every request.

Table 23 presents each of the variables for sessionless mode.

Table 23. Sessionless Mode Variables 
Variable
Description

webserver

URL of the Web server that has Siebel Web Engine installed, such as www.myserver.com.

path

Default is eai. Virtual path on the server referring to the specific SWE configuration.

source

Named subsystem as specified in the [HTTP Services] section in the application configuration (.cfg) file.

username

Siebel user name for the Siebel Application Object Manager login.

NOTE:  Passing user credentials in the URL is not supported in Siebel CRM version 8.2, and Siebel CRM version 8.1.1.9 and later.

password

Password for the login user name.

data text

Business service input data. Most of the time, this is the text of an XML document that on the server side is converted to a PropertySet and passed to the business service. For more information on how to pass Properties and PropertySet to Business Services, see Siebel Business Process Framework: Workflow Guide.

Example Request for the HTTP Protocol in Sessionless Mode

In this example using HTTP POST, the URL describes the parameters for the HTTP Inbound Transport call over HTTP. Unlike session mode, the SWEExtCmd is Execute, not ExecuteLogin.

URL = http://webserver/path/start.swe

HTTP Body = SWEExtSource=source&SWEExtCmd=Execute&UserName=username&Password=
password&SWEExtData=data text

NOTE:  When using sessionless mode with the POST method, the XML data text must be URL-encoded to prevent any errors.

When using the sessionless mode with the POST method, the data text includes the login credentials as well as the XML document. Therefore, it is recommended that the data text be URL-encoded and that the Content-Type header be set to application/x-www-form-urlencoded without specifying the character set (for example, ;charset=UTF-8).

Use an escape code for any special characters (that is, use an ampersand, followed by the special character's escape characters, followed by a semi-colon) before encoding them for the URL. For more information, see the topic on special (escape) characters in XML Reference: Siebel Enterprise Application Integration.

Example for Sessionless Mode

URL = http://www.example.com/eai_enu/start.swe

HTTP Body = SWEExtSource=SiebelQuery&SWEExtCmd=Execute&UserName=user1&Password=login123
&SWEExtData=<?xml version="1.0" encoding="UTF-8"?>

<SiebelMessage MessageId="" MessageType="Integration Object" IntObjectName="Sample Account">

<ListofSampleAccount>

<Account>

  <Name>A. K. Parker Distribution</Name>

  <ListOfContact>

<Contact>

  <FirstName>Stan</FirstName>

  <LastName>Graner</LastName>

</Contact>

  </ListOfContact>

</Account>

</ListofSampleAccount>

</SiebelMessage>

    
Transports and Interfaces: Siebel Enterprise Application Integration Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices.