Signals an existing application to shut itself down and reload. This can be useful when the web application context is not reloadable and you have updated classes or property files in the /WEB-INF/classes directory or when you have added or updated jar files in the /WEB-INF/lib directory.
...
Property Name | Property Code | Required | Description |
|---|---|---|---|
| Tomcat Catalina Home |
| Yes | The CATALINA_HOME directory for the Tomcat installation. |
| Tomcat Manager URL |
| Yes | The url of the Manager web application within the Tomcat server. In Tomcat 6, the manager url is likely http://localhost:8080/manager. In Tomcat 7+, the manager url is likely http://localhost:8080/manager/text. |
| Tomcat Username |
| Yes | The name of the Tomcat user with which to connect to the Manager web application. This user must be configured with the manager-script role. |
| Tomcat Password |
| Yes | The password for the |
...
Input Name | Input Code | Required | Description |
|---|---|---|---|
Outputs
Output Name | Required | Description |
|---|---|---|
Artifacts
This operation doesn't consume or produce any artifacts.
...
- The
JAVA_HOMEenvironment variable must be set to a supported JDK for the version of Tomcat being used. - The Tomcat user specified by property property
FDTOM_USERNAMEmust must be granted the manager (Tomcat 6.0.x) or manager-script (Tomcat 7+) role. - The target Tomcat server must be running prior to calling this operation.
- An application with the given
FDTOM_CONTEXT_ROOTmust be deployed and be in the running state. - Application reloading (to pick up changes to the classes or web.xml file) is not supported when a web application is deployed directly from a WAR file. It only works when the web application is deployed from an unpacked directory. If you are using a WAR file, you should undeploy and then deploy again to pick up your changes.
...