Untitled

Oracle8 ConText Cartridge Workbench

Release Notes

Release 2.3.6.0.0

December 1997

__________________________________________

Primary Authors: D. Yitzik Brenman, Graham R. Hoare

Contributors: Franco Cravero, Dave Allewell, John Barry, Roy Clarke

This software/documentation contains proprietary information of Oracle Corporation; it is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited.

If this software/documentation is delivered to a U.S. Government Agency of the Department of Defense, then it is delivered with Restricted Rights and the following legend is applicable:

RESTRICTED RIGHTS LEGEND:

Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, Rights in Technical Data and Computer Software (October 1988).

If this software/documentation is delivered to a U.S. Government Agency not within the Department of Defense, then it is delivered with "Restricted Rights," as defined in FAR 52.227-14, Rights in Data - General, including Alternate III (June 1987).

Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065

The information in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error free.

Oracle, SQL*Loader, Net8, SQL*Plus, and ConText are registered trademarks of Oracle Corporation. Oracle8, PL/SQL, and Gist are trademarks of Oracle Corporation.

All other trade names referenced are the service mark, trademark, or registered trademark of the respective manufacturer.

_______________________________________________

These Release Notes include updated information and known restrictions to the Oracle8 ConText Cartridge Workbench, Release 2.3.6.0.0.

TABLE OF CONTENTS

1. New Features

1.1 Configuration Manager

1.2 Viewer Plugin

1.3 Viewer Cartridge

1.4 I/O Utility

1.5 TextServer3 Dictionary Migration Tool

2. Installation Issues

2.1 Disk Space Requirements

2.2 Level of Browser Support for the Browser Plugin

2.3 Registering the Viewer Control

3. Upgrade Issues

3.1 Upgrading ConText Workbench

4. Setup Issues

4.1 Pre-setup Requirements for the Configuration Manager and Viewer Cartridge

4.2 Setting Up the Configuration Manager

4.2.1 Oracle8 ConText Cartridge Configuration Manager dialog box

4.2.2 Remote Web Application Server dialog box

4.2.3 Information dialog box

4.2.4 Copy Files From Setup Machine to WAS Machine

4.3 Setting Up the Viewer Cartridge

4.3.1 Oracle8 ConText Cartridge Configuration Manager dialog box

4.3.2 Remote Web Application Server dialog box

4.3.3 Information dialog box

4.3.4 Copy Files From Setup Machine to WAS Machine

4.4 Post-setup Tasks

4.4.1 Restart Oracle Web Application Server (or Oracle Web Server)

4.5 Setup Failure

4.6 Manual Installation and Configuration Following Setup Failure

4.6.1 Manual Installation of Database packages for the Configuration Manager

4.6.2 Manual Congfiguration and Deconfiguraiont of the Configuration Manager

4.6.3 Manual Congfiguration and Deconfiguraiont of the Viewer Cartridge

5. Usage Issues

5.1 Enabling User Login for System Administration Tool

5.2 Identifying Databases for System Administration Tool

5.3 Setting Up the Oracle Forms Sample Application (CTXQUERY)

5.4 Installing the Batch Jobs Queue

5.5 Removing Requests from the Batch Jobs Queue

6. Known Problems

6.1 Out-of-date Status May Cause Errors in the System Administration Tool Page

6.2 Embedded Graphics Not Supported in Viewer

6.3 Netscape Navigator Refresh Problem

6.4 Viewer Cartridge and Oracle Web Server v2.1

6.5 Configuration Manager and Oracle8 Databases on UNIX Platforms

7. Bugs Fixed In This Release

1. New Features

1.1 Configuration Manager

The Configuration Manager is a Web application for administering ConText and managing the text objects in the ConText data dictionary on non-Windows platforms, including Network Computers (NCs). It also incorporates the Template Processor, an easy-to-use tool for developing database-aware Web applications.

Note: In this release, the Configuration Manager does not support creating or maintaining thesauri. If you want to create and maintain thesauri, use the System Administration tool (Windows NT and Windows 95 only) provided with the ConText Workbench.

An HTML-based help system is delivered with the Configuration Manager. The Configuration Manager uses ConText to index the help system, providing full text indexing that enable you to search the help system.

Only one installation of the Configuration Manager is required per database; each installation runs under the CTXSYS user.

Note: The Configuration Manager is not automatically set up during installation. To use the Configuration Manager, you must first perform the tasks outlined in "4.2 Setting Up the Configuration Manager" in this document.

For more information about using the Configuration Manager, see the Oracle8 ConText Cartridge Workbench User's Guide.

1.2 Viewer Plugin

The client-side Viewer Plugin (Windows NT and Windows 95 only) uses the Viewer Cartridge to provide WYSIWYG viewing of MS Word (version 2, 6) and WordPerfect (version 5.x, 6.x) documents in a Web browser. All other formats supported by ConText are displayed as plain (ASCII) text. The Viewer Plugin also supports query term highlighting for displayed documents.

The Viewer Plugin actually consists of a set of libraries which must be installed on each client machine from which you want to view documents using the Viewer Plugin.

In addition, because the View Data form in the Configuration Manager uses the Viewer Plugin to view hits from the query hitlist, the Viewer Plugin must be installed on each client machine from which you want to view documents queried in the Configuration Manager.

1.3 Viewer Cartridge

The Viewer Cartridge pacakges data for the Viewer Plugin; it generates the highlight information for a document, fetches the document from the ConText database, and then sends the document as a file (Mime-type "application/x-ctxv") to the Web browser, which uses the Viewer Plugin (if available) to display the document.

Alternatively, for other Mime-types, the Web browser can use its own mapping to invoke a helper application or plugin which can display the ConText-indexed documents. In such cases, Viewer Cartridge does not need the Viewer Plugin as long as suitable URLs have been built.

While the Viewer Plugin must be installed on each client machine, only one installation of the Configuration Manager is required per database; each installation runs under the CTXSYS user.

Note: The Viewer Cartridge is not automatically set up during installation. To use the Viewer Cartridge, you must first perform the tasks outlined in "4.3 Setting Up the Viewer Cartridge" in this document.

For more information about using the Viewer Cartridge, see the Oracle8 ConText Cartridge Workbench User's Guide.

1.4 I/O Utility

An I/O command-line utility is provided with ConText Workbench to allow text loading from client files in a 32-bit Windows environment (Windows NT or Windows 95) to database tables, and vice versa.

The I/O Utility is a stand-alone executable that performs the following operations:

- write data from a (possibly RAW) database field to an operating system file

- read data from an operating system file and update a (possibly RAW) database field

- execute any piece of SQL or PL/SQL that can be executed in an anonymous PL/SQL block

- spawn an operating system command

- load comma-delimited data into the database

- load directory hierarchies into the database

- filter any ASCII text file before loading into database

These operations are carried out in sequence as defined by a parameter file.

For more information about parameter files and the I/O Utility, see the Oracle8 ConText Cartridge Workbench User's Guide.

1.5 TextServer3 Dictionary Migration Tool

The TextServer3 Dictionary Migration Tool is provided to assist with migrating from TextServer3 to ConText. It is not a complete migration tool, but it does allow you to:

- create a policy in ConText for each indexable column of a TextServer3 table

- migrate thesauri and synonym rings from TextServer3 to ConText

- create a section group in ConText for each section group in TextServer3

The tool is delivered as a PL/SQL package called CTXWMG_MIGRATE. The package must be installed on the same database as ConText. The package contains six procedures, which generate SQL scripts that you can customize to your precise requirements:

MIGRATE generates a script for each indexable column in a TextServer3 text

table; each script is used to create a column policy in ConText.

MIGRATE_THES generates a load file containing a named TextServer3 thesaurus; plus,

optionally, any synonym rings owned by the TextServer3 user.

MIGRATE_SYN generates a load file containing a named TextServer3 synonym ring.

MIGRATE_ALL_THES generates a load file containing all TextServer3 thesauri owned by

a TextServer3 user.

