CA RiskMinder UNIX Installation Guide › Deploying RiskMinder On a Single System › Performing Post-Installation Tasks › Deploying Administration Console

Deploying Administration Console

Note: If you are deploying the Administration Console on IBM WebSphere 7.0, then see appendix, "Deploying Administration Console on IBM WebSphere 7.0" instead of the instructions in this section.

Administration Console is a browser-based interface to RiskMinder that enables you to customize the server configurations and manage the deployed system.

You need the arcotadmin.war file to deploy the RiskMinder Administration Console. All Administration Console information is logged in the arcotadmin.log file. After you deploy arcotadmin.war, you can verify if it was correctly deployed by using this (arcotadmin.log) log file. This log file is in the $ARCOT_HOME/arcot/logs directory.

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

To deploy the Administration Console WAR file on your application server and verify that it was successfully deployed:

1. Change the working directory to:

   <install_location>/arcot/sbin
   

2. Type source arrfenv and press Enter to set the Arcot 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. Refer to your application server vendor documentation for detailed instructions.
   For example, in the case of Apache Tomcat, you must deploy the WAR file at <APP_SERVER_HOME>/webapps/.

5. (For 32-bit WebSphere Only) Configure reload of the Admin class when the application files are updated.
   1. Navigate to Application, Enterprise Applications, and then access the Admin settings page.
   2. Under Class loader order, select the Classes loaded with local class loader first (parent last) option.
   3. Under WAR class loader policy, select the Single class loader for application.
   4. Click Apply.
   5. Restart the Admin application.
6. (For JBoss 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 a backup of the existing JBoss logging libraries. These library files are available at:

      <JBOSS_HOME>/lib/
      

   9. Upgrade the JBoss 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. Restart the application server.
2. Verify that the console was successfully deployed:
   1. Navigate to the following location:

      <install_location>/arcot/logs/
      

   2. Open the arcotadmin.log file in any editor and locate the following lines:
      • 2.0.3
      • Arcot Administration Console Configured Successfully.

      These lines indicate that your Administration Console was deployed successfully.

   3. Also ensure that the log files do not contain any FATAL and WARNING messages.
   4. Close the file.