IBM Content Analytics with Enterprise Search, Version 3.0.0 Operating systems: Windows

Mapping collection data to CIFS drives

On Windows, you can configure the system to use Common Internet File System (CIFS) network drives to store collection data.

To divide collection data among multiple locations, you can create an environment variable for IBM® Content Analytics with Enterprise Search and map the shared CIFS network drives that you want to use.

Ensure that the administrator ID can access the network drives. The network drives must be accessible even when the administrator is not interactively logged in.
The number of available mapped drives that you configure is limited by your operating system.
The mapped drive letter should not already exist. That is, do not use a drive letter that is already used by a physical device, such a high-density drive or CD-ROM drive.
The drives that you map are not displayed when the administrator is logged in.
The Universal Naming Convention (UNC) path cannot end with a backward slash (\) character.
For some CIFS drives, depending on which version of Windows, a CIFS server, or a Network Attached Storage (NAS) product is installed, you cannot map collection data to CIFS drives.

To map CIFS network drives for storing collection data, do the following steps after you install IBM Content Analytics with Enterprise Search. In a multiple server configuration, repeat these steps on all servers.

Create the following system environment variable:
ES_MAP_DRIVE=drive_letter:UNC_path [;drive_letter:UNC_path ...]

Where:
drive_letter

Specifies the network drive letter to be mapped.

UNC_path

Specifies the path to be used for storing collection data, such as \\ExampleCo\directory1.

To map multiple network drives, type a semicolon (;) followed by the additional drive letter and UNC path statements. The following example shows two directory paths mapped to two drive letters:

ES_MAP_DRIVE=T:\\ExampleCo1\esdata;U:\\ExampleCo2\esdata
Restart the computer.
Specify the directory in which to store the collection data on the mapped drives.
1. Create a collection and click Advanced options.
2. For the Location for collection data option, select Custom Location and enter the path to the directory in which to store the collection data. For example, if you defined the variable ES_MAP_DRIVE=T:\\ExampleCo1\esdata;U:\\ExampleCo2\esdata and specified the custom location as T:\\myCollectionData, then IBM Content Analytics with Enterprise Search will store the collection data in the \\ExampleCo1\esdata\myCollectionData directory.

Examples:

Correct: Different servers map to different physical locations: Controller server: ES_MAP_DRIVE=T:\\server1\dir1
Search server: ES_MAP_DRIVE=T:\\server1\dir2
Correct: Different servers map to the same top-level path but different subdirectories: Controller server: ES_MAP_DRIVE=T:\\server1\dir1\esdata1
Search server: ES_MAP_DRIVE=T:\\server1\dir1\esdata2
Correct: Different servers map to the same physical location: Controller server: ES_MAP_DRIVE=T:\\server1\dir1
Search server: ES_MAP_DRIVE=T:\\server1\dir1
Incorrect: Different servers share the same physical path: Controller server: ES_MAP_DRIVE=T:\\server1\dir1
Search server: ES_MAP_DRIVE=T:\\server1\dir1\dir2

Feedback