Profile Attributes not working in thin client (Doc ID 495575.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Tools - Version 7.5.2.214 SIA [16066] and later
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.5.2.214 [16066] Fin Svcs
Database: Oracle 9.2.0.2
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8

This document was previously published as Siebel SR 38-1015866241.

Checked for Relevance on 23-Oct-2013

Symptoms

In our attempts to make use of profile attributes, we invoked a business service to set some profile attributes (e.g. Login name) from the WebLogin RTE (thin client), and found that it did not behave as expected.

We found that when the RTE was specified to fire for particular login IDs, it would set the profile attributes correctly as expected. However, when the RTE was NOT firing for other login IDs, we found that the previously set profile attributes remained for the current user.

So for example, assuming ProfileAttr is being set to LoginName by a business service invoked from the WebLogin RTE:

1. Login: JAKOVLJEVIC     ProfileAttr: JAKOVLJEVIC
2. Login: LEE                      ProfileAttr: LEE
3. Inactivate RTE
4. Login: WONG                 ProfileAttr: LEE
5. Login: BOWE                  ProfileAttr: LEE

Our understanding is that for 4 and 5, the ProfileAttr should have been blank, since it had not been set. However, it appears that it is somehow being cached, and is even sharing across different users / logins.

This problem only appears to be occurring for thin client, as when we used the Login RTE (for dedicated client) instead, and tested the same scenario in dedicated client, we had no issues, and the profile attributes were specific to each user / session.

We have since moved the invocation of the business service to the Application_Start event in script, which works as expected (as long as we are 'filtering out' the anonymous logon).

However, the profile attribute behaviour encountered in thin client is concerning, as it could have adverse effects on application functionality.

Any insight into this unexpected behaviour would be very much appreciated.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms