System Administration

This page contains the following content:

Related pages:

Define the Eclipse Application Environment

An application environment name is used for component registration in OPEN DISCOVERY Services, that is, to identify components as belonging to each OPEN DISCOVERY application (Eclipse, eCapture, and/or Allegro). By default, this is the configuration database name defined during installation of each OPEN DISCOVERY application (or the name defined during migration to version 2015.0.0 or later).

If you are an advanced administrator who will use SQL to view OPEN DISCOVERY data, you can change the Eclipse environment name(s) to make it easier to identify and/or remember when you are viewing OPEN DISCOVERY data in SQL.

To change the Eclipse application environment name:

Get started:

Consider naming conventions for environment names for all OPEN DISCOVERY applications, and/or if you have multiple instances of an application(s) installed at your site.

On your site’s Eclipse website, log in as a user who is a member of the Super Admin group.

  1. Click the Eclipse button, , and select Administration.

  2. If the System Administration pane is collapsed, click the pane title to expand it.

  3. Click Application Environment, then click the Eclipse environment name.

  4. Click .

  5. Enter the new name in the Application Environment field (128 Unicode characters maximum).

  6. Click Save. OPEN DISCOVERY will be automatically updated.

 

Microsoft SQL-Based Activities

Logging SQL Commands

If problems occur with the Eclipse database, it is possible to store SQL commands in a log file for troubleshooting purposes.

IMPORTANT! Because this log file may consume significant amounts of disk space and impact system performance, do not log SQL commands unless you have first contacted IPRO Support and they have instructed you to do so. Contact IPRO Support for more information.

To log SQL commands:

  1. Log in to Eclipse Administration as an Eclipse administrator.

  2. On the System Management ribbon, click System Administration.

  3. Select the Log SQL Commands option.

  4. If needed, change the location for the log file.

  5. Follow instructions provided by IPRO Support regarding the use of this file and the amount of time commands should be logged.

  6. After commands have begun to be logged, click  to view the file.

Changing Maximum Native File Size

To help ensure efficient operation of Eclipse, a maximum size is set for native files. If a native file exceeds this value, users must open it using the native application instead of viewing the file on the Native Viewer tab.

The default maximum file size is 12 MB; if necessary, this value can be changed in SQL. For information on changing the maximum native file size, contact IPRO Support.

Change Native File Loading Message Time

When a large native file is loaded to the Native Viewer tab (after you have selected a document for viewing and clicked the View button on the tab), a progress message displays. The default time it takes before this message displays is 1 second (1000 ms). Thus, if it takes less than 1 second for a file to load, the message will not display.

You can change the time before the message displays in SQL by entering a different value (in milliseconds). For example, entering 2000 would cause the message to display only if it takes over 2 seconds for the file to load. To make this change, contact IPRO Support.

Archive/Restore the Eclipse Database

Administrators who are proficient in SQL can archive an Eclipse database that is no longer needed or restore an archived database should it need to be brought back online. IPRO Support can also assist you with these procedures.

Items to Archive

When archiving an Eclipse database, several data locations and files need to be considered. Regarding optional items, the speed with which a database might need to be restored can help determine which optional items are archived.

  • Required:

    • SQL Case database files

    • Data Directory location (Tiff on the Fly Images)

    • Uploaded Exhibits Path (Transcripts)

    • All files on data storage - Native/Image/Produced Image

  • Optional:

    • Index Location (can be rebuilt once the database is back online)

    • Analytics index files and staging folders (can be rebuilt once the database is back online)

    • Production database SQL files (The production database stores only the staging data for the production when it was run. It is not necessary for restoring a database.)

For assistance in archiving or restoring an Eclipse database, contact IPRO Support.