This variable has a possible value of 0 or 1. Used to enable or disable Oracle BI Server result cache hits. If the administrator user (defined upon install) has a Logging level defined as 4 and the session variable LOGLEVEL defined in the repository has a value of 0 (zero), the value of 0 applies.Ĭontains a description of the user, typically populated from the LDAP profile of the user.Ĭontains the locale of the user, typically populated from the LDAP profile of the user. This system session variable overrides a variable defined in the Users object in the Administration Tool. The value of LOGLEVEL, a number between 0 and 5, determines the logging level that the Oracle BI Server uses for user queries. This variable is typically populated from the LDAP profile of the user. It is also saved as the author field for catalog objects. It contains the name that is displayed to the user in the greeting in the Oracle BI Presentation Services user interface. See Security Guide for Oracle Business Intelligence Enterprise Edition for more information about the PROXY system session variable. ![]() A proxy user is a user that has been authorized to act for another user. ![]() ![]() GUIDs for application roles are the same as the application role names.Ĭontains the permissions held by the user, such as oracle.bi.server.manageRepositories. If a semicolon must be included as part of a role name, precede the semicolon with a backslash character (\).Ĭontains the global unique identifiers (GUIDs) for the application roles to which the user belongs. When a user belongs to multiple roles, include the role names in the same column, separated by semicolons,for example, RoleA RoleB RoleC. If a semicolon must be included as part of a group name, precede the semicolon with a backslash character (\).Ĭontains the application roles to which the user belongs. When a user belongs to multiple groups, include the group names in the same column, separated by semicolons (for example, GroupA GroupB GroupC). Legacy groups are mapped to application roles automatically. Exists only for compatibility with previous releases. When the user logs in to act as some other user, the value of the USER session variable matches the USERID the user is acting as.Ĭontains the global unique identifier (GUID) of the user, typically populated from the LDAP profile of the user.Ĭontains the groups to which the user belongs. The USER value always matches the PROXY variable, that is the act as value. This section contains the following topics: For information about using session variables when setting up security, see Managing Session Variables in Security Guide for Oracle Business Intelligence Enterprise Edition. If a user is authenticated successfully, session variables can be used to set filters and permissions for that session. Session variables are primarily used when authenticating users against external sources such as database tables or LDAP servers. Each instance of a session variable could be initialized to a different value. ![]() Unlike a repository variable, there are as many instances of a session variable as there are active sessions on the Oracle BI Server. When a user begins a session, the Oracle BI Server creates new instances of session variables and initializes them. Unlike dynamic repository variables, however, the initialization of session variables is not scheduled. Session variables obtain their values from initialization blocks.
0 Comments
Leave a Reply. |