MIGRATE_ALL_SYNS generates a load file containing all TextServer3 synonym rings owned

by a TextServer3 user.

MIGRATE_SG generates a load file containing a script for creating a section group.

The TextServer3 Dictionary Migration tool is installable from an icon that is created when the ConText Workbench is installed.

For more information about installing and using the TextServer3 Dictionary Migration Tool, see the Oracle8 ConText Cartridge Workbench User's Guide.

2. Installation Issues

2.1 Disk Space Requirements

The disk space requirement for installing the ConText Workbench components is approximately 10 Megabytes.

Note: These 10 Megabytes do not include the disk space required for Oracle Forms, which is needed only for using the sample application and must be installed separately. Nor does it include the disk space required by the Oracle product dependencies.

2.2 Level of Browser Support for the Viewer Plugin

For Release 2.3.6, the Viewer Plugin is supported on Netscape Browser, Version 2 and upwards, on Windows NT and Windows 95.

2.3 Registering the Viewer Control

The Viewer Control should normally be automatically registered for use during installation. If, for some reason, the viewer is not registered, it can be registered manually using the REGSVR32.EXE utility.

For example:

ORACLE_HOME\bin\regsvr32 ctxv32.ocx

Note: The viewer is not unregistered during deinstallation. You must manually unregister it using REGSVR32.EXE before deinstallation.

For example:

ORACLE_HOME\bin\regsvr32 /u ctxv32.ocx

3. Upgrade Issues

3.1 Upgrading ConText Workbench

Upgrading the ConText Workbench is not necessary. When you install the ConText Workbench, the Installer automatically overwrites any previous installations.

For example, the ConText client, Release 1.1, consisted of the System Administration tool and the Oracle Forms sample application. If these Release 1.1 components exist in your current installation, they are overwritten with the equivalent ConText Workbench, Release 2.3.6, components during installation.

Note: To use the System Administration tool and sample application with ConText, Release 2.3.6, you must install the ConText Workbench, Release 2.3.6; the System Administration tool and sample application from previous releases of ConText will not work with Release 2.3.6.

However, the System Administration tool in Release 2.3.6 will work with all previous 2.x releases of the ConText.

4. Setup Issues

Installation of Oracle8 ConText Cartridge Workbench is automatic. However, the Installer does not automatically set up the Configuration Manager and the Viewer Cartridge. Instead, it creates two icons which can be used later to set up these components.

Note: Setup does not need to be performed for each client that uses the Configuration Manager or Viewer Cartridge; setup of both the Configuration Manager and Viewer Cartridge only needs to be performed once for each Oracle8 installation.

4.1 Pre-setup Requirements for the Configuration Manager and Viewer Cartridge

Before setting up the Configuration Manager or Viewer Cartridge, the following conditions must be met:

- Oracle8 must be installed and a database instance started

- Oracle8 ConText Cartridge must be installed and at least one ConText server started

- Oracle Web Application Server 3.0 (or Oracle Web Server 2.1), hereafter referred to as 'WAS', must be installed, and at least one runtime listener and one admin listener started

- If the Oracle8 database is installed on a different machine than the machine from which you are performing Configuration Manager or Viewer Cartridge setup, you must create a Net8 alias on the setup machine for the Oracle8 database on the other machine

- If WAS and Oracle8 are installed on different machines, you must create a Net8 alias on the WAS machine for the Oracle8 database on the other machine

4.2 Setting Up the Configuration Manager

Setting up the Congfiguration Manager requires:

- configuring WAS for the Configuration Manager (performed by Installer)

- creating database packages in the Oracle8 database (performed by Installer)

- copying files from the setup machine to the machine on which WAS is installed (performed either by the Installer or the user)

To set up the Configuration Manager, click the Configuration Manager Setup icon in the ConText program group (created by the Oracle Installer during ConText Workbench installation). The Oracle8 ConText Cartridge Configuration Manager Setup dialog box appears.

4.2.1 Oracle8 ConText Cartridge Configuration Manager Setup dialog box

Use this dialog box to provide configuration and database connection information for WAS and Oracle8.

In the Web Application Server section of the dialog box, enter the following information:

1) Machine name - Enter the name of the machine on which WAS is installed. By default, the name of the current machine appears.

If WAS is installed on the same machine from which you are performing Configuration Manager setup, use the default. This is considered a low-cost, 'local' setup.

Otherwise, enter the full host name, including the domain, of the 'remote' machine on which WAS is installed.

2) Admin port - Enter the port number of the admin listener for WAS. The default ('8888') is the default admin listener port for Oracle Web Application Server 3.0.

3) Admin user/password - Enter the username and password for the admin listener. The default username ('admin') is the default for Oracle Web Application Server 3.0.

4) Listener name : port - Enter the name and port of the runtime listener for WAS. The defaults ('www' and '80' ) are the default runtime listener name and port for Oracle Web Application Server 3.0 on NT.

Other runtime listener name defaults include:

Version Listener name

Web Server 2.1 on Unix weblsn

Web Server 2.1 on NT websvr

Note: If you have any doubts about the information required for this section, consult your WAS administrator.

In the Database Configuration section of the dialog box, enter the following information

1) User/Password - Enter the username and password for the owner of the Configuration Manager installation. In general, the owner is the CTXSYS user.

2) Password Type - In general, select the 'Database' option. If in doubt, consult your Database Administrator.

3) Database Connection - Select the 'Local' option if WAS and Oracle8 are installed on the same machine. If you select 'Local', you must also supply a database instance name (Oracle SID) in the Instance field.

Select the 'Remote' option if WAS and Oracle8 are installed on separate machines. If so, you must also supply a Net8 alias in the Alias field. Note that the alias is between the machines on which WAS and Oracle8 are installed, not the alias between the setup machine and the Oracle8 machine.

4) NLS_LANG - Enter the NLS_LANG value for Oracle8. This value is used by WAS to determine the character set used between WAS and Oracle8.

Click [OK] to continue setup of the Configuration Manager or click [Cancel] to cancel setup. If you click [OK], the Remote Web Application Server dialog box appears.

4.2.2 Remote Web Application Server dialog box

Use this dialog box to enter information about the remote machine on which WAS is installed. In addition, use this dialog box to enter database connection information between the setup machine and the Oracle8 machine.

Note: This dialog box does not appear if the machine from which the Configuration Manager setup is being performed is the same machine on which both WAS and Oracle8 are installed.

Enter the following information in this dialog box:

1) Use the radio buttons to specify the operating system for the machine on which WAS is installed. Note that the 'Other' option should not be selected because WAS is currently only available on Windows NT and UNIX platforms.

2) Some files must be copied to the machine on which WAS is installed. Use the radio buttons to select whether the files are copied automatically by the Installer or manually by the user.

The files can be copied automatically only if:

- the machine from which the Configuration Manager setup is performed is the same as the machine on which WAS is installed

- the WAS Oracle Home directory is mounted to the machine from which the Configuration Manager setup is being performed

Otherwise, the files must be copied manually by the user. If the files must be copied manually, note the directory which contains the files to be copied and the directory to which they must be copied.

3) Enter the Net8 alias between the machine from which Configuration Manager setup is being performed and the machine on which Oracle8 is installed. Note that this alias is not the alias between the WAS and Oracle8 machines.

Click [OK] to continue the setup of the Configuration Manger or click [Cancel] to cancel the setup. If you click [OK], an information box appears.

4.2.3 Information dialog box

This dialog box reminds you about the username/password combination used as security when accessing the Configuration Manager. If you need to change the password, or increase security, consult your Web Application Server administrator before continuing.

Click [OK] to continue the setup of the Configuration Manger or click [Cancel] to cancel the setup. If you click [OK], a dialog box appears to display the progress of the setup.

4.2.4 Copying Files From Setup Machine to WAS Machine

After the Installer completes the setup, if necessary, copy the required Configuration Manager files from the setup machine to the machine on which WAS is installed.

Note: If WAS is installed on a UNIX platform, ensure that the file names are all-lowercase when copied to the WAS machine.

