Since Personify360 is a multi-tier application where users never log into the database, understanding the behind-the-scenes functionality can be difficult. When system administrators want to see what a specific PC is doing, they cannot do this from the database itself since they will view all activities from all users. Users are not specifically identified to the database since the application server is asking for information from the database and not the user. This is a security feature for Personify360 used to prevent people from logging into the database. By not defining each user as a user in the database, you cannot access the data except through Personify360.
The debug tools in Personify360 solve this problem by allowing system administrators to see what one PC is doing in terms of passing commands, SQL calls to the database, and how code is written for a particular screen.
Diagnostics (such as the SQL Tracer and the Debug Tracer) can be turned on and off using the config.xml file:
The debug tools include the following: