Managing and Configuring Discoverer 4-9
4.3 How to start, stop, and restart the Discoverer preferences server component using opmnctl
You might need to stop and restart the Discoverer preferences server component for maintenance for example, when you apply a Discoverer patch. You can stop, start,
and restart the Discoverer preferences server component by using opmnctl commands.
To stop, restart, or start the Discoverer preferences server component by using opmnctl
commands:
1. At the command line, navigate to the ORACLE_INSTANCEbin directory.
2.
Enter the following command:
■
To stop the preferences server component: opmnctl stopproc ias-component=Discoverer_instance-name
■
To start the preferences server component: opmnctl startproc ias-component=Discoverer_instance-name
■
To restart the preferences server component: opmnctl restartproc ias-component=Discoverer_instance-name
4.4 About starting and stopping Discoverer servlets
You might need to stop and restart Discoverer servlets to perform maintenance tasks for example. You can start and stop Discoverer servlets running on a standalone
machine in an Oracle farm from any machine in the farm.
For more information about the Discoverer servlets, see Section 1.9.1, About the
Discoverer Java EE applications .
4.4.1 What happens when you start Discoverer servlets?
When you start the Discoverer Java EE applications:
■
If all the Discoverer servlets are running, Discoverer Viewer, Discoverer Plus, Discoverer Portlet Provider, and Discoverer Web Services can connect to
Discoverer sessions and serve requests. Users can, for example, open workbooks by using Discoverer Viewer, build worksheets by using Discoverer Plus, create
portlets by using Discoverer Portlet Provider, and return data by using Discoverer Web Services.
The Current Status indicator is set to Up, showing that the Discoverer Java EE applications are running.
■
If the Discoverer Java EE applications fail to start:
– The Current Status indicator is set to Down, showing that the Discoverer Java
EE applications are not running.
Note: When you stop the Discoverer preferences server component,
Discoverer continues to work using the current set of default preferences. Any changes made are valid only for the current session;
changes to preferences made during the current session are lost when the session is closed.
4-10 Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer
– Fusion Middleware Control displays an error message indicating why the
Discoverer Java EE applications failed to start.
4.4.2 What happens when you stop Discoverer servlets?
When you stop the Discoverer Java EE applications:
■
Discoverer Plus and Viewer users cannot access the Discoverer Plus and Viewer URLs and an information message is displayed informing users that the
Discoverer Java EE applications are down that is, a No Response from Web Server.
■
Discoverer Portlet Provider users cannot publish new portlets, edit defaults, and customize or refresh portlets. An information message is displayed informing
users that the Discoverer Java EE applications are down that is, a No Response from Web Server.
■
Discoverer servlets release system resources that they are using.
■
Discoverer displays existing portlets in Oracle Portal pages by using cached data.
■
All Discoverer sessions are terminated.
■
The following processes are terminated if running:
– Discoverer Session
– Discoverer Java EE applications
■
Discoverer Plus, Discoverer Viewer, Discoverer Portlet Provider, and Discoverer Web Services cannot connect to Discoverer sessions or serve requests that is, users
cannot open workbooks by using Discoverer Viewer, build worksheets by using Discoverer Plus, create portlets by using Discoverer Portlet Provider, or return
data by using Discoverer Web Services.
■
The Current Status indicator is set to Down, showing that the Discoverer Java EE applications are not running.
■
If the Discoverer Java EE applications service fails to stop:
– If all of the components are running, the Current Status indicator shows that
the Discoverer Java EE applications are running.
– If some not all of the components are running, the Current Status indicator
shows that the Discoverer Java EE applications are in an unknown state.
– Discoverer displays an error message indicating why the Discoverer Java EE
applications failed to stop.
4.4.3 How to start and stop the Discoverer Java EE applications by using Fusion Middleware Control