Monitor the Indexed Data Set and Re-Index as Needed
As your source data changes, you need to re-index it using the same IDM Identifier to capture those changes so Secure Access will use them when scanning documents. You can automate the re-indexing process to trigger a re-index when the source data has changed. Using the indexer monitor option causes the indexer to perform an initial index, then monitor your source data for updates and re-index as necessary. This is a useful option in a dynamic environment. In monitor mode, after performing an initial index the indexer checks the source data for changes every ten minutes, and if a change is detected, re-indexes the data.
You can run the indexer in monitor mode as a background process to automatically rerun the DLP indexer periodically to update your source data to Secure Access.
Use the following command to start the indexer in monitor mode:
java -jar <directory-path>\dlp-indexer.jar -i "<directory_paths or file-names separated by commas>" -u <IDM-id> -k <_authKey _> -s <authSecret> -y -m
Where:
-
<directory-path>\dlp-indexer.jar — the relative path to the location of the DLP indexer.
-
<directory_paths or file-names separated by commas>—the relative path to the directory containing your data, or a comma-separated list of files or directories.
-
<IDM_id>—the ID of the IDM Identifier retrievable from Secure Access UI. (See Step 6.)
-
<authKey>— the API Key previously saved at Step 7d of Create an Indexed Document Match Identifier.
-
<authSecret>— the API Secret previously saved at Step 7d of Create an Indexed Document Match Identifier.
-
The -y argument causes the indexer to automatically overwrite an existing index.
When you run the indexer to re-index an existing IDM, it prompts for a yes/no confirmation before overwriting that IDM. Using the -y argument allows you to run the indexer without manually responding to the prompt.
-
The -m argument causes the indexer to operate in monitor mode.