Oracle Discoverer 3i Viewer Edition Installation and Administration Guide

Z26688-02

Contents

Prev Next

2
Installing Oracle Discoverer 3i Viewer Edition

Please read the release notes (Readme.wri) in conjunction with this guide. These contain the latest information and may affect instructions in this guide.

Oracle Discoverer 3i Viewer Edition does not require any downloads, plugins nor installation of any code on the client. The only client requirement is to be able to communicate via HTTP and render HTML or XML. See Section 2.1.3, "Software requirements" for the browser specification.

Before installing the components of Oracle Discoverer 3i Viewer Edition, Oracle Discoverer Server must first be fully installed and configured.

This chapter provides the information you need to install the necessary components to run Oracle Discoverer 3i Viewer Edition. The information covered in this chapter includes:

2.1 Hardware and Software Requirements

This section references the minimum hardware requirements and the software necessary to install and run Oracle Discoverer 3i Viewer Edition.

2.1.1 Client hardware requirements

Oracle Discoverer 3i Viewer Edition is rendered in html and requires no extra hardware, only the ability to run a browser (See Section 2.1.3.1, "Client Web Browsers").

2.1.2 Server hardware requirements

For servers running Discoverer Server sessions:

2.1.2.1 Server memory requirements

The following table list the RAM needed for each Discoverer Server component.

Table 2-1 Server memory requirements by component
Discoverer Component  RAM Required 

Locator 

5.5 MB (and 4.5 MB for JRE) 

Session 

Minimum 3.8 MB per active concurrent session (actual requirements vary based on workbook size and complexity) 

Preferences 

0.5MB 

2.1.3 Software requirements

The software requirements for the environment are:

2.1.3.1 Client Web Browsers

The following Web browsers support Oracle Discoverer 3i Viewer Edition:

Table 2-2 Supported browsers by platform (All higher versions supported)
Operating System  Microsoft Internet Explorer
3.02* 4.01
 
Netscape Navigator
3.0* 4.0X
 

Windows NT 4.0 

x

x

x

x

Windows 98 

 

x

x

x

Windows 95 

x

x

x

x

Solaris/SPARC 

 

 

x

x

Although version 3.x browsers are supported for use with Oracle Discoverer 3i Viewer Edition (see Table 2-2), version 4.x (and above) browsers are recommended for optimum viewing.

Service pack 5 for NT is recommended.

2.1.3.2 HTTP Servers supported by Oracle Discoverer 3i Viewer Edition

Oracle Discoverer 3i Viewer Edition supports the following HTTP servers/servlet engines:

The HTTP servers must be able to handle global mime types for .exe files.

2.1.3.3 Additional environment information required

You also need the following information to install Discoverer 3i Application server:

2.2 Planning the Discoverer Server Configuration

The following table shows which components you can install, on which server, and the required types of server:

Table 2-3 Servers Required for Discoverer Server Components
Discoverer Server name  Installable component  Type of server 

HTTP Server 

Locator  

Windows 4.0 NT Server or Solaris 

HTTP Server 

Discoverer 3i Viewer Edition 

Any HTTP Server (for example, NT or Solaris) 

Master Discoverer Server 

Preferences 

Windows 4.0 NT Server 

Master Discoverer Server 

Session 

Windows 4.0 NT Server 

Other Discoverer Server 

Session 

Windows 4.0 NT Server 

Refer to your Web Server documentation to find out whether you can install to NT Workstation or not.

The Locator, Session, and Preferences components must all be installed on the same subnet. If you plan to install multiple instances of Discoverer 3i Application server on the subnet, for example one instance for the Accounting Department and another for Engineering, install a Locator component and Preferences component for each instance, and be sure to give the instances unique names during the installation process.

The following illustration shows typical configurations of Discoverer Server.


Note:

Configure the Net8*Client software to provide access to the Oracle databases the users will access. Those databases contain the Discoverer EUL, Business Areas, and workbooks. If you want to provide access to the databases other than through the tnsnames.ora file, you can use an Oracle Name Server that is identified in your SQLNET.ora file. 


When installing Discoverer Server in a distributed mode, designate one machine as the Master Discoverer Server to host the Discoverer Preferences and Session component. Each machine that will run Oracle Discoverer 3i Viewer Edition sessions requires a Session component.

Because each concurrent active session can require 3.8 to 18 MB of RAM, you can estimate the number of concurrent sessions that each machine can support. To help you allocate machine resources for concurrent sessions, load balancing among the machines is part of the setup procedure. See Section 2.3.4.1.1, "Examples of Load Balancing" for a complete description of load balancing.

2.3 Installing Discoverer 3i Server

Step-by-step instructions explain how to install or remove the following:

The following section headings explain the process:

2.3.1 Installing Discoverer 3i Server and Servlet Software

You can install Oracle Discoverer 3i Edition Server and Servlet software on a single computer or distributed over several servers. A distributed installation is recommended for wide use of Discoverer Server. A single-computer installation is typically for running a demonstration, evaluating Discoverer Server, or setting it up for a small group of users.


WARNING: :

Before you start to install Oracle Discoverer 3i Viewer Edition please ensure that all Discoverer processes are shut down on the machine you are installing on. This includes Discoverer 3.1W, Discoverer 3i, processes and locators.
If you find any Discoverer processes running you must end them before beginning the installation. 


2.3.1.1 Web Server and Servlet Prerequisites

You can deploy Oracle Discoverer 3i Viewer Edition across a range of different Web Servers and Servlet Engines, these must be installed before you can install and configure the Oracle Discoverer 3i Viewer Edition Servlet component.

For a brief overview of servlets and servlet engines see Section 1.3.2.1, "What is a Servlet?" and Section 1.3.2.2, "What is a Servlet Engine?".

For step-by-step installation instructions for the servlet see the appropriate areas in Section 2.3.1.3, "Installing Discoverer 3i Server Distributed on Multiple Machines", Section 2.3.1.4, "Installing Oracle Discoverer 3i Viewer Edition Component and Master Server on a Single Machine" or Section 2.3.1.5, "Custom Installation".

For general web server and servlet configuration details see Section 2.3.5, "Common Configuration" .


Note:

All configurations have been tested on the Microsoft's NT 4.0 with Service Pack 5. 


2.3.1.1.1 Web Servers supported

Ensure that one of the following web servers is installed before continuing.

2.3.1.1.2 Java Environments supported

Any of the following can be used and must be installed before installing Oracle Discoverer 3i Viewer Edition.

Figure 2-1 Servlet engine compatibility chart with supported web servers

Web Server Servlet Engine
JRun v2.3.3 ServletExec v2.2c JServ v1.0 Built-in servlet engine
MS IIS 4.x  x x    
MS PWS 4.x  x x    
Netscape ES 4.0*        x
Apache 1.3.6  x   x  
Apache 1.3.9  x x x  
OAS 4.0.8        x

* Netscape ES 4.0 comes with its own built in servlet Engine, but you can also use other servlet engines

2.3.1.1.3 Servlet Engines supported

Any of the following can be used and must be installed before installing Oracle Discoverer 3i Viewer Edition.

2.3.1.1.4 What is not covered in this guide

2.3.1.2 Suggested Installation path

Depending on what you have already installed a number of installation options are available. The installation options and the choices available for each option, are presented here as a guide.

Decide which of the following categories you fall into before installation:

2.3.1.3 Installing Discoverer 3i Server Distributed on Multiple Machines

Installing on multiple machines involves the following steps:

