3 Managing Oracle BI Discoverer Connections

This chapter applies only if the Discoverer installation is associated with an Oracle Internet Directory and with the two database schemas that Discoverer requires (the PStore and Portlet Provider schemas). For more information, see Section 1.3, "About Oracle BI Discoverer installations."

If Discoverer is not associated with an Oracle Internet Directory (and the PStore and Portlet Provider schemas), then Discoverer connections (SSO-enabled) are not available to end users. Non-SSO public and private connections are available even if Discoverer is not associated with an Oracle Internet Directory.

This chapter explains how to create and manage Oracle BI Discoverer connections, and includes the following topics:

3.1 What is an Oracle BI Discoverer connection?

Discoverer connections enable Discoverer end users to start Discoverer without having to re-enter database login details each time they start Discoverer.

An Oracle BI Discoverer connection consists of the following database login details:

Database username to identify the Discoverer end user

Database password to authenticate the Discoverer end user

Name of the database containing the information that the Discoverer end user wants to analyze

(optional) An Oracle Applications responsibility to specify the Discoverer end user's responsibility when using Discoverer with Oracle Applications

(relational data source only) The End User Layer to be used

The language that should be used in Discoverer

In the example shown in Figure 3-1, a connection named Customer Reports has been created. This connection contains login information to enable end users to connect to the database containing customer reports, without having to enter login details.

Figure 3-1 Connections page in Oracle BI Discoverer Plus

Notes

A connection is visible to both Discoverer Plus and Discoverer Viewer end users.

If end users do not want to store login details in a connection, they can enter login details directly by using the Connect Directly area of the Discoverer connections page.

3.1.1 About Discoverer private connections and Single Sign-On

If single sign-on is enabled, Discoverer private connections work as follows:

When Discoverer end users select a Discoverer private connection for the first time, they are prompted to enter their Oracle Single Sign-On or Oracle Access Manager details (if they have not been authenticated).

After Discoverer end users have been authenticated by Oracle Single Sign-On or Oracle Access Manager, they can select a Discoverer private connection without entering the Discoverer password.

If single sign-on is enabled, Discoverer end users can use their private connections from any client machine. If single sign-on is not enabled, private connections are stored as cookies, and are accessible only on the machine and browser on which they were created. For more information about Single Sign-On, see Section 3.1.1, "About Discoverer private connections and Single Sign-On."

Public connections are created and maintained by Discoverer middle tier managers.

For example, if you want to provide Discoverer end users with access to the Discoverer sample workbooks, you might create a public connection called 'Sample workbooks'.

Public connections have the following characteristics:

A public connection is available to Discoverer Plus and Discoverer Viewer end users.

Note:

When you create a public connection to a multidimensional data source, the public connection is available only to Discoverer Viewer and Discoverer Portlet Provider users. Public OLAP connections are not available to Discoverer Plus OLAP users.

Public connections enable Discoverer Plus and Discoverer Viewer end users to access data to which the PUBLIC role has access.

In a secure Discoverer environment you might want to use only public connections, so that you can restrict database access to login details that you specify. In other words, you might want to prevent Discoverer end users from creating private connections. For more information, see Section 3.6, "How to create public connections."

Public connections are not available to Discoverer Plus OLAP users. If you disallow private connections, Discoverer Plus OLAP users always have to connect to Discoverer directly.

When you enable Discoverer end users to create their own private connections:

End users can specify any login details (such as username, password, database, and EUL) for the connections that they create.

End users can open any workbook in any EUL to which they successfully connect (if they have sufficient database privileges).

When end users create private connections:

If they specify a database by using an alias, they can connect to databases that have an entry in the tnsnames.ora file.

If they specify a database by using the full tnsnames entry for the database (SID, address, and port), they can connect to databases that do not have an entry in the tnsnames.ora file on the Discoverer middle tier.

For example, you might enter the following string in the Database field:

3.6 How to create public connections

You create a public connection when you want to provide predefined login details to Discoverer Plus and Discoverer Viewer users. For example, you might create a public connection called Start tutorial, which connects to the tutorial database as a tutorial user.

Note:

When you create a public connection to a multidimensional data source, the public connection is available only to Discoverer Viewer and Discoverer Portlet Provider users. Public OLAP connections are not available to Discoverer Plus OLAP users.

The Database Details column on the Discoverer connections page is visible only in Internet Explorer.

If existing public connections are not displayed under Public Connections, then it means that the Oracle Business Intelligence installation is not associated with an Oracle Internet Directory and with the two database schemas that Discoverer requires (the PStore and Portlet Provider schemas). For more information, see Section 1.3, "About Oracle BI Discoverer installations."

Click Create

The Create Public Connection page is displayed.

Enter the connection details and then click OK to save the details.

The new connection that you created is displayed in the Discoverer Public Connections list.

When Discoverer end users connect to Discoverer Plus or Discoverer Viewer, they can select the connection that you created.

If you specify a database by using the full tnsnames entry for the database (SID, address, and port), you can connect to databases that do not have an entry in the tnsnames.ora file on the Discoverer middle tier.

For example, you might enter the following string in the Database field:

By default, users must enter the TNS alias of the database when creating connections to Discoverer. You can, however, allow users to enter a connect string rather than a TNS alias, by setting the environment variable DISCOVERER_ALLOW_DB_CONNECT_STRING to YES.

3.7 How to delete public connections

You delete a public connection when you no longer want to provide predefined login details to Discoverer Plus and Discoverer Viewer users.

In the Private Connections region, specify whether users can create private connections, by using the Allow users to define and use their own private connections in Discoverer Plus and Discoverer Viewer check box.

If you want Discoverer end users to be able to create their own private connections, select the check box. Otherwise, clear the check box.