My Oracle Support Banner

Siebel 2019 Changes To Vanilla BS "Web Engine HTTP TXN" Method: GetWebSessionInfo (Doc ID 2643664.1)

Last updated on FEBRUARY 01, 2021

Applies to:

Siebel CRM - Version 19.9 and later
Information in this document applies to any platform.


With Siebel 2016, BS "Web Engine HTTP TXN" method: GetWebSessionInfo to generate a SessionId for self service apps. This Sessoin id was further encrypted and logged into a custom table.

With Siebel 2019, session Id is about 320 chars. With Siebel 2016, session Id was about 204 chars

Column length to store encrypted session id is set to 355 Varchar and cannot be changed easily.
****With Siebel 2019 encrypted session id length goes around 440.******

In Siebel 2019, logic used by this BS seems to be changed? Please confirm if in Siebel 2019, session id generated by this vanilla BS is longer than Siebel 2016?


Test Case Steps:

Step 1. Create New Workspace WS_1
Add the following Server Script to "Activity List Applet With Navigation"

Step 2. Add the following values under "Application User Prop" for "Siebel Universal Agent"
Name = ClientBusinessService13
Value = Web Engine HTTP TXN

Step 3. Deliver WS_1
Step 4. Navigate to Activities --> Activity List --> My Activities
Step 5. Check the value of SRN, SessionID and cookie values as printed in c:\myTrace.txt via Trace commands.



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.