5 Configuring OBIEE

This section describes how to set up the OBIEE server with the RPD and catalog for ad hoc reporting needs as required. It contains the following topics:

5.1 Deploying the RPD and Catalog

To deploy the RPD and Catalog:

  1. Install OBIEE 12.2.1.2.

  2. While running the configuration, create a blank OBIEE domain. For details, see Configuring Oracle Business Intelligence at

    https://docs.oracle.com/middleware/1221/core/BIEIG/GUID-4F0BD89A-C8BE-4851-8D0C-422779D5BC1D.htm#INSOA375

  3. Navigate to the following location on the middle tier installation home:

    <TRC_MTIER_HOME>/trcmt/ohf_products/OBIEE/

  4. Copy RPD.zip and OracleHealthSciencesCohortExplorer.zip to the OBIEE server.

  5. Extract them to a folder on the OBIEE server. This yields the RPD file and the catalog folder.

  6. In the Oracle BI Administration Tool, open the extracted Oracle BI repository (OracleHealthSciencesCohortExplorer.rpd) in offline mode and configure database connections.

    1. Open the Oracle BI Administration Tool using either:

      <OBIEE_DOMAIN_HOME>\bitools\bin\admintool.cmd

      or

      admintool.sh

    2. In the Oracle BI Administration Tool, from the File menu, select Open, then Offline.

    3. Select OracleHealthSciencesCohortExplorer.rpd.

    4. Enter the repository password to log into the OracleHealthSciencesCohortExplorer.rpd file. The default password is cohort.

      Note:

      Change the RPD password by selecting Change Password from the File menu. Enter the old and new passwords.

    5. Click OK.

  7. Modify the connection pools in the RPD:

    1. In the physical layer, expand the OracleHealthScienceCohortExplorer node and double-click Connection Pool.

    2. Change the following:

      Data source name: Enter the TNS entry name of the OHF database instance where OHTR is installed.

      User name: Provide the APP schema user name.

      Password: Provide the password of the APP schema user. Confirm the new password and click OK.

    3. From the File menu, select Save to save the RPD. When the "Do you wish to check global consistency" dialog box appears, click No.

  8. Upload the RPD using the following command:

    <OBIEE_DOMAIN_HOME>/bitools/bin/datamodel.sh uploadrpd -I <Path extracted to as mentioned in step 5>\OracleHealthSciencesCohortExplorer.rpd -SI ssi -U weblogic -P <weblogic credentials>

    You are prompted for the RPD password, which is cohort.

  9. Copy the contents of the catalog folder to

    <OBIEE_DOMAIN_HOME>/bidata/service_instances/ssi [Service Instance Name]/metadata/content/catalog

  10. Check whether tnsnames.ora is present in the location. If not, create it and add a TNS entry for the DB connection. To create the file:

    <OBIEE_DOMAIN_HOME>/config/fmwconfig/bienv/core/tnsnames.ora

    To add the TNS entry:

    trcpdb = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = <ohfdb_server.domain>)(PORT = <PORT_NUMBER>))) (CONNECT_DATA = (SERVICE_NAME = <OHDFDB_SERVICE_NAME>)))

  11. Restart the OBIEE services from the Enterprise Manager:

    1. Log into the Enterprise Manager.

    2. Expand the Target Navigation Menu and navigate to Business Intelligence > biinstance.

    3. Click the Availability tab.

    4. In the Processes tab, click Restart All. This will restart the BI Instance services.

    5. Log into OBIEE.

5.2 Creating OBIEE Groups and Users

5.2.1 Creating OBIEE Groups

  1. Log into the Administrator Console for the OBIEE Server at http://<obiee_server>:<admin_port>/console.

    <admin_port> is the port where OBIEE WebLogic Enterprise Manager is installed.

  2. Click Security Realms in the Domain Structure panel.

  3. Navigate to myrealm > Users and Groups.

  4. Click the Groups subtab.

  5. Click New and create the following groups:

    • BIServiceAdministrators

    • BIContentAuthors

    • BIConsumers

  6. Click OK.

5.2.2 Creating OBIEE Users

