Configure logging for Identity Manager

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 will be written to your application server's standard output file (server.log, for example).

Environment

Release: Up to 14.3 and 14.4 and later.

Component: Identity Manager

Resolution

--CONFIGURING log4j FOR IDENTITY MANAGER 14.3 and prior versions--

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

 

--CONFIGURING log4j FOR IDENTITY MANAGER 14.4 and later versions--

Use the logging_v2.jsp page. For initial setup of log4j v2 see Configuring Logging.

http://<im_appServer>:port/iam/im/logging_v2.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_v2.jsp

and

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