Installation Guides › Policy Server Installation Guide › Troubleshooting › Administrative UI Troubleshooting › Default Log File does not Provide Enough Information

Default Log File does not Provide Enough Information

Symptom:

I am trying to troubleshoot the Administrative UI installation and the default log file does not provide enough information.

Solution:

When you start the Administrative UI Task Engine, by default, output is sent to the default log file. The location of the default log file is dependent on the type of application server on which the Administrative UI is running.

• Jboss—jboss_home/server/server_name/log/server.log
  • jboss_home

    Specifies the Jboss installation path.

  • server_name

    Specifies the Jboss server name.

• WebSphere—websphere_home/AppServer/profiles/profile_name/logs/server_name/SystemOut.log
  • websphere_home

    Specifies the WebSphere installation path.

  • profile_name

    Specifies the WebSphere profile name.

  • server_name

    Specifies the WebSphere server name.

• WebLogic—WebLogic logs are available on the WebLogic console.

You can use the SiteMinderLog4j.properties file, which is located in the deploy/IdentityMinder.ear/user_console.war/META-INF to configure SOA Security Manager-specific logging settings.

• deploy

  Specifies the location of where your application server deploys applications.

Note: More information on how to configure the SiteMinderLog4j.properties file is commented in the file.