Oracle Discoverer 3i Viewer Configuration Guide for Oracle9i Application Server for Windows Release 3.3.57 A87361-01 |
|  |  | Contents

# 2
Running, Maintaining and Supporting
Oracle Discoverer 3i Viewer

This chapter explains how to run and maintain Discoverer 3i Viewer.

The topics include:

- Running Discoverer 3i Viewer

- Using the Discoverer NT Service

- Registering and Unregistering Discoverer Services Components

- Editing the End User Preferences

- Shutting Down

- Adding and Removing Server Machines

- Setting up a secure link using HTTPS

- Frequently Asked Questions

## 2.1 Running Discoverer 3i Viewer

Once you have completed the Oracle9i Application Server installation (see the Oracle9i Application Server Installation Guide) you can run Discoverer 3i Viewer.

To run Discoverer 3i Viewer complete the following steps:

1. Start a browser window and type in your own details using the following as a guide:

   http://hostname.domain/servlets/discoservlet

   Where hostname.domain represents the Web server machine that the HTTP server is installed on. You must replace this with its fully qualified host name. For example:

   http://machinename.oracle.com/servlets/discoservlet

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

1. Enter your User Name, Password and database connect string.

2. (Optional) If you are connecting as an Oracle Applications user (to an Oracle Applications database) select the Oracle Applications User check box
   If the Oracle Applications User check box is not displayed in the connect screen above, refer to Section A.1, "Specifying display of the Applications User Checkbox in Connect Dialog".

3. Click Connect

You are now running Oracle Discoverer 3i Viewer.

## 2.2 Using the Discoverer NT Service

### 2.2.1 What is an NT Service?

An NT Service is a special process that NT can start automatically at startup. Typical NT Services start various computer operations, such as networking and remote access procedures, server operations, and telephony processes.

### 2.2.2 What is the Discoverer NT Service?

When you install Discoverer, the Discoverer NT service is created as an automatic NT Service called "OracleDiscoverer3i". The Discoverer NT service automatically starts the Discoverer Services Locator component and the CORBA services whenever the NT machine is started. Using the Discoverer NT service, you can also stop all of these components by simply stopping the service from running.

A key benefit of having Discoverer Services Locator component and the CORBA services components started as a single NT service is that you do not need to remain logged onto a machine for the service (and therefore the Locator and the CORBA services) to stay running. If you launched each component individually on each machine, you would need to stay logged onto the machine(s) as the administrator. Logging off would automatically stop the components.

The Discoverer NT service runs the appropriate components based on the type of server you selected when installing Discoverer. The following table shows the components started by the Discoverer NT service for the servers.

##### Table 2-1 Discoverer NT service components

Server | Locator | CORBA services | OAD
--- | --- | --- | ---
Master Discoverer Server |  | X | X
HTTP Server | X | X |
Additional Discoverer Server |  | X | X
Single Machine Installation | X | X | X

### 2.2.3 How does the Discoverer NT service start?

When you install Discoverer, the Discoverer NT service's Startup property is set to Automatic. In other words, the service starts automatically whenever the machine is started. However, once the service has started automatically you can subsequently stop it and restart it manually.

For a custom installation, the Discoverer NT service automatically starts the Locator and Smart Agent (OSAgent) on machines where you installed the Locator. On machines where you installed the Session and Preferences components, the Discoverer NT service automatically starts the CORBA services.

You can also change the Discoverer NT service's Startup property to Manual. In other words, the service does not automatically start when the computer is started. This may be useful if your network requires special services that have to start and stop in a particular sequence. You can start the other services, and then manually start the Discoverer NT service at the appropriate time.

### 2.2.4 To start and stop the Discoverer NT service manually:

1. From the Windows Start menu, choose Settings | Control Panel and double-click on the Services icon to display the Services dialog box.

   The Services dialog box contains OracleDiscoverer3i.

   Status--shows if the service is started and running. If the service has not been started, the status column is blank.

   Startup--shows how the service is started, either manually or automatically. The Discoverer NT service is set to start automatically.

2. To stop the Discoverer NT service, select it in the dialog box and click the Stop button. Then close the dialog box.

