FileNet P8 Application Engine, Version 5.1       Application server:  WebSphere Application Server     

Deploying the application (WebSphere Application Server 6.1)

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

About this task

To deploy Application Engine:

Procedure

  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 app_engine.war or app_engine.ear file created by the installation program. For example, AE_install_path/deploy/app_engine.war or AE_install_path/deploy/app_engine.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 app_engine.war or app_engine.ear file. For example, AE_install_path/deploy/app_engine.war or AE_install_path/deploy/app_engine.ear. Do not enter the machine name.
  4. If you are deploying a WAR file, enter the context root.

    Enter Workplace and click Next to proceed to deploying a new application.

    Tip: The context root is the name of the application that you log in to by using the web interface, such as: http://ApplicationEngineServerName:port#/Context_Root.
  5. Click Prompt only when additional information is required, and click Next. Complete the dialog boxes for installing a new application by using the following settings:

    For Application name, enter Workplace, or the name you chose to call the application.

    For WebServer, specify the server you are planning to use. Verify that your application name is selected and associated with the correct WebServer.

    For Map virtual hosts for Web modules, for virtual host, choose the default_host.

    (WAR file deployment only) For Context root, specify Workplace, or whatever you want to call the application.

  6. Save your configuration.
  7. Navigate to Applications > Enterprise Applications > Workplace > Class loading and update detection.
  8. Set the polling interval for updated files with a number appropriate for your environment, for example, 3 seconds.
  9. Change the Class loader order to Classes loaded with application class loader first.
  10. Click Apply.
  11. Click Workplace > Manage Modules.
  12. Click Workplace.
  13. Change the Class loader order to Classes loaded with application class loader first.
    Important: Change this setting only for the specific web application. Do not change the similar settings for the entire application server.
  14. If you are using container-managed authentication, navigate to Enterprise Applications > Workplace > Security role to user/group mapping. Verify that the All Authenticated column is checked for the "All Authenticated" role.
  15. Save all your changes to the master configuration.
  16. Stop and restart the WebSphere Application Server instance where the application is installed.

    To troubleshoot the deployment, check the following log:

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

  17. Start Application Engine (or whatever you named your application) from the administrative console.
  18. High availabilityIn a high availability environment, by using the application server administration tool, verify that the Application Engine application is running.
    1. Open a Web browser and type in the URL for the Application Engine application.
      • If you are using a load-balancer or proxy server the URL has the form:
        Application Engine
        http://virtual_name:port_number/Workplace
      • If connecting to an individual cluster node the URL would have the form:
        Application Engine
        http://clustered_server_name:port_number/Workplace/
      Sign-in by using the virtual name to properly set the base Application Engine 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.


Last updated: March 2016
p8pin128.htm

© Copyright IBM Corporation 2013, 2016.