Profile Attributes are not initialized for Web Service calls using SessionToken (Stateless/Stateful) and WS-Security

(Doc ID 1512458.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel CRM Call Center - Version 7.8.2 [19213] and later
Information in this document applies to any platform.


Implementation of integration solution with Siebel CRM, that makes use Stateless approach to invoke an Inbound Web Service

(Siebel URL: http://<siebel_web_server:port>/eai_<lng>/start.swe?SWEExtSource=WebService&SWECmd=Execute&WSSOAP=1),

should TAKE INTO ACCOUNT that values of dynamic and static profile attributes will not be re-initialized again (re-set to default or empty values) AT EACH Web Service call.

* * *

For example:

1)  The "GetProfileAttr" method of the Siebel Application object, invoked to check value of the profile attribute named: "ApplicationName",

 may not always return correct application name (value of the "CFGApplicationName" parameter of the EAI Object Manager component)

 if the profile attribute value was changed by the "SetProfileAttr" method  in some previously called Web Service.

So the condition in a eScript statement: if( TheApplication().GetProfileAttr("ApplicationName") = "..."  - will not properly evaluated so ecxecution the business logic wil go improperly.


2) Another case may be that a Profile Attribute is Set (SetProfileAttr()) in the Request Filter Service .  The Response Filter Service code /logic if it is based on retrieving the Profile Attribute (GetProfileAttr) will not be triggered.

This was the behavior observed while using WS-Security.


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