In a typical CCS integration, you deploy multiple CCS servers to maximize performance. These servers include a primary CCS server and one or more secondary CCS servers.
The first CCS server that you install is always the primary CCS server. The primary CCS server runs all the components necessary for external applications to use the CCS.
The primary CCS server includes the following components:
This web service is the Content Classification Service. External applications call this service to classify documents and retrieve classifications from the Classification Cache.
The CCS web service runs as the NetworkService account.
The policy engine applies policy to documents passed to the CCS by external applications. Policy analysis of the document determines whether it matches one of the current classification definitions. The policy engine then returns the analysis results (either a confirmed classification or a non-match) to the primary CCS server.
The central management server (CMS) stores the policy settings used by policy engines to classify documents.
The CMS includes a CA Data Protection database. By default, this database is installed on the same computer as the primary CCS server. But if you prefer, you can install the database on a remote computer.
Note: A SQL Server database engine must already be installed before you install a CCS server, either on the target computer for the CCS server or on a remote server.
The iConsole is a web-based console that enables administrators to edit the available document classifications.
The CCS preclassification agent can scan and classify documents offline. Preclassifying documents avoids the need to retrieve and analyze document content in real time.
This console enables administrators to manage CA Data Protection operations. For CCS integration, you mainly use the Administration console to manage classification service scans.
By default, these components are installed on the same host server but you can distribute them over multiple servers. For example, you may prefer to use a dedicated server for your CMS. If your organization has already deployed CA Data Protection, such a distributed deployment may suit your needs better.
Secondary CCS servers provide additional processing capacity to maximize CCS performance. Secondary CCS servers only host the CCS web service, a policy engine, and a CA Data Protection database.
After you install the primary CCS server, any subsequent CCS servers that you install are your secondary CCS servers.
All secondary CCS servers are automatically parented to the CMS that was installed on the primary CCS server.
Each secondary CCS server includes a CA Data Protection database. By default, the database is installed on the same computer as the secondary CCS server. But if you prefer, you can install the CA Data Protection database on a remote computer.
Note: A SQL Server database engine must already be installed before you install a CCS server, either on the target computer for the CCS server or on a remote server. Because the load on the database is minimal, the Express Editions of SQL Server are suitable for the CCS.
The supported versions are:
The 2008 Express Edition is included in the CCS distribution image.
Note: For SQL Server 2005, ensure that the SQL Server Browser service has started.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|