Go to primary content
Oracle® Argus Analytics User's Guide
Release 8.1
E76207-01
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
 

7 Implementing Security

This chapter contains the following topics:

7.1 About Security in Oracle Argus Analytics

Oracle Argus Analytics spans several applications:

Oracle Argus Safety is the data source.

Informatica ETL Execution plans and transforms Oracle Argus Safety data structures into the star schemas required by Oracle Business Intelligence Enterprise Edition (OBIEE).

OBIEE reads from the star schemas and provides the user interface, where end-users can view and analyze data through dashboards and reports.

Oracle Argus Analytics security includes:

  • Authentication
    Oracle Argus Analytics user accounts are maintained in WLS Embedded LDAP. A customer who is using OAM to authenticate the source system access can also configure it for OBIEE authentication.

  • Authorization
    You assign user accounts to user groups in WLS Embedded LDAP. On login, OBIEE ascertains the authenticated user's user group, where user groups with the same name determine which parts of Oracle Argus Analytics the user can use.

    Predefined OBIEE user groups determine the privileges allowed to users and allow access to the shipped Oracle Argus Analytics dashboards and reports. You can create additional user groups as needed in OBIEE.

  • Data Access
    In Oracle Argus Analytics, access is also performed at row level. This is done by extracting the access records for studies, products and sites from the source system.

7.1.1 Example

This section describes how to set up security for the following basic types of users as an example.

  • Oracle Argus Analytics End Users are people who can view Oracle Argus Safety data in Oracle Argus Analytics through dashboards and reports. The specific dashboards and reports they can view is determined by the user groups they belong to.

  • Oracle Argus Analytics Programmers are people who are authorized to create their own reports in the Answers component of Oracle Business Intelligence Enterprise Edition/Oracle Argus Analytics, which does not require any programming skills. You can distinguish between people who can simply create ad hoc reports and those who can save the reports they create to a dashboard so that other people can use them.

  • ETL Programmers are people who can modify the functionality of Oracle Argus Analytics by modifying the predefined ETL Programs that Oracle Argus Analytics uses to transform transactional source data in Informatica/ODI repository for use in Oracle Argus Analytics. They may also create new ETL Programs to support custom dashboards and reports in Oracle Argus Analytics.

  • Oracle Argus Analytics Schedulers are people who schedule Oracle Argus Analytics jobs, including the data loading job and the user data access jobs. They need privileges similar to ETL Programmers.

  • DAC/INFA/ODI Administrators are people who set up DAC, Informatica, or ODI Setups, and grant privileges to other users.

7.2 Setting Up User Authentication

DAC/ODI handles creation and maintenance of users for ETL administration of Oracle Argus Analytics. OBIEE handles reports related user authentication for Oracle Argus Analytics .

7.2.1 Creating User Accounts in DAC/ODI

You can create user accounts in the following way:

  • Create users in DAC. For more information, refer to the Oracle® Business Intelligence Data Warehouse Administration Console Guide.

  • Create users in ODI. For more information, refer to the Oracle® Fusion Middleware Developer's Guide for Oracle Data Integrator 12c.

7.2.2 Creating Users and Groups for Oracle Argus Analytics

Refer to the Oracle Argus Analytics Installation Guide for instructions on creating users and groups.

7.2.3 Implementing Security using OAM and Configuring SSL for Oracle Argus Analytics

Refer to the Oracle Argus Analytics Installation Guide for instructions on SSO installation to implement security using OAM, and on configuring SSL for Oracle Argus Analytics.