2-22 Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer
Figure 2–2 Connect to Discoverer Viewer page
Note : If single sign-on is enabled, you are first asked to authenticate as a Oracle
Single Sign-On or Oracle Access Manager user.
2.
Do one of the following:
■
Select a connection in the Connection column. Tip:
If no connections are displayed in the Connection column, you must
create a connection before continuing. For more information about creating private connections, see Oracle Fusion Middleware Users Guide for Oracle
Business Intelligence Discoverer Viewer. You can also use public connections that have been created by the Discoverer manager for more information, see
Section 3.6, How to create public connections .
■
Enter login details directly using the Connect Directly area, and click Go.
The Worksheet list page is displayed.
3. Select a worksheet in the Name column to display the workbook in Discoverer
Viewer. You are now running Discoverer Viewer.
Notes
■
To start Discoverer Viewer over HTTPS, enter the Discoverer Viewer HTTPS URL for example, https:host.domain:HTTPS portdiscovererviewer. For more
information about running Discoverer Viewer over HTTPS, see Section 2.5, About
running Discoverer over HTTPS .
2.12 How to modify the URL that starts Discoverer
In general, you start Discoverer by entering a URL in a browser, as described in this chapter. That URL has a format similar to the following:
http:host.domain:portdiscoverercomponent-name
Starting Oracle BI Discoverer 2-23
The discovererpart of that URL is called the context root. If your organization requires that all users enter URLs that have specific formats that is, have a certain
context root, then you can modify the default URL that starts Discoverer to match those requirements. After you modify the default URL, share that URL with the
Discoverer users in your organization.
The following procedure describes how to modify the default URL for Discoverer by changing the context root. As part of the modification, you stop and restart all OPMN
processes and WLS_DISCO Managed Server. WLS_DISCO Managed Server has a complete set of Java EE containers written entirely in Java that execute on the Java
Virtual Machine JVM of the standard Java Development Kit JDK. Discoverer has a Java EE application that is deployed to WLS_DISCO. The Discoverer application is
accessed through the port for the Oracle HTTP Server.
The following procedure uses an example of modifying the URL to include the myBIBI11 directory in the context root.
1.
Stop the OPMN using the following opmnctl command: ORACLE_INSTANCEbinopmnctl stopall
2.
Run the command changeContextRoot, which is located in the ORACLE_ INSTANCE
DiscovererDiscoverer_instance-nameutil folder as follows:
changeContextRoot presentContextRoot newContextRoot To include the directory myBIBI11 in the context root, run the command as
follows: changeContextRoot discoverer myBIBI11discoverer
3.
If SSO is enabled, edit the module_disco.conf file by following these steps:
a.
Open the module_disco.conf file from the ORACLE_ INSTANCE
\config\OHS\ohs-component-name\moduleconf directory in a text editor.
b.
Navigate to the following line: Location discovererportletproviderviewer
c.
Edit the line to read like: Location myBIBI11discovererportletproviderviewer
d.
Navigate to the following line: Location discoverer
e.
Edit the line to read like: Location myBIBI11discoverer
f.
Save your changes and close the file.
4.
Restart OPMN using the following command: ORACLE_INSTANCEbinopmnctl startall
To use the modified context root, you must update the Discoverer application as described in the Update redeploy an Enterprise application section of Oracle Fusion
Middleware Oracle WebLogic Server Administration Console Help
2-24 Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer
After you modify the files and restart the service as described in the previous procedure, users can start Discoverer components using the following URLs:
■
Discoverer Plus: http:host.domain:portmyBIBI11discovererplus
■
Discoverer Viewer: http:host.domain:portmyBIBI11discovererviewer
■
Discoverer Portlet Provider: http:host.domain:portmyBIBI11discovererportletprovider
Note : If single sign-on is enabled for Discoverer, to modify the URL you must change
the Location tag for each Discoverer component in the mod_osso.conf file. For example, to change the URL for Discoverer Plus, change Location
discovererplus to Location myBIBI11discovererplus in the mod_osso.conf file.
For more information about editing mod_osso.conf, see Section 13.8.1.2, How to
enable and disable Single Sign-On for Discoverer.
3
Managing Oracle BI Discoverer Connections 3-1
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:
■
Section 3.1, What is an Oracle BI Discoverer connection?