Once setup is complete and the necessary files have been copied to the WAS machine, you can start the Configuration Manager by clicking on the new Configuration Manager icon created by the Installer in the ConText program group.

4.3 Setting Up the Viewer Cartridge

Setting up the Viewer Cartridge requires:

- configuring WAS for the Viewer Cartridge (performed by Installer)

- copying files from the setup machine to the machine on which WAS is installed (performed either by the Installer or the user)

Note: Because the View Data form of the Configuration Manager uses the Viewer Cartridge to display documents, if you want to view documents that you query in the Configuration Manager, you must set up the Viewer Cartridge along with the Configuration Manager.

To set up the Viewer Cartridge, click the Viewer Cartridge Setup icon in the ConText program group (created by the Oracle Installer during ConText Workbench installation). The Oracle8 ConText Cartridge Viewer Cartridge Setup dialog box appears.

4.3.1 Oracle8 ConText Cartridge Viewer Cartridge Setup dialog box

Use this dialog box to provide configuration and database connection information for WAS and Oracle8.

In the Web Application Server section of the dialog box, enter the following information:

1) Machine name - Enter the name of the machine on which WAS is installed. By default, the name of the current machine appears.

If WAS is installed on the same machine from which you are performing Viewer Cartridge setup, use the default. This is considered a low-cost, 'local' setup.

Otherwise, enter the full host name, including the domain, of the 'remote' machine on which WAS is installed.

2) Admin port - Enter the port number of the admin listener for WAS. The default ('8888') is the default admin listener port for Oracle Web Application Server 3.0.

3) Admin user/password - Enter the username and password for the admin listener. The default ('admin') is the default admin listener username for Oracle Web Application Server 3.0.

4) Listener name : port - Enter the name and port of the runtime listener for WAS. The defaults ('www' and '80') are the default runtime listener name and port for Oracle Web Application Server 3.0 on NT.

Other runtime listener name defaults include:

Version Listener name

Web Server 2.1 on Unix weblsn

Web Server 2.1 on NT websvr

Note: If you have any doubts about the information required for this section, consult your WAS administrator.

In the Database Configuration section of the dialog box, enter the following information

1) User/Password - Enter the username and password for the owner of the Viewer Cartridge installation. In general, the owner is the CTXSYS user.

2) Connection Alias - Enter the Net8 alias (database connection) between Oracle8 and WAS. There may be several database connections for the Viewer Cartridge. This field allows you to enter an alias for the default database connection. The combined username/password and connection information will then be used to set up the default connection for access by the URL.

The alias you give is used as the first entry in the list of connections in the configuration file located in $ORACLE_HOME/ctxw/middle/ctxvcart (UNIX-based operating system) or ORACLE_HOME\CTXW\MIDDLE\CTXVCART (Windows NT) on the WAS machine. You can add further entries (database connections) to this configuration file if you wish (see the Oracle ConText Option Workbench User's Guide).

Click [OK] to continue setup of the Viewer Cartridge or click [Cancel] to cancel setup. If you click [OK], the Remote Web Application Server dialog box appears.

4.3.2 Remote Web Application Server dialog box

Note: This dialog box does not appear if the machine from which the Viewer Cartridge setup is being performed is the same machine on which both WAS and Oracle8 are installed.

Enter the following information in this dialog box:

2) Some files must be copied to the machine on which WAS is installed. Use the radio buttons to select whether the files are copied automatically by the Installer or manually by the user.

The files can be copied automatically only if:

- the machine from which the Viewer Cartridge setup is performed is the same as the machine on which WAS is installed

- the WAS Oracle Home directory is mounted to the machine from which the Viewer Cartridge setup is performed

Otherwise, the files must be copied manually by the user. If the files must copied manually, note the directory which contains the files to be copied and the directory to which they must be copied.

3) Enter the Net8 alias between the machine from which Viewer Cartridge setup is performed and the machine on which Oracle8 is installed. Note that this alias is not the alias between the WAS and Oracle8 machines.

