Local vs. Remote File Indexing

3DSpace Index uses two types of file indexing: "local" or "remote".

Important: Local file indexing is a best practice. Not following it may lead to server instability.

This task shows you how to:

Use Local File Indexing
Use Remote File Indexing

Use Local File Indexing

Local file indexing means that the MQL/File Collaboration Server (FCS) talks directly to the conversion process.

Context: Local file indexing requires a local convert.exe process on the machine where the file is synchronized.

Run the 3DSpace Index installation with the File Converter Only option, either on the machine running the MQL process or on the different FCS servers.
For more information, see Install 3DSpace Index.
Optional: If the port selected during the "File Converter Only" installation is different from the default one (19000), change the indexport parameter in the store definition.
You can do that either on the machine running the MQL process or on the FCS server, with the following command:
```
MQL> mod store XXX indexport Index_baseport_number ;
```
Note: You can also change the indexhost parameter and override the default localhost value to specify the host value for convert activity.

Use Remote File Indexing

Remote file indexing means that MQL/FCS cannot talk directly to the convert process.

Important: The file convert process needs to be able to read from the workspace/tmpdir of the FCS directory. By default, the tmpdir is /tmp/. The Administrator can define the workspace directory by using the -D parameter for the FCS JVM options. For example:

... -D ematrix.fcs.workSpaceDir=/opt/VERSION/workspace