FileNet P8 Application Engine, Version 5.0.+       Application server:  WebSphere Application Server     

Re-creating the WAR or EAR file

Any time that you make changes to files in the /Workplace directory, such as changes to web.xml for container-managed authentication, SSO support, or any other edits, you must re-create the WAR or EAR file and redeploy your changes.

Remember: Before re-creating the EAR file, you must first re-create the WAR file.

To re-create the WAR or EAR files:

  1. Verify that all modified /Workplace directory files have been saved.
  2. Recreate the app_engine.war file by running the script for your platform.
    Option Description
    UNIX AE_install_path/deploy/create_app_engine_war.sh
    Windows AE_install_path\deploy\create_app_engine_war.bat
  3. (For WAR file deployment) Rename the newly recreated app_engine.war file to Workplace.war or custom_name.war to create the context root for your application. For example, the default app_engine.war will generate the following context root: http://server_name:port# /app_engine. Renaming the WAR file Workplace.war will generate the following context root: http://server_name:port#/Workplace.
    Important: You must rename the WAR file every time you regenerate it. The create_app_engine_war script will by default create a file with the name app_engine.war.
    Important: Do not rename the WAR file if you are using the WAR file to recreate the EAR file for deployment.
  4. (For EAR file deployments only) Re-create the app_engine.ear file by running the script for your platform.
    Option Description
    UNIX AE_install_path/deploy/create_app_engine_ear.sh
    Windows AE_install_path\deploy\create_app_engine_ear.bat


Feedback

Last updated: November 2010


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