Debug Pages: System Information and Advanced Editing

Click the wrench icon > About to view basic information about the IdentityIQ installation such as server host, the current IdentityIQ version and schema version, locale and time zone for the client, and an array of Java system properties. This information may be requested by support when opening a trouble ticket.

The Object Browser is the default Debug page. It provides access to the XML representations of data and configuration objects in the IdentityIQ system. You can view, create, edit, and delete objects in the Object Browser; users should exercise caution when modifying objects directly.

IMPORTANT: There is no rollback mechanism for edits to objects that are saved in the Debug pages. Although objects can be viewed and edited in the Debug pages, it is a best practice to export or check out the object, edit the XML as needed outside of IdentityIQ, and then import the updated object to a test environment for validation before importing into your production instance. This also allows you to manage your changes in a source control system, to facilitate rollback. Use caution when editing objects in the Debug pages, as there is no mechanism in the Debug pages for rolling back changes once they have been saved.

The iiq console export/import and checkout/checkin commands can be used for managing changes to objects. The export command exports all objects of the class you specify. The checkout command lets you write a copy of a single object. See IdentityIQ Console.

Click the wrench icon > Memory to view the Free, Total, & Max JVM memory.

There are two options on this page that can be run to help manage memory:

• Run Finalizers runs the finalize() methods on all classes in memory. The functionality performed by finalize() methods depends on how they were written for each class.

• Run Garbage Collector pauses all activity in the JVM, removes everything Java doesn’t need in memory, and resumes the JVM.

Click the wrench icon > Caches to access the System Caches page, which offers five buttons for managing the Hibernate Caches: Reset Miscellaneous Caches, Reset Managed Attribute Cache, Load Managed Attribute Cache, Dump Managed Attribute Cache and ResetIntegrationConfig Cache. These are infrequently used but can sometimes be used to clear or reset caches without having to stop and restart the application server.

Click the wrench icon > Count to view a list of the objects in your IdentityIQ instance, with a count of each object.

Click the wrench icon > Beans to view the Managed Beans page. This page displays all JMX beans registered with the application server. This same information is also available through the an application server utility such as JConsole.

Click the wrench icon > Threads to view all Java threads and their current state. This page is a good resource for diagnosing problems if slow or less responsive performance occurs. In that case, check to see if many threads appear in a TIME_WAITING state or if there is a large number of unused threads. These can indicate failed processes or, occasionally, performance-impacting bugs.

Click the wrench icon > Call Timings to review statistics about the time taken to perform certain database activities. Outliers can be identified and Database/Application Server tuning parameters can be applied once the root cause of any performance problem is determined. If you use "Meter" statements in any of your code, the statistics will be shown here.

Click the wrench icon > Logging to view or change the path to the Log4j properties file. Click Reload Logging Configuration to dynamically reload the Log4j2 properties file without bouncing the application server; this enables any changes made to logging levels on various system classes in the log4j2.properties file.

Click the wrench icon > Database to view basic database pooling information.

Click the wrench icon > Connections to see the connections from the database connection pool that the server is currently using.