Click [OK] to continue the setup of the Viewer Cartridge or click [Cancel] to cancel the setup. If you click [OK], an information box appears.

4.3.3 Information dialog box

This dialog box reminds you about the username/password combination used as security when accessing the Viewer Cartridge. If you need to change the password, or increase security, consult your Web Application Server administrator before continuing.

Click [OK] to continue the setup of the Viewer Cartridge or click [Cancel] to cancel the setup. If you click [OK], a dialog box appears to display the progress of the setup.

4.3.4 Copy Files from Setup Machine to WAS Machine

After the Installer completes the setup, if necessary, copy the required Viewer Cartridge files from the setup machine to the machine on which WAS is installed.

Note: If WAS is installed on a UNIX platform, ensure that the file names are all-lowercase when copied to the WAS machine.

Once setup is complete and the necessary files have been copied to the WAS machine, you can view documents in a Web browser using the Viewer Cartridge URL with the necessary parameters (document ID, policy name, and query expression, if any).

For more information about using the Viewer Cartridge, see the Oracle8 ConText Cartridge Workbench User's Guide.

4.4 Post-setup Tasks

4.4.1. Restart Oracle Web Application Server (or Oracle Web Server)

After setup of either the Configuration Manager or Viewer Cartridge, you must restart the listeners on the Web Application Server.

4.5 Setup Failure

There are two distinct setup phases where a log file is made available in case of failure:

- installation of the components against the Web Application Server

- installation/creation of the database packages (via the I/O Utility)

In either case, a dialog box is displayed, asking 'Do you wish to view the log file?'

Click [Yes] to view the log file, [No] to continue without viewing the log file, or [Cancel] to quit the setup process.

If you choose to view the log file, every event is listed; you can then isolate the event that failed, click [OK], and then click [Yes] to retry the failed phase; or click [No] to carry on with the installation; or click [Cancel] to quit the installation. Oracle Corporation recommends you choose [Yes] to retry and check with your Oracle Support contact. If you choose [No], installation will continue, but some ConText Workbench components may not work properly.

4.6 Manual Installation and Configuration Following Setup Failure

Note: The actions described in this section are not part of the automatic setup procedures. They are of use only if the appropriate part of the setup has failed.

4.6.1 Manual Installation of Database Packages for the Configuration Manager

As part of the setup of the Configuration Manager, the Installer creates a set of database packages. If these packages cannot be created for some reason, you must create them manually.

A SQL*Plus script is provided for this purpose. It is installed with the Configuration Manager. The script only needs to be run if the normal setup of the Configuraiton Manager fails. In this case, the location of the installation files depends on whether the setup was attempted against WAS running on the local machine or a remote machine.

For more information about manually installing the database packages, see Oracle8 ConText Cartridge Workbench User's Guide.

4.6.2 Manual Configuration and Deconfiguration of WAS for the Configuration Manager

In the event that the WAS configuration portion of the Configuration Manager setup fails, manual configuration is necessary to set up Oracle WebServer 2.1 or Oracle Web Application Server 3.0 for use with the Configuration Manager.

Deconfiguration procedures can also be applied to remove the Configuration Manager from Oracle WebServer 2.1 or Oracle Web Application Server 3.0.

For more information about manually configuring and deconfiguring WAS for the Configuration Manager, see Oracle8 ConText Cartridge Workbench User's Guide.

4.6.3 Manual Configuration and Deconfiguration of WAS for the Viewer Cartridge

In the event that the WAS configuration portion of the Viewer Cartridge setup fails, manual configuration is necessary to set up Oracle WebServer 2.1 or Oracle Web Application Server 3.0 for use with the Viewer Cartridge .

Deconfiguration procedures can also be applied to remove the Viewer Cartridge from Oracle WebServer 2.1 or Oracle Web Application Server 3.0.

For more information about manually configuring and deconfiguring WAS for the Configuration Manager, see Oracle8 ConText Cartridge Workbench User's Guide.

5. Usage Issues

5.1 Enabling User Login for System Administration Tool

