Subsystem Logging - assure_dq - Latest

Assure DQ Administrative Console

Product type
Software
Portfolio
Verify
Product family
Assure
Product
Assure DQ
Version
Latest
ft:locale
en-US
Product name
Assure DQ, ER, Insight and Perceive
ft:title
Assure DQ Administrative Console
Copyright
2025
First publish date
2005
ft:lastEdition
2025-11-28
ft:lastPublication
2025-11-28T07:19:50.245000
L1_Product_Gateway
Verify
L2_Product_Segment
Data Quality
L3_Product_Brand
Precisely Infogix
L4_Investment_Segment
Legacy Infogix DQ
L5_Product_Group
Legacy Infogix DQ
L6_Product_Name
Product Feature
Assure DQ

The Infogix administrative console bundles sets of logging categories into subsystems that span multiple components and classes. The process to enable logging can be cumbersome if you need to turn on logging for multiple categories. The process is simplified and less prone to error if you enable debug logging for the entire subsystem. The actions that you take on this screen are reflected in the categories listed on the Manage Logging screen.

The Manage Subsystem Debug Logging screen allows you to enable or disable logging for an entire subsystem with a single click. The screen includes a description for each subsystem. One advantage to this type of logging is that you do not need to know the name of each category.

The logging subsystems displayed on the Manage Subsystem Debug Logging screen will vary, depending on the application from which you accessed the administrative console and your application server type.

If you enable the JBoss Security Debug Logging subsystem, the setting is not retained if you stop the server. The setting for product-level logging subsystems is retained if you stop and then restart the server.

We recommend that you do not leave subsystem debug logging enabled for an extended period. When you use this feature, enable the logging, recreate the problem, review the logs, and then immediately disable the subsystem.