Introduction
Deploying Classification in Identity Manager
Classification Overview
Required Components
Component Workflow
Activating Classification
Configuring Classification: Taxonomies, Categories, and Rules
Install the Classification Components
Identify the Classification Service Account
Deploy the Classification Server
Deploy Classification Workers
Examining the Classification Deployment
Using the Classification Logs
Review Deployed Classification Workers
Review the Classification Service
Enable and Disable Automatic Classification on Specific Managed Hosts
Enabling Categorization on Folders (Security Index Roots)
Managing the File Types to be Classified
Restart or Upgrade Agents for Classification
Perform a Data Re-classification with PowerShell
Assign Classification Application Roles
An Overview of Classification Configuration
Steps Required to Implement Classification
Creating Taxonomies
Setting Up Manual Categorization
Implementing Rules for Automated Categorization
Working with Categorized Resources
An Overview of Rules
How Rules Affect Categorization
Writing XML Rules
Managing Rules in the Classification System
Associating Rules to Categories
Testing and Reviewing Automated Classification
Classifying Resources
When Do Categorization and Classification Occur?
Importing and Exporting Taxonomies
Working with a Taxonomy XML File
Managing the Life Cycle of Taxonomies and Categories
Advanced Rule Applications
Testing a Rule against a Resource
Testing all Rules Against a Resource
Viewing the Text from a Resource
Determining Why Categorizations Were Applied to a Resource
Viewing Categorized Resources
Making a Category Available to the Automated System
Working with the Categorization of Your Resources
Appendix A: PowerShell cmdlets
What Categories Can You Apply?
Working With Manually Categorized Resources
Working With Automatically Categorized Resources
Categorization Statistics and Views
Adding the PowerShell Snap-ins
Deploying the Classification Server and the Classification Worker
Troubleshooting Deployment
Managing Taxonomies
Appendix B: Oracle Configuration
Appendix C: Classifying Data with Data Governance Templates
Available Templates
Glossary
Rules Management
The following cmdlets in the Quest.Classification snapin can be used to manage rules. For information on using the Web Portal, see Implementing Rules for Automated Categorization.
| Use this cmdlet | If you want to... |
| Add-QXmlRule | Add a new XML rule to the system. You must know the location of the XML file. |
| Remove-QXmlRule | Remove an XML rule from the system. You must know the category ID and the rule ID. |
| Get-QXmlRule | View the properties of an XML rule in the system. You must know the rule ID. |
| Get-QXmlRules | View a list of all XML rules in the system, or get the ID of a rule. |
| Set-QXmlRule | Change the properties of an XML rule in the system. You must know the rule ID. |
Classification Analysis
The following cmdlets in the Quest.Classification snapin can be used to analyze classification and troubleshoot category and rule development. For information, see Testing and Reviewing Automated Classification.
| Use this cmdlet | If you want to... |
| Get-QClassificationAnalysis | Gain deeper understanding into a resource’s categorization. View all categories with matching rules. |
| Get-QAppliedCategories | View a list of the categories applied to a resource. |
| Get-QResourceTextExtracted | See what text is being evaluated for a resource. |
| Get-QAllRuleResults | View the results of all rules in the system when run against a test file. |
| Get-QRuleResults | View the results of a specific rule in the system when run against a test file. |
Appendix B: Oracle Configuration
Using an Oracle Database for Classification
If you are using an Oracle database, you need to create the required tablespaces before installing the Classification server. You can either run the following SQL script or manually create the tablespaces.
 |
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 create and configure the tablespaces with a script
- Connect to your SQL editor as the Sys account with the SYSDBA role and run the following script:
DEFINE topic_tbs_name = 'TopicService' DEFINE topic_tbs_file = 'topicservice_ts.dbf' DEFINE topic_user_name = 'TopicService' DEFINE topic_user_pwd = 'myPassword1' DEFINE content_tbs_name = 'ContentService' DEFINE content_tbs_file = 'contentservice_ts.dbf' DEFINE content_user_name = 'ContentService' DEFINE content_user_pwd = 'myPassword1' DEFINE temp_tbs_name = 'TEMP' --Create TopicService tablespace and User CREATE TABLESPACE &topic_tbs_name DATAFILE '&topic_tbs_file' SIZE 10M AUTOEXTEND ON NEXT 100M MAXSIZE UNLIMITED LOGGING EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO FLASHBACK ON; CREATE USER &topic_user_name IDENTIFIED BY &topic_user_pwd DEFAULT TABLESPACE &topic_tbs_name TEMPORARY TABLESPACE &temp_tbs_name QUOTA UNLIMITED ON &topic_tbs_name; GRANT CONNECT, CREATE SESSION TO &topic_user_name; GRANT CREATE TABLE, CREATE PROCEDURE, CREATE SEQUENCE, CREATE TRIGGER, CREATE ROLE TO &topic_user_name; --Create ContentService tablespace and User CREATE TABLESPACE &content_tbs_name DATAFILE '&content_tbs_file' SIZE 10M AUTOEXTEND ON NEXT 100M MAXSIZE UNLIMITED LOGGING EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO FLASHBACK ON; CREATE USER &content_user_name IDENTIFIED BY &content_user_pwd DEFAULT TABLESPACE &content_tbs_name TEMPORARY TABLESPACE &temp_tbs_name QUOTA UNLIMITED ON &content_tbs_name; GRANT CONNECT, CREATE SESSION TO &content_user_name; GRANT CREATE TABLE, CREATE PROCEDURE, CREATE SEQUENCE, CREATE TRIGGER, CREATE ROLE TO &content_user_name;
To manually create and configure the tablespaces
- Create a tablespace for the Topic Service to use.
- Create an Oracle user for the Topic Service to use that has a default tablespace of the tablespace created in step 1.
- Grant the user CONNET, CREATE SESSION, CREATE TABLE, CREATE PROCEDURE, CREATE SEQUENCE, CREATE TRIGGER, CREATE ROLE in that tablespace.
- Create a tablespace for the Content Service to use.
- Create an Oracle user for the Content Service to use that has a default tablespace of the tablespace created in step 4.
- Grant the user created in step 5 CONNECT, CREATE SESSION, CREATE TABLE, CREATE PROCEDURE, CREATE SEQUENCE, CREATE TRIGGER, CREATE ROLE in that tablespce.
When the installer creates the database, it creates a role that grants CONNECT, CREATE SESSION, SELECT, INSERT, DELETE, UPDATE and EXECUTE on the QCS objects. It will also assign the user to that role.