Create a user having the same credentials as the application user for OHTR and add them to one of the appropriate groups created in Section 5.2.1.

  1. Log into the Administrator Console for the OBIEE Server at http://<obiee_server>:<admin_port>/console.

    <admin_port> is the port where OBIEE WebLogic Enterprise Manager is installed.

  2. Click Security Realms in the Domain Structure panel.

  3. Navigate to myrealm > Users and Groups.

  4. Click New. Create the user with appropriate credentials.

  5. Select the user from the list and click the Groups Tab.

  6. Assign one of the user groups (created in Section 5.2.1) to the user.

    Note:

    The username created for OHTR and OBIEE WebLogic servers should match for access to data based on the VPD policies and other configurations.

5.2.3 Mapping Default OBIEE Roles to User Groups

  1. Log into the OBIEE Enterprise Manager at http://<obiee_server>:<admin_port>/em.

  2. Click the Weblogic Domain drop-down menu.

  3. Select Security > Application Roles.

  4. In the drop-down Application Stripe ensure obi is entered and click Search Application Roles (arrow icon). A list is displayed.

    Description of approles.gif follows
    Description of the illustration ''approles.gif''

  5. Select the row for BIServiceAdministrator and click Edit.

  6. In the Members table, click Add. The search dialog is displayed.

  7. Select Type as Group.

  8. Click Principal Name > Starts With.

  9. Enter BIServiceAdministrators.

  10. Click the arrow button to search.

  11. In the Searched Principals, select the row for BIServiceAdministrators.

  12. Click OK to add the group as a member.

  13. Click OK to save the changes.

  14. Repeat steps 3-13 to add:

    • Role BIContentAuthor to group BiContentAuthors

    • Role BIConsumer to group BIConsumers

  15. Log into the Analytics application

    http://<OBIEE_SERVER>:<ANALYTICS_PORT>/analytics with the user created in Section 5.2.2.

Granting BIAuthors to Create New Analysis

  1. Log into the Analytics application as the "weblogic" user or a user that is part of the BIServiceAdministrators group.

  2. Click Administration.

  3. Select Manage Privileges.

  4. Locate the entry Subject Area: TRC.

  5. Click the BI Service Administrator hyperlink. A dialog box is displayed.

  6. Click + to search roles to be added for the BI Content Author.

  7. Select the BI Content Author entry and click the arrow button to add it to the Selected Members list.

  8. Check whether Set Permission to is set to Granted.

  9. Click OK.

  10. Ensure that the BI Content Author role is selected and click OK to reflect the changes for the Subject Area: TRC.

  11. Log in as a user who is a part of the group BIContenAuthors and verify that you have access to the TRC subject area.

5.2.4 Deploying Help Files for OBIEE Dashboard

  1. Copy the file <OHTR_MTIER_HOME>/ohf_products/Weblogic/TrcDashboardHelp.war to the OBIEE server location from where it can be deployed.

    For example, create a folder upload in the location <OBIEE_DOMAIN_HOME>/servers/bi_server1/.

  2. Log into the Administrator Console for the OBIEE Server at http://<OBIEE_SERVER>:<ADMIN_PORT>/console.

  3. Navigate to the Deployments page.

  4. Click Lock & Edit.

  5. In the Summary of Deployments page, click Install.

  6. Provide the path where TrcDashboardHelp.war is copied. For example, <OBIEE_DOMAIN_HOME>\servers\bi_server1\upload.

  7. Select TrcDashboardHelp.war from the location and click Next.

  8. Select Install this deployment as an application.

  9. Let the scope remain Global and click Next.

  10. In the Available targets for TrcDashboardHelp, select the Clusters (for example, bi_cluster) check box.

  11. Click Next.

  12. Retain the default options in the remaining screens and click Finish.

  13. Click Activate Changes. The following message appears:

    All changes have been activated. No restarts are necessary.

  14. Verify that the TrcDashboardHelp application is started by navigating to Deployments > Control tab.

  15. Search for the application TrcDashboardHelp.

  16. If its not in the Active State, select the check box for TrcDashboardHelp and click Start > Servicing all requests.

  17. Context-sensitive help in the dashboard will now be available.