Additional product information for IBM eDiscovery Manager Version 2.2 Fix Pack 4

News


Abstract

This technote contains additional and updated information about IBM® eDiscovery Manager Version 2.2 Fix Pack 4.

Content

The information in this technote is a supplement to the following product information:


These release notes include additional and updated information about:

  • Upgrade and installation of eDiscovery Manager
  • Migration
  • Configuration
  • Using eDiscovery Manager

1. Upgrade and installation of eDiscovery Manager

1.1 Installation and upgrade scenarios

You can install eDiscovery Manager Version 2.2 Fix Pack 4 only on systems that are already running one of the following versions of eDiscovery Manager.


1.2 Before you upgrade to eDiscovery Manager Version 2.2 Fix Pack 4

Before you upgrade to eDiscovery Manager Version 2.2 Fix Pack 4:


The following information is specific to IBM Content Manager. If the deferred DDL execution feature of Content Manager EE is enabled, temporarily disable it. You can re-enable this feature after installing eDiscovery Manager.

The following information is specific to IBM FileNet P8. If the object store is configured to use date partitioning during content-based retrieval, temporarily disable date partitioning by using FileNet Enterprise Manager. You can re-enable this feature after installing eDiscovery Manager.

  • Perform prerequisite upgrade tasks:

The following information is specific to IBM Content Manager. See the instructions in the Before upgrading eDiscovery Manager (Content Manager EE) information center topic. You can ignore step 8.

The following information is specific to IBM FileNet P8. See the instructions in the Before upgrading eDiscovery Manager (FileNet P8) information center topic. You can ignore step 6.

  • The installation program will update the <edmhome>\config\docviewer.config file. Before you run the installation program, create a backup version of the file. After the upgrade is installed, you can modify the docviewer.config file as necessary.

1.3 After you upgrade to eDiscovery Manager Version 2.2 Fix Pack 4

When you upgrade to eDiscovery Manager Version 2.2 Fix Pack 4 from eDiscovery Manager Version 2.2, eDiscovery Manager Version 2.2 Fix Pack 1 or eDiscovery Manager Version 2.2 Fix Pack 2, your existing EmailTemplate.xsl file is backed up and a new version of the file is installed. If you modified this file in a previous release and you want to keep your changes, use the backup file as a reference and apply your changes to the new version of the file. Both the backup file and the new version of the file are in the config subdirectory of the eDiscovery Manager installation directory. The backup file is named EmailTemplate.xsl.bkup0.

1.4 Installing eDiscovery Manager Version 2.2 Fix Pack 4 to WebSphere® Application Server Version 8.0 or a new WebSphere Application server home or profile

To install eDiscovery Manager Version 2.2 Fix Pack 4 to WebSphere Application Server Version 8.0 or to a different WebSphere Application server home or profile, perform the following steps:

1. Before you install eDiscovery Manager, make sure that your preferred WebSphere Application Server meets the prerequisites and is installed.

2. Install eDiscovery Manager Version 2.2 Fix Pack 4 and select your preferred WebSphere Application Server home and profile during the installation process.

3. If you install eDM 2.2. FP4 to a different WebSphere Application server or profile from your previous eDiscovery Manager installation, complete the following steps:

    3.1 Delete the old WebSphere Application Server profile that was dedicated to eDiscovery Manager. To delete the old WebSphere Application Server profile that was dedicated to eDiscovery Manager, follow instructions in WebSphere Application Server documentation. Here're instructions for deleting profiles in WebSphere Application Server Version 7.0.

    If you do not want to delete the old profile, manually remove the eDiscovery Manager applications by using the WebSphere Administrative console. To manually remove the eDiscovery Manager applications, open the WebSphere Administrative console and go to Applications-->Application Types--->WebSphere enterprise applications, select EDMClient and EDMWorkMgrServer, then click Uninstall.
    3.2 If the HTTP transport port number is different from your previous installation, update the port number that is defined in the files <eDMHome> \shortcuts\scripts\EDMClient.bat/sh and <eDMHome> \shortcuts\scripts\EDMHelp.bat/sh
    Example: <eDMHome> \shortcuts\scripts\EDMClient.bat/.sh contains:

    START /max http://localhost:9080/EDMClient 
    If the HTTP transport port is no longer 9080, change the port to the correct value and do the same for eDMHelp.bat/.sh

    To determine the HTTP transport port number, change directory to <WASHOME> /profiles/ <profileName> /logs, edit the file named AboutThisProfile.txt, and look for the line "HTTP transport port: <port number>"

    Example: HTTP transport port: 9083


The following information is specific to IBM FileNet P8. 1.5 New indexes increase performance

Beginning in eDiscovery Manager Version 2.2 Fix Pack 4, you can create the following new indexes to improve performance for the task status/scheduled search page:

CREATE INDEX I_EDMCaseSysID ON Generic (uxx_EDMCaseSysID, create_date desc)

