The Classification package obtained through the download contains all the files required to add the Classification functionality to your Quest One Identity Manager Data Governance Edition deployment.

To install Classification extension

• Run the DataGovernance_ServerComponentsInstaller_x64.msi to install the files on the Data Governance server to make it ready for a Classification deployment.
  Once the installation is complete, you need to activate Classification in Quest One Identity Manager, deploy a Classification server and Classification Workers in your environment, and enable classification on individual managed hosts.

Network communication between the Data Governance Edition agents and server and the Classification components is all performed using REST services over HTTPS channels. By default the HTTPS channels are secured using a self-signed certificate, but customers can provide their own certificate. Communication is further secured using a trusted subsystem security model. Before any Classification components can be deployed, one of the Data Governance Edition service accounts must be identified as the “Classification Identity”. When the Classification components are deployed they are configured to run as this identity. All communication related to classification will be performed using this identity.

The classification identity must be a member of the local administrators group on all agent computers where classification is to be deployed.

To identify a service account as the Classification Identity

1. In the Data Governance Navigation view, select Service accounts.
2. In the Results list, double-click the required service account.
   From the service account overview, you can view the domains associated with the selected service account.
3. From the Tasks view, select Change master data.
4. Select the Classification Identity check box, and click Save.

   This service account credentials must also be added to the local users group “Quest QCS Users” on each computer that hosts the Classification Server, Classification Workers and classification agent. This group should have been created on the initial install of each service.

If the administrator changes the classification service account for any reason, all of the deployed services will need to be changed manually to use the new classification service account. To do this, you must go to every instance of a Classification server, Worker server, or Classification agent and ensure that they are logged on using the new service account credentials.

To update the service account as the Classification Identity

1. Log on to the computer where the Classification Server is installed.
2. Open Services, locate the Quest QCS Apache and Quest QCS Tomcat x64 services, right-click and select Properties.
3. Select the Log On tab, select the Account and enter the password and click OK.
4. Log on to the computer where the Worker server is installed.
5. Open Services, locate the Quest QCS Worker and Quest QCS Rule Engine services, right-click and select Properties.
6. Select the Log On tab, select the Account and enter the password and click OK.
7. Log on to all managed hosts with classification enabled.
8. Open Services, locate the Quest One Identity Manager Data Governance Classification Agent Service, right-click and select Properties.
9. Select the Log On tab, select the Account and enter the password and click OK.

See also

The Classification Server can be installed on the same computer where the Data Governance Server is installed. However, for load balancing it is recommended to install the Data Governance and Classification Server on different computers and deploy Classification Workers as required.

The Classification server requires 500 MB of space for installation, 200 MB space for logs, plus an additional 2 GB per 1 million resources for data processing.

If you are using an Oracle database, you need to create the required tablespaces before installing the Classification server. You must also ensure that the Classification server has the ADO client for Oracle (32bit version of ODP.Net) installed. Supported versions include ODAC 11.2 Release 3 or higher. For details, see Using an Oracle Database for Classification.

To deploy the Classification Server

1. In the Navigation view, expand the Classification node, and select Configuration.
   The Classification Server address and port information will be displayed.
2. Click Deploy to add the Classification server.
   A check will be made to ensure that a service account has been identified as the classification service account.
3. Browse to the target server and click Next.
   The database requirements depend upon whether you are using a SQL or Oracle database.
4. If you are using a SQL database, select the required authentication method and associated credentials, and click Next.
5. If you are using an Oracle database, enter the Service name, the Username and Password for the Content and Topic databases, and click Next.

   To locate the Service name, run the following cmd on the Oracle DB server: lsnrctl status.

6. 
   The Classification server will now be deployed with the specified configuration.

Identity Manager includes taxonomy templates to help you to understand the classification components and process. The templates include sample taxonomies, categories, text extractors, and rules that can be used for classification. Typically, the file is located in the C:\Program Files\Quest Software\ QCS\Templates folder. If an error occurs in the server deployment, you can use the Deploy-QDefaultTaxonomies to deploy the taxonomies.

Upgrading the Classification Server

To upgrade a Classification Server

1. In the Navigation view, expand the Classification node, and select the Configuration node.
   From here you will see all the currently deployed services.
2. Click Upgrade.
3. Click Next to proceed.
4. Enter the database credentials and click Next.
5. Click Finish.

   Existing taxonomies are unaffected by a server upgrade.

   If you have a custom Classification Server deployment (created with PowerShell and non-default parameters), you will need to use PowerShell (Deploy-QClassificationServer) to upgrade the server.

To remove a Classification Server

1. In the Navigation view, expand the Classification node, and select the Configuration node.
   From here you will see all the currently deployed services.
2. Click Remove.
3. Click Yes to confirm the removal.

The Classification worker cannot be installed on a domain controller.

To add a Classification Worker

1. In the Navigation view, expand the Classification node, and select the Configuration node.
   From here you will see all the currently deployed servers.
2. Select Add Classification Worker from the Tasks view.
   You can deploy one server per computer and the computer must be in a managed domain.
3. Select the computer where you want to add the server, and click Deploy.
4. Click Close.

To remove a Classification Worker

1. In the Navigation view, expand the Classification node, and select the Configuration node.
   From here you will see all the currently deployed workers.
2. Select the required Classification Worker, and select Remove from the Tasks view.
3. Click Yes to remove the Classification Worker from the deployment.
   When you remove the worker, the rules engine for classifying data will no longer be processed on this computer.

To upgrade a Classification Worker

1. In the Navigation view, expand the Classification node, and select the Configuration node.
   From here you will see all the currently deployed workers. If a newer version is available, you will need to perform an upgrade.
2. Select the desired Classification Workers, and right-click and select Upgrade.
3. Click Yes to confirm the upgrade.
4. Click Close once the upgrade is complete.

   You can also upgrade the worker with the Deploy-QClassificationWorker cmdlet.