Enabling logs

You must check various log files when you debug a BMC Atrium Single Sign-On issue. If there are no errors in arjava plugin log then you do not have to worry about those errors.

Log file disk space requirements

An additional 7-10 GB of space is recommended for log file growth, depending on the volume of users and products integrating with the BMC Atrium Single Sign-On server.

To manage log file storage space effectively, perform the following tasks:

• Delete the debug log files periodically, especially if the debug level is set to message.
• Check the .access and .error log files periodically in the logs directory.
• Consider configuring the log rotation to delete the oldest log files.

Enable logging on the BMC Atrium Single Sign-On server

1. Stop the BMC Atrium Single Sign-On server.
2. Enable Open AM server logging:
3. 1. Delete logs from AtriumSSO\tomcat\webapps\atriumsso\WEB-INF\config\atriumsso\debug\debug.out.
   2. Delete the log files from C:\Program Files\BMC Software\AtriumSSO\tomcat\temp\atsso*.log.
   3. Log on to the BMC Atrium Single Sign-On Admin Console to enable Open Server logging.
   4. Select Configuration > Server and Sites and then click Debugging.
   5. Debug level to Message.
   6. Merge debug files to ON.
   7. Save.
4. Enable Atrium Atrium Single Sign-On logging:
   On a non-Windows platform
   1. Open the setenv.sh file.
   2. In JAVA_OPTS, add "-Datsso.log.level=FINEST".
   3. Save the file.
   On a Windows platform
   1. Open a command window.
   2. Change directory to C:\Program Files\BMC Software\AtriumSSO\tomcat\bin.

   3. Run the following command:

      tomcat7w //ES//BMCAtriumSSOTomcat.

   4. Click the java tab.
   5. Add "-Datsso.log.level=FINEST" to the java Options tab, and click Apply.
   6. Click the General tab.
   7. Start the service.

Enabling logging on BMC Remedy Mid Tier

1. Stop the BMC Remedy Mid Tier service
2. Go to C:\Program Files\Apache Software Foundation\Tomcat7.0\temp\ and delete the atsso.log file.
3. Go to C:\Program Files\Apache Software Foundation\Tomcat7.0\ and delete the logs*<YYYY-MM-DD>.log file (where YYYY-MM-DD is the current date).
   
   On non-Windows platforms
   1. Open the setenv.sh file.
   2. In JAVA_OPTS, add "-Datsso.log.level=FINEST".
   3. Save the file.
   
   On Windows platforms
   1. Open a command window.
   2. Change the directory to C:\Program Files\BMC Software\AtriumSSO\tomcat\bin.

   3. Run the following command:

      tomcat7w

   4. Click the java tab.
   5. Add "-Datsso.log.level=FINEST" to the java Options tab and click Apply.
   6. Click the General tab.
   7. Start the service.

Log files to send

After enabling the logs, you must perform your test and send the following logs:

• From BMC Remedy Mid Tier:

  • ARSystem\midtier\logs\armidtier.log
  • Apache Software Foundation\Tomcat7.0\temp\atsso.log
  • Apache Software Foundation\Tomcat7.0\logs*YYYY-MM-DD*log files

• From BMC Atrium Single Sign-On:

  • AtriumSSO\tomcat\temp\atsso.log
  • AtriumSSO\tomcat\logs*YYYY-MM-DD*log files
  • AtriumSSO\tomcat\webapps\atriumsso\WEB-INF\config\atriumsso\debug\debug.out

Log files for installation failures

When installation fails, get the logs from the following folders to isolate the issue:

• ..\AtriumSSO\tomcat\webapps\atriumsso\WEB-INF\config\atriumsso\log
• ..\AtriumSSO\tomcat\webapps\atriumsso\WEB-INF\config\atriumsso\debug
• ..\AtriumSSO\tomcat\temp
• ..\AtriumSSO\tomcat\logs
• ...\AtriumSSO\tomcat\webapps\atriumsso\WEB-INF\config\opends\logs