Transports and Interfaces: Siebel Enterprise Application Integration > EAI HTTP Transport > Examples Using HTTP Request >

Controlling Login Sessions with Session Mode


The session mode allows control over login sessions. In this mode you log in first and open a session. Any message can be exchanged without having to log in again until you explicitly log off.

The following example shows parameters for Login, Request, and Logoff in a session mode HTTP request. Session cookies are required in a case such as this.

NOTE:  You enter each of the following URLs as a continuous line of code.

  • The following URL logs in to a server with passed parameters for username and password:

    HTTPLoginURLTemplate = "http://$ServerPath$/start.swe?SWEExtSource=$Source$&SWEExtCmd=ExecuteLogin&User
    Name=$Username$&Password=$Password$"

  • The following URL passes a query string as the SWEExtData value along with the GET request:

    HTTPRequestURLTemplate = "http://$ServerPath$/start.swe?SWEExtData=<Prop>somedata</Prop>HTTPRequestMethod='GET'"

  • The following URL logs off from the server:

    HTTPLogoffURLTemplate = "http://$ServerPath$/start.swe?SWEExtCmd=Logoff"

    ServerPath = "siebel1/eai"

    Username = "pdavis"

    Password = "1234abcd"

    Source = "testdoc"

In the preceding example, the ServerPath variable value of siebel1/eai is substituted for the token $ServerPath$. The Source variable value of testdoc is substituted for the $Source$ token, the Username variable value of pdavis for the token $Username$, and the Password variable value of 1234abcd for the $Password$ token.

Any XML document represented by the entry for SWEExtData can be put into the body. This would change the sample code so that the HTTPRequestURLTemplate would read as:

HTTPRequestURLTemplate = "http://$ServerPath$/start.swe?

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