FileNet P8 Workplace XT, Version 1.1.5       Application server:  WebSphere Application Server     

Deploying Workplace XT on WebSphere Application Server 6.1

Deploy Workplace XT as an application in the WebSphere® 6.1 administrative console. You can specify the context root for the application URL during the deployment.

To deploy Workplace XT:
  1. Log on to the WebSphere administrative console.
  2. Navigate to Applications > Enterprise Applications > Install.
  3. Select the file to deploy.
    • (If the administrative console is running locally) Select Local file system and enter or browse to the location of the web_client.war or web_client.ear file created by the installation program. For example, install_path/deploy/web_client.war or install_path/deploy/web_client.ear. Do not enter the machine name.
    • (If the administrative console is remote) Select Remote file system and enter the fully-qualified path name to the web_client.war or web_client.ear file. For example, install_path/deploy/web_client.war or install_path/deploy/web_client.ear. Do not enter the machine name.
  4. If you are deploying a WAR file, enter the Context root.
    Tip: The context root is the name of the application you log in to using the web interface. Do not include spaces. If you enter WorkplaceXT, the application URL will be http://server_name:port#/WorkplaceXT.
  5. Click Prompt me only when additional information is required, and click Next to proceed to deploying a new application.
  6. Complete the dialogs for installing a new application, using the following settings:
    • On the Select installation options page, for Application name, enter Workplace XT, or the name you chose to call the application.
    • On the Map modules to servers page, for Clusters and Servers, specify the server you are planning to use. Verify that your application name is selected and associated with the correct server and nodes, if applicable.
    • On the Map virtual hosts for Web modules page, for virtual host, choose the default_host.
  7. Save your configuration.
  8. Navigate to Applications > Enterprise Applications > Workplace XT > Class loading and update detection.
  9. Set the polling interval for updated files with a number appropriate for your environment, for example, 3 seconds.
  10. Change the Class loader order to Classes loaded with application class loader first.
  11. Click Apply.
  12. Click Workplace XT > Manage Modules.
  13. Click Workplace XT.
  14. Change the Class loader order to Classes loaded with application class loader first.
    Important: Do this only for the specific web application. Do not change the similar settings for the entire application server.
  15. Navigate to Enterprise Applications > Workplace XT > Security role to user/group mapping.
  16. Verify that the All Authenticated column is checked for the "All Authenticated" role.
  17. Verify that the Everyone column is checked for the Everyone role.
  18. Save all your changes to the master configuration.
  19. Stop and restart WebSphere Application Server.
  20. (Windows only) From the Windows Services Console, restart the Process Workplace XT Services Manager service.
  21. Restart Process Task Manager and Component Manager.
  22. Exit the Process Task Manager application.
  23. Start Workplace XT from the administrative console.
  24. By using the application server administration tool, verify that the Workplace XT application is running.
    1. Open a Web browser and type in the URL for the Workplace XT application.
      • If you are using a load-balancer or proxy server the URL has the form:
        Workplace XT
        http://virtual_name:port_number/WorkplaceXT
      • If connecting to an individual cluster node the URL would have the form:
        Workplace XT
        http://clustered_server_name:port_number/WorkplaceXT/
      Sign-in by using the virtual name to properly set the base Workplace XT URL. If it is not set correctly you must change it in Site Preferences.
    2. Verify that the sign-in page displays, and log in as a user.
    3. Fail one of the nodes.
    4. Verify that you can reload the sign-in page, and log in as the same user.
  25. To troubleshoot the deployment, check the following log:

    WAS_install_path/AppServer/profiles/profile_name/logs/server_name/SystemOut.log



Feedback

Last updated: March 2013
wxtip035.htm

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