Before Oracle users can connect to a database from the System Administration tool, the CTXSYS Oracle user may have to connect once to the database. If this is required, the ConText System Administration tool will notify you.

Note: CTXSYS needs to connect only once per database. Once CTXSYS connects to a database for the first time, the database is enabled thereafter for all users with the appropriate privileges for the System Administration tool.

5.2 Identifying Databases for System Administration Tool

The TNSNAMES.ORA file lists all of the available databases to which an Oracle user can connect via SQL*Net. If a user wants to connect to a database that does not appear in the list of known databases in the System Administration tool, an entry for the database must be added to TNSNAMES.ORA and the System Administration tool restarted.

5.3 Setting Up the Oracle Forms Sample Application (CTXQUERY)

Before the sample forms application provided with the ConText Workbench can be used, Oracle Forms (32-bit), version 4.5.7.4.0 or higher, must be installed.

Note: If a version higher than 4.5.7.4.0 is installed, the sample application file (CTXQUERY.FMB) may need to be regenerated.

In addition to the installation of Oracle Forms, the following tasks must be performed on the server machine:

- creating the ARTICLES sample table

- populating the sample table with text

- creating a text index for the text column in the table

The scripts for performing these tasks are installed automatically during installation of ConText.

For more information about running these scripts, see Oracle8 ConText Cartridge Application Developer's Guide.

5.4 Installing the Batch Jobs Queue

The Batch Jobs queue in the System Administration tool provides a mechanism for requesting index creation and optimization in batch mode. If the Batch Jobs queue is not installed and enabled, all indexing operations must be performed in real-time and the System Administration tool blocks users from performing other actions until the indexing operation completes.

To install the Batch Jobs queue for a database, the CTXSYS user must connect to the database and use the Admin -> Install menu item once. The queue is installed and automatically enabled.

All users who connect to the database can now submit index operations in either real-time or batch mode.

Note: Installing the Batch Jobs queue creates an internal table and PL/SQL package, both owned by CTXSYS, in the ConText data dictionary.

5.5 Removing Requests from the Batch Jobs Queue

The Batch Jobs queue does not automatically remove jobs that have finished or are broken. These jobs must be manually removed from the Batch Jobs queue using the Admin -> Purge Finished/Broken Jobs menu item.

Note: Only finished and broken jobs can be removed from the queue. Failed jobs in the queue cannot be removed because the jobs may succeed when resubmitted.

6. Known Problems

6.1 Out-of-date Status May Cause Errors in the System Administration Tool

When the status of an object, such as a policy or the Services Queue, displayed in the administration tool does not reflect the actual system status, the administration tool will display an error message and exit if a user attempts to modify the object.

For example, the administration tool displays a status of NO_INDEX for a policy; however, the policy has been used to create a text index and the display has not been updated to reflect the change in status. If a user attempts to delete the policy, an error message is returned stating the policy has been used to create an index and the administration tool exits.

To ensure the display is up-to-date, use the Refresh menu item.

Note: If the status of an object changes as the System Administration tool display is refreshed, the refreshed display may not reflect the actual system status.

6.2 Embedded Graphics Not Supported in Viewer

In Release 2.3.6 of ConText Workbench, the Viewer Control and Viewer Plugin do not display graphics that are embedded in a document.

6.3 Netscape Navigator Refresh Problem

In Netscape Navigator Version 3, a document that is present in the local cache, and which has previously been displayed, is sometimes not redisplayed immediately on request. It appears that this version of Netscape Navigator does not always refresh the page, and a blank page ensues instead. For pages with forms in some cases the browser may not redisplay all the buttons.

The workaround is to toggle between the Netscape window and other windows on the desktop. Netscape Navigator then normally performs a refresh as required.

6.4 Viewer Cartridge and Oracle Web Server v2.1

When using the Viewer Cartridge against Oracle WebServer v2.1 on Solaris, the thin JDBC driver should be used. To do this edit the "[Default]" section in the ctxvcart.cfg file (located on the server machine) as follows:

- change "database=tnsalias" to "database=host:port:sid"