3. To start the service, select it in the dialog box and click Start. Then close the dialog box.

   Note: If your end users run Discoverer against an Oracle Application, always shut down the Listener before you start the Locator.

### 2.2.5 To change the Discoverer NT service to manual startup:

1. From the Windows Start menu, choose Settings | Control Panel and double-click on the Services icon.

   The Services dialog box appears.

2. Select OracleDiscoverer3i in the Services dialog box.

3. Click the Startup button.

   The Service dialog box for the OracleDiscoverer3i appears.

4. In the Startup Type section of the Service dialog box, select Manual.

5. Click OK.

### 2.2.6 Seeing Service Errors

The NT Event Log displays any errors that occur during startup of the Discoverer NT service. To see the NT Event Log, choose Start | Programs | Administrative Tools (Common) | Event Viewer.

Discoverer also keeps an internal log of errors that may occur when running the Locator on an HTTP Server. To see a list of Locator errors, open the Locator.log file in the <iSUITES_HOME>\apache\apache\htdocs\DISCWB33\applet directory in the HTTP Server's root directory (or other directory if you installed the Discoverer client in some other directory).

## 2.3 Registering and Unregistering Discoverer Services Components

The Discoverer Services components must be registered with the Visibroker OAD (Object Activation Daemon). The components are registered during installation. If you remove or shut down a machine, you should unregister Discoverer Services components.

You can register and unregister components using the Windows Start menu or using the command line.

You can view the registered components for one machine or for the entire network.

To register and unregister components (and to view registered components), the VisiBroker OAD must be running and responding.

### 2.3.1 To make sure the OAD is running and responding:

If you are not sure whether the OAD is running:

1. Press Ctrl-Alt-Del and click the Task Manager button to run the Windows Task Manager.

2. Select the Processes tab.

3. Confirm that oad.exe is running and responding.

If the OAD is not running:

1. From the Windows Start menu, choose Settings | Control Panel and double-click on the Services icon to display the Services dialog box.

2. Select OracleDiscoverer3i and click the Start button.

3. When the OAD is started, click Close.

If the OAD is running but not responding

1. From the Windows Start menu, choose Settings | Control Panel and double-click on the Services icon to display the Services dialog box.

2. Click the Stop button, then click the Start button again.

3. When the OAD is started, click Close.

### 2.3.2 To see the registered components on one machine:

1. Make sure the OAD is running.

2. Open an MS-DOS window (choose Start | Command Prompt).

3. At the command prompt, type:

   `oadutil list` and press return.

Note: Running the oadutil command displays only the list of components registered on the machine. It does not display all the components registered on the network of Discoverer machines.

In this example, the components are registered with the Discoverer Instance name of "UKP15601." Two components are registered on the machine:

1. Preferences (-preference; UKP15601OracleDiscovererPreference3.3)

2. Session (-session; UKP15601OracleDiscovererSession3.3).

A Collector file for logging events is also registered, (-collector; UKP15601OracleDiscovererCollector3.3).

If you used the command on one of the Other Discoverer Servers, only the Session component would be registered.

### 2.3.3 To see all the registered components on the network:

1. Make sure the OAD is running.

2. Open an MS-DOS window (choose Start | Command Prompt).

3. At the command prompt, type:

   `osfind` and press return.

A list shows all of the components running on the network.

### 2.3.4 Registering and Unregistering Components from the Windows Start Menu

On the machine where you want to register or unregister components:

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

2. Choose the component that you want to register or unregister.

   A confirmation screen appears.

### 2.3.5 Registering and Unregistering from the Command Line

Use the Run dialog box from the Windows Start menu. You can register components using batch scripts. The batch scripts are located in the <ORACLE_806_HOME>\Discwb33\util directory of the machine where the components are installed.

#### 2.3.5.1 To Register the Preferences and Session components with the OAD

The Preferences and Session components must be registered with the OAD. The OAD will start a new session per connection of the client. For your convenience, scripts are available to help you with registering the Preference and Session components with the OAD.

The scripts are named:

- registerSession.bat

- registerPreference.bat

To register the Session from the command line:

1. Open an MS-DOS window.

2. Change the directory to <ORACLE_806_HOME>\Discwb33\util.

3. Type

`> registerSession.ba`t

To register the Preferences from the command line:

1. Open an MS-DOS window.

2. Change the directory to <ORACLE_806_HOME>\Discwb33\util.

3. Type

`> registerPreference.ba`t

#### 2.3.5.2 To Unregister the Preferences and Session components from the OAD

For your convenience, scripts are available to help you with unregistering the Preference and Session components with the OAD.

The scripts are named:

- unregisterSession.bat

- unregisterPreference.bat

To unregister the Preferences component from the OAD:

1. Open an MS-DOS window.

2. Change the directory to <ORACLE_806_HOME>\Discwb33\util.

3. Type

`> unRegisterPreference.ba`t

To unregister the Session component from the OAD:

1. Open an MS-DOS window.

2. Change the directory to <ORACLE_806_HOME>\Discwb33\util.

3. Type

`> unRegisterSession.ba`t

## 2.4 Editing the End User Preferences

### 2.4.1 What are the End User Preferences?

The End User Preferences control default Oracle Discoverer behavior.

The Preferences file (pref.txt) controls default settings that apply to all end users. When a new session starts, the settings in the pref.txt file take affect.

In some cases, end users can override these settings from the Discoverer Plus Options dialog. Individual preferences are stored for each user as a unique combination of database and userid, and loaded whenever the user starts a new session. Therefore, users can log on from different client machines and still have their individual settings take effect. You can view the individual end user preference settings from within the Windows NT Registry Editor.

Also see the "Discoverer Administration Edition Administration Guide" for more information.

Note: Editing Preferences, such as adding a machine IP address, does not require that you shut down the Preferences component. Thus, users can continue working uninterrupted while you edit.

### 2.4.2 To set End User Preferences:

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

2. The Pref.txt file appears in Notepad.

3. Edit the items in the pref.txt file. See Table 2-2, "Registry settings stored in the pref.txt file".

4. Save the file and quit Notepad.

5. 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.

6. To continue, press the Enter key.

   The Preferences are updated in the Windows NT Registry. Preferences are now set for the Discoverer Services.

The following table shows the items in the pref.txt file

##### Table 2-2 Registry settings stored in the pref.txt file

