Curriculum
- 22 Sections
- 74 Lessons
- Lifetime
Expand all sectionsCollapse all sections
- Introduction4
- Understanding Application On-Boarding4
- Understanding Rules and Filters2
- Non - Authoritative Application On-boarding8
- 5.1Active Directory as Non – authoritative application12 Minutes
- 5.2Active Directory Account Aggregation25 Minutes
- 5.3Connector Rules and Identity Mapping30 Minutes
- 5.4IQService17 Minutes
- 5.5Feature String and Pass-Through Authentication24 Minutes
- 5.6Group Aggregation15 Minutes
- 5.7Provisioning Plan21 Minutes
- 5.8Group Provisioning20 Minutes
- LifeCycle Management7
- Certifications, Groups and Capability5
- Policy, Form and QuickLink3
- Events2
- Roles2
- LifeCycle and Compliance Manager1
- More On LifeCycle Management5
- Project Build2
- IntegrationConfig1
- Audits and Reports2
- Extended Attributes1
- Scopes1
- REST in IIQ1
- Custom Connector2
- Plugin development2
- Out-of-the-box Connector and Misc13
- 21.1ServiceNow Connector27 Minutes
- 21.2Service Now ticket raise27 Minutes
- 21.3Okta Connector13 Minutes
- 21.4SSO by Okta31 Minutes
- 21.5Self Signed Certificate7 Minutes
- 21.6SSO by Rule11 Minutes
- 21.7Deployment Accelerator20 Minutes
- 21.8Interview Question Part 122 Minutes
- 21.9Interview Question Part 228 Minutes
- 21.10WebService Connector Part 128 Minutes
- 21.11WebService Connector Part 229 Minutes
- 21.12WebService Connector Part 330 Minutes
- 21.13Salesforce Integration19 Minutes
- Resource Center4
- SailPoint IIQ Certification Quiz2
4 Comments
i added below logger in log4j.properties file but logs are not printing in logs file..
log4j.logger.sailpoint.demo.ad=debug
Pls see comment in another thread related to log4j
2021-01-26 22:26:21,737 WARN localhost-startStop-1 sailpoint.server.JavaLoggingSuppressor:100 – The application detected that a custom logging file exists: F:\Tomcat\conf\logging.properties. The application was unable to suppress various debugging messages.
2021-01-26 22:26:21,745 WARN localhost-startStop-1 sailpoint.server.JavaLoggingSuppressor:101 – In order to manually suppress Jersey debugging messages, the following logger levels must be adjusted to ”WARNING”: com.sun.jersey.api.core.PackagesResourceConfig, com.sun.jersey.server.impl.application.DeferredResourceConfig, and com.sun.jersey.server.impl.application.WebApplicationImpl
2021-01-26 22:26:21,746 WARN localhost-startStop-1 sailpoint.server.JavaLoggingSuppressor:102 – In order to manually suppress JSF debugging messages, the following logger level must be adjusted to ”SEVERE”: org.apache.myfaces.shared_tomahawk.renderkit.html.HtmlRendererUtils
Hi, Probably you need to set log level (log4j.rootlogger) to debug or higher. Priority level is
OFF
FATAL
ERROR
WARN
INFO
DEBUG
TRACE
ALL
You have to edit sailpoint log4j properties which is in WEB-INF\classes I believe.
or you can set the logging level in code as well with something like this
Logger.getRootLogger().setLevel(Level.DEBUG);
or if you want to avoid adding imports:
org.apache.log4j.Logger.getRootLogger().setLevel(
org.apache.log4j.Level.DEBUG);
Note: this doesn’t work in log4j2 because setLevel has been removed from the API, and there doesn’t appear to be equivalent functionality