My Oracle Support Banner

Migration To IP2015: Not Reusing Existing Session, Always Creating A New One (_SN, SRN) (Doc ID 2349578.1)

Last updated on JANUARY 17, 2018

Applies to:

Siebel CRM - Version[21215] and later
Information in this document applies to any platform.


How to use SRN without creating multiple sessions?

Currently the Siebel application is invoked from an external application using SWE commands. To perform the navigation to the different view's customer is using URL parameters, that are retrieved with vanilla BS "Web Engine HTTP TXN".

Sample of Swe command in version:

The view BESExecuteNPTContext reads parameter SWENargs, and using the value in ViewCode navigates to the desired siebel screen

On IP2015 testing environment the invoked URL was changed to use the SRN parameter as described in the documentation.

The first approach was to replace the _sn variable by the SRN variable, using the following URL


In this approach, the session is not reused and in every invocation a new session is created.

As a second approach the _sn and SRN variable are used at the same time and session management performed correctly, but we cannot navigate to the desired view, because we are unable to read the parameters passed in the URL, because what Siebel gets is a "SWECmd=GotoPostedAction(...)" when the original command was "SWECmd=GotoView(...)"
Our conclusion was that when the two parameters (_SN+SRN) are used in swe command, the analyzed request is not the original and for this reason it is not possible to access the injected url parameters (SWENargs).

How can we revert to the original intended behaviour?


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.