User Access to Configuration Manager, FSM, and Oracle Data Integrator

On installation the Oracle BI Applications system is configured to use WebLogic Server embedded LDAP for authentication. Work with your security administrator to grant users access to Oracle BI Applications Configuration Manager, Functional Setup Manager, and Oracle Data Integrator.

Access to Configuration Manager and Functional Setup Manager is controlled through these duty roles:

BI Applications Administrator Duty
BI Applications Functional Developer Duty
BI Applications Implementation Manager Duty
Load Plan Operator Duty
Load Plan Administrator Duty

The security administrator must grant the appropriate duty roles to a user based on the user's job responsibilities. For information on the Configuration Manager and Functional Setup Manager screens that each duty role has access to, see 'Security Overview of Oracle BI Applications Configuration Manager and Functional Setup Manager' in Oracle Business Intelligence Applications Security Guide.

The BI Applications administrator, load plan operator, and load plan administrator users will require appropriate access to Oracle Data Integrator. In addition to these users being created in the LDAP system, you must create these users in the ODI Repository and grant them the Supervisor profile or an appropriate ODI profile. The BI Applications administrator must be granted the Supervisor role in Oracle Data Integrator. Work with your security administrator to grant the duty roles.

For more information about managing security in Oracle Data Integrator, see Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.

Additionally, you must complete the following steps to configure the Signout link to work for Oracle Business Intelligence Applications Configuration Manager (BIACM) on an Oracle Access Manager (OAM) enabled environment:

Execute the commands through WLST as shown below:

addOAMSSOProvider(loginuri="/${app.context}/adfAuthentication",
logouturi="/oamsso/logout.html", autologinuri="/obrar.cgi")
Example:
cd <MW_HOME>/oracle_common/common/bin
./wlst.sh
connect ('biadmin,'welcome1','t3://<WLS_HOST>:<WLS_PORT');
wls:/>addOAMSSOProvider(loginuri="/${app.context}/adfAuthentication",
logouturi="/oamsso/logout.html", autologinuri="/obrar.cgi")

Bounce bi_server1.