How to put FIM 3.0 3.1 or 3.1.1 into debug mode
Originally Published: 2007-04-19
Last Modified: 2023-10-06
Article Number
Applies To
RSA Federated Identity Manager (FIM) 3.1
RSA Federated Identity Manager (FIM) 3.1.1
BEA Weblogic 8.1
IBM WebSphere 6.0
Issue
Debug mode is not enabled
Resolution
To enable debug mode, change to the following directory:
..\rsa-fim30-config\properties or ..\rsa-fim-config\properties (depending on your version of FIM 3.x, you will have one or the other)
Rename the original log4j.xml file to something else (i.e. log4j.xml.original)
Copy the DebugLogConfig.xml to log4j.xml
Restart your FIM Application server. You will see a new Debug.log in FIM log directory.
Related Articles
Enabling RSA My Page in an RSA ID Plus trial tenant (Video) Number of Views Which region is my SecurID Access Cloud Authentication Service tenant in? Number of Views How (and why) do I enable Authentication Manager Prime multi-tenant mode? Number of Views Deployment of the aveksa.ear in a clustered environment fails with 305000 ms timeout error in RSA Identity Governance & Li… Number of Views Logging into RSA My Page and registering an authenticator in an RSA ID Plus trial tenant (Video) Number of Views
Trending Articles
Artifacts to gather in RSA Identity Governance & Lifecycle How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle How to Download and Reinstall the AFX Server Archive in RSA Governance & Lifecycle
Don't see what you're looking for?
