CABI (Jaspersoft) debug option for logging is not working

book

Article ID: 206816

calendar_today

Updated On:

Products

DX Infrastructure Management CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM) CA Unified Infrastructure Management for z Systems

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.

Cause

- wasp cfg

Environment

Release : 20.3

Component : UIM - OPERATOR CONSOLE

- cabi 4.30

Resolution

When running cabi 4.3, 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.

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

Additional Information

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