CREATE INDEX I_EDMScheduleID ON Generic(uxx_EDMScheduleID)

2. Migration

2.1 Supported migration path from IBM eMail Search

If you are migrating from IBM eMail Search, you must:

  1. Install eDiscovery Manager Version 2.1.
  2. Migrate from IBM eMail Search.
  3. Upgrade to eDiscovery Manager Version 2.1.1.
  4. Upgrade to eDiscovery Manager Version 2.2.
  5. Upgrade to eDiscovery Manager Version 2.2 Fix Pack 4.

3. Configuration

3.1 Configuring export for multipart documents

When you create collections for multipart documents (documents that contain multiple parts such as attachments, images, etc.), use the CUSTOM collection type.

3.2 Configuring an Universal Naming Convention (UNC) path to an export directory

You can configure a UNC path (example: \\network\folder ) in the Export directory field on the Export Setting Administration page. The following rules apply:

1. The eDiscovery Manager machine and remote machine must be on the same domain or workgroup.
2. The eDiscovery Manager server must be started by the log-on user who is visible from both machines.
3. This user has RW permission to the shared directory specified in the UNC path.
4. The UNC path may not contain the following characters: *?$~!@#%^&+

Note: An alternative to using a UNC path is to map a network drive for the export directory.

IBM WebSphere Application Server might not be able to locate mapped network drives in Microsoft® Windows under certain circumstances.

If WebSphere Application Server is set up to run as a non-service, such as from the command line, the user starting the server (or the user who started the nodeagent) must be the same user who mapped the network drive. If WebSphere Application Server is set up to run as a service, the user account used to start the service must also be the same user who mapped the network drive.

Note: an alternative to using a mapped network drive is to configure a UNC path for the export directory.

3.3 Configuring IBM eDiscovery Manager to open and save compressed attachments

By default, when you click a link to open an attachment, it is displayed in HTML. If you want to open and save attachments in their native format, you need to edit the defaultAttachConversionFormat property in the <EDM_HOME>\config directory\docviewer.config.

To edit the docviewer.config file:

  1. Open the <EDM_HOME>\config directory\docviewer.config file.
  2. Search for defaultAttachConversionFormat=0
  3. Change defaultAttachConversionFormat=0 to defaultAttachConversionFormat=1 and save the file.
  4. Restart the eDiscovery Manager application server. Document attachments can now be viewed and saved in their native format.

3.4 Customizing the client task refresh interval

To disable or change the time interval between automatic refreshes of task information within the client user interface, add the following property to the ral.properties file:

taskPollingInterval=n

Where n is the number of seconds that the client will wait between the end of one task refresh action and the beginning of the next. The number must be an integer between 20 and 99999, or 0. Specify 0 to disable the task refresh. Specifying no value, or a value from 1-19, causes a default of 20 seconds to be used. The default value of 20 seconds is also used if an invalid value such as "1000000" or "Daisy" is entered.

Task information is displayed on the task pages within the client user interface, and on the bar above the main application area of the client.

4. Using eDiscovery Manager

4.1 Directory naming convention for exported IBM Connections multipart documents

All parts of exported IBM Connections multipart documents are stored in the baseName_uid directory, where baseName is the name of the base part (the first part) of the document with file extension omitted and uid is the document's unique identifier. If the baseName contains special characters such as \ / : * ? " < > |, then the name of the directory contains an underscore ( _ ) in place of the characters. For example, if the baseName is "Delete: scrum", the export directory created will be named "Delete_ scrum".

4.2 Support for parametric queries on fields of type integer

Beginning with eDiscovery Manager Version 2.2 Fix Pack 4, you can search across a range of values in integer fields.

The following examples show how queries can be constructed.


TIEFLAG:

10000

TIEFLAG:

=10000

TIEFLAG:

<10000

TIEFLAG:

<>10000

TIEFLAG:

>=10000 AND <=20000

TIEFLAG:

>=10000 AND <=20000 OR =15000

TIEFLAG:

!=5000 AND (>20000 OR <10000) AND !=25000


Syntax:
relational_operator integer [ boolean_operator relational_operator integer] [ boolean_operator relational_operator integer] ...

Where:
  • relational_operator can be >, <, >=, <=, =, != or <>
  • boolean_operator can either be AND or OR


The implicit order of operator precedence is AND, followed by OR. Parentheses may be used to override the implicit order.

4.3 Exporting IBM Connections documents to HTML can consume a large amount of disk space

The HTML export of IBM Connections documents can use substantially more disk space than a regular (native) export.

The HTML export of IBM Connections documents uses more disk space because style sheets are copied for each exported document. You will need substantially more disk space for HTML exports.

Change history

History Date Change
Released

Rate this page:

(0 users)Average rating

Document information


More support for:

eDiscovery Manager

Software version:

2.2.0.4

Operating system(s):

AIX, Windows 2003 server, Windows 2008 server

Reference #:

1584541

Modified date:

2013-02-11

Translate my page

Machine Translation

Content navigation