What happens when you enable and disable Discoverer client-tier components

Managing and Configuring Discoverer 4-11 ■ To start the Discoverer servlets Discoverer Plus, Discoverer Viewer, Discoverer Portlet Provider, and Discoverer Web Services, click Start Up. ■ To stop the Discoverer servlets, click Shut Down.

4.4.4 About starting and stopping the Discoverer Java EE applications using WLST

You can use the WebLogic Scripting Tool WLST to start and stop Discoverer Java EE applications. For more information about using WLST commands, see the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

4.5 About enabling and disabling Discoverer client-tier components

You might want to disable and enable Discoverer client-tier components Discoverer Plus, Discoverer Viewer, Discoverer Portlet Provider, and Discoverer Web Services for the following reasons: ■ To prevent new users from connecting to Discoverer ■ To restrict access to Discoverer components

4.5.1 What happens when you enable and disable Discoverer client-tier components

When you enable Discoverer client-tier components, ■ If Discoverer Java EE applications are running, the client-tier components continue normal operation. ■ If Discoverer Java EE applications are not running, nothing happens immediately. When you start the Discoverer Java EE applications, the Discoverer client-tier components resume normal operation When you disable Discoverer Plus and Discoverer Viewer, ■ If Discoverer Java EE applications are not running, nothing happens. ■ All existing Discoverer Plus or Discoverer Viewer sessions continue to run until users end their sessions. ■ A message is displayed informing the Discoverer end user that the component is disabled. ■ Requests for new user sessions are not accepted. Users whose sessions time out due to inactivity cannot continue to use Discoverer Plus or Discoverer Viewer. Note : A user time out is determined differently between Discoverer Plus and Discoverer Viewer as follows: Note: Alternatively, you can start and stop Discoverer Java EE applications through the WebLogic Administration Console, by performing the following steps: 1. Start the WebLogic Administration Console by using the following URL: http:host:7001console 2. Under Domain Structure in the left navigation pane, click Deployments. 3. In the list of deployments, select the Discoverer row. The Start and Stop buttons are enabled. 4. Click the appropriate button, depending on whether you want to start or stop the applications. 4-12 Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer – Discoverer Plus uses the server process to determine user time outs – Discoverer Viewer uses the servlet to determine user time outs ■ When a user attempts to access a Discoverer Plus or Discoverer Viewer URL, Discoverer displays an error message explaining that the service is unavailable. When you disable Discoverer Portlet Provider, ■ If Discoverer Java EE applications are not running, nothing happens. ■ New Discoverer portlets cannot be added to Portal pages. ■ A user cannot use the Edit Defaults option or the Customize option for existing portlets. ■ If a user is editing defaults or customizing a portlet when the component is disabled, they can finish the task. ■ Scheduled refreshes that are in progress can continue until they are complete. However, scheduled refreshes that have not yet started do not run until you enable the Portlet Provider component. ■ If a user attempts to add a new portlet, edit defaults, or customize an existing portlet, Discoverer displays a message explaining that the service is not available. ■ Discoverer continues to display data in existing Discoverer portlets using the last cached data.

4.5.2 How to disable Discoverer client-tier components