2.3.1.3.1 To Install the Oracle Discoverer 3i Viewer Edition Servlet on an HTTP Server Running Windows NT

  1. Insert the Oracle Discoverer 3i Viewer Edition CD. The Oracle Installer starts. If the Installer does not start, double-click Setup.exe in the root directory on the CD.

    The Oracle Installation Settings dialog box opens.


  2. Type or choose the following information and click OK:

    • Company Name--Your company's name

    • Name--Select [DEFAULT_HOME] for Discoverer Server 3.3.

    • Location--Select the path for [DEFAULT_HOME]. If you previously installed products into the DEFAULT_HOME, you will not be able to modify this directory.

    • Language--The language used on this server.


      Note:

      The language setting does not determine which translated files get installed for Discoverer components. All Discoverer-specific translations are always installed. The Language settings also sets the NLS_LANG variable on NT systems. 


    The View Installation and Administration Guide dialog appears.

  1. Before continuing with the installation, click Yes to view the Discoverer 3i Viewer Installation and Administration Guide. Your computer's default Web browser opens and displays the Installation Guide's table of contents. View online or print out the Installation Guide.

    When you return to the Oracle Installer, the Discoverer Server Installation Options dialog appears.

  2. Click Distributed Installation and click OK.

    The Distributed Installation Options dialog box opens.

  3. Because you are installing the software for the HTTP server, click HTTP Server Components and click OK.

    The Directory Selection dialog box opens.

  4. Type the directory name or browse to a location where you want to install the Oracle Discoverer 3i Viewer Edition files. These files include the Oracle Discoverer 3i Viewer Edition Servlet, Help, Docs and the Images used to generate output pages displayed on a client machine on input of a URL by a user. These files need to be installed in directory on the HTTP server where remote users can also access them.

    This directory will be referred to as disco3ivhome in later sections of the installation. It is recommended that you call the directory disco3ivhome.


    Note:

    Where Oracle Discoverer 3i User Edition is already installed, Oracle Discoverer 3i Viewer Edition can, if needed, be installed to an additional HTTP server. This may be necessary where the existing HTTP server does not have its own servlet engine. In this case an alternative HTTP server (with its own Servlet engine) can be installed on another machine and Oracle Discoverer 3i Viewer Edition can then be installed to that HTTP server, in this case Oracle Discoverer 3i User Edition and 3i Viewer Edition can both be run from the same installation.  


  5. Click OK.

    The Directory Selection dialog box opens. It lists the default Oracle Home directory. You can choose another directory if you want


    Note:

    If you have already installed any other Discoverer Server components, such as the Preferences or Session components, onto this machine, you will not see this dialog. 


  6. Click OK.

    The Discoverer Server Instance Name dialog box opens.


    If do not accept the default value above, write down the name you entered here as it will be needed later in the installation.
    ______________________________________________________________
    If you want to have multiple installations of Discoverer 3i on a single subnet, each installation "instance" must be unique. For example, one instance may be dedicated to the Accounts Payable department, and another instance may be dedicated to the Engineering department. Each instance must have a unique name. This name is used in the .XML file configuration, (See Section 2.3.4.4, "Oracle Discoverer 3i Viewer Edition .XML File Configuration").


    Note:

    The Instance name is prepended to the name strings that identify the Discoverer components (Locator, Preferences, and Session). For example, in the sample shown above, the batch file that registers Discoverer Preferences would identify the same as 3ivOracleDiscovererPreferences33. This ensures that each instance of Discoverer Server on the network refers to its own components. 


  7. Type a name for the instance and click OK.

    Installation begins. The installation on the HTTP server installs the Oracle Discoverer 3i Viewer Edition servlet files and the Discoverer Locator. When the installation is finished, the Installation Complete message appears.

  8. Click Yes to read the README file. It contains late-breaking information about Oracle Discoverer 3i Viewer Edition that may affect your servers and users.

  9. When you're finished with the README file, close it.

    Installation creates and installs an automatic NT Service named "OracleDiscoverer3i" which loads and starts the Locator component and CORBA services.


    Note:

    The Locator will also detect the Preference component and Session component(s) that you will install later. 


    You are now ready to install the software on the Master Discoverer Server (for more information, see Section 2.3.1.3.2, "To Install the Discoverer Server Components on the Master Discoverer Server").

    2.3.1.3.2 To Install the Discoverer Server Components on the Master Discoverer Server

    If you are already running Discoverer Server services for this or any other Discoverer product, they must be shut down before continuing. To do this select `Services' from the Control Panel and stop the service "OracleDiscoverer3i".

    The Master Discoverer Server must be a Windows NT 4.0 Server.

    1. Insert the Discoverer 3i Viewer Edition CD into the machine you designate as the Master Discoverer Server.

      The Oracle Installation Settings dialog box opens.


      Make sure to select the [DEFAULT_HOME] directory.

    2. Click OK.

      The View Installation and Administration Guide dialog appears.

    1. Before continuing with the installation, click Yes to view the Discoverer 3i Viewer Installation and Administration Guide. Your computer's default Web browser opens and displays the Installation Guide's table of contents. View online or print out the Installation Guide.

      When you return to the Oracle Installer, the Discoverer Server Installation Options dialog appears.


    2. Because you are continuing the distributed installation, click Distributed Installation and click OK.

      The Distributed Installation Options dialog box opens.


    3. Click Master Discoverer Server and click OK.

      The Directory Selection dialog box opens. It shows the default Oracle home directory under your DEFAULT_HOME directory.


    4. Click OK.

      The Discoverer Server Instance Name dialog box opens.


      If you do not accept the default value in the example above, write down the name you entered here as it will be needed later in the installation.
      ______________________________________________________________
    5. Type the same Instance name that you entered for the HTTP Server. Click OK.

      Installation begins. The installation for the Master Discoverer Server installs and registers two Oracle Discoverer components: Discoverer Preferences and Discoverer Session. When the installation is finished, the Installation Complete message appears.


    6. Click No because you've already read the README file when installing on the HTTP Server.

    7. Exit the Installer.

      Installation creates and installs an NT Service named "OracleDiscoverer3i" which automatically loads and starts the Locator and CORBA services. To stop and restart this service from the Windows Start menu, select Setting | Control Panel | Services.

      You do not need to register the Preferences and Session components with the Locator because the OracleDiscoverer3i service automatically does this for you. However, if for any reason your components are not properly registered with the Locator, see Section 2.3.4.3, "Registering Server Components".

      Installation on the Master Discoverer Server also creates two Program Groups: Oracle Discoverer 3i Server and Oracle Discoverer 3i Server Setup

      If you're installing on additional machines, continue with Section 2.3.1.3.3, "To Install Discoverer Server Components on Additional Machines".

      If you are not installing on additional machines and the database is on the same machine as the Master Discoverer Server, continue with Section 2.3.4.4, "Oracle Discoverer 3i Viewer Edition .XML File Configuration".

      If you are not installing on additional machines and the database is on a different machine to the Master Discoverer Server, you will need to add an entry to the tnsnames.ora file (for more information, see Section 2.3.4.2, "Editing the tnsnames.ora Files"). When you have modified the tnsnames.ora file, continue with Section 2.3.4.4, "Oracle Discoverer 3i Viewer Edition .XML File Configuration".


      Note:

      You do not have to install on the additional machines at this time. Instead you could configure Discoverer Server first, and then install on the additional machines later. See Section 2.3.4.3, "Registering Server Components" for details about configuration. 


      2.3.1.3.3 To Install Discoverer Server Components on Additional Machines

      If you are already running Discoverer Server services for this or any other Discoverer product, they must be shut down before continuing. To do this select `Services' from the Control Panel and stop the service "OracleDiscoverer3i".

      Installing on additional machines installs the Discoverer Session component on each one. The additional machines must be Windows NT 4.0 servers. Install Discoverer Session components on each additional machine to support more users. This is how the system scales. A reminder: These machines are not the same machines you used for the HTTP and Master Discoverer Server.

      1. Insert the Oracle Discoverer 3i Viewer Edition CD into a machine that will be used to run sessions.

        The Oracle Installation Settings dialog box opens.

        Make sure to select the [DEFAULT_HOME] directory.

      2. Click OK.

        The View Installation and Administration Guide dialog appears.

      3. Before continuing with the installation, click Yes to view the Discoverer 3i Viewer Installation and Administration Guide. Your computer's default Web browser opens and displays the Installation Guide's table of contents. View online or print out the Installation Guide.

        When you return to the Oracle Installer, the Discoverer Server Installation Options dialog appears.


      4. Because you are continuing the distributed installation, click Distributed Installation and click OK.

        The Distributed Installation Options dialog box opens.


      5. Click Other Discoverer Server and click OK.

        The Directory Selection dialog box opens. It shows the default Oracle home directory under your DEFAULT_HOME directory.


      6. Click OK.

        The Discoverer Server Instance Name dialog box opens.


        If you do not accept the default value in the example above, write down the name you entered here as it will be needed later in the installation.
        ______________________________________________________________

      1. Type the same Instance name that you entered for the HTTP Server. Click OK.

      Installation begins. The installation for the Other Discoverer Server installs and registers the Discoverer Session component. When the installation is finished, the Installation Complete message appears.


    8. Click No because you've already read the README file when installing on the HTTP Server.

    9. Exit the Installer.

      Installation creates and installs an NT Service named "OracleDiscoverer3i" which automatically loads and starts the Locator and CORBA services. To stop and restart this service from the Windows Start menu, select Setting | Control Panel | Services.

      You do not need to register the Session component with the Locator because the OracleDiscoverer3i service automatically does this for you. However, if for any reason your components are not properly registered with the Locator, see Section 2.3.4.3, "Registering Server Components".

    10. Repeat on all the machines that you want to use for Discoverer 3i sessions.

      See Section 2.3.2, "The Installed Directories" for a listing of the directories installed on the server.

      Each additional machine can run multiple sessions; therefore, the number of additional machines you choose to use for sessions depends on how many concurrent sessions the users need, the amount of memory available, the speed of the hardware, and so forth. Add the list of machine IP addresses to the Pref.txt file and the tnsnames.ora file. For more information, see Section 2.3.4.1, "Editing the Discoverer Server Preferences" and Section 2.3.4.2, "Editing the tnsnames.ora Files".

      To complete the installation see Section 2.3.4.4, "Oracle Discoverer 3i Viewer Edition .XML File Configuration".

      2.3.1.3.4 To Install the Discoverer Server Software on Solaris running an HTTP Server

      The Discoverer HTTP server software can be installed on machines running Solaris. Installation on an HTTP server running Solaris requires four steps:

      • install the Java Runtime Environment (JRE) 1.1.6.04 or higher if you do not already have it installed

      • install VisiBroker for Java 3.4.0.0

      • install Oracle Discoverer 3i Viewer Edition client and Locator

      • activate the Locator component

      Install the software while you are logged in with the appropriate privileges (typically `root').

      The VisiBroker utilities are Java applications that require the JRE to run. The VisiBroker utilities are required to activate the Locator component and also to support communication among Discoverer 3i components located on other machines.

      The Locator component must be running for the Oracle Discoverer 3i Viewer Edition servlet to connect to an available session. You can activate the Locator automatically during system initialization or from a user account.

      The instructions to install on a Solaris system use the following filenames, but you would replace these filenames with the filenames you choose for your installation:

      • <temp>--the temporary directory you choose during installation

      • <jre>--the directory where JRE 1.1.6.04 is installed

      • <dis_root>--the directory where the Oracle Discoverer 3i Viewer Edition client is installed

      • <name>--the Instance name that identifies the Discoverer 3i components

      • <user>--the user with appropriate privileges who starts the Locator component

      Installing JRE 1.1.6.04

      The VisiBroker utilities require a compatible Java Runtime Environment (JRE). Oracle Discoverer 3i Viewer Edition includes JRE version 1.1.7.28o or higher, which can be installed without conflicting with other JRE or JDK versions currently on the server.

      1. On the installation machine, open the /Solaris directory of the Discoverer 3i CD-ROM.

      2. Copy /Solaris/jre116Sparc.tar to the <temp> directory.

      3. Unarchive the file <temp>/jre116Sparc.tar using the following command:

        tar xvf ./jre11728oSparc.tar

        This will extract three files:

        Solaris_JRE_1.1.6_04_sparc.bin

        sparc_jdk_patches.tar.Z

        readme

      4. Before installing JRE 1.1.6.04, view the readme file to determine if your OS version requires any patches from the sparc_jdk_patches.tar.Z file.

      5. Run the file: Solaris_JRE_1.1.6_04_sparc.bin.

        The JRE files are installed into a subdirectory of the current directory.

      6. Change to the directory where you want to install the JRE directory tree, for example <jre>.

      7. Type:

        /bin/sh <temp>/Solaris_JRE_1.1.6_04_sparc.bin

        The following new directory is created:

        <jre>/Solaris_JRE_1.1.6_04/

        where <jre> is the name of the directory where you want the JRE directory tree installed.

        That completes installation of JRE 1.1.6.04.

      Installing VisiBroker for Java 3.3.4.0 for Java

      1. Create a directory /usr/local/vbroker.

      2. Copy /Solaris/vbroker34.tar from the Discoverer 3i CD-ROM to /usr/local.

      3. Change directory to /usr/local/ and unarchive vbroker34.tar using the following command:

        tar xvf /usr/local/vbroker/vbroker34.tar

      4. Set the following environment variables:
        Table 2-4 Solaris Environment Variables
        Environment Variable  Value 

        VBROKER_ADM 

        /usr/local/vbroker/adm 

        VBROKER_JAVAVM 

        <jre>/Solaris_JRE_1.1.6_04/bin/jre 

        path (append to existing value) 

        /usr/local/vbroker/bin 

        That completes installation of VisiBroker 3.3.4.0 for Java.

      Activating the Locator Component

      Before activating the Locator component, the OAD and CORBA services must be running on the Discoverer Server machine. Also, you must set the Solaris OS parameter named File Descriptors to 1024 or less (as Solaris has a limitation of 1024 descriptors per process). See your Solaris OS documentation for instructions to set this parameter.


      NOTE: "The system imposes a per-process soft limit on open files, OPEN_MAX (usually 64), which can be increased, and a per-process hard limit (usually 1024), which cannot be increased." (.. from Solaris Manual) 


      1. Copy 3iviewer.tar from the Discoverer 3i CD-ROM to the <temp> directory.

      2. Change directory to the <dis_root> directory and unarchive 3iviewer.tar using the following command:

        tar xvf <temp>/3iviewer.tar

      3. Copy the file start_locator from the Discoverer 3i CD-ROM to <dis_root>/disco3iv/DISCWB33/applet.

      4. Change the mode of the start_locator file using the following command:

        chmod 744 start_locator

      5. Edit the file start_locator to add the Instance name <iname> to the front of the Locator variables:
        Table 2-5 Locator Variables
        Current Value  New Value 
        OracleDiscovererPreference3.3  <iname>OracleDiscovererPreference3.3 
        OracleDiscovererLocator3.3  <iname>OracleDiscovererLocator3.3 

        For example, the following is the original code in the file:

        vbj oracle.disco.locator.Locator -preference OracleDiscovererPreferences3.3 -locator OracleDiscovererLocator3.3

        If the instance name is 3iv, edit the file as follows:

        vbj oracle.disco.locator.Locator -preference 3ivOracleDiscovererPreferences3.3 -locator 3ivOracleDiscovererLocator3.3

      6. Run the following command:

        osagent -p 14000&

        to start the VisiBroker SmartAgent.

        The VisiBroker SmartAgent must be running before you can activate the Locator component. You can start the SmartAgent from any directory because the path for osagent was added to the environment path when the VisiBroker files for Java 3.4 were installed earlier. An "&" at the end of the command is optional, but is recommended because the SmartAgent must be running whenever the Locator is running.

      7. While still in the <dis_root>/disco3iv/DISCWB33/ directory, start the Locator component with the following command:

        start_locator&

        The "&" is optional but is also recommended.

      You can now delete the temporary installation files located in <temp>.

      To complete the installation see Section 2.3.1.3.2, "To Install the Discoverer Server Components on the Master Discoverer Server".


      Note:

      The Locator component must be running for Oracle Discoverer 3i Viewer Edition to function. Make sure that all current recovery and maintenance scripts that may restart the system or in some other way stop the Locator process take the Locator process into account. 


      2.3.1.3.5 To Install the Discoverer Software on an HTTP Server Not Running Windows NT or Solaris

      If you are already running Discoverer Server services for this or any other Discoverer product, they must be shut down before continuing. To do this select `Services' from the Control Panel and stop the service "OracleDiscoverer3i".

      In this configuration the Locator component runs on a Windows NT machine, which can be one of the Discoverer Servers. You must first install the Discoverer 3i Viewer Edition component on a Windows NT machine, and then copy (or FTP) the files and downloadables to the non-NT machine. After the files are on the non-NT HTTP server, you install the Locator on a Windows NT machine that will run a Discoverer session. The Discoverer 3i Viewer Edition component can then be deinstalled from the Windows NT machine later if not required.

      1. To install the Oracle Discoverer 3i Viewer Edition component on a Windows NT machine, follow the steps in Section 2.3.1.3.1, "To Install the Oracle Discoverer 3i Viewer Edition Servlet on an HTTP Server Running Windows NT" (when you have completed the steps in Section 2.3.1.3.1, do not move on to Section 2.3.1.3.2 but return to this section).

      2. Locate the Viewer Edition component files (e.g. in D:\disco3ivhome) and copy (or FTP) the \disco3ivhome directory and its contents to a directory on the non-NT machine that you will be using for the HTTP server (e.g. /usr/local/disco3ivhome).

      3. Locate the Visibroker component files vbjorb.jar and vbjapp.jar (e.g. in D:\<oracle_home>\vbroker\lib) and copy (or FTP) these files to a directory on the non-NT machine that you will be using for the HTTP server (e.g. /usr/local/vbroker/lib).

        You will need the above Visibroker files when configuring the servlet engine.

        The rest of this section describes how to install the Locator component. If you want to run the Locator on the same Windows NT machine as in step 1, the Locator component is already installed. You can therefore ignore the rest of this section and go straight to Section 2.3.1.3.2, "To Install the Discoverer Server Components on the Master Discoverer Server".

      4. To install the Locator component insert the Oracle Discoverer 3i Viewer Edition CD into the Windows NT machine that will host the Locator component.

        The Oracle Installation Settings dialog box opens.

      5. Type or choose the following information and click OK:

        • Company Name--Your company's name

        • Name--Select [DEFAULT_HOME] for Discoverer Server 3.3.

        • Location--Select the path for [DEFAULT_HOME]. If you previously installed products into the DEFAULT_HOME, you will not be able to modify this directory.

        • Language--The language used on this server.

        The View Installation and Administration Guide dialog appears.

      6. Before continuing with the installation, click Yes to view the Discoverer 3i Viewer Installation and Administration Guide. Your computer's default Web browser opens and displays the Installation Guide's table of contents. View online or print out the Installation Guide.

        When you return to the Oracle Installer, the Discoverer Server Installation Options dialog appears.

      7. Select Custom or Remove and click OK.

        The Software Asset Manager appears.

      8. Double-click on the Oracle Discoverer (Web) component to expand it.

      9. Select the Discoverer Locator Component and click the Install button.

        The Discoverer Server Instance Name dialog box opens.


        If you do not accept the default value in the example above, write down the name you entered here as it will be needed later in the installation.

        ______________________________________________________________

      1. Type the same Instance name that you entered for the HTTP server. Click OK.

      Installation begins. When the installation is finished, the Installation Complete message appears.


    11. The installer returns to the Software Asset Manager.

    12. Exit the Installer.

      Installation creates and installs an NT Service named "OracleDiscoverer3i" which automatically loads and starts the Locator and CORBA services. To stop and restart this service from the Windows Start menu, select Setting | Control Panel | Services.

      You are now ready to install (i.e. on the NT machine) the Discoverer software on the Master Discoverer Server and on Other Discoverer Servers. See Section 2.3.1.3.2, "To Install the Discoverer Server Components on the Master Discoverer Server"and Section 2.3.1.3.3, "To Install Discoverer Server Components on Additional Machines".

      2.3.1.4 Installing Oracle Discoverer 3i Viewer Edition Component and Master Server on a Single Machine

      If you are already running Discoverer Server services for this or any other Discoverer product, they must be shut down before continuing. To do this select `Services' from the Control Panel and stop the service "OracleDiscoverer3i".

      If you already have Oracle Discoverer 3i Server installed then go to Section 2.3.1.5, "Custom Installation".

      A single machine installation must be on a Windows NT 4.0 machine with an HTTP server.

      1. Insert the Oracle Discoverer 3i Viewer Edition CD. The Oracle Installer starts. If the Installer does not start, double-click Setup.exe in the root directory on the CD.

        The Oracle Installation Settings dialog box opens.


      2. Type or choose the following information and click OK.

        • Company Name--Your company's name

        • Name--Select [DEFAULT_HOME] for Discoverer 3i.

        • Location--Select the path for [DEFAULT_HOME]. If you previously installed products into the DEFAULT_HOME, you will not be able to modify this directory.

        • Language--The language used on this server.

        The View Installation and Administration Guide dialog appears.

      3. Before continuing with the installation, click Yes to view the Discoverer 3i Viewer Installation and Administration Guide. Your computer's default Web browser opens and displays the Installation Guide's table of contents. View online or print out the Installation Guide.

        When you return to the Oracle Installer, the Discoverer Server Installation Options dialog appears.


      4. Click Single Machine Installation and click OK.

        The Directory Selection dialog box opens.

        Type or browse to a directory name where you want to install the Oracle Discoverer 3i Viewer Edition component files. These files include the Oracle Discoverer 3i Viewer Edition servlet, Help, Docs and Images used to generate output pages displayed on a client machine on input of a URL by a user.
        This directory will be referred to as disco3ivhome in later sections of the installation. It is recommended that you call the directory disco3ivhome.
        For example, type D:\disco3ivhome


        Note:

        In a situation where Oracle Discoverer 3i User Edition is already installed, Oracle Discoverer 3i Viewer Edition can, if needed, be installed to an additional HTTP server. This may be necessary where the existing HTTP server does not have its own servlet engine. In this case an alternative HTTP server (with its own Servlet engine) can be installed on another machine and Oracle Discoverer 3i Viewer Edition can then be installed to that HTTP server, in this case both Oracle Discoverer 3i User Edition and 3i Viewer Edition can be run on the same installation.  



        Note:

        If you don't install the Oracle Discoverer 3i Viewer Edition files in the root or primary directory, you must create a virtual directory alias or URL prefix and map it to this directory. Please see your HTTP server documentation for more information. 


      5. Click OK.

        The Directory Selection dialog box opens. It shows the default Oracle home directory under your DEFAULT_HOME directory. You can choose another directory if you want.


      6. Click OK.

        The Discoverer Server Instance Name dialog box opens.


        If you do not accept the default value in the example above, write down the name you entered here as it will be needed later in the installation.

        ______________________________________________________________


      Note:

      The Instance name is prepended to the name strings that identify the Discoverer components (Locator, Preferences, and Session). For example, in the sample shown above, the batch file that registers Discoverer Preferences creates the name, 3ivOracleDiscovererPreferences33. This ensures that each instance of Discoverer Server on the network refers to its own components. 


    13. Type a name for the instance and click OK.

      You may need this Instance name if installing the Discoverer Server components on other machines later, so you may want to write it down. This name is used in the .XML file configuration, (See Section 2.3.4.4, "Oracle Discoverer 3i Viewer Edition .XML File Configuration").

      Installation begins. All of the necessary files are installed on the machine. When the installation is finished, the Installation Complete message appears.


    14. Click Yes to read the README file. It contains late-breaking information about Oracle Discoverer 3i Viewer Edition that may affect your servers and users.

    15. When you're finished with the README file, close it.

      All the Discoverer 3i Viewer Edition components are installed and registered on the server. Installation creates and installs an automatic NT Service named "OracleDiscoverer3i" that loads and starts the Locator component and CORBA services. To stop and restart this service from the Windows Start menu, select Setting | Control Panel | Services.

      You do not need to register the Preferences and Session components with the Locator because the OracleDiscoverer3i service automatically does this for you. However, if for any reason your components are not properly registered with the Locator, see Section 2.3.4.3, "Registering Server Components".

      If the database is on the same machine, continue with Section 2.3.4.4, "Oracle Discoverer 3i Viewer Edition .XML File Configuration".

      If the database is on a different machine, you will need to add an entry to the tnsnames.ora file (for more information, see Section 2.3.4.2, "Editing the tnsnames.ora Files"). When you have modified the tnsnames.ora file, continue with Section 2.3.4.4, "Oracle Discoverer 3i Viewer Edition .XML File Configuration"

      2.3.1.5 Custom Installation

      If you are already running Discoverer Server services for this or any other Discoverer product, they must be shut down before continuing. To do this select `Services' from the Control Panel and stop the service "OracleDiscoverer3i".

      If you already have Oracle Discoverer 3i server installed, you will need only install the Oracle Discoverer 3i Viewer Edition component.

      Use the Custom Installation option to install the Oracle Discoverer 3i Viewer Edition component if you have previously installed the Discoverer Server distributed on multiple machines. However, the same server requirements apply as with a distributed installation:

      • The HTTP server can be a Windows NT 4.0 server or UNIX server, but the Master Discoverer Server and any additional servers must be Windows NT 4.0 servers. If the HTTP server is not a Windows NT 4.0 server, install the Discoverer Server on a Windows NT 4.0 server, then send the installed files via FTP to the UNIX server.

      • The Oracle Discoverer 3i Viewer Edition component must be installed on the same machine as the HTTP Server and the servlet engine. The Discoverer Locator must be installed on a Windows NT or Solaris machine.

      • There can be only one Preferences component and one Locator component for each instance of Discoverer 3i on a subnet. There can be many Discoverer Sessions components.

      • Each machine being used to run sessions must have a Discoverer Session component installed.

      1. Insert the Oracle Discoverer 3i Viewer Edition CD. The Oracle Installer starts. If the Installer does not start, double-click Setup.exe in the root directory on the CD.

        The Oracle Installation Settings dialog box opens.


      2. Type or choose the following information and then click OK.

        • Company Name--Your company's name

        • Name--Select [DEFAULT_HOME] for Discoverer Server 3.3.

        • Location--Select the path for [DEFAULT_HOME]. If you previously installed products into the DEFAULT_HOME, you will not be able to modify this directory.

        • Language--The language used on this server.

        The View Installation and Administration Guide dialog appears.

      3. Before continuing with the installation, click Yes to view the Discoverer 3i Viewer Installation and Administration Guide. Your computer's default Web browser opens and displays the Installation Guide's table of contents. View online or print out the Installation Guide.

        When you return to the Oracle Installer, the Discoverer Server Installation Options dialog appears.


      4. Click Custom or Remove and then click OK.

        The Software Asset Manager appears.

      5. Double-click the Oracle Discoverer (Web) item in the Available Products list to display the list of individual components. Click to select the items that you want to install.

      6. Click Install.

      7. In the Directory Selection dialog box, verify the directory where you want the component installed and click OK.

      8. Repeat for each component that you want to install on the current machine.

      To complete the installation see Section 2.3.4.4, "Oracle Discoverer 3i Viewer Edition .XML File Configuration".

      2.3.2 The Installed Directories

      Table 2-6, shows the directories installed for the HTTP server and the Discoverer Master server:

      Table 2-6
      HTTP Server Directories  Discoverer Master Server Directories 

      Root/Alias 

      Oracle_Home 

       

      \disco3iv 

       

      \Discwb33 

       

       

      \html 

       

       

      \classes 

       

       

       

       

      \help 

       

       

      \util 

       

       

       

       

      \images 

       

       

       

       

       

      \doc 

       

       

       

      -

      The directory, Discwb33, on the Discoverer Master Server contains the dlls and binary files for the Preference and Session components.

      • disco3iv--the Oracle Discoverer 3i Viewer Edition .jar and readme files

        • html--the disco3iv.XML configuration file and .XSL stylesheet files

          • help--the html help files accessible while using Oracle Discoverer 3i Viewer Edition

          • images--the images used by the user interface and help pages

        • doc--the html files for the Oracle Discoverer 3i Viewer Edition Installation and Administration Guide

      • Discwb33

        • classes--the archive classes for the Locator component

        • util--A set of batch files for registering and unregistering components

      2.3.2.1 The Executables

      The executable files for the Discoverer Server components are located in the directory, <Oracle_Home>\Discwb33. The executables are:

      • Session--dis33ws.exe

      • Preferences--dis33pr.exe

      The executable dis33srv.exe launches the OracleDiscoverer3i service.

      The Locator component produces the Locator.ior file.

      2.3.3 Removing Discoverer Server Components

      If you are already running Discoverer Server services for this or any other Discoverer product, they must be shut down before continuing. To do this select `Services' from the Control Panel and stop the service "OracleDiscoverer3i".

      You can remove some or all of the Discoverer Server components from each machine.

      1. Insert the Oracle Discoverer 3i Viewer Edition CD into the machine from which you want to remove components. The Oracle Installer starts. If the Installer does not start, double-click Setup.exe in the root directory on the CD.

        The Oracle Installation Settings dialog box opens.


      2. Type or choose the following information and the click OK.

        • Company Name--Your company's name

        • Name--Select [DEFAULT_HOME] for Discoverer 3i Server.

        • Location--Select the path for [DEFAULT_HOME]. If you previously installed products into the DEFAULT_HOME, you will not be able to modify this directory.

        • Language--The language used on this server.

        The View Installation and Administration Guide dialog appears.

      3. Before continuing with the removal, click Yes to view the Discoverer 3i Viewer Installation and Administration Guide. Your computer's default Web browser opens and displays the Installation Guide's table of contents. View online or print out the Installation Guide.

        When you return to the Oracle Installer, the Discoverer Server Installation Options dialog appears.


      4. Click Custom or Remove and then click OK.

        The Software Asset Manager appears.

      5. In the list of products installed on the machine, select those that you want to remove. Shift-click to select multiple components.

      6. Click Remove.

      7. In the message dialog box that appears, verify the components are the proper ones to remove and then click OK.

      2.3.4 Additional Discoverer Server configuration tasks

      There are a number of additional configuration tasks that you might have to perform. Depending on how you have installed Discoverer, some of these tasks are optional and some of them are mandatory. Use the following table to decide which tasks to perform and the suggested sequence in which to perform them.

      Seq  Task  Required when  Go to this section 

      Edit Discoverer Server preferences 

      Required when performing a distributed install 

      Section 2.3.4.1 

      Edit tnsnames.ora file 

      Required if the database is on a different machine 

      Section 2.3.4.2 

      Register server components 

      Only required if for any reason the server components have not been properly registered with the Locator during installation. 

      Section 2.3.4.3 

      Edit the disco3iv.xml file 

      Always required 

      Section 2.3.4.4 

      2.3.4.1 Editing the Discoverer Server Preferences

      The Discoverer Preferences component is located on the Master Discoverer Server for a distributed install, and on the HTTP server (the only machine) for a single machine install.

      The Preferences must contain either the IP address or machine name of each machine that will run Discoverer 3i sessions. However, the order of the IP addresses listed in the Preferences determines the order in which sessions are started on each machine that has a Session component installed. Therefore, you can effectively balance the load placed on the servers by listing the machines in a particular order.

      This section contains the following topics:

      2.3.4.1.1 Examples of Load Balancing

      The Locator uses the list of IP addresses or machine names in the Preferences based on the round-robin method to determine which machine starts the next requested session. The Locator requests a session on each machine, in order, until it reaches the end of the list of IP addresses. When the Locator reaches the end of the list, it returns to the beginning of the list and starts over.

      Consequently, to determine the machine to start the first session, second session, third session, and so on, you should consider the speed and performance of each server machine. For planning purposes, you can estimate that each session requires approximately 3.8 to 18 MB of memory.

      For example, you may also want one machine to handle five sessions before the next machine is used. If so, you type the first machine's IP address five times before the next machine's address.

      Because load balancing can greatly affect performance, we recommend you plan the balancing before editing the Preferences file.

      Example #1 Load balancing - equal machines

      You have Discoverer Sessions installed on two Application servers. Each machine has the same processor speed and RAM. The IP addresses for these two machines are:

      Table 2-7 Sample Server Names
      Server  Name  IP address 

      Application Server #1 

      disco1 

      123.456.789.1 

      Application Server #2 

      disco2 

      123.456.789.2 

      You want Application server #1 to handle the first request, Application server #2 to handle the next, Application server #1 the next, and so on.

      The Preferences file entry would look like this:

        Machine IPs="disco1, disco2"

        or

        Machine IPs="123.456.789.1, 123.456.789.2"

      Entries in the Preferences file are comma space delimited (i.e. entries are separated by a comma followed by a space). Enclose the entries in "double quotes."


      Note:

      Using IP addresses is somewhat faster because using machine names requires one extra lookup. See your System administrator for details about using IP addresses versus machine names. 


      Example #2 Load balancing - one fast machine plus two other machines

      You have Discoverer Sessions installed on three Application servers. The first Application server has faster processors and more RAM. The second and third Application servers are equal to each other in processor speed and RAM.

      The IP addresses for these three machines are:

      Table 2-8 Sample Server Names
      Server  Name  IP address 

      Application Server #1 

      serve1 

      123.456.789.1 

      Application Server #2 

      serve2 

      123.456.789.2 

      Application Server #3 

      serve3 

      123.456.789.3 

      You want Application server #1 to handle the first three requests, Application server #2 to handle next one, Application server #3 the next one, then back to Application sever #1 for the next three requests.

      The Preferences file entry would look like this:

        Machine IPs="serve1, serve1,serve1, serve2, serve3"

        or

        Machine IPs="123.456.789.1,123.456.789.1,123.456.789.1, 123.456.789.2, 123.456.789.3"

      2.3.4.1.2 To Edit the Preferences File

      The only information required in the Preferences file is the IP addresses or machine names of the servers used for Discoverer 3i. The other items in the Preferences file can be edited to suit your network or user requirements. See Section 3.3, "Editing the End User Preferences" for more information.

      The Preferences file is named Prefs.txt. A backup copy of Prefs.txt is located at <orahome>\Discwb33\util\defaults.txt (or at the location where you installed the Master Discoverer Server, specifically, the Preferences component). If you make a mistake when editing, lose, or corrupt the Prefs.txt file, you can restore the file to its default values from the backup copy.

      To edit the Preferences file, edit it on the machine where you installed the Preferences component:

      1. From the Windows Start menu, choose Programs | Oracle Discoverer Server 3i Setup | Edit Preferences.


        The file, Prefs.txt, opens in the Notepad application.

      2. Type the IP address or machine name for each machine at the line labeled MachineIPs entry at the top of the file.

      3. Separate the IP addresses or machine names by commas and enclose the entire list in "double quotes." For example: "server1, server2, server3".

      4. When you're finished editing the Preferences file, save it and exit Notepad.

      2.3.4.1.3 Apply Preferences

      From the Windows Start menu, choose Programs | Oracle Discoverer Server 3i Setup | Apply Preferences.

        A confirmation window shows that the new preferences have been saved. If you suspect that the file contains errors, check the error.txt file in the current directory.

        To continue, press any key.

      The preferences are updated in the Windows NT Registry. Preferences are now set for the Discoverer Server Instance.

      2.3.4.2 Editing the tnsnames.ora Files

      The tnsnames.ora file should be identical on each machine that will run a session. The tnsnames.ora file contains the names and aliases of all the databases that users can access using Discoverer 3i or any other Oracle product. To make sure the tnsnames.ora file is correct, enter the SID(s) for each database in your tnsnames.ora file.

      One way to edit the tnsanmes.ora file:

      1. From the Windows Start menu, choose Programs | Oracle for Windows NT | Oracle Net8 Easy Config.

        A program then runs so you can edit the Net8 configuration.

      If the Discoverer Session component is installed on several machines, you can copy the correct tnsnames.ora file to the other machines.

      2.3.4.3 Registering Server Components

      For information on unregistering components or registering from the command line, see Section 3.4, "Registering and Unregistering components" .

      To register the Session and Preferences components:

      1. On the machine where you want to register or unregister components, go to the Windows Start menu and choose Programs | Oracle Discoverer Server 3i Setup.


      2. Select Register Preferences.

      A confirmation screen appears.

      1. Select Register Sessions.

      A confirmation screen appears.

      1. Select Register Collector.

      A confirmation screen appears.

      2.3.4.4 Oracle Discoverer 3i Viewer Edition .XML File Configuration

      If you used the default installation options with a single Oracle Discoverer Server instance called `3iv' then you do not need to edit this file.

      If you have multiple Discoverer Servers or used a different name, then follow the instructions below.

      The Oracle Discoverer 3i Viewer Edition Servlet component has one file that needs to be configured:

      disco3iv.xml

      Before editing this file, we strongly recommend you take a copy of the file for future reference.

      When you have made the changes to the disco3iv.xml file, continue with Section 2.3.5, "Common Configuration".

      2.3.4.4.1 Setting values to enable the Oracle Discoverer 3i Viewer to locate the Oracle Discoverer 3i server

      Oracle Discoverer 3i Viewer Edition needs to find the Oracle Discoverer 3i server, it does this using the disco3iv.xml file. Edit this file using Notepad.

      You will need to set the correct Discoverer server instance name entered during installation. (See Section 2.3.1, "Installing Discoverer 3i Server and Servlet Software" ). This value can be obtained from your administrator. This must be typed with correct capitalization, exactly as it was entered earlier. For single machine installs or for multiple machines on the same network subnet, this is the only change required.

      For multiple machines that use a different subnet mask to the Discoverer Server (or when you are installing onto a non-NT HTTP server), you will need to edit a further section in this file to specify a different network submask.

      If in doubt, edit the section assuming a different network subnet mask since this will work even if the computers actually have the same subnet mask.

      The following excerpt is from the D:\disco3ivhome\disco3iv\html\disco3iv.xml file. The text that needs to be configured is indicated in the file:

      .

      <disco_config> 

       

      <server> 

       

      <!-- 

      MAKE CHANGES HERE .... SAVE A COPY OF THIS FILE BEFORE EDITING 

       

       

       

       

       

       

      If you used the default installation options with a single Discoverer Server instance called '3iv' then you do not need to edit this file. 

       

       

      If you used a different Discoverer Server instance name, in the line below change '3iv' to be the name you entered for the Discoverer Server during installation
      Make sure you enter the EXACT name, with correct capitalization.
      E.g. If the instance name is MyInstance, then session name="MyInstanceOracleDiscovererSession3.3" --> 

       

       

       

      <session name="3ivOracleDiscovererSession3.3"> 

       

      <!-- 

      For single machine installs or multiple machines on the same subnet, only the step above is required.
      If Discoverer 3i Viewer is installed on multiple machines on a different subnet than the Discoverer 3i Server then follow the instructions below.

      1. Remove the 2 comment lines below marked 'REMOVE THIS COMMENT LINE (A)' and 'REMOVE THIS COMMENT LINE (B)'

      2. If you used a different Discoverer Server instance name instead of the default '3iv', change '3iv' to be the name you entered for the Discoverer Server during installation.
      Make sure you enter the EXACT name, with correct capitalization.
      E.g. If the instance name is MyInstance, then locator name="MyInstanceOracleDiscovererSession3.3"

      3. Change %LOCATOR_URL% to be the absolute URL (including the trailing '/' ) for the file locator.ior in your
      Discoverer Server installation. You will need to locate where this file is installed using a file search.
      If the machine with this file on is not running a web server, you will need to copy the locator.ior file to your web server, and set the URL accordingly.
      E.g. path="http://Discoserver.company.com/orant/discwb33/Applet/" 

       

      --> 

       

       

      <!-- REMOVE THIS COMMENT LINE (A) only if Discoverer 3i Viewer is installed on a different subnet than the Discoverer 3i Server 

       

       

       

      <locator name="3ivOracleDiscovererLocator3.3"
      path="http://%LOCATOR_URL%" >
      </locator> 

       

      REMOVE THIS COMMENT LINE (B) only if Discoverer 3i Viewer is installed on a different subnet than the Discoverer 3i Server -->  

       

       

       

      </session> 

       

      </server> 

       

       

      <application auto_connect="false" apps_login="false" auto_open_worksheet="true" auto_open_eul="true" /> 

       

      <document> 

       

       

      <argument name="xsl_path" type="href">disco3iv.xsl</argument> 

       

       

      <argument name="help_path" type="href">help</argument> 

       

       

      <argument name="image_path" type="href">images</argument> 

       

      <!-- 

      To enable the inclusion of the Applications login check box on the connect dialog set the argument below to true --> 

       

       

       

       

       

       

      <argument name="show_login_method_control">true</argument> 

       

      </document> 

       

      </disco_config> 

      2.3.4.4.2 Specifying display of the Applications User Checkbox in Connect Dialog

      You can set up the Connect dialog to enable an Oracle Applications user to log on using an Applications `Responsibility' by displaying the Applications User checkbox.

      To set up the Connect dialog to display (or hide) the Applications User checkbox, access the configuration file located in D:\disco3ivhome\disco3iv\html\disco3iv.xml and set the "show_login_method_control" argument to true or false as required.

      2.3.5 Common Configuration

      This section highlights common aspects of configuration applying to naming conventions, web servers, servlet engines and the Java Virtual Machine (JVM).

      When you have read this section, continue by configuring one of the following:

      2.3.5.1 Naming preferences

      Naming conventions may vary from machine to machine. The directories and machine names shown here may be different for your machine but are used in examples in the rest of this installation.

      2.3.5.1.1 Oracle Home

      This is full path to the Oracle Home directory. We shall use the example D:\orant

      2.3.5.1.2 Web Alias:

      This is the virtual path to the web server directory where the Discoverer 3i Viewer Edition component is installed. This can be any name you want. We shall use the example disco3ivfiles.

      2.3.5.1.3 Discoverer 3i Viewer files location

      This is the physical directory where the directory disco3iv is installed. This was the directory chosen during the installation in response to the question "Where should the Discoverer Viewer be installed on your HTTP server?". We will use the example D:\disco3ivhome

      2.3.5.1.4 Web server machine

      This is the machine name that the HTTP server is installed on. You must include a fully qualified host name.
      We will use the example mywebserver.company.com

      2.3.5.2 Common configuration for web servers

      Certain items need to be configured the same regardless of which web server is used.

      All the Web servers need to be configured so that a `directory alias' maps to the installation directory for Oracle Discoverer 3i Viewer Edition.

      2.3.5.3 Common configuration for servlet engines

      Certain items need to be configured the same regardless of which servlet is used. This section describes them.

      The naming conventions used vary depending on location and naming preferences.

      2.3.5.3.1 Defining the name

      This means registering a name that will be used to invoke the servlet. For default purposes set this to `discoservlet'

      2.3.5.3.2 Defining the classpath for the servlet code

      The servlet engine needs to know the name of the class that is used to start the servlet.

      This is always `oracle.disco3iv.Disco3iv'

      2.3.5.3.3 Defining the location of the servlet code

      Servlet engines differ in that some look in default directories whilst other can be pointed to an explicit class or .jar (Java Archive) file.

      This will always refer to the `disco3iv.jar' file although the location of the file may differ.

      2.3.5.3.4 Servlet parameters

      The servlet engine must be configured so that when the Discoverer servlet is launched a parameter is passed in.

      The parameter name is `config' and its value is `http://mywebserver.company.com/disco3ivfiles/html/disco3iv.xml'

      2.3.5.4 Information required by the Java Virtual Machine (JVM)

      JVM's are referenced in Servlet engines and need to be configured in order to run smoothly.

      2.3.5.4.1 JVM Classpath

      There are two extra .jar files that need to be added to the classpath for servlet engines.

      These are vbjorb.jar and vbjapp.jar

      Most servlet engines have a classpath setting option so that these can be appended to the classpath.

      2.3.5.4.2 JVM parameters

      There are two parameters that need to be passed into the JVM, so that instead of using Sun's default ORB, Visibroker's ORB is used instead.

      The parameters and their values are shown below:

      org.omg.CORBA.ORBClass=com.visigenic.vbroker.orb.ORB 
      org.omg.CORBA.ORBSingletonClass=com.visigenic.vbroker.orb.ORB
      
      

      It is also recommended to increase the maximum Java heap size that the Java Virtual Machine (JVM) will use.
      E.g. For Apache, add -mx256m to increase the memory to 256MB. (See Section 2.3.6.3.1, "Add the JVM parameters").

      How these are passed in will vary from one Servlet Engine to another.

      2.3.6 Configuring Apache Web Server and Servlet Engine

      The recommended suite of software for use with Apache is:

      • Apache Server 1.3.9

      • JRE (Java Runtime Environment) 1.2

      • JSDK (Java Servlet Development Kit) 2.0

      • Apache JServ 1.0

      Apache should be installed as a service on Windows NT to avoid problems closing the JVM when it is stopped and restarted as a console application.

      To check your Apache Server is running use a web browser and enter the fully qualified machine name as the URL E.g.:

      mywebserver.company.com

      To check your Apache JServ is running, enter the following URL:

      mywebserver.company.com/servlets/IsItWorking
      On Solaris this should read:
      mywebserver.company.com/example/Hello

      You should verify that Apache Server and Apache JServ are running before continuing.

      In the event of errors, check the Apache log files located in the directory:

      On Windows NT this is Apache\logs and Apache JServ\logs
      On Solaris this is in one location /usr/local/apache/logs).

      This section includes the following topics:

      2.3.6.1 Defining a directory alias for an Apache web server

      Edit the httpd.conf file in your Apache directory.

      For example:
      On Windows NT if D:\Apache was where you installed Apache then D:\Apache\conf directory is where you will find httpd.conf file.

      On Solaris if /usr/local/apache was where you installed Apache then /usr/local/apache/conf directory is where you will find httpd.conf file

      Add the following line in the `Aliases' section:

      For Windows NT

      Alias /disco3ivfiles/ "D:/disco3ivhome/disco3iv/"
      
      

      For Solaris

      Alias /disco3ivfiles/ "/usr/local/disco3ivhome/
      disco3iv/"
      
      

      Where disco3ivfiles can be any name you want and the directory in which the file disco3iv.jar is installed is:

        For Windows NT: D:\disco3ivhome\disco3iv

        For Solaris: /usr/local/disco3ivhome/disco3iv/

      NOTE: Be sure to enter this line carefully, including the trailing slashes after each section.

      Below is an excerpt from a httpd.conf file showing the above line inserted (for Windows NT).

      # Aliases: Add here as many aliases as you need (with no limit). The format is 
      # Alias fakename realname
      #
      # Note that if you include a trailing / on fakename then the server will
      # require it to be present in the URL.  So "/icons" isn't aliased in this
      # example, only "/icons/"..
      #
      Alias /icons/ "D:/apache/icons/" 
      Alias /disco3ivfiles/ "D:/disco3ivhome/disco3iv/"

      NOTE: These are forward slashes not back slashes.

      (For Solaris : Alias /icons/ "/usr/local/apache/icons" )
      (For Solaris : Alias /disco3ivfiles/ "/usr/local/disco3ivhome/disco3iv/" )
      
      
      2.3.6.1.1 Checking the directory alias

      Stop and restart Apache.

      Start a web browser and type mywebserver.company.com/disco3ivfiles/

      Where mywebserver.company.com/ is the machine name that the HTTP server is installed on.

      You should see a directory with the disco3iv.jar file present as shown below.

      NOTE: Make sure you append a `/' at the end of the address otherwise you will not see the contents of the directory.

      The above image shows what you can expect to see.

      2.3.6.2 Editing zone.properties file of Apache JServe

      This can be found where you installed Apache JServ

      2.3.6.2.1 Location of the zone.properties file

      If you installed Apache JServ in the \JServ directory ( /usr/local/jerv on Solaris ), the file will be in the \JServ\conf directory
      ( /usr/local/jserv/conf on Solaris ). If JServe is Version 1.1 or above, the zone.properties file will be found in the \JServ\servlets directory (Or /usr/local/jserv/servlets on Solaris ).

      2.3.6.2.2 Add the repository.

      This means telling JServ where to find the disco3iv.jar file

      Append the path for the file to the end of the `repositories' line

      E.g. Before appending line:

      For Windows NT
      repositories=D:\JServ\servlets For Solaris
      repositories=/usr/local/jserv/servlets (For Solaris)

      After appending line:

      For Windows NT:
      repositories=D:\JServ\servlets,D:\disco3ivhome\disco3iv\disco3iv.jar
      (where D:\disco3ivhome\disco3iv is the full path for disco3iv.jar)
      For Solaris:
      repositories=/usr/local/jserv/servlets,/usr/local/disco3ivhome/disco3iv/ disco3iv.jar
      (where /usr/local/disco3ivhome/disco3iv/ is the full path for disco3iv.jar)
      2.3.6.2.3 Add the servlet to the startup servlets

      Add the following line in the `Startup Servlets' section

      servlets.startup=discoservlet
      
      2.3.6.2.4 Define a servlet alias for the servlet

      Add the following line to the `Servlet Aliases' section

      servlet.discoservlet.code=oracle.disco3iv.Disco3iv
      
      2.3.6.2.5 Define parameters for the servlet

      Add the following line to the `Aliased Servlet Init Parameters' section

      servlet.discoservlet.initArgs=config=http://mywebserver.company.com/
      disco3ivfiles/html/disco3iv.xml
      (Note: the above line must be a single unbroken line with no manual line break or carriage return) Where mywebserver.company.com is the machine name that the HTTP Server is installed on. Remember to change this if you copy and paste this text.

      2.3.6.3 Editing jserv.properties file of JServe

      This can be found where you installed Apache JServ

      eg If you installed Apache JServ in the \JServ directory ( /usr/local/jserv for Solaris) the file can be found in the \JServ\conf sub directory ( /usr/local/jserv/conf for Solaris).

      2.3.6.3.1 Add the JVM parameters

      Add the following line to the `Arguments passed to Java interpreter (optional)' section

      wrapper.bin.parameters=-Dorg.omg.CORBA.ORBClass=
      com.visigenic.vbroker.orb.ORB -Dorg.omg.CORBA.ORBSingletonClass= com.visigenic.vbroker.orb.ORB
      (Note: There is a space between `.orb.ORB' and `-Dorg' above. Also, the above line must be a single unbroken line with no manual line break or carriage return). (Note: It is also recommended to increase the maximum memory available to the JVM i.e. "wrapper.bin.parameters=-mx256m -Dorg.omg.CORBA.ORBClass=
      com.visigenic.vbroker.orb.ORB -Dorg.omg.CORBA.ORBSingletonClass= com.visigenic.vbroker.orb.ORB" to increase this to 256mbytes)
      2.3.6.3.2 Add the ClassPath value

      Add the following line to the `CLASSPATH environment value passed to the JVM' section

      For Windows NT:
      wrapper.classpath=
      D:\orant\vbroker\lib\vbjorb.jar;D:\orant\vbroker\lib\vbjapp.jar Where D:\orant is the location of the Oracle Home directory. (NOTE: Also, the above line must be a single unbroken line with no manual line break or carriage return) For Solaris: wrapper.classpath=
      /usr/local/vbroker/lib/vbjorb.jar;/usr/local/vbroker/lib/vbjapp.jar
      Where /usr/local/vbroker is the directory where you installed Visibroker. (NOTE: Also, the above line must be a single unbroken line with no manual line break or carriage return)

      2.3.6.4 Running JServe

      For Windows NT:

      1. Stop the Apache Web Server.

      2. Wait ten seconds and restart the Apache Web Server.

      3. Start a browser window and type the following:

      mywebserver.company.com/servlets/discoservlet

      For Solaris:

      1. Stop the Apache Web Server.

      2. Restart the Apache Web Server.

      3. Start a browser window and type the following:

      mywebserver.company.com/servlets/discoservlet

      This should start Oracle Discoverer 3i Viewer and you should see the login screen:

      Your installation is now complete.

      2.3.7 Configuring Netscape Enterprise Server 4.0 and Servlet Engine

      This section includes the following topics:

      NES4.0 has its own built in servlet engine. Use the following instructions to configure the servlet engine. Note that the instructions apply to both NT and Solaris unless specified otherwise.

      2.3.7.1 Defining a directory alias

      Start a browser and type the following:

      mywebserver.company.com:8888

      Where mywebserver.company.com is the machine name the HTTP server is installed on.

      You will get a login prompt.

      Enter the user id and password (These were entered during the Netscape ES installation).

      The default is admin for both user id and password.

      Click the `Manage' button in the above window.

      1. Select the `Content Mgmt' tab from the above window.

      2. Select the `Additional Document Directories' option.

      3. Enter `disco3ivfiles' as the `URL prefix' value

      4. Specify the `Map to Directory:' value as follows:

        • (for NT) enter `D:/disco3ivhome/disco3iv' as the `Map to Directory:' value

        • (for Solaris) enter `/usr/local/disco3ivhome/disco3iv'as the `Map to Directory:' value

      5. Leave `Apply Style' as `None'

      6. Click OK.

      7. Click on the `Save and Apply' option.

      2.3.7.2 Checking the directory alias

      Start a new browser and enter the following as a URL address:

      mywebserver.company.com/disco3ivfiles/

      Where mywebserver.company.com is the machine name the HTTP server is installed on.

      You should be presented with the above contents

      2.3.7.3 Configure NES servlet engine

      Start NES Admin and select the Servlets tab

      Select the `Enable/Disable Servlets' tab and ensure that the `Activate the Servlet Engine' and `Enable JSP?' options are set to `Yes'.

      1. Click on OK.

      2. Click on the `Save and Apply' changes button.

      3. Select the `Preferences' tab and click the Server Off button to stop the server.

      2.3.7.4 Editing the servlets.properties configuration file

      Edit the servlets.properties file.

      This can be found in the NES installation directory. For example:

      • (under NT) if you have installed NES to D:\Netscape\Server4 the file can be found in the D:\Netscape\Server4\https-mywebserver\config directory

      • (under Solaris) if you have installed NES to /usr/local/netscape/server4 the file can be found in the /usr/local/netscape/server4/https-mywebserver/config directory

      where mywebserver is the name of the machine the Server has been installed on.

      Append three lines to the end of the file as follows:

      • for NT, append the following three lines:

        servlet.discoservlet.classpath=D:/disco3ivhome/disco3iv/disco3iv.jar
        servlet.discoservlet.code=oracle.disco3iv.Disco3iv
        servlet.discoservlet.initArgs=config=http://mywebserver.company.com/
        disco3ivfiles/html/disco3iv.xml
        
        

        where D:/disco3ivhome is the full path for the disco3iv.jar

      • for Solaris, append the following three lines:

        servlet.discoservlet.classpath=/usr/local/disco3ivhome/disco3iv/disco3iv.jar 
        servlet.discoservlet.code=oracle.disco3iv.Disco3iv 
        servlet.discoservlet.initArgs=config=http://mywebserver.company.com/ 
        disco3ivfiles/html/disco3iv.xml 
        
        

        where /usr/local/disco3ivhome is the full path for the disco3iv.jar

      Save and exit.

      2.3.7.5 Editing the rules.properties configuration file

      Edit the rules.properties file.

      This can be found in the NES installation directory. For example:

      • (under NT) if you have installed NES to D:\Netscape\Server4 the file can be found in the D:\Netscape\Server4\https-mywebserver\config directory

      • (under Solaris) if you have installed NES to /usr/local/netscape/server4 the file can be found in the /usr/local/netscape/server4/https-mywebserver/config directory

      where mywebserver is the name of the machine the Server has been installed on.

      Append the following line to the end of the file

      /discoservlet=discoservlet
      
      

      Save and exit.

      2.3.7.6 Edit the jvm12.conf configuration file

      Edit jvm12.conf

      This can be found in the NES installation directory. For example:

      • (under NT) if you have installed NES to D:\Netscape\Server4 the file can be found in the D:\Netscape\Server4\https-mywebserver\config directory

      • (under Solaris) if you have installed NES to /usr/local/netscape/server4 the file can be found in the /usr/local/netscape/server4/https-mywebserver/config directory

      where mywebserver is the name of the machine the Server has been installed on.

      2.3.7.6.1 Adding classpath information

      To make sure that vbjorb.jar and vbjapp.jar are loaded first, modify the `jvm.classpath' line as follows:

      • for NT, add the following text:

        D:/orant/vbroker/lib/vbjorb.jar;D:/orant/vbroker/lib/vbjapp.jar;
        
        

        Before you add the text, the line looks like this:

        jvm.classpath=D:/Netscape/Server4/plugins/samples/servlets/beans/
        SDKBeans.jar;D:/Netscape/Server4/bin/https/jar/xml4j_1_1_9.jar;D:/Netscape/
        Server4/bin/https/jar/Bugbase.jar;D:/Netscape/Server4/bin/https/jar/
        Calljsac.jar
        
        

        After you add the text, the line looks like this:

        jvm.classpath=D:/orant/vbroker/lib/vbjorb.jar;D:/orant/vbroker/lib/
        vbjapp.jar;D:/Netscape/Server4/plugins/samples/servlets/beans/
        SDKBeans.jar;D:/Netscape/Server4/bin/https/jar/xml4j_1_1_9.jar;D:/Netscape/
        Server4/bin/https/jar/Bugbase.jar;D:/Netscape/Server4/bin/https/jar/
        Calljsac.jar
        
        

        where D:/orant is the directory where you installed Visibroker.

      • for Solaris, add the following text:

        /usr/local/vbroker/lib/vbjorb.jar;/usr/local/vbroker/lib/vbjapp.jar;
        
        

        Before you add the text, the line looks like this:

        jvm.classpath=/usr/local/netscape/server4/plugins/samples/servlets/beans/ 
        SDKBeans.jar;/usr/local/netscape/server4/bin/https/jar/xml4j_1_1_9.jar;/usr/
        local/netscape/server4/bin/https/jar/Bugbase.jar;/usr/local/netscape/
        server4/bin/https/jar/Calljsac.jar
        
        

        After you add the text, the line looks like this:

        jvm.classpath=/usr/local/vbroker/lib/vbjorb.jar;/usr/local/vbroker/lib/ 
        vbjapp.jar;/usr/local/netscape/server4/plugins/samples/servlets/beans/ 
        SDKBeans.jar;/usr/local/netscape/server4/bin/https/jar/xml4j_1_1_9.jar;/usr/
        local/netscape/server4/bin/https/jar/Bugbase.jar;/usr/local/netscape/
        server4/bin/https/jar/Calljsac.jar
        
        

        where /usr/local/vbroker is the directory where you installed Visibroker.

      Note that in both cases, the classpath must not include a manual line break or carriage return.

      2.3.7.6.2 Adding JVM parameters

      Append the following 2 lines at the bottom of the file

      org.omg.CORBA.ORBClass=com.visigenic.vbroker.orb.ORB
      org.omg.CORBA.ORBSingletonClass=com.visigenic.vbroker.orb.ORB
      
      

      Save the file and exit.

      2.3.7.7 Edit the start-jre configuration file

      Edit the start-jre file.

      This can be found in the NES installation directory. For example:

      • (under NT) if you have installed NES to D:\Netscape\Server4 the file can be found in the D:\Netscape\Server4\https-admserv directory

      • (under Solaris) if you have installed NES to /usr/local/netscape/server4 the file can be found in the /usr/local/netscape/server4/https-admserv directory

      2.3.7.7.1 Adding classpath information

      To include the location of the disco3iv.jar file and to make sure that vbjorb.jar and vbjapp.jar are loaded first , modify the `NSES_classpath' line as follows:

      • for NT, add the following text:

        D:/disco3ivhome/disco3iv/disco3ivjar;D:/orant/vbroker/lib/vbjorb.jar;D:/orant/
        vbroker/lib/vbjapp.jar;
        
        

        Before you add the text, the line looks like this:

        NSES_classpath=D:/Netscape/Server4/plugins/samples/servlets/beans/
        SDKBeans.jar;D:/Netscape/Server4/bin/https/jar/xml4j_1_1_9.jar;D:/Netscape/
        Server4/bin/https/jar/Bugbase.jar;D:/Netscape/Server4/bin/https/jar/
        Calljsac.jar
        
        

        After you add the text, the line looks like this:

        NSES_classpath=D:/disco3ivhome/disco3iv/disco3ivjar;D:/orant/vbroker/lib/
        vbjorb.jar;D:/orant/vbroker/lib/vbjapp.jar;D:/Netscape/Server4/plugins/
        samples/servlets/beans/SDKBeans.jar;D:/Netscape/Server4/bin/https/jar/
        xml4j_1_1_9.jar;D:/Netscape/Server4/bin/https/jar/Bugbase.jar;D:/Netscape/
        Server4/bin/https/jar/Calljsac.jar
        
        

        where D:/disco3ivhome is the location of /disco3iv/disco3ivjar, and D:/orant is the directory where you installed Visibroker.

      • for Solaris, add the following text:

        /usr/local/disco3ivhome/disco3iv/disco3iv.jar;/usr/local/vbroker/lib/
        vbjorb.jar;/usr/local/vbroker/lib/vbjapp.jar;
        
        

        Before you add the text, the line looks like this:

        NSES_classpath=/usr/local/netscape/server4/plugins/samples/servlets/beans/ 
        SDKBeans.jar;/usr/local/netscape/server4/bin/https/jar/xml4j_1_1_9.jar;/usr/
        local/netscape/server4/bin/https/jar/Bugbase.jar;/usr/local/netscape/
        server4/bin/https/jar/Calljsac.jar
        
        

        After you add the text, the line looks like this:

        NSES_classpath=/usr/local/disco3ivhome/disco3iv/disco3iv.jar;/usr/local/
        vbroker/lib/vbjorb.jar;/usr/local/vbroker/lib/ vbjapp.jar;/usr/local/
        netscape/server4/plugins/samples/servlets/beans/ SDKBeans.jar;/usr/local/
        netscape/server4/bin/https/jar/xml4j_1_1_9.jar;/usr/local/netscape/server4/
        bin/https/jar/Bugbase.jar;/usr/local/netscape/server4/bin/https/jar/
        Calljsac.jar
        
        

        where /usr/local/disco3ivhome is the location of /disco3iv/disco3iv.jar and /usr/local/vbroker is the directory where you installed Visibroker.

      Note that in both cases, the classpath must not include a manual line break or carriage return.

      2.3.7.8 Running the NES 4.0 servlet

      Before you start the servlet go to Section 2.3.4.4, "Oracle Discoverer 3i Viewer Edition .XML File Configuration" and follow the instructions there for updating the .xml file with the correct value for the Discoverer session name.

      To restart the Web Server do the following:

      1. Select the `Preferences' tab and click the Server On button to start the server.

      2. The following window is displayed:

      1. Click the `Load Configuration Files' button in the above window
        The following dialog is displayed

      1. Click `OK' to continue
        The Server Manager window is displayed

      1. Click the `Server On' button to restart the server
        The following dialog is displayed:

      1. Click `OK'
        Your server is now running.

      2. Start a browser window and type the following:

      mywebserver.company.com/discoservlet

      Where mywebserver.company.com is the machine name the HTTP server is installed on.

      This should start Discoverer 3i Viewer.

      Your configuration is complete.

      2.3.8 Configuring JRun Servlet Engine

      This servlet engine can be used with a number of different web servers.

      This section includes the following topics:

      2.3.8.1 Web servers supported by JRun

      JRun is a separate Servlet Engine that can run with different Web Servers.

      • Apache 1.3.6/1.3.9/1.3.11

      • IIS 4.0/PWS 4.0

      • Netscape Enterprise Server 4.0

      Although JRun has a user interface all configuration files are stored as text files which are simpler to edit and manage.

      2.3.8.2 Defining a directory alias under Apache 1.3.9

      If you are using JRun servlet engine under Apache then See Section 2.3.6.1, "Defining a directory alias for an Apache web server" for details.

      2.3.8.3 Defining a directory alias under Netscape Enterprise Server 4.0

      If you are using JRun servlet engine under Netscape Enterprise Server 4.0 then see Section 2.3.6.1, "Defining a directory alias for an Apache web server" for details.

      2.3.8.4 Defining a directory alias under IIS 4.0

      Start up the Microsoft Internet Service Manager

      Select default web site under the machine name you wish to configure.

      Right click to get the menu and select the `New - >Virtual Directory'

      Enter `disco3ivfiles' as the virtual directory and press `Next'.

      Enter `d:\disco3ivhome\disco3iv' and press `Next'.

      Ensure that all check boxes are checked and press `Finish'

      2.3.8.5 Checking the directory alias under IIS

      Select `Default Web Site' under the machine name you wish to configure.

      Right click and select `Start' if it is not greyed out (i.e. it has not already been selected).

      Start a browser and enter the following

      `mywebserver.company.com/disco3ivfiles/'

      This should give you the following window:

      2.3.8.6 Defining a directory alias under PWS 4.0

      Start up the Personal Web Manager

      Make sure the `Allow Directory Browsing' checkbox is ticked as it is unchecked by default.

      Click on the `Add button' and enter the following information:

      Make sure the `Execute' checkbox is ticked as it is unchecked by default.

      Click OK.

      2.3.8.7 Checking the Directory Alias for PWS 4.0 Web Server

      Stop and restart IIS/PWS and then type in the following address into the address window

      `mywebserver.company.com/disco3ivfiles/'

      This should give you the following window:

      2.3.8.8 Editing the Java Service Manager configuration file for JRun Servlet

      Edit the jsm.properties file.

      This can be found in the JRun installation directory.

      Eg if you installed JRun to D:\JRun then the file can be found in the

      D:\JRun\jsm-default\properties.

      2.3.8.8.1 Adding classpath information

      You need to prepend the following string to your classpath value.

      D:/orant/vbroker/lib/vbjorb.jar;D:/orant/vbroker/lib/vbjapp.jar;D:/
      disco3ivhome/disco3iv/disco3iv.jar;
      
      

      Before change it looks like this:

      java.classpath=D:/JRun/classes;D:/JRun/jsm-default/classes;D:/JRun/lib/
      jrun.jar;D:/JRun/lib/servlet.jar;D:/JRun/webl/WebL.jar;D:/JRun/lib/jsp.jar;D:/
      JRun/lib/xml4j.jar;D:/JRun/lib/xt.jar;D:/JRun/lib/fesi.jar;D:/JRun/lib/
      cfanywhere.jar;D:/JRun/lib/NetComponents.jar;D:/JRun/lib/OROMatcher.jar;D:/JRun/
      lib/tools.jar;D:/JRun/instantdb/classes;D:/JRun/lib/jrunadmin/
      jrunadmin.jar;d:\\jdk1.2.1\\/lib/classes.zip;d:\\jdk1.2.1\\/lib/
      rt.jar;d:\\jdk1.2.1\\/lib/i18n.jar;d:\\jdk1.2.1\\/jre/lib/rt.jar;d:\\jdk1.2.1\\/
      jre/lib/i18n.jar;d:\\jdk1.2.1\\/lib/tools.jar;D:/JRun/lib/jrunadmin/swing.jar;
      
      

      Afterwards it looks like this:

      java.classpath=D:/orant/vbroker/lib/vbjorb.jar;D:/orant/vbroker/lib/
      vbjapp.jar;D:/disco3ivhome/disco3iv/disco3iv.jar;D:/JRun/classes;D:/JRun/
      jsm-default/classes;D:/JRun/lib/jrun.jar;D:/JRun/lib/servlet.jar;D:/JRun/webl/
      WebL.jar;D:/JRun/lib/jsp.jar;D:/JRun/lib/xml4j.jar;D:/JRun/lib/xt.jar;D:/JRun/
      lib/fesi.jar;D:/JRun/lib/cfanywhere.jar;D:/JRun/lib/NetComponents.jar;D:/JRun/
      lib/OROMatcher.jar;D:/JRun/lib/tools.jar;D:/JRun/instantdb/classes;D:/JRun/lib/
      jrunadmin/jrunadmin.jar;d:\\jdk1.2.1\\/lib/classes.zip;d:\\jdk1.2.1\\/lib/
      rt.jar;d:\\jdk1.2.1\\/lib/i18n.jar;d:\\jdk1.2.1\\/jre/lib/rt.jar;d:\\jdk1.2.1\\/
      jre/lib/i18n.jar;d:\\jdk1.2.1\\/lib/tools.jar;D:/JRun/lib/jrunadmin/swing.jar;
      
      (where D:/disco3ivhome/disco3iv is the full path for disco3iv.jar)
      (Note: the above classpath must not include a manual line break or carriage 
      return)
      
      
      2.3.8.8.2 Adding JVM Parameters

      Append the following line to the end of the file

      java.args=-Dorg.omg.CORBA.ORBClass=com.visigenic.vbroker.orb.ORB 
      -Dorg.omg.CORBA.ORBSingletonClass=com.visigenic.vbroker.orb.ORB
      
      (Note: the above classpath must not include a manual line break or carriage 
      return)
      
      

      Save the file and exit.

      2.3.8.9 Editing the servlets.properties configuration file for the JRun Servlet

      The file is called servlets.properties

      This can be found in the JRun installation directory.

      If you installed JRun to D:\JRun then the file can be found at

      D:\JRun\jsm-default\services\jse\properties

      2.3.8.9.1 Defining the servlet

      Add the following lines to the end of the file

      servlet.discoservlet.code=oracle.disco3iv.Disco3iv
      servlet.discoservlet.args=config=http://mywebserver.company.com/disco3ivfiles/
      html/disco3iv.xml
      servlet.discoservlet.preload=true
      
      

      Save the file and exit.

      2.3.8.10 Running the JRun Servlet

      In order to run the servlet you need to stop and restart in the following order

      1. Stop JRun

      2. Stop Web Server

      3. Start Web Server

      4. Start JRun

      Before you start the servlet go to Section 2.3.4.4, "Oracle Discoverer 3i Viewer Edition .XML File Configuration" and follow the instructions there for updating the .xml file with the correct value for the Discoverer session name.

      Start a browser window and type the following:

      mywebserver.company.com/servlet/discoservlet
      

      Where mywebserver.company.com is the machine name the HTTP server is installed on.

      This should start Discoverer 3i Viewer.

      Your installation is now complete.

      2.3.9 Configuring ServletExec 2.2c Servlet

      This section includes the following topics:

      2.3.9.1 Editing the servlets.properties configuration file

      The file is called servlets.properties

      This can be found in the ServletExec installation directory.

      If you installed ServletExec to D:\ServletExec then the file can be found at

      D:\ServletExec\ServletExec Data\default

      2.3.9.1.1 Defining the servlet

      Append the following 4 lines to the end of the document

      # discoservlet servlet 
      servlet.discoservlet.code=oracle.disco3iv.Disco3iv
      servlet.discoservlet.codebase=D:/disco3ivhome/disco3iv.jar
      servlet.discoservlet.initArgs=config=http://mywebserver.company.com/ disco3ivfiles/html/disco3iv.xml

      Save the file and exit.

      2.3.9.2 Editing the rules.properties configuration file

      The file is called rules.properties and can be found in the ServletExec installation directory.

      If you installed ServletExec to D:\ServletExec then the file can be found at

      D:\ServletExec\ServletExec Data\default

      Append the following line to the end of the file

      /discoservlet=discoservlet
      
      

      Save the file and exit.

      2.3.9.3 Editing the Classpath.pref file

      The file is called Classpath.pref

      This can be found in the ServletExec installation directory.

      If you installed ServletExec to D:\ServletExec then the file can be found at

      D:\ServletExec\ServletExec Data

      Append the following text to the existing line.

      ;D:/orant/vbroker/lib/vbjorb.jar;D:/orant/vbroker/lib/vbjapp.jar
      
      

      So before the line will look like this:

      D:\SE4\classes
      
      

      Afterwards it will look like this:

      D:\SE4\classes 
      ;D:/orant/vbroker/lib/vbjorb.jar;D:/orant/vbroker/lib/vbjapp.jar
      
      (Note: the above line must not include a manual line break or carriage return)
      
      

      Save file and exit

      2.3.9.4 Running the Servlet

      Stop and restart the Web Server

      Before you start the servlet go to Section 2.3.4.4, "Oracle Discoverer 3i Viewer Edition .XML File Configuration" and follow the instructions there for updating the .xml file with the correct value for the Discoverer session name.

      Start a web browser and type the following

      mywebserver.company.com/servlet/discoservlet

      Where mywebserver.company.com is the machine name the HTTP server is installed on.

      This should start Discoverer 3i Viewer.

      Your installation is now complete.

      2.3.10 Configuring Oracle Application Server

      2.3.10.1 Unpacking disco3iv.jar

      You must first unpack the disco3iv.jar file found in the D:\disco3ivhome\disco3iv directory.

      It is necessary to download JRE 1.2.2 from www.javasoft.com to gain access to the unpacker executable jar.exe.

      1. Download JRE 1.2.2 from www.javasoft.com

      2. Install JRE 1.2.2 by double-clicking the downloaded JRE file (jre1_2_2-005-win.exe)

      3. In an MSDOS window change directory to: d:\disco3ivhome\disco3iv\

      4. In the MSDOS window, type in the command: jar -xvf disco3iv.jar

      After hitting `Return' and executing the command, you will get similar results at the end of the extraction as shown below.

      2.3.10.2 Setting the Listener Properties

      Start the Oracle Application Server Manager by selecting Start | Oracle Application Server | Oracle Application Server Manager.

      Type your username and password.

      Expand the top level item.

      Expand the `HTTP Listeners' section and select your default HTTP listener.

      By default there is always 2 listeners.

      The `mywebserver.company.com:admin' listener is used for administration of the web site.

      The `mywebserver.company.com:www' listener is used for web browsers to access your web server.

      1. Expand the `mywebserver.company.com:www' listener.

      2. Select `Server'

      3. Set `Directory Indexing' to TRUE (default is FALSE).

      4. Click on `Apply'.

      5. Click OK to close the Success dialog box.

      2.3.10.3 Defining a Directory Alias

      1. Select `Directory'

      2. Enter `D:\disco3ivhome\disco3iv\' for `File System Directory'

      3. Leave `Flag' as default (NR)

      4. Enter `/disco3ivfiles/' for `Virtual Directory'

      5. Click on `Apply'

      6. Click OK to close the Success dialog box.

      7. Stop and restart the OAS web server.

      8. Start a browser and enter the following into the address window:

      `mywebserver.company.com/disco3ivfiles/'

      You should get the contents of the directory similar to the above.

      2.3.10.4 Creating an Application

      1. In the Oracle Application Server Manager, click on the `Applications' element.

      2. Click on the green `+' button on the toolbar in the above window (shown highlighted in above figure)

      3. In the `Add Application' dialog box click on Application Type and select `Jservlet'

      4. Ensure that the `Configuration Mode is set to `Manually'.

      5. Click `Apply'

      2.3.10.5 Configuring the Application

      1. Enter `DiscoApplication' for `Application Name'

      2. Enter `DiscoApplication' for `Display Name'

      3. Enter `1.0' for `Application Version'

      4. Click `Apply'

      5. In the above dialog box click `Add Cartridge to this Application'

      2.3.10.6 Configure the Cartridge

      1. Enter `DiscoCartridge' for `Cartridge Name'.

      2. Enter `DiscoCartridge' for `Display Name'.

      3. Enter `/discoservlet' for `Virtual Path'.

      4. Enter `D:\disco3ivhome\disco3iv\' for Physical Path to the unpacked disco3iv.jar'.

      5. Click the `Apply' button

      6. Click OK to close the Success dialog box.

      2.3.10.7 Configuring the Application Environment

      1. Expand the `DiscoApplication' icon.

      2. Expand the `Configuration' icon.

      3. Select the'Environment Variables' option.

      4. Add the following line to the start of the value for `CLASSPATH'

        D:\disco3ivhome\disco3iv\disco3iv.jar;D:\orant\VBROKER\lib\VBJAPP.JAR;D:\orant\V
        BROKER\lib\VBJORB.JAR;
        

      1. Click on the `Apply' button to update the CLASSPATH variable.

      2. Click OK to close the Success dialog box.

      2.3.10.8 Configuring the Java Environment

      1. Select the `Java Environment' option.

      2. Enter `Servlet.oracle.disco3iv.Disco3iv.initArgs' in the left field

      3. Enter `config=http://mywebserver.company.com/disco3ivfiles/html/disco3iv.xml' in the right field.

      4. Click on Apply.

      5. Click OK to close the Success dialog box.

      2.3.10.9 Starting the Servlet

      Before you start the servlet go to Section 2.3.4.4, "Oracle Discoverer 3i Viewer Edition .XML File Configuration" and follow the instructions there for updating the .xml file with the correct value for the Discoverer session name.

      1. Stop and restart the OAS Web Server

      2. Start a web browser

      3. Enter the following for URL:

      http://mywebserver.company.com/discoservlet/oracle.disco3iv.Disco3iv

      You should see the following screen

      The servlet is now running and your installation is complete.

      2.3.11 Setting up a secure link using HTTPS

      To ensure that your entire discoverer document is secure and to get your browser to acknowledge a "secure" page, it is necessary to make a minor adjustment to your disco3iv.xml file.

      Make changes as follows:

      1. Open your disco3iv.xml file for editing

      2. Change the image_path so to includes https and the full path to the image directory.

      <argument name="image_path" type="href"> images</argument><argument name="image_path" type="href">https://mywebserver.company.com/disco3ivhome/ images</argument>

      Below is an example of the change:

      disco3iv.xml - Before change<argument name="help_path" type="href">help</argument><argument name="image_path" type="href"> images</argument><argument name="show_login_method_control">true</argument> </document></disco_config>disco3iv.xml - After change

      <argument name="help_path" type="href">help</argument><argument name="image_path" type="href">https://mywebserver.company.com/disco3ivfiles/images</argument><argument name="show_login_method_control">true</argument> </document></disco_config>

      2.3.12 Upgrading from Discoverer Viewer Version 3.1

      If you already have an existing installation of Discoverer Viewer Version 3.1 you can install Version 3i alongside it using the process described in the preceeding sections. On completion of the upgrade, both versions of Discoverer viewer can run in parallel.

      If you wish to de-install Discoverer Viewer Version 3.1, it is necessary to perform the following steps which can all be carried out from your Discoverer 3i Viewer install media :

      1. De-install Discoverer Viewer 3.1

      2. De-install Visibroker

      3. Re-install Visibroker


Prev Next
Oracle
Copyright © 2000 Oracle Corporation.

All Rights Reserved.

Contents