Enable email notification debug logging

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Steps to enable debug logging for the Clarity email notification process.

Before proceeding:

1. Check in CSA to see if "Detect Log Configuration Changes Automatically" flag is checked
2. If this setting is not checked, review the steps below first as we require you to stop and start the BG and APP services for logging to take effect.

Resolution

Edit the Clarity Application Logger Configuration:

1. Login to the Clarity application as an admin user
2. Modify the URL field to: http://example.com/niku/nu#action:security.logs
3. Click on Edit Configuration
4. Scroll down to Category and click Add Category
5. Type the component name: com.niku.union.notification into the Other Name window
6. Change Appender to STDOUT.
7. Change the Priority drop-down box to debug.
8. Click the Save button.
9. If you have multiple application servers repeat steps 3-8 above
10. If "Detect Log Configuration Changes Automatically" flag is NOT checked stop and start the BG and  APP services
    

Generate an email notification

1. Generate an email notification by running a process with Action Items or schedule a report with notification on completion.
2. Do this a few times on different applications to kick start emails to be sent out

Disable debugging

Turning on the debugger degrades the performance of the application. So after getting the logs please turn debugger off.

Additional Information

For On Premise clients ,support will request you to share log files from $CLARITY_HOME\logs folder:

• app-ca.log
• bg-ca.log

Note:
If 'useAuthentication' is set to 'True', but 'username' and 'password' are blank, then mails will not be sent out of the application in the latest versions of the product. This is an incorrect configuration that has to be correct in the NSA / CSA.