Before you can use a content agent, you must create an index of digital fingerprints for all files protected by the agent. Until an index has been built and the content agent has been published, the agent cannot be used in user policy. That is, any content agent trigger that uses an unpublished agent will be unable to detect fingerprinted files.
If you change or extend the files protected by a specific content agent, you must rebuild the index and republish the agent. If you have made substantial changes to the files protected by a content agent, we recommend that you purge the index to remove all digital fingerprints and then rebuild it.
To build a content index
After adding the files that you want a content agent to protect, you must build an index of these files.
This launches a scanning job. If you need to cancel the job, click the
Stop Build button.
When the build process is complete, you must publish the associated content agent.
To rebuild a content index
You need to rebuild an index if the list of files protected by a specific content agent changes. If you build an index again, it contains the fingerprints for original list of protected files plus the fingerprints any new or modified files. This means that the rebuilt index may contain fingerprints for both new and old versions of the same file. To eliminate multiple versions of the same file from the index, you must purge and rebuild the index.
The rebuild procedure is the same as when you build an index for the first time:
When the build process is complete, the index contains the original list of protected files plus any new or modified files.
You must now publish the updated content agent.
To purge a content index
You now need to rebuild the index.
| Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |