CABI (Jaspersoft) debug option for logging is not working

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)
• Unified Infrastructure Management for Mainframe

Issue/Introduction

We set the debug option in Jaspersoft so we can reveal the underlying queries for CABI and assess the query performance due to slowness in the CABI pages but it is not working as expected.

Environment

Release : UIM 20.3/20.4

Component : CABI

 

Cause

- wasp cfg

Resolution

When running cabi 7.x/8.x, there is an entry in the wasp.cfg that is interfering with the debug option in Jaspersoft, hence you don't see the DEBUG option take effect, and no SELECT statements in the jaspersoft.log.

As per the default wasp.cfg:

<startup>
    options = -Dfile.encoding=UTF-8 -Dorg.apache.commons.logging.LogFactory=org.apache.commons.logging.impl.LogFactoryImpl

Change the section above to:

<startup>
    options = -Dfile.encoding=UTF-8

and then restart the CABI robot.

Please attach the jasperserver.log file after doing below steps on jasperserver url

          - login as 'superuser' 
          - go to server settings>> log settings
            and set the following logger to DEBUG:
           SQL query executer
           SQL generated for domain queries

The Jaspersoft debug should then work as expected, along with the SELECT statement/query timings.

Note: If you made changes to the following file:

C:\Program Files (x86)\Nimsoft\probes\service\wasp\webapps\cabijs\WEB-INF\log4j2.properties

you will want to roll it back, or copy in the following file and overwrite the one in the above location. After which you will need to restart the robot:

C:\Program Files (x86)\Nimsoft\c\buildomatic\install_resources\war\jasperserver-pro\WEB-INF\log4j2.properties

Additional Information

How to debug Operator Console (CABI) page slowness using Jasperserver debug
https://knowledge.broadcom.com/external/article?articleId=204496