This technote contains information about IBM eDiscovery Manager Version 2.2 Fix Pack 2 that was not available when the help system was incorporated into the product and when the product information was published in the IBM Archive and eDiscovery Solution Information Center on ibm.com.
The information in this technote is a supplement to the following product information:
- Additional product information for IBM eDiscovery Manager Version 2.2 Fix Pack 1
- Additional product information for IBM eDiscovery Manager Version 2.2
- Documentation updates for IBM eDiscovery Manager Version 2.2
- IBM Archive and eDiscovery Solution Information Center
These release notes include additional and updated information about:
- Upgrade and installation of eDiscovery Manager
- 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 2 only on systems that are already running version 2.2. Version 2.2 of eDiscovery Manager is a prerequisite for version 2.2 Fix Pack 2.
1.2 Before you upgrade to eDiscovery Manager Version 2.2 Fix Pack 2
Before you upgrade to eDiscovery Manager Version 2.2 Fix Pack 2:
- Verify that your system meets the minimum hardware and software requirements that are listed in System requirements for IBM eDiscovery Manager Version 2.2 Fix Pack 2.
- Temporarily disable the following features, if relevant:
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.
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:
See the instructions in the Before upgrading eDiscovery Manager (Content Manager EE) information center topic. You can ignore step 8.
See the instructions in the Before upgrading eDiscovery Manager (FileNet P8) information center topic. You can ignore step 6.
1.3 Security update for Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package now installed automatically
Beginning in version 2.2 Fix Pack 2, eDiscovery Manager installs the security update for Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package. You no longer need to download and install this update.
2.1 Supported migration path from IBM eMail Search
If you are migrating from IBM eMail Search, you must:
- Install eDiscovery Manager Version 2.1.
- Migrate from IBM eMail Search.
- Upgrade to eDiscovery Manager Version 2.1.1.
- Upgrade to eDiscovery Manager Version 2.2.
- Upgrade to eDiscovery Manager Version 2.2 Fix Pack 2.
3.1 Attachment file handling for email that is exported with the Native export format
This section is specific to email that was archived by IBM Content Collector to the compound data model.
When eDiscovery Manager exports email by using the Native export format, attachments are exported as part of the email itself. (For example, each MSG file contains both a Microsoft Exchange email and any attachments to that email.) Additionally, attachments are exported separately and placed in an Attachments subdirectory of the export directory.
Microsoft Exchange and SMTP email: If you do not need attachments to be stored separately, you can configure eDiscovery Manager to remove the Attachments subdirectory when the export completes. Do this by enabling the LotusBatchComplete plug-in for the Native export format on the Export Formats pane of the Administration page.
Lotus Notes email: When you installed eDiscovery Manager, if you indicated that you have an archive that contains Lotus Notes email, the installation program automatically enabled the LotusBatchComplete plug-in for the Native export format. For this reason, the Attachments subdirectory is always removed when the export of Lotus Notes email completes.
3.2 Database tuning to improve performance when loading audit reports (FileNet P8)
To improve the speed at which audit reports are displayed on the Audit Reports page, create the following index:
Create index I_OCID_ID on docversion (object_class_id, object_id);
3.3 Limitation no longer applies for collections and search templates that contain parent object classes
This information is relevant only for sites that have FileNet P8 object classes that are hierarchical.
Beginning in this release, if you create a collection for a parent object class, do not add any child object classes of the parent to that collection. You can create separate collections for the child object classes, but you should not put parent and child object classes in the same collection. Additionally, you can no longer associate parent and child collections with the same search template. The search template associated with a parent collection must be different than the search template associated with a child collection. (Note that existing search templates that are associated with both a parent collection and one or more child collections will continue to work.)
When users search a parent collection, eDiscovery Manager returns items from both the parent object class and any child object classes. If you defined a collection for a child object class, child class metadata is returned with the child items. If you did not define a collection for a child class, parent class metadata is returned with the child item.
If you have collections that include both parent and child object classes, do the following for each collection:
1. Modify all search templates that are associated with the collection to remove all search fields, combined fields, and grouped fields that map to content repository properties of the child object classes.
2. Modify the collection to remove all child object classes and remove all search mappings for content repository properties of the child object classes.
3. For each child object class that you want users to be able to search separately from its parent object class, create a collection.
4. Associate child collections with different search templates than their parent collections are associated with.
4. Using eDiscovery Manager
4.1 Invisible control characters are ignored during exports
When a user exports content to the EDRM, HTML, or PDF export format, eDiscovery Manager ignores a small set of invisible control characters because the intermediate XML transform does not support them. Ignoring these characters does not affect the visible content of a document; the control characters cannot be displayed. The text of the document is preserved unaltered.
5.1 Installation completed with errors: Cannot open or remove a file containing a running program
The eDiscovery Manager installation completed with errors and the installation log file showed that a file was still in use.
The Installation Complete window of the eDiscovery Manager installation program reports that the installation completed with errors, for example:
The installation completed with errors.
To get more detailed information, see the eDiscovery Manager installation log files.
eDiscovery Manager installation log files:
The installation log file contains one or more entries like this:
Install File: /opt/IBM/eDM/lib/libcsnimexport.a
Additional Notes: ERROR - ZeroGme: /opt/IBM/eDM/lib/libcsnimexport.a (Cannot open or remove a file containing a running program.)
The libcsnimexport.a file was still in use and could not be overwritten.
Resolving the problem
To resolve this problem:
- Stop the eDiscovery Manager server, if it is running.
- Stop any processes called dominoExport.
- Reinstall eDiscovery Manager.
Updates to the product information
To view updates to the eDiscovery Manager product information, see Documentation updates for IBM eDiscovery Manager Version 2.2.
|Section 3.3||November 2011||Added note regarding existing search templates|
|Section 3.3||September 2011||Added section 3.3, "Limitation no longer applies for collections and search templates that contain parent object classes"|