Configuring export settings

Before your users can export content, you must configure export settings.

1. On the Administration page, click Export Settings in the Navigation pane.
2. Enter the absolute path of the directory to use as the default export location.
   Note: IBM® WebSphere® Application Server might not be able to locate mapped network drives in Microsoft Windows under certain circumstances. Because of how permissions are assigned to mapped network drives, not all users are able to access these drives through the drive letters. Only the services that are owned by the Local System Account can map network drives that can be seen by all other accounts. In this case, you must configure the path of the directory that contains all exported content as a Universal Naming Convention (UNC) path.

   This path can be up to 120 characters in length; however, it is best to keep this path name as short as possible to avoid possible truncation problems. See the information center topic on Using short names for export directories, files, and tasks.

   When a user exports content, the user can specify a subdirectory that is created under this default export directory, or they can specify an absolute path to another location.

   Tip: By default, the export directory is located on the eDiscovery Manager system. (Exception: When Lotus Notes® emails are exported, the export directory is located on the Lotus® Domino® server.) If your users have restricted access to the eDiscovery Manager system, you can provide them with access to their exported content by specifying a shared network drive as the export directory. For example, if eDiscovery Manager runs on an AIX® system and your users run Windows systems, you can create a Windows NFS mount on the AIX system for content exports.

   If you are configuring a shared drive or UNC path, see the WebSphere Application Server topic "Mapped network drives in Windows are not visible to WebSphere Application Server".

3. Enter the maximum number of simultaneous export tasks that you want eDiscovery Manager to support. Enter a number between 1 and 5. The default is 1.
   Recommendation: Be conservative when you change the value of the Maximum concurrent exports field and be sure to take the hardware configuration into account. Increasing this value places more stress on the content management system and might adversely affect archiving and indexing.
4. Enter the maximum number of threads to allocate for all exports. Enter a number between 1 and 99. The default is 8.

   The value in the Maximum threads for all exports field is divided by the value in the Maximum concurrent exports field to determine the number of threads to allocate to each export.

   Note: If the value in the Maximum concurrent exports field is greater than or equal to the value in the Maximum threads for all exports field, each export task is allocated one thread.

   Recommendation: Be conservative when you change the value of the Maximum threads for all exports field and be sure to take the hardware configuration into account. Increasing this value places more stress on the content management system and might adversely affect archiving and indexing.
5. Click Apply.

   Your changes are immediately visible to you. However, your changes will take effect only after the eDiscovery Manager application server is restarted. Existing eDiscovery Manager sessions and currently running tasks continue to operate under the configuration settings that were in place when the users of those sessions logged in to the eDiscovery Manager web client.