CA AuthMinder UNIX Installation Guide › Deploying AuthMinder on Distributed Systems › Performing Post-Installation Tasks on the First System › Deploying Administration Console

Deploying Administration Console

Note: If you plan to deploy Administration Console on WebSphere 7.0, then see the instructions that are provided in appendix, "Deploying Administration Console on IBM WebSphere 7.0".

You need the file arcotadmin.war to deploy the AuthMinder Administration Console. This file is available at:

<install_location>/arcot/java/webapps/

Note: To manage AuthMinder Server by using Administration Console, ensure that Administration Console can access the system where AuthMinder Server is installed by its host name.

To deploy Administration Console:

1. Change the working directory to:

   <install_location>/arcot/sbin
   

2. Type source arwfenv and press Enter to set the $ARCOT_HOME environment variable.
3. Restart the application server for the changes to take effect.
4. Deploy arcotadmin.war in the appropriate directory on the application server.

   Note: The deployment procedure depends on the application server that you are using. See your application server vendor documentation for detailed instructions.
   For example, in the case of Apache Tomcat, deploy the WAR file at <APP_SERVER_HOME>/webapps/.

5. (For JBoss Application Server Only) Perform the following steps if you have deployed Administration Console on JBoss Application Server:
   1. Copy the Bouncy Castle JAR file (bcprov-jdk15-146.jar) from <install_location>/arcot/java/lib/ to the following location:

      <JBOSS_HOME>/common/lib
      

   2. Navigate to the following location:

      <JBOSS_HOME>/server/default/conf/
      

   3. Open jboss-log4j.xml file in a text editor.
   4. Add the following log configuration in the <log4j:configuration> section:

      <appender name="arcotadminlog" class="org.apache.log4j.RollingFileAppender">
      <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"></errorHandler>
      <param name="Threshold" value="INFO"/>
      <param name="MaxFileSize" value="10MB"/>
      <param name="MaxBackupIndex" value="100"/>
      <param name="Encoding" value="UTF-8"/>
      <param name="Append" value="true"/>
      <param name="File" value="${arcot.home}/logs/arcotadmin.log"/>
      <layout class="org.apache.log4j.PatternLayout">
      <param name="ConversionPattern" value="%d{yyyy-MM-dd hh:mm:ss,SSS z} : [%t] : %-5p : %-5c{3} : %m%n"/>
      </layout>
      <filter class="org.jboss.logging.filter.TCLMCFilter">
      <param name="AcceptOnMatch" value="true"/>
      <param name="DeployURL" value="arcotadmin.war"/>
      </filter>
      <!-- end the filter chain here -->
      <filter class="org.apache.log4j.varia.DenyAllFilter"></filter>
      </appender>
      

   5. Add the following log category:

      <category name="com.arcot">
      <priority value="INFO" />
      <appender-ref ref="arcotadminlog"></appender-ref>
      </category>
      

   6. Add the following category for cryptographic operations:

      <category name="com.arcot.crypto.impl.NCipherCrypter">
      <priority value="FATAL" />
      <appender-ref ref="arcotadminlog"></appender-ref>
      </category>
      

   7. Save and close the file.
   8. Take the backup of existing JBoss Application Server logging libraries. These library files are available at:

      <JBOSS_HOME>/lib
      

   9. Upgrade the JBoss Application Server logging libraries available at <JBOSS_HOME>/lib to version 2.1.1. The following table lists the JAR file names and the location from where you can download the files:

1. Ensure that the application is restarted.