Before you can use a content agent, you must create a content index. A content index identifies the files protected by a content agent. Each content agent has its own content index.
The index contains digital fingerprints of the files that you want the content agent to protect. These fingerprints represent unique document signatures and are made available to CA Data Protection policy engines and endpoint agents. CA Data Protection generates the index by running a scanning job to collate the digital fingerprints.
In technical terms, CA Data Protection generates the index by running a specialized FSA scanning job to collate the digital fingerprints. It then creates the index file on the FSA host server. When you publish the content agent (see the next section), the index file is replicated to CA Data Protection policy engines and endpoint agents.
Follow these steps:
A scanning job starts. To cancel the scanning job, click the Stop Build button.
When the scanning job completes, the Status field in the Content Registration Agent pane updates the number of available index files.
Copyright © 2015 CA Technologies.
All rights reserved.
|
|