ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Process debugging - Enabling for Troubleshooting

book

Article ID: 189828

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

This KB provides steps on how to enable debugging for troubleshooting process issues

Environment

Release : All Supported Releases

Component : CA PPM BUSINESS PROCESS MANAGEMENT

Resolution

  1. Open the Clarity log configuration page (ClarityPPM_URL/niku/nu#action:security.logs)
  2. From the Logs tab drop down, select 'Edit configuration). (Alternatively, you can go to the log configuration section via CSA)

     3. Set the priority level of  "com.niku.bpm" to "ALL"
     4. If com.niku.bpm doesn't exist in the name list already, you can add it by doing the below:

    • Click Add Category
    • Paste com.niku.bpm into Other Name field for the newly created row
    • Set Appender = STDOUT
    • Priority = All

     5. Once the issue has been reproduced, download the bg-ca.logs and then disable the debugging (com.niku.bpm can be set to priority of Fatal)
     6. For more specific process debugging, the below 2 categories can be set for Debug

    • com.niku.bpm.engine -- Logs process engine core activities
    • com.niku.bpm.eventmgr -- Logs event manager activities 

Additional Information