InfoSphere Enterprise Records, Version 4.5.1.3+       Application server:  JBOSS Application Server     

(JBoss Application Server 4 and 5) Deploying the InfoSphere Enterprise Records web application

Use the records_manager.war file or the records_manager.ear file in the RM_install_path/FileNet/RM/deploy directory to deploy the IBM® InfoSphere™ Enterprise Records web application on the JBoss Application Server 4.0 and later.

To deploy the InfoSphere Enterprise Records web application:

  1. Decide which name to use for the InfoSphere Enterprise Records web Application. You can keep the default name of RecordsManager. You can change the name by renaming the records_manager.war file.

    For example, the default records_manager.war generates the following context root: http://server_name:port/records_manager

    Renaming the WAR file RecordsManager.war generates the following context root:http://server_name:port/RecordsManager

    Perform this step only if you are using a WAR file for deployment, and you want to use RecordsManager or a custom name for the context root of the application. The context root is part of the URL that users type to access the InfoSphere Enterprise Records application. By default, when you deploy from a WAR file, the context root is the first part of the WAR file name.

    Restriction:

    You must rename the WAR file every time that you regenerate it. The script create_records_manager_war.sh (UNIX®) or create_records_manager_war.exe (Windows®) by default creates a file named records_manager.war.

  2. Deploy and start InfoSphere Enterprise Records:
    Deploy from Deployment steps
    Exploded directory
    1. On the JBoss Application Server server, copy the RecordsManager directory from RM_install_path to: JBOSS_HOME/server/server_name/deploy/
    2. Append the extension .war to the RecordsManager directory: JBOSS_HOME/server/server_name/deploy/RecordsManager.war
    WAR file

    On the JBoss Application Server server, copy the records_manager.war file from: RM_install_path/deploy to: JBOSS_HOME/server/server_name/deploy/

    EAR file

    On the JBoss Application Server server, copy the records_manager.ear file from: RM_install_path/deploy to: JBOSS_HOME/server/server_name/deploy/

  3. If the user that runs the application server differs from the user who installed InfoSphere Enterprise Records, give the former read and write permissions on the following directories:
    • JBOSS_HOME/server/server_name/deploy/records_manager.war
    • JBOSS_HOME/server/server_name/deploy/records_manager.ear
    • RM_install_path
    On Windows machines, this step is required only for NTFS-formatted partitions.
  4. On a JBoss Application Server using Container Managed Authentication (CMA) only, you must enable CMA seamless sign-in between Application Engine or Workplace XT and InfoSphere Enterprise Records on JBoss Application Server.

    To enable CMA on JBoss Application Server, edit the server.xml file and uncomment the following section:

    <Valve className="org.apache.catalina.authenticator.SingleSignOn" />

    The default location for the server.xml file is:

    JBoss Application Server 4.0.5
    JBOSS_HOME/server/server_name/deploy/jbossweb-tomcat55.sar/
    JBoss Application Server 4.2.3
    JBOSS_HOME/server/server_name/deploy/jboss-web.deployer//
    JBoss Application Server 5 (5.1.0 and later)
    JBOSS_HOME/server/server_name/deploy/jbossweb.sar//
  5. Start or restart the JBoss Application Server.
  6. To determine whether InfoSphere Enterprise Records is successfully deployed, verify that the server.log file in JBOSS_HOME/server/server_name/log shows the deployment of the WAR or EAR file you used in Step 2.


Feedback

Last updated: November 2010


© Copyright IBM Corporation 2010.
This information center is powered by Eclipse technology. (http://www.eclipse.org)