Skip Headers
Oracle® Life Sciences Data Hub System Administrator's Guide
Release 2.1.4

Part Number E18305-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

11 Setting Up Oracle Business Intelligence Visualizations

This chapter contains the following topics:

When used with Oracle Life Sciences Data Hub (Oracle LSH), each OBIEE Subject Area is based on a single Oracle LSH Business Area with Table Descriptors that are mapped to Table instances. The OBIEE Subject Area displays the data contained in these Table instances. Each Business Area is linked to an OBIEE Presentation Services Server. Users can launch OBIEE from inside Oracle LSH or through a URL for the Presentation Services Server linked to the Business Area.

Each Presentation Services Server can support multiple Business Areas. Oracle LSH automatically merges the OBIEE repository (.rpd) file for each Business Area linked to the same Presentation Services Server into one large .rpd file.

Note:

See the Oracle Life Sciences Data Hub Installation Guide chapter on integrating Oracle LSH with other systems for additional installation and configuration information. See Chapter 1, "Setting Up Services" for more information on service locations and services.

Setting Up a Single-Computer Configuration

You can install the Oracle Business Intelligence (Oracle BI) Server and the Oracle BI Presentation Services Server on a Windows computer and install the Oracle LSH Distributed Processing (DP) Server on the same computer. All Business Areas defined in Oracle LSH point to this Presentation Services Server. Oracle LSH merges the .rpd files for all Business Areas into a single large .rpd file.

Figure 11-1 Single-Computer Setup

Description of Figure 11-1 follows
Description of "Figure 11-1 Single-Computer Setup"

Service Location and Services Required in a Single Computer Installation

In Oracle LSH you define a single service location for the single OBIEE computer; see "Defining Service Locations". There is no required naming convention for the service location.

You must define all three OBIEE Services for the service location; see "Defining Services" for more detailed instructions.

  • OBIEE Business Area Install Service. In the Execution Command field of this service, enter the path of the obieeinstall.cmd script. For example: C:\LSH_DP_SERVER\obiee\obieeinstall.cmd

    Note:

    During installation this script should have been copied into the DP Server Home directory or a subdirectory of it.
  • OBIEE Business Area Deploy Service. In the Details field, enter database connection information and the name of the .rpd file you have defined for the Oracle BI Presentation Services Server; for example: dsn=ilpcr211,callinterface=OCI10G,RPD=LSH_MASTER

    Note:

    For database connection instructions, see the Oracle Life Sciences Data Hub Installation Guide.
  • OBIEE Business Area IDE Service. In the Execution Command field, enter the URL of the Oracle BI Presentation Services Server. For example: http://C1:9704/analytics/saw.dll?Answers

Note:

For the OBIEE IDE Service, specify a number of Service Instances equal to the maximum number of users you expect to query the repository at the same time, plus a buffer; see "Service Instances".

If you do not create enough service instances, users may lose access to the database in the middle of a task. For example, if you define 10 service instances and 11 people log in to the same OBIEE URL, when the last person logs in, the system looks for a session that has been running longer than the defined Reuse Wait time for the service. If there is such a session, the system recycles it even if the user is active, and the original user loses his or her connection to the database.

It is better to solve this problem by defining a large number of service instances than a high reuse wait time because the same user cannot open a new session—for example, if he or she wants to select different launch settings—until his or her original session reaches the reuse wait time.

Setting Up a Multiple-Computer Configuration

This section contains the following topics:

If you want to install the Oracle BI Presentation Services Server on a UNIX machine, or on an additional Windows machine, you can install just the Oracle BI Presentation Services Server and the Oracle LSH DP Server on the second machine, without the Oracle BI Server.

You can choose to have either a single, merged .rpd file or a different one for each Presentation Service instance. In either case, multiple Business Areas can use the same Presentation Services Server.

Define a pair of service locations for each Presentation Services Server computer: one on the Presentation Services computer ending in _RESTART and one on the BI Server computer with the same name except without the _RESTART string; see "Defining Service Locations".

Edit the DP Server Start script on each computer with the exact name you give the service location. Instructions are in the Oracle Life Sciences Data Hub Installation Guide chapter on installing Oracle LSH itself.

Note:

Do not use spaces, slashes, or special characters such as single quotes (') in the service location name. This may cause problems when you define a remote location and connection to password-protect the .rpd file.

Figure 11-2 Multiple-Computer Setup

Description of Figure 11-2 follows
Description of "Figure 11-2 Multiple-Computer Setup"

Service Locations and Services Required in a Multiple Computer Installation

In Oracle LSH you must define a pair of service locations, one with services running on the BI Server computer and the other with services running on the Presentation Services computer, for each separate Presentation Services computer.

Service Location Name The name of the service location for the Presentation Services computer must be the same as the corresponding service location for the BI Server plus the string _RESTART.

Note:

Do not use spaces, slashes, or special characters such as single quotes (') in the service location name. This may cause problems when you define a remote location and connection to password-protect the .rpd file.

When Definers create a new OBIEE Business Area, they must select a service location to use. The drop-down list displays all OBIEE service locations that do not end in _RESTART.

For example, as shown in Figure 11-2, the service location and service requirements when the BI Server and Presentation Services Server are on different computers are:

  • Give the first service location a name such as OBIEE_ABC and define all three OBIEE services for it:

    • OBIEE Business Area Install Service. In the Execution Command field of this service, enter the complete directory path and filename for the Windows execution command script on the BI Server computer; for example : C:\LSH_DP_SERVER\obiee\obieeinstall.cmd.

    • OBIEE Business Area Deploy Service. In the Details field, enter database connection information and the name of the .rpd file you have defined for the Oracle BI Presentation Services Server; for example: dsn=ilpcr211,callinterface=OCI10G,RPD=Study02

    • OBIEE Business Area IDE Service. In the Execution Command field of this service, enter the Presentation Services URL, for example: http://C2:9704/analytics/saw.dll?Answers

  • Give the second service location a name that is the same as the first service location plus the string _RESTART; for example, OBIEE_ABC_RESTART. Define one service for this service location: the OBIEE Business Area Install Service.

    • In the Execution Command field of this service, enter the complete directory path of the correct execution command script for the operating system; for example, on Windows:

      C:\LSH_DP_SERVER\obiee\obieerestart.cmd

      or on UNIX:

      /slot/ems1/appmgr/lshdpserver/obiee/obieepsrestart.sh

    • If the Presentation Services Server is a UNIX computer, enter os=unix in the Details field of this service.

Note:

In a multiple-computer configuration you can also use the Presentation Services Server that is installed by default on the same computer as the BI Server. In this case you need one more service location defined the same way as for a single-computer configuration; see "Service Location and Services Required in a Single Computer Installation".

Single and Multiple Repository Files

OBIEE repository (.rpd) files reside on the BI Server. The Business Area meta-data and OBIEE Administration Tool logic for all Business Areas that use a particular Presentation Services Server are merged into a single .rpd file. If you have multiple Presentation Services Servers, you can choose to have a different .rpd file for each one or a single, merged file. Functionally there is no difference whether you choose to have a single .rpd file or a different one for each Presentation Services Server.

  • To use a single, merged .rpd file, enter the same .rpd file name in the definition of the Deploy service of each pair.

  • To have a separate .rpd file for each Presentation Services Server, enter a different .rpd file name in the definition of the Deploy service of each pair.

Note:

You must add an entry to the NQSConfig.ini file on the BI Server for each repository file and set up the Analytics Web DSN to use the repository file; see "Assign Repository Filename(s) to each Oracle BI Presentation Services Instance".

Additional Setup

This section contains the following topics:

Set Up Database Connectivity

To run Oracle Business Intelligence visualizations through Oracle LSH, you must set up connectivity between the Oracle LSH database and the BI Server database. You can use a system ODBC DSN or the Oracle Call Interface (OCI10g) to connect the Oracle BI Server to the Oracle LSH database server.

Set Up Database Connectivity Using a System DSN Create a valid Oracle driver-based System Data Source Name (DSN) on the computer where the Oracle Business Intelligence server is installed.

Consult Microsoft Windows online help for instructions on creating the System DSN.

Use the Test Connection button to test the connection.

Set Up Database Connectivity Using OCI 10g/11g 

Create an entry in the BI Server's tnsnames.ora file with the name and connection details fo the LSH database server.

Test the connection by trying to connect to the Oracle LSH database using SQL*Plus as apps.

Note:

You must have an entry for the Oracle LSH database in the tnsnames.ora file in your Oracle Home.

Assign Repository Filename(s) to each Oracle BI Presentation Services Instance

Do the following on each computer with a Presentation Services instance installed:

Add an Entry to the NQSConfig File for Each Repository File

Each time the BI Server is restarted, all the .rpd files defined in NQSConfig.ini are loaded and one of them in defaulted. If an .rpd file is not defined in NQSConfig.ini, is is not available for visualizations.

If you are using a single-computer configuration, you have only one .rpd file. If you are using a multi-computer configuration, you can choose to use one .rpd file for all Presentation Services Servers or a different .rpd file for each one by entering the same or different value in the Details field of the Deploy service for the relevant OBIEE service location; see the chapter on Oracle Business Intelligence visualizations in the Oracle Life Sciences Data Hub System Administrator's Guide. This value determines which .rpd file is used for which Presentation Services Server.

On the Oracle BI server computer, open the NQSConfig.ini file and make an entry for each repository file under the Repository section that includes both a logical name and the .rpd file name. You must designate one .rpd file as the default, as shown in the following example. Oracle recommends setting the .rpd for the Presentation Services Server installed on the BI Server as the default. For example:

REPOSITORY
logical_name1 = RPD_name1.rpd, DEFAULT;
logical_name2 = RPD_name2.rpd

Each .rpd file name must exactly match the .rpd file name defined in the Details field of the Deploy service for one of the the OBIEE service locations.

Note:

Neither the logical name nor the .rpd file name is displayed in OBIEE Answers or in Oracle LSH. The Subject Area's name in OBIEE Answers is populated with the Business Area's name.

Set up the Analytics Web DSN to Use the Repository File

On each computer with the Presentation Services Server installed, set up the Analytics Web DSN to use the Oracle LSH Repository file.

The Presentation Services will try to find its .rpd file during this process, and setup will not succeed if it does not find an .rpd file with the same name that you entered in the NQSConfig.ini file on the Oracle BI server computer and in the Details field of the service location Deploy service definition.

  1. Do one of the following:

    • Define and install a Business Area in Oracle LSH; see the Oracle Life Sciences Data Hub Application Developer's Guide. This deploys a default .rpd file for the Business Area generated in Oracle LSH.

    • Put a dummy .rpd file in the Server\Repository folder under the Oracle BI installation folder (for example, D:\OracleBI\Server\Repository). You can rename and use the file paint.rpd that comes with OBIEE.

  2. In Windows, go to Control Panel, then Administrative Tools, then Data Sources (ODBC), then System DSN, and open the Analytics Web DSN Configuration screen.

  3. Enter the name of the Oracle BI Server computer in the Server field of the Analytics Web DSN configuration screen. Click Next.

  4. Check Change the default repository to and enter the logical name of the .rpd file that you set as the default in the NQSConfig.ini file on the Oracle BI server computer.

  5. Check Connect to Oracle BI Server to obtain default settings for the additional configuration options and supply the Oracle BI Server login ID and password.

  6. Click Next. The Presentation Services Server tries to connect to the BI Server and looks for the .rpd file.

  7. If the connection succeeds, you can see the name of the Oracle LSH Business Area instance under the Database column. Click Finish.

Set Up Oracle Business Intelligence Administration Tool

To use the Oracle Business Intelligence Administration Tool, each Definer must do the following on his or her local PC:

  • Install Oracle Business Intelligence Client Tools in the location specified by the system administrator.

  • Insert the CD-ROM supplied by the system administrator.

  • Ensure that cdrconfig.xml has the correct directory path for the Oracle BI Administration tool.

  • In the Oracle BI Administration Tool, set up connectivity with the Oracle LSH database. See "Set Up Database Connectivity" for information.

Security Configuration

This section contains the following topics:

Data Security

Security access to data is controlled in Oracle LSH: people with Oracle LSH user accounts that have access to the Business Area can see data in the corresponding Subject Area in OBIEE Answers. No OBIEE user accounts are required. Users with the required privileges can see blinded and noncurrent data if they launch OBIEE Answers from within Oracle LSH and request to see such data.

When users launch OBIEE Answers from outside Oracle LSH, through the URL of the OBIEE Presentation Services Server, they cannot see blinded or noncurrent data even if they have the required privileges within Oracle LSH.

Creating an OBIEE Remote Location and Connection for RPD Password Security

Oracle recommends that you define a remote location and connection for each non-restart OBIEE service location in order to provide password protection for the deployed .rpd file in the Administration Tool.

When the Definer installs an OBIEE Business Area in Oracle LSH, the deploy script deploys the latest version of the .rpd file to the BI Server. During the deployment, Oracle LSH passes a user name and password to the deployment script if a remote location and connection are defined for the service location.

When the Definer works on the .rpd file in the Administration Tool, he or she must log in as administrator and enter the password you specify in the remote connection definition. You can change this password at any time.

If you do not define a remote location and connection for the service location, no password is required to work on the .rpd file in the Administration Tool.

Create an OBIEE Remote Location

To define a Remote Location:

  1. Click the Remote Location subtab under the Administration tab. The Maintain Remote Locations screen opens.

  2. Click Add Remote Location. The Create Remote Location screen appears.

  3. Enter values in the following fields:

    • Name. Enter the exact same name you have given for the service location.

    • Description. Not required.

    • DBLINK Prefix. Enter any value. The system does not use this value.

    • Connect String. Enter any value. The system does not use this value.

    • Adapter. Select OBIEE from the drop-down list.

    • Conversion Multiplier. Do not enter a value.

  4. Classification: The system does not use these values.

  5. Click Apply to save your work. The system opens the main screen for the new Remote Location.

    By default, the Remote Location inherits the user group assignments of the Adapter Area.

Create an OBIEE Remote Location Connection

For each OBIEE Remote Location, create a Remote Connection.

To define a Connection:

  1. In the main screen for the Remote Location for which you want to create a Connection, click Create Connection. The Create Connection screen opens.

  2. Enter values in the following fields:

    • Name. Enter a name for the Connection.

    • Description. Not required.

    • User Name. Enter administrator.

    • Password. Enter the password you want to require for the .rpd file. Oracle LSH encrypts the password for security.

    • Connection Type. The system does not use this value.

    • Remote Location. The system populates the field with the name of the Remote Location for which you are defining this Connection.

  3. Classification: The system does not use these values.

  4. Click Apply to save your work. The system displays the main screen for the new Connection.

Using Separate URLs to Control Access

Each Presentation Services Server must be installed on a different computer and has a different URL. You can use this setup to control what users can see in OBIEE. For example:

  • If you have only one Business Area using a particular Presentation Services Server, users launching OBIEE with that URL can see only the Subject Area that corresponds to that Business Area. You can include the Subject Area in the URL so that users go directly to the Subject Area page; for example: http://C2:9704/analytics/saw.dll?Answers&SubjectArea=X

  • You can organize your Business Areas so that only related Business Areas use the same Presentation Services Server; for example, all studies in a single project have a Business Area, and there is another Business Area for the project as a whole. Users launching OBIEE with that URL can see only the Subject Areas related to that project, and can see data only for the Subject Areas that correspond to Business Areas on which they have View privileges.