How to improve performance with business description processing in RSA Identity Governance & Lifecycle
Originally Published: 2017-08-11
Article Number
Applies To
RSA Version/Condition: 7.0.x
Issue
Cause
- The use of wildcards versus using exact match.
- There are a large number of "soft" deleted records in table T_AV_BUSINESS_DESCRIPTION.
- Using a huge volume of Business Descriptions when they are not needed.
- Under-configured hardware.
Resolution
- Change any wildcard matches to do an exact match. In the User Interface go to Admin > Descriptions and for each tab, do an Export (all) and save them to a file. Search for exactmatch="false" and change the filter value to remove any wildcards (%) and match the object name exactly. You may need to split them out into multiple entries, each with a unique filter matching the object name and ensure to set exactmatch="true".
<?xml version="1.0"?>
<BusinessDescriptions>
<BusinessDescription filter="BLR Technical board" exactmatch="true" type="UserGroup">
<AltName>Alternate Name for Group BLR Technical board</AltName>
<Tooltip>ToolTip for Group BLR Technical board</Tooltip>
<LongDesc>Long Description for Group BLR Technical board</LongDesc>
<HelpURL>http://www.aveksa.com</HelpURL>
</BusinessDescription>
<BusinessDescription filter="B" exactmatch="false" type="UserGroup">
<AltName>Alternate Name for Group starting with B</AltName>
<Tooltip>ToolTip for Group starting with B</Tooltip>
<LongDesc>Long Description for Group starting with B</LongDesc>
<HelpURL>http://www.aveksa.com</HelpURL>
</BusinessDescription>
</BusinessDescriptions>
- Check the number of "soft" deleted Business Descriptions. If the number is large, it is suggested that you contact RSA Customer Support to aid in deleting them.
SELECT COUNT(*) FROM t_av_business_description WHERE is_deleted='TRUE';
- Avoid unnecessary use of Business Descriptions. Do not add a Business Description if the current collected information is understandable by the end user.
Related Articles
Password Lockout Examples 89Number of Views RSA Governance & Lifecycle Data Processors: Setting is Disabled flag in REST account collectors 26Number of Views Citrix MetaFrame bypassing authentication on a per-session basis 7Number of Views Violation dialog in RSA Via Lifecycle & Governance shows the error "Request could not be handled" after importing an entit… 42Number of Views Role commit fails for roles with membership rules in RSA Identity Governance & Lifecycle 101Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) How to delete old or pending certificate signing requests for RSA Authentication Manager console or virtual host replaceme… Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to import CA signed console cert from AM 8.x primary into a new primary with same FQDN How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device
Don't see what you're looking for?