Tuesday, November 2, 2010

OES Security Module Logging in WebLogic domains with Enterprise Manager

This isn't the "official" solution, but a quick note on how I jury rigged my logging to get it working.

Both the OES WebLogic SM and the Enterprise Manager seem to use log4j to do their logging. Since the SM spins up first you will see the normal sorts of things you'd expect in the OES SM's log file as the SM WebLogic server boots. Then suddenly the log juts stops.

This is because the Enterprise Manager app (EM) re-initializes the log4j system with its own config file. To solve it just add the lines you want from OES' log4j.properties to the config file ./config/fmwconfig/servers/AdminServer/applications/em/META-INF/emomslogging.properties

Hope this helps someone else!
Posted by Chris Johnson (Oracle) at 4:17 PM
Labels: , ,

2 comments:

  1. sivaDecember 1, 2010 at 6:36:00 AM PST

    Hi Chris,

    I am trying to configure LDAP as a user store for Oracle Entitlements server. But, Couldn't find any documents related to that.

    Can you help me in this regard?

    Thanks

    Siva

    ReplyDelete
  2. Chris Johnson (Oracle)December 14, 2010 at 1:35:00 AM PST

    Siva,

    There is no way to wire OES' admin GUI to an LDAP directory.

    You might find http://fusionsecurity.blogspot.com/2009/12/writing-managable-policies-in-oes.html useful.

    To add the LDAP directory in at RUNTIME all you need to do is add the LDAP authenticator to the app server or SM's configuration.

    HTH!

    ReplyDelete

Note: Only a member of this blog may post a comment.

Subscribe to: Post Comments (Atom)