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.

Configure logging for Identity Manager

book

Article ID: 132851

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal

Issue/Introduction

Configure logging for the "im" and "ims" logging categories. These two categories, im and ims, will log most of the information required for general troubleshooting.

The logging willing be written to your application server's standard output fle (server.log, for example).

Environment

Release:


Component:

Resolution

CONFIGURING log4j FOR IDENTITY MANAGER

Set the "im" and "ims" logging categories to DEBUG in the file "log4j_[ApplicationServer].properties" located in the deployed IM .ear location, for example:

In ../iam_im.ear/config/com/netegrity/config/log4j_jboss.properties, in the "IMS logging" section set the two logging lines as follows.

 # IMS logging

 log4j.category.ims=DEBUG

 log4j.category.im=DEBUG

An application server restart is required for the changes to take effect.

-------------------

Alternatively, if the logging.jsp has been enabled, log4j can be configured via a browser pointing to the logging.jsp page on the IM application server:

http://<im_appServer>:port/iam/im/logging.jsp

On the logging.jsp page select DEBUG for all im.* and ims.* categories, click Update at the bottom of the page and verify that DEBUG is selected for the im and ims categories. No restart is required.

Logging.jsp changes apply only to the application server node on which you accessed the jsp. If you have multiple nodes in your cluster set the logging jsp on each server node of the cluster, e. g. for two nodes configure logging.jsp on both

http://<im_appServer_1>:port/iam/im/logging.jsp

and

http://<im_appServer_2>:port/iam/im/logging.jsp