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

(WebSphere Application Server 6.1 and 7) Deploying the InfoSphere Enterprise Records web application

After you install IBM® InfoSphere™ Enterprise Records, you must deploy the web application on WebSphere® Application Server. You might need to recreate the WAR or EAR files before you can deploy the web application.

To deploy the InfoSphere Enterprise Records web application:

  1. From the WebSphere Application Server administrative console, expand the Applications container and select Install New Application.
    1. Select the file to deploy by completing the following sub-steps:
      • If the WebSphere Application Server administrative console is running locally, select Local Path and enter or browse to the location of the records_manager.war or records_manager.ear file created by Setup. By default, the files are located under RM_install_path/deploy. Do not enter the machine name.
      • If the WebSphere Application Server administrative console is remote, select Server path and enter the fully qualified path to the records_manager.war or records_manager.ear file. Do not enter the machine name.
    2. If you are deploying a WAR file, enter the context root (for example, RecordsManager, and click Next tp proceed to deploying a new application. The context root is the name of the application you log in to using the web interface, such as: http://RecordsManagerServerName:port#/ContextRoot
  2. For WebSphere Application Server 7.0, at Preparing for the application installation, select Fast Path.
  3. At Install New Application, Step 1, specify the application name and click Next. For example, specify RecordsManager, or the name you chose to call the application.
  4. At Install New Application, Step 2, Map modules to servers, check RecordsManager and click Next.
  5. At Install New Application, Step 3, Map virtual hosts for Web Modules, check the application name and keep the default virtual host (default_host), and then click Next.
  6. At Install New Application, Step 4, verify your configuration and click Finish.
  7. Save the configuration.
  8. Configure the class loader settings, as follows:
    1. From the Administrative Console, expand Applications.
    2. Click Enterprise Applications.
    3. Click the application name (default RecordsManager).
    4. From the Configuration tab, click Class loading and update detection.
    5. Change Class loader order to Classes loaded with application class loader first for WebSphere Application Server 6.1 or Classes loaded with application class loader first (parent last) for WebSphere Application Server 7.0.
      Important: Do this only for the specific web application. Do not change the similar settings for the entire application server.
    6. Change the polling interval to a number appropriate for your environment.
    7. Click Apply.
  9. If InfoSphere Enterprise Records was installed with Container Managed Authentication:
    1. From the WebSphere Application Server administrative console, expand Applications, click Enterprise Applications, and then click your application name.
    2. From the Configuration tab, click Security roles to users/group mapping.
      • For WebSphere Application Server 6.1, for the All Authenticated role row, verify that only the check box in the All Authenticated? column is selected. For the Everyone role row, verify that only the check box in the Everyone? column is selected.
      • For WebSphere Application Server 7.0, navigate to Enterprise Applications > Workplace XT > Security roles to users/group mapping. Select the All Authenticated role and click Map Special Subjects. Map the All Authenticated role to the All Authenticated in Applications realm. Select the Everyone role and click Map Special Subjects. Map the Everyone role to Everyone.
    3. Click Apply, click Save, and then click Save changes to the Master Configuration.
      Important: Verify that the changes were saved before you proceed with the next step.
    4. Click Next.
  10. Configure the Web Module class loader setting:
    1. In the WebSphere Application Server administrative console, expand Applications.
    2. Click Enterprise Applications.
    3. Click the application name (default RecordsManager).
    4. Under Modules, click Manage Modules.
    5. Select the application name.
    6. Change Class loader order to Classes loaded with application class loader first for WebSphere Application Server 6.1 or Classes loaded with application class loader first (parent last) for WebSphere Application Server 7.0.
      Restriction: Do this only for the specific web application. There are similar settings for the entire application server. Do not change these settings.
    7. Click Apply, click Save, and then click Save changes to the Master Configuration.
      Important: Verify that the changes were saved before you proceed with the next step.
  11. Stop and restart the application server.
  12. Start the enterprise application, as follows:
    1. From the WebSphere Application Server administrative console, expand Applications.
    2. Click Enterprise Application.
    3. Select the box to the left of the application name and click Start.


Feedback

Last updated: November 2010


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