Affected Feature | Preference Item Key Name | Description | Default/Values
--- | --- | --- | ---
Locator | MachineIPs | IP addresses or machine names of all Discoverer Server Application servers. This is the only required item in the pref.txt file. |
| DCW33_LOCATOR_JVM | Optional key. If present in the Registry under HKEY_LOCAL_ MACHINE | SOFTWARE | ORACLE, it should point to the path of a JVM used by the Locator. Setting this key allows the Discoverer Administrator to log off the machine where the Locator is installed without also stopping the Locator. |
Session Manager | Timeout | Amount of time after which Discoverer 3i disconnects an idle session from the database. Minimum time is 180 seconds. | 1800 (seconds)
| RowsPerHTML | Number of rows to display per HTML page. | 25 (any whole number)
Application | CacheFlushPercentage | Percentage of cache flushed if the cache is full. | 25
| MaxVirtualDiskMem | Maximum amount of disk memory allowed for the data cache. | 1024000000
| MaxVirtualHeapMem | Maximum amount of heap memory allowed for the data cache. | 1024000000
| QueryBehavior | Action to take after opening a workbook. | 0 (0 = Run Query Automatically, 1 = Don't Run Query, 2 = Ask for Confirmation)
| ShowDialogBitmaps | End users see the bitmap graphics on Discoverer Plus dialogs. | 1 (0 = off, 1 = on)
| DataFormat | Applies HTML formatting to data cells in worksheets. | "<fontFormat fontName="Dialog" pitch="10" bold="false" italic="false" underline="false" strikethrough="false" foreground="0,0,0" background="255, 255, 255" halign="right" valign="top"></fontFormat>"
| HeadingFormat | Applies HTML formatting to heading cells in worksheets. | "<fontFormat fontName="Dialog" pitch="10" bold="false" italic="false" underline="false" strikethrough="false" foreground="0,0,0" background="204, 204, 204" halign="left" valign="top"></fontFormat>"
| TotalsFormat | Applies HTML formatting to cells that contain totals in worksheets. | "<fontFormat fontName="Dialog" pitch="10" bold="false" italic="false" underline="false" strikethrough="false" foreground="0,0,0" background="255, 255, 255" halign="left" valign="top"></fontFormat>"
| NullValue | Specifies how null values are displayed in worksheets, for example, "NULL", "N/A", "0". | "NULL"
Database | DisableFanTrapDetection | Disables detection for fan trap in user queries. | 0 (0 = on, 1 = off)
| DisableMultiJoinDetection | Disables multiple join detection. | 1 (0 = on, 1 = off)
| DisableAutoQuery | If set to 0, queries do not automatically run when a worksheet opens. | 0 (0 = on, 1 = off)
| ItemClassDelay | Fetch list of values for this amount of time before timing out. | 15 (seconds)
| PredictionThresholdSeconds | Warn user if the predicted query time will exceed the number of seconds. | 60 (seconds)
| PredictionThresholdSeconds Enabled | Query prediction threshold disabled (0) or enabled (1). | 1
| QueryTimeLimit | Limit on query time in seconds. | 1800 (seconds)
| QueryTimeLimitEnabled | Query time limit disabled (0) or enabled (1). | 1
| RowFetchLimit | The maximum number of rows fetched (or retrieved). | 10000 (rows)
| RowFetchLimitEnabled | RowFetchLimit parameter is disabled (0) or enabled (1). | 1
| RowsPerFetch | The number of rows to fetch at once. | 100 (rows)
| SummaryThreshold | Use summary table only if it is no older than this number of days. | 30 (days) 0 do not use summary at all
| SummaryThresholdEnabled | If enabled (1), will use the value specified by SummaryThreshold. Otherwise, Discoverer will always use summary tables if they are available. | 1
| DefaultEUL | Sets the EUL you want all users to connect to. Each user can override this default from the Discoverer Plus Options dialog. | Any EUL you have created.
Oracle Applications Mode | AppsGWYUID | Specifies the public username and password for the AOL security DLL. | "APPLSYSPUB/PUB"
| AppsFNDNAM | Specified the schema in which certain vital Oracle Applications data is stored. | "APPS"
| ShowUserTypeChoice | Activates an end-user checkbox that allows them to specify whether they want to run Discoverer against an Oracle Application. | 1
| DefaultUserTypeIsApps | Specifies that users run Discoverer by default against an Oracle Application. | 1
Internal settings | BusinessAreaFastFetchLevel | Controls the amount of pre-caching that occurs for components and items whenever a Business Area is fetched. | 1
| ObjectsAlwaysAccessible | Verify that Business Area objects and items exist in the database. | 0 (0=verify; 1=don't verify and assume that the objects and items exist)
| SummaryObjectsUseCachedAccessibility | Controls whether to access the summary-derived objects in the cache. | 0
| AvoidServerWildcardBug | Set to 1 if running against RDBMS 7.3.2 with NLS_LANG set to Japanese_Japan.JA16SJIS to avoid certain list box appearing empty. | 0
| RdbFastSQLOff |  | 0
Query Prediction and Performance | QPPEnable | Uses query prediction/performance (QPP) if set to 1. | 1 (0 = false, 1 = true)
| QPPCreateNewStats | Records new statistics if set to 1. | 1 (0 = false, 1 = true)
| QPPLoadStatsByObjectUseKey | Records statistics for same objects first if set to 1. | 1 (0 = false, 1 = true)
| QPPUseCpuTime | Query prediction uses CPU time within its algorithm. | 1 (0 = false, 1 = true)
| QPPAvgCostTimeAlgorithm |  | 2
| QPPMaxObjectUseKey | Affects the amount of statistics to cache in memory for query prediction. | 30
| QPPCBOEnforced | Will use cost-based optimizer if set to 1. Will use default optimizer if set to 0. | 1
| QPPObtainCostMethod |  | 1
| QPPMinCost | Only records or uses statistics with a cost greater than this value. | 0
| QPPMaxStats | Only loads this many previous statistics. | 500
| QPPMinActCpuTime | Only records or uses statistics with a CPU time greater than this value. | 0
| QPPMinActElapsedTime | Only records or uses statistics with an actual elapsed time greater than this value. | 0
| QPPMinEstElapsedTime | Only records or uses statistics with an estimated elapsed time greater than this value. | 0
| UseOptimizerHints | Will add optimized hints to SQL if set 1. | 0
| QuerySQLFastFetchLevel |  | 1
| SQLTrace | False (off). | 0
Crosstab Layout | Title | Displays titles that were created in Discoverer 3.1 worksheets. | 1 (0 = no, 1 = yes)
| Cell XGridline | Show horizontal gridlines. | 0 (0 = no, 1 = yes)
| Cell YGridline | Show vertical gridlines. | 0 (0 = no, 1 = yes)
| Axis Style | Crosstab axis position. | 2 (1 = inline, 2 = outline)
Table Layout | Title | Displays titles that were created in Discoverer 3.1 worksheets. | 1 (0 = no, 1 = yes)
| Cell XGridline | Show horizontal gridlines. | 0 (0 = no, 1 = yes)
| Cell YGridline | Show vertical gridlines. | 0 (0 = no, 1 = yes)
| Row Headings | Display row numbers on table worksheets. | 0 (0 = no, 1 = yes)

.

## 2.5 Shutting Down

If you need to perform maintenance, change hardware settings, or perform any other tasks, you should take the server machine off line while working. This prevents users from starting sessions on that server while you work. You can shut down Discoverer in two ways:

- Shut down individual server machines

- Shut down the entire Discoverer system

A reminder: You do not need to shut down to edit Discoverer Preferences.

If the machine you want to shut down runs the Discoverer Services Locator component or Preferences component, you need to shut down the entire Discoverer system. These components are used to create a session, regardless of which server the Session component is on. Therefore, stopping any of these components affects the entire Discoverer system.

### 2.5.1 Shutting Down Individual Servers

You can shut down a server in two ways:

- gradually, allowing current users to disconnect when they are ready

- immediately, forcing current users to end their Discoverer session

#### 2.5.1.1 To Shut Down Individual Servers Gradually

Shutting down a server gradually enables you to prevent new sessions from starting but allow current users to complete their sessions.

1. On the machine you want to shut down, from the Windows Start menu, choose Settings | Control Panel and then double-click the Services icon.

   The Services dialog box appears.

2. Select OracleDiscoverer3i and click the Stop button.

   Stopping the Oracle Discoverer NT service stops the CORBA services and the Locator component, which prevents any new sessions from being started on this machine. Sessions in progress are not affected by shutting down the Oracle Discoverer NT service. Thus, users will not be interrupted while working.

   After all the current users have disconnected from their sessions, you can perform your maintenance tasks. If you want to register or unregister components, the Oracle Discoverer NT service must first be restarted.

   To check that all users have disconnected, open the Windows Task Manager and be sure no instances of the Session executable (dis33ws.exe) are running.

#### 2.5.1.2 To Shut Down Individual Servers Immediately

An immediate shut down stops new user sessions from starting and stops the current sessions. To do this, you stop the Oracle Discoverer NT service on the machine (to prevent new sessions from being started) and then you stop the sessions currently running.

1. On the machine you want to shut down, from the Windows Start menu, choose Settings | Control Panel and then double-click the Services icon.

   The Services dialog box appears.

2. Select OracleDiscoverer3i and click the Stop button.

3. Press Ctrl + Alt + Del and open the Windows Task Manager.

4. Select the Processes tab.

5. Choose dis33ws.exe.

6. Click End Task.

7. Repeat steps 4 and 5for each session (dis33ws.exe) running in the Task Manager.

### 2.5.2 Shutting Down the Entire Discoverer System

To shut down the entire Discoverer system, you shut down individual machines in a specific order.

You can shut down the entire Discoverer system in two ways:

- gradually, allowing current users to disconnect when they are ready

- immediately, forcing current users to end their Discoverer session

#### 2.5.2.1 To Shut Down the Discoverer System Gradually

Shutting down the Discoverer system gradually enables you to prevent new sessions from starting but allow current users to complete their sessions. To shut down gradually, you stop the Oracle Discoverer NT service on each server and then let users finish their sessions.

1. On each server, choose Settings | Control Panel from the Windows Start menu and then double-click the Services icon.

2. Select OracleDiscoverer3i and click the Stop button.

   Stopping the Oracle Discoverer NT service stops the CORBA services and the Locator component, which prevents any new sessions from being started on this machine. Sessions in progress are not affected by shutting down the Oracle Discoverer NT service. Thus, users will not be interrupted while working.

   You now shut down the Preferences component.

   Warning: Do not shut down the Preferences component until all sessions are stopped. Shutting down the Preferences component while sessions are active can cause problems with active sessions.

3. Press Ctrl + Alt + Delete and open the Windows Task Manager.

4. Choose dis33pr.exe and click End Task to shut down the Preferences component.

When all of the current users have completed their sessions, the Discoverer system shuts down.

#### 2.5.2.2 To Shut Down the Discoverer System Immediately

An immediate shut down stops new user sessions from starting and stops the current sessions. To perform an immediate shut down, you:

- stop the Oracle Discoverer NT service on each machine (to prevent new sessions from being started)

- stop the sessions currently running

- stop the Preferences component

1. On each server:

   1. From the Windows Start menu, choose Settings | Control Panel and then double-click the Services icon.

   2. Select OracleDiscoverer3i and click the Stop button.

2. On each machine running a current session:

   1. Press Ctrl + Alt + Del to open the Windows Task Manager.

   2. Choose dis33ws.exe.

   3. Click End Task.

   4. Repeat steps 4 and 5 for each session (dis33ws.exe) and preferences (dis33pr.exe) running in the Task Manager.

## 2.6 Adding and Removing Server Machines

You can add or remove server machines from your Discoverer system at any time.

### 2.6.1 Adding an Additional Discoverer Server machine

Follow the instructions in Chapter 3, "Installing Oracle Discoverer 3i Viewer on multiple machines" to add a new server machine to the Discoverer system.

### 2.6.2 To Permanently Remove an Additional Discoverer Server machine

Disabling the Discoverer NT service or changing its Startup property to Manual effectively removes an Additional Discoverer Server machine from the Discoverer system. You do not have to uninstall any software. However, you must also edit the pref.txt file on the Master Discoverer Server machine to remove the Additional Discoverer Server machine's IP address from it.

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

   The pref.txt file opens in Notepad.

2. Remove the machine's IP address from the pref.txt file. Save the pref.txt file and close Notepad.

3. Choose Start | Programs | Oracle Discoverer Server 3i Setup | Apply Preferences.

4. From the Windows Start menu, choose Programs | Oracle Discoverer Server 3i Setup again and select a component on that server that you want to unregister.

   The components to select depends on the server you want to remove:

   - to remove the Master Discoverer Server machine, unregister both the Session component and the Preferences component

   - to remove Additional Discoverer Server machines, unregister the Session component

5. Repeat for each component that you want to unregister.

6. Now from the Windows Start menu, choose Settings | Control Panel and double-click the Services icon.

   The Services dialog box appears.

7. Select OracleDiscoverer3i and click the Startup button.

   The Service dialog box appears.

8. In the Startup Type section of the Service dialog box, select Manual or Disabled and click OK.

Now, the server machine will not automatically start the Discoverer NT service and therefore will not be part of the Discoverer system.

Note: To temporarily remove a server, shut down the Discoverer NT service.

## 2.7 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 the disco3iv.xml file.

Make changes as follows:

1. Open the disco3iv.xml file for editing

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

   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.8 Frequently Asked Questions

What environment variables are set?

During installation, two environment variables are set for the VisiBroker products:

VBROKER_JAVAVM = <ORACLE_806_HOME>\jre11728o\bin\jre
VBROKER_TAG = -D

The CLASSPATH variable is not modified.

The PATH variable is updated with:

PATH = <iSUITES_HOME>\bin;<ORACLE_806_HOME>\vbroker\bin;<ORACLE_806_HOME>\bin; <iSUITES_HOME>\Apache\Perl\5.00503\bin\mswin32-x86;%PATH%

This minimizes any conflict with other products.

What happens if the Locator or Preferences components stop running?

If the Locator component goes down, no more users can log in to the system until it comes back up. Existing sessions are not affected.

The Locator component is designed so that it does not need to be shut down even when you edit the pref.txt file. By default the Locator component will pick up the edited values when the next client is connected.

Similarly, if the Preferences component goes down, the Locator component will continue to function and sessions already in progress are not affected. When the Preferences component is brought back up, the Locator component will bind to the Preferences component again.

What do I need to do if I get a network error?

If Discoverer 3i Viewer receives a network exception during login, check the following:

- Are there any directories or jar files in the CLASSPATH or PATH that might interfere with Discoverer 3i? Discoverer 3i uses VisiBroker CORBA V3.4 and JDK 1.2.

- Make sure the Locator component is up and running. Did you see any error messages in the locator.log file? Make sure the locator.ior file is in the DiscWb33\applet directory.

- Make sure the VisiBroker SmartAgent and OAD are up and running and that a new session can be started.

- Make sure the Preferences component is up and running. To confirm that the Preferences component is up and running, use the Windows Task Manager and make sure that Dis33pr.exe is running.

What do I need to do when I get ORA-12154 TNS: Could not resolve service name?

This is an Oracle error that appears when the session cannot connect to the database alias specified in the Connect field. Check that the:

- database alias is in the tnsnames.ora file

- database alias exists in the tnsnames.ora file on every machine that runs sessions.

Hint: If you have SQL*Plus (or any other Oracle product) running on that machine, try connecting to the database with that product.

What do I need to do when I get a message that the Locator component cannot bind to the Preferences component?

If the Locator component cannot bind to the Preferences component, check the following:

- Is the Preferences component up and running? To see if the Preferences component is running, use the Windows Task Manager. See Section 2.2, "Using the Discoverer NT Service" to restart the Preferences component.

- Is a SmartAgent running on the subnet? To see a list of agents, OADs, and other registered components running on the subnet, open an MS-DOS window and on the command line, type `osfind`. Note that the agents are listed first. If the SmartAgent is not running, see Section 2.2, "Using the Discoverer NT Service" to restart it.

- Is the Preferences component installed? To confirm that the Preferences component is up and running, use the Windows Task Manager and make sure that Dis33pr.exe is running.

- Is the Preferences component registered with its OAD? To confirm that the Preferences component is registered, see Section 2.3.2, "To see the registered components on one machine:". This must be done on the machine on which the Preferences component was installed. If the Preferences component is not registered, see Section 2.3.5.1, "To Register the Preferences and Session components with the OAD".

- Is the machine running the Preferences component on the same subnet as the machine running the Locator component and the machines running Session components? To see a list of agents, OADs, and other registered components running on the subnet, open an MS-DOS window and on the command line, type `osfind`. Note that the agents are listed first. The Preferences component must be installed on the same subnet.

- Is the pref.txt file corrupted? You cannot directly determine from the pref.txt file that it is corrupted. To test if the pref.txt file is corrupted:

  1. Save a copy of the pref.txt file.

  2. Delete the original pref.txt file.

  3. From the Windows Start menu, select Run.

  4. In the Run window, type regedit and press [Enter].

  5. Find the registry key at
     HKEY_LOCAL_MACHINE\software\oracle\WebDisco3.3.

  6. Delete that registry key.

  7. Copy the file: "<ORACLE_806_HOME>\DISCWB33\util\defaults.txt" to "pref.txt."

  8. Choose Start | Programs | Oracle Discoverer Server 3i Setup | Apply Preferences.

  9. Run a Discoverer session.

     If the session runs correctly, the original pref.txt file was probably corrupted.

  10. Quit the session.

  11. Delete the saved copy of the original pref.txt file because it contains the corrupted elements.

  12. Reset the end user preferences by editing the new pref.txt file as described in Section 2.4, "Editing the End User Preferences".

| Copyright © 2000 Oracle Corporation. All Rights Reserved. |
|  |  | Contents