Configuring JCS endpoint debug logging for the CA IAM CS

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal
• CA Identity Suite

Issue/Introduction

Instructions on turning up debug logging at the connector level for a connector managed by the CA IAM CS. This is to generate an additional endpoint specific JCS log other than the jcs_daily log.

 

Environment

All Identity Manager

Resolution

To turn up specific debug logging for a connector managed by the CA IAM CS, 2 steps are needed:

1. Under the Java Connector Server installation location in the /etc folder rename the org.ops4j.pax.logging.cfg file to org.ops4j.pax.logging.cfg.original and then make a copy of the org.ops4j.pax.logging.cfg.verbose file and name it org.ops4j.pax.logging.cfg and restart the Java Connector Server.

This will generate verbose logging in the \CA\Identity Manager\Connector Server\jcs\logs\jcs_daily.log and also enable generation of endpoint specific logs under \CA\Identity Manager\Connector Server\jcs\logs\<ENDPOINT_TYPE\jcs_conn_<ENDPOINT_NAME>.log by having the log4j.category.jcs_conn property switched from value of OFF to value of DEBUG

2. Then in the Provisioning Manager for each specific acquired endpoint you would enable logging for all message severities to the text file destination which will write to the above mentioned \CA\Identity Manager\Connector Server\jcs\logs\<ENDPOINT_TYPE\jcs_conn_<ENDPOINT_NAME>.log