IdP Running on JBoss

The JBoss Application Server supports web applications by embedding Apache's Tomcat Servlet/JSP container within the application server. Therefore the instructions for running a Shibboleth !IdP in JBoss are the same as running it in Tomcat with one exception, noted below. You may wish to refer to the JBoss documentation for setting up the application server to work behind Apache HTTPD as JBoss's embedded Tomcat version suffers from the same SSL Client Certificate Authentication problem that a normal standalone Tomcat environment does.

IdP Logging Configuration

Like most J2EE application servers JBoss has a special service that controls logging. To configure the IdP's logging to work within JBoss you will need to follow these instructions instead of those listed in the !IdP configuration guide.

1. If your IdP configuration currently uses a Log4J configuration file you'll need to remove any ErrorLog, TransactionLog, and Log4JConfig elements from your !IdP configuration file.
2. Remove the Log4J jar from the IdP WAR (JBoss uses a different version of Log4J and you could get odd exception if they conflict).
3. Configure the JBoss logging service to log Shibboleth messages. JBoss's logging configuration file can be found at $JBOSS_HOME/server/<your_server_profile>/conf/log4j.xml and is simply an XML Log4J configuration file.

When configuring JBoss's logging service you probably want to log messages for the following categories:

• edu.internet2.middleware.shibboleth - to catch IdP specific messages
• org.opensaml - to catch OpenSAML messages
• Shibboleth-TRANSACTION - to catch IdP transaction messages (corresponds to the TransactionLog configuration element in the IdP configuration file)
• shibboleth-error - to catch specific error messages (corresponds to the ErrorLog configuration element in the IdP configuration file)