Oracle Discoverer 4i Configuration Guide for Oracle9i Application Server Release 4.1 for UNIX A87572-01 |
Library | Service | Contents | Index

# 1
Overview of Oracle Discoverer 4i

Oracle Discoverer is a business intelligence tool for analyzing data. Using Oracle Discoverer's award-winning user interface, users can access and analyze database data.

There are two Oracle Discoverer 4i products:

- Oracle Discoverer 4i Plus is the Internet version of the award-winning product, Discoverer Plus (Release 4.1). With Discoverer, business professionals can get and analyze data in a company's database without having to understand difficult database concepts. Using Wizard dialogs and menus, Discoverer guides them through the steps to get and analyze data to support their business decisions.

- Oracle Discoverer 4i Viewer is a tool for viewing workbooks created by users of the client/server or web versions of Discoverer Plus. Oracle Discoverer 4i Viewer can also be used to integrate database output into a web site and portal and is easily customized to conform to a particular web site look and feel, or to build custom Discoverer applications for the web. Oracle Discoverer 4i Viewer is also optimized for performance and designed to minimize network traffic.

## 1.1 Oracle Discoverer 4i and Oracle9i Application Server

Oracle Discoverer 4i is installed as part of Oracle9i Application Server. The default installation is to install all Discoverer components on a single machine. However, you can install different components on different machines to improve performance (for more information, refer to Chapter 3, "Installing Oracle Discoverer 4i on multiple machines".

## 1.2 The Discoverer 4i architecture

Oracle Discoverer 4i has a multi-tiered architecture. This architecture takes advantage of the distributed nature of the Web environment. While it is possible to install all tiers of the Discoverer 4i architecture on the same machine, we recommend distributing your installation over multiple machines to maximize performance.

### 1.2.1 The three tier architecture of Discoverer 4i Plus

Discoverer 4i Plus has a three tier architecture:

- Client

- Discoverer Services

- Database

### 1.2.2 The n-tier architecture of Discoverer 4i Viewer

Discoverer 4i Viewer has an n-tier architecture:

- Client

- HTTP Server

- Discoverer Services

- Database

### 1.2.3 The Client tier (Discoverer Plus and Viewer)

The first tier of the Discoverer 4i architecture is the client--a user's computer.

There is no setup or installation to do on the client machine, nor does this machine need to have access to any database.

#### 1.2.3.1 The Client tier and Discoverer Plus

In the case of Discoverer Plus, the only requirement for the client machine is that it runs a Java-enabled Web browser (e.g. Microsoft Internet Explorer, or Netscape Navigator with Oracle JInitiator). By accessing the URL that you (the Discoverer administrator) provide, users can log on and run Discoverer to analyze data.

#### 1.2.3.2 The Client tier and Discoverer Viewer

In the case of Discoverer Viewer, the only requirement for the client machine is that it can run HTML through a web browser (e.g. Microsoft Internet Explorer or Netscape Navigator). By accessing the URL that you (the Discoverer Administrator) provide, users can connect and run Oracle Discoverer 4i Viewer to view data.

### 1.2.4 The HTTP Server tier (Discoverer Viewer only)

For Discoverer Viewer, the HTTP Server tier (and specifically the HTTP Server's servlet engine) is where the Discoverer 4i Viewer servlet is installed. Running the Java-enabled servlet engine on the HTTP Server tier removes the need for Java to run on the client tier.

Note that in a multiple machine installation, a component from the Discoverer Services tier (the Locator component) is usually installed on the same machine as the HTTP Server tier.

#### 1.2.4.1 What is a servlet?

A servlet comprises modules of Java code that run on a server machine to answer HTTP requests from client machines. Using a servlet minimizes client-side processing.

#### 1.2.4.2 What is a servlet engine?

A servlet engine comes as part of (or as a plug-in to) the HTTP Server software and is the environment in which servlets run. The servlet engine incorporates a Java Virtual Machine (JVM) and implements the Java Servlet API.

#### 1.2.4.3 What is the Discoverer 4i Viewer Servlet?

The Discoverer 4iViewer Servlet uses an XML/XSL processor to generate HTML pages from HTTP requests.

The Discoverer 4iViewer Servlet and the XML/XSL processor are installed in the HTTP Server's servlet engine

### 1.2.5 The Discoverer Services tier (Discoverer Plus and Viewer)

The Discoverer Services tier is the portion of the Discoverer architecture that the Discoverer administrator installs and maintains.

The Discoverer Services tier consists of the following components:

- the Discoverer Plus Java applet and HTML pages (Discoverer Plus only)

- the Locator component (Discoverer Plus and Viewer)

- the Session component (Discoverer Plus and Viewer)

- the Preferences component (Discoverer Plus and Viewer)

The Discoverer Java applet and HTML pages are installed on an HTTP server machine. The Locator is also usually installed on the HTTP server. The remaining components are installed on one or more application servers. You can install Discoverer Services on one server machine or across many machines.

In addition, the following CORBA (Common Object Request Broker Architecture) components from VisiBroker are installed:

- Object Activation Daemon (OAD)

- SmartAgent

These CORBA components are responsible for activating new components and providing a location service when a user requests that a Discoverer session begin.

#### 1.2.5.1 The Discoverer Java Applet and HTML Pages (Discoverer Plus only)

The Discoverer Java applet provides the Discoverer 4i Plus user interface and functionality for analyzing data in the database. The applet runs in a Java-enabled browser on a client machine.

The HTML pages are the Web pages that the user sees when logging on to the URL location for Discoverer 4i Plus.

Note: The first time a user logs on, the Discoverer Java applet is initialized and cached on the user's machine. Later, when the user logs on again, the Discoverer Java applet runs from the local cache and does not need to be downloaded.

#### 1.2.5.2 The Session Component (Discoverer Plus and Viewer)

The Session component provides the link between the client machine (running either Discoverer 4i Plus or Discoverer 4i Viewer) and the database. The Session component contains all of the application logic and performs all of the Discoverer operations such as connecting to the database or opening a workbook.

A machine that has a Session component installed can run multiple concurrent sessions for clients. To increase overall performance, you can install the Session component on many individual machines, and each machine can run multiple concurrent sessions. Distributing the Session component on several machines also improves availability. If one machine is not operating, other machines handle the session requests.

The Session component can run on any server machine (i.e. HTTP server machine or application server machine) in the Discoverer Services configuration that runs a version of UNIX to which Discoverer has been ported.

#### 1.2.5.3 The Locator Component (Discoverer Plus and Viewer)

The purpose of the Locator component is to receive a request for a session from the client machine (running either Discoverer 4i Plus or Discoverer 4i Viewer), find the next available application server machine, start a new session, and return a reference for the new session back to the client. Once the client has received this reference, the client and the session communicate directly and the Locator waits for the next request. Install the Locator component on the HTTP Server machine (i.e. the machine running the HTTP Server software). You need only one Locator component on the network for the Discoverer Services.

This structure means that, after a session begins, the HTTP Server machine is no longer involved with the communication between the client and the session. A major advantage of this structure is that no additional traffic is routed through the HTTP Server machine after the session has started, so the performance of the HTTP Server machine is not affected as the number of sessions increases. Another benefit is that if the HTTP Server machine or the Locator component fails, the user session is not interrupted because the client is communicating directly with the application server.

The Locator component also helps balance the load on the available application servers because it determines which application server will start each requested session. You can specify how the Locator allocates sessions to achieve the best performance.

#### 1.2.5.4 The Preferences Component (Discoverer Plus and Viewer)

The Preferences component provides a single location for preference settings for all users of Discoverer 4i (both Discoverer 4i Plus and Discoverer 4i Viewer. The Discoverer Services rely on stored preference settings to dictate certain aspects of behavior. You install only one Preferences component for the Oracle Discoverer Services.

Having a single Preferences component is important in a distributed environment where different components can run on different machines. The Preferences component provides consistent preference settings for all components regardless of where they are running. The Preferences component must be installed on a server running a version of UNIX to which Discoverer has been ported.

### 1.2.6 The Database Tier (Discoverer Plus and Viewer)

The database tier of the Discoverer architecture contains:

- the data that users want

- the End User Layer (EUL) that provides an easy to understand view of the data

- the Discoverer workbooks that users can work with to view and analyze the data

You use the Discoverer Administration Edition to create and maintain the EUL.

Note: Before users can use Discoverer to analyze data, the database must contain a Discoverer Release 4.1 EUL. You must create or update the EUL with Oracle Discoverer Administration Edition Release 4.1 or later.

### 1.2.7 Which server machines to install the Discoverer Services components on?

The Discoverer Services software components must each be installed on a server machine. There are three types of server machine that implement the Discoverer architecture:

- the HTTP Server machine

- the Application Server machine(s)

- the Master Discoverer Server machine

These server machines need not be physically different machines. In fact, in a default Oracle9i Application Server installation the HTTP Server machine, the Application Server machine, and the Master Discoverer Server machine are all the same machine.

#### 1.2.7.1 The HTTP Server machine

The HTTP Server machine is a machine running HTTP Server software on which you install the Locator component. You only need one HTTP Server machine as part of your Discoverer environment.

If you install the different Discoverer Services software components on a single machine, that machine is both the HTTP Server machine and the Application Server machine.

#### 1.2.7.2 The Application Server machine(s)

The Application Server machine is the machine on which you install the Preferences component and the Session component. You can have one Application Server machine or many Application Server machines as part of your Discoverer environment.

If you install the different Discoverer Services software components on a single machine, that machine is both the Application Server machine and the HTTP Server machine.

If you distribute the different Discoverer Services software components across several machines, you must install the Session component (but not the Preferences component) on every machine. In this scenario, each machine is an Application Server and multiple sessions can be started on each machine. Note that the Preferences component is only installed on one Application Server machine (referred to as the Master Discoverer Server machine). The other Application Server machines are referred to as Additional Discoverer machines.

##### 1.2.7.2.1 The Master Discoverer Server machine

If you install the Session component on multiple Application Server machines, you must designate one of those Application Server machine as the Master Discoverer Server. In addition to the Session component, you must also install the Preferences component on the Master Discoverer Server. Note that the Master Discoverer Server is the only machine on which you install the Preferences component.

## 1.3 How Oracle Discoverer 4i works

### 1.3.1 The Oracle Discoverer 4i Plus process

1. The user launches a Web browser on a client computer and types the URL of the HTTP Server.

2. The Web browser accesses the URL on the HTTP Server.

3. The HTTP Server retrieves the HTML pages and the Discoverer applet and transmits them to the client computer.

4. The Discoverer applet finds the Locator (the recommended location for the Locator is on the HTTP Server).

5. The Locator starts a Session component on an Application Server machine and a Discoverer session starts.

6. The Session component creates a reference and passes the reference to the Locator.

7. The Locator passes the reference to the client computer.

8. The client computer uses the reference to contact the Discoverer session directly. The HTTP server is no longer being accesed.

9. The Discoverer session requests and receives data from the database.

10. The Discoverer session transmits data to the Web browser on the client machine.

### 1.3.2 The Oracle Discoverer 4i Viewer process

1. The user launches a Web browser on a client computer and types the URL of the HTTP Server.

2. The Web browser accesses the URL on the HTTP Server.

3. The Discoverer 4i Viewer Servlet interprets the HTTP request.

4. The Locator starts a Session component on an Application Server machine and a Discoverer session starts.

5. The Discoverer session requests and receives data from the database.

6. The Discoverer session transmits data to the Discoverer 4i Viewer Servlet.

7. The Discoverer 4i Viewer Servlet generates an HTML page and sends it to the browser.

#### 1.3.2.1 How the Discoverer 4i Viewer Servlet interprets the HTTP request

The Oracle Discoverer 4i Viewer Servlet interprets the HTTP request from the client browser, and makes the necessary calls to the Discoverer Services.

The server response represented in XML is generated by the Servlet and sent to an XML/XSL processor.

The XML/XSL processor combines XML with an XSL configuration file that defines the representation of the User Interface and generates the output (e.g. HTML) to send back to the browser.

The Oracle Discoverer 4i Viewer Servlet is composed of two primary layers - the application logic layer and the presentation logic layer.

The application logic layer manages the handling of the HTTP request, the state of the Discoverer Services, and generates the XML representing the logical state of the Discoverer server and the data for a given client.

The presentation logic layer takes the XML and uses XSL to generate a response in a given format (e.g. HTML, Microsoft Excel, XML etc.). The presentation logic can be customized to alter the appearance of the user interface (by editing XSL files). See Chapter 5, "Customizing Oracle Discoverer 4i Viewer" for details.

## 1.4 Scalability and load balancing

Oracle Discoverer 4i Plus and Oracle Discoverer 4i Viewer are automatically installed to run on the Oracle9i Application Server as a single machine installation. However they are designed to be deployed on multiple machines (for more information, refer to Chapter 3, "Installing Oracle Discoverer 4i on multiple machines").

The Discoverer Services can be replicated so that different sessions can be started on alternate machines to balance the load.

In this way very large numbers of Discoverer users may be supported, since there is no single bottleneck. Multiple Discoverer sessions can run on a single machine, or can be spread across multiple machines as required.

The Discoverer 4i Viewer Servlet can also be distributed.

| Copyright © 2000 Oracle Corporation. All Rights Reserved. |
Library | Service | Contents | Index