Chat now with support
Chat with Support

Classification Module 6.1.3 - User Guide

Introduction Deploying Classification in Identity Manager Configuring Classification: Taxonomies, Categories, and Rules
An Overview of Classification Configuration Steps Required to Implement Classification Creating Taxonomies Implementing Rules for Automated Categorization Classifying Resources When Do Categorization and Classification Occur? Managing the Life Cycle of Taxonomies and Categories
Working with Categorized Resources Appendix A: PowerShell Commands Appendix B: Oracle Configuration Appendix C: Classifying Data with Data Governance Templates Appendix D: Creating a Taxonomy to Classify Data

Required Ports

Data Governance Server and Agent
Port Direction Description
8721 Incoming HTTP protocol. Communication with Data Governance agents.
8722 Incoming TCP protocol. Communication with PowerShell and Quest One Identity Manager clients and web server.
8723 Incoming HTTP protocol and REST services. Communication with PowerShell and Quest One Identity Manager clients and web server.
18530 - 18630 Incoming TCP protocol. Communication with Data Governance agents. (Each agent on the same server uses a dynamic port within the range.)
18529 Incoming HTTP protocol. Agents only. Communication with the Classification Server for processing classification content.
Classification Server
Port Direction Description
8725 Incoming Apache
HTTPS protocol, REST services. Classification services that supplies classification functionality to all Data Governance required components.
8726 Incoming Message Queue
8727 Incoming Message Queue Management
8728 Incoming Tomcat
Classification Worker
Port Direction Description
8730 Incoming Worker WCF Host

HTTPS protocol, REST services. Communication with Worker services.
8729 Incoming RuleEngine WCF Host

HTTPS protocol, REST services. Communication with Classification Worker services.

Performance Calculations

The following performance counters can help you to understand how Classification is affecting your system’s performance.

Content Provider
COunter Description
# assets / sec Number of resource callback requests to the Data Governance agent for content per second.
KB of binary
content in / sec 		Rate of binary content flowing into the agent for processing into plain text.
KB of binary
content out / sec		 Rate of plain text content flowing out of the agent to the rules engine.
File Handler
COunter Description
# assets / sec Rate at which files are queued in the classification system to be processed by the rules engine.
Rule Engine
COunter Description
# assets / sec Number of resources being processed by the rule engine.
# matches Total number of rules that matched. Note: This does not mean that a resource was classified.
entity extractor bytes / second Rate at which the plain text extracted from the resource is being processed.
KB plain text
process / sec		 Rate at which plain text content is examined for rule matches.
rules processed / sec Rate at which rules are run against plain text content.
Rule Engine Extractors
COunter Description
Average processing time Average time it takes for one text extractor to process one resource.
Rule Engine Rules
COunter Description
Average processing time Average time it takes for one rule to process one resource.

Adjusting CPU Throttling Levels

Extracting text for the purpose of categorization and classification may cause strain on the agent computer’s CPU. To ensure the classification process does not disrupt any other services running on your computer, you can enable CPU throttling. The optimal value depends upon the other services that are running on the agent computer and how much CPU capacity you want dedicated to the classification process. If the value is set to, for example, 75, the classification agent (the Quest.Titan.Classification.Service process) will not respond to requests from the classification server if the process uses more than 75% of CPU. Setting this value too low will limit the classification process.

To set the throttling value

  1. On the agent computer create the "contentRequester" registry key in [HKEY_LOCAL_MACHINE\SOFTWARE\Quest Software\Broadway\Agent\Services\].
  2. Create "cpuUsageThreshold" DWORD value.
  3. Set the desired throttling value (for example, 75).
  4. Restart the Data Governance service.

To disable the throttling, set the value to 0.

Deploying Classification in Identity Manager

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating