Any time that you change 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.
About this task
Remember: Before re-creating the EAR file, you
must first re-create the WAR file.
To re-create the WAR or
EAR files:
Procedure
- Verify that all modified /Workplace directory
files have been saved.
- Re-create the app_engine.war file
by running the script for your platform.
| Option |
Description |
|---|
| AIX®, HPUX, Linux, Linux on System z®, Solaris |
AE_install_path/deploy/create_app_engine_war.sh |
| Windows |
AE_install_path\deploy\create_app_engine_war.bat |
- (For WAR file deployment) Rename the newly re-created 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 generates the following
context root: http://server_name:port#/app_engine.
Renaming the WAR file Workplace.war generates
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
by default creates a file with the name app_engine.war.
Important: Do not rename the WAR file if you are using
the WAR file to re-create the EAR file for deployment.
- (For EAR file deployments only) re-create the app_engine.ear file
by running the script for your platform.
| Option |
Description |
|---|
| AIX, HPUX, Linux, Linux on System
z, Solaris |
AE_install_path/deploy/create_app_engine_ear.sh |
| Windows |
AE_install_path\deploy\create_app_engine_ear.bat |