- add line "subprotocol=thin"

In a UNIX-based operating system, the ctxvcart.cfg file is located in $ORACLE_HOME/ctxw/middle/ctxvcart.

In Windows NT, the file is located in ORACLE_HOME\CTXW\MIDDLE\CTXCART

6.5 Configuration Manager and Oracle8 Databases on UNIX Platforms

When attempting to use the Configuration Manager to connect to an Oracle8 database running on a platform other than Windows NT, users may receive an ORA-3113 error. To resolve this issue, please contact Oracle Worldwide Support and request the patch for bug 593630.

7. Bugs Fixed in This Release

Bug No Description

420518 VIEWING THE ASCII FILES AND OCX AND TRUE VIEW

510330 CANCEL BUTTON HAS TO BE PRESSED TWICE

510342 ERROR MESSAGES WHILE DELETING SECTIONS

510351 OPTIONAL END TAG

511041 SECURITY VIOLATION WHILE CONNECTING TO THE DATABASE

511070 RUNTIME ERROR WHILE EDITING EMPTY SECTION GROUP

511123 CANCEL BUTTON NEEDS TO BE GREYED OUT AFTER DELETING A

SECTION

511163 RUNTIME ERRORS ENTERING PREFERENCES

511615 ALL OF THE OCCURRENCES OF THE SEARCH TOKEN ARE HIGHLIGHTED

AT ONCE

511830 HIGHLIGHTING IS OFF BY N BYTES IN WORDPERFECT5.X

511873 PLUGIN HIGHLIGHTING IS OFF IN HTML FILES

512209 DRG-00100: INTERNAL ERROR, ARGUMENTS : [52101],[DRXR.C],[281],[],[]

517369 ORA-6502, ORA-6512, TRYING TO VIEW THESAURUS IN GUI ADMIN TOOL

522512 NO HELP AVAILABLE FOR A NUMBER OF TOPICS IN ADMIN TOOL

525224 UNNECESSARY NOTIFICATION REGARDING INSTALLATION OF I/O UTILITY

525322 APPLICATION ERROR WHILE INSTALLING ADMIN TOOL

536569 CANNOT CREATE PREFERENCE IN OTHER USERS' SCHEMA

536591 CTXSYS CANNOT CREATE A POLICY IN ANOTHER USER'S SCHEMA:

536621 SERVER PERSONALITY DISPLAYED INCORRECTLY

536627 PREFERENCES ARE NOT ALIGNED IN CREATE POLICY PAGE

536729 INCORRECT SERVER INFORMATION DISPLAYED

536731 BOLD CHARACTERS IN HELP MENU

536736 MENU BUTTON CAUSES THE APPLICATION TO QUIT

536741 CONTENTS BUTTON DOESNT WORK

537169 NO BACKGROUND COLOR WHEN DESCRIPTION BOX IS EMPTY

541274 TITLE "MENU" LOCATED UNDER MENU ICON IS NOT WORKING (EXCEPT

WHEN YOU ARE IN HELP)

541276 TITLE "FIND" UNDER FIND ICON IN HELP IS NOT WORKING

545259 LENGTH OF START AND END TAGS

546950 HIGHLIGHTS WITH ASCII MAY BE INCORRECT IF NEXT HIGHLIGHT

FORCED

550427 NO HELP FOR SETTINGS

550432 MISSING OPEN QUOTES IN HELP

550519 STOP LIST PREFERENCE CREATED WITHOUT A NAME

550524 ADDITIONAL NULL STOP WORD IN STOPWORD PREFERENCE

550529 CM DOESNT ACCEPT MULTIPLE KEEP TAGS

550542 MISSING STARTJOINS

550572 CM DOESNT SUPPORT TEMPLATE POLICIES

551792 WHEN PLUGIN DLL IS RELEASED IT CAUSES A GPF IN MFC42.DLL

551801 THE JAVA CARTRIDGE DOES NOT EXPLICITLY DISCONNECT FROM

DATABASE

562876 RUNTIME ERROR IN ADMIN TOOL