A simple step-by-step blog on how to configure the OIM 10g (9101) logs into a file
Step 1: enable logfile
(This is the step Oracle missed out to enable the log files)
Locate the log.properties file within the # and comment the one without the "logfile" entry.
#log4j.rootLogger=WARN,stdout,logfile
log4j.rootLogger=WARN,stdout
# and comment the one without the "logfile" entry.
log4j.rootLogger=WARN,stdout,logfile
#log4j.rootLogger=WARN,stdout
Step 2: Turn up the logging
Based on the level of logging, 'un-REM the lines further down in the same file
#################################
# XELLERATE #
#################################
log4j.logger.XELLERATE=WARN
# We would like to have DDM operations at the DEBUG level
# as we may not have a second chance to perform the same
# operation if something fails
log4j.logger.XELLERATE.DDM=DEBUG
#log4j.logger.XELLERATE.ACCOUNTMANAGEMENT=DEBUG
log4j.logger.XELLERATE.SERVER=DEBUG
#log4j.logger.XELLERATE.RESOURCEMANAGEMENT=DEBUG
#log4j.logger.XELLERATE.REQUESTS=DEBUG
Step 3: Path to logs
Again, within the same log.properties file, make sure that the path exist where the App Server can create the log file for OIM.
#
# File Appender
# Uncomment if you want to output to a file and change the file name and path
#
log4j.appender.logfile=org.apache.log4j.DailyRollingFileAppender
log4j.appender.logfile.DatePattern='.'yyyy-MM-dd
log4j.appender.logfile.File=/opt/oracle/xellerate/logs/xel.log
log4j.appender.logfile.MaxBackupIndex=20
log4j.appender.logfile.layout=org.apache.log4j.PatternLayout
log4j.appender.logfile.layout.ConversionPattern=%p %t %c - %m%n
Step4: Save and Bounce Application Server
Save the modification to of the log.properties file and then restart the application server. Once you've restarted, you should be able to see the log file being populated
About the author
Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles
Comments
Other Posts
AS I was migrating my environment into an S3 environment, I wanted to leverage off the SES services that AWS provide, more specifically, to leverage the off the SMTP functionality by sending an email via PHP
Read More...
The WeMos D1 is a ESP8266 WiFi based board is an extension to the current out-of-the-box library that comes with the Arduino installation. Because of this, you need to import in the libraries as well as acknowledging the specific board. This process is highly confusion with a number of different individuals talking about a number of different ways to integrate.
Read More...
NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration.
Read More...
For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM. The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector. However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...