Hot Deploying a War File
Hot deployment is accomplished by executing the wm.tomcat.admin:hotDeploy service. When this service executes, it checks the Integration Server_directory \instances\instance_name\web\webapps directory.
When you place a new war file in the directory, if an
Integration Server package named the same as the war file does not exist, the
hotDeploy service creates a new package. Be sure the name of your war file contains only characters that are valid for a package name; for more information, see
webMethods Service Development Help. The
hotDeploy service then unpacks the web application files to the \web directory of the
Integration Server package for the web application.
When you place an updated war file in the directory, the
hotDeploy service unpacks the web application files from the updated war file into the \web directory of the
Integration Server package, replacing all files in the \web directory that have the same name as files in the war file.
When you delete a war file from the directory, the
hotDeploy service takes no action. It does
not delete the web application from the \web directory of the
Integration Server package for the web application. The web application will still be available. If you want to delete the web application, see
Deleting Web Applications.
To hot deploy a web application
1. If the Integration Server package for the web application already exists, ensure the name of the war file exactly matches the name of the package (including uppercase and lowercase letters). If the package does not already exist, the wm.tomcat.admin:hotDeploy service will create it during hot deployment.
2. If your web application uses tags from the webMethods tag library for JSP within your web application’s JSP files to invoke Integration Server services and obtain pipeline data, be sure your web application has access to the tag library. Do the following:
a. Copy the webm-taglib.tld file that is located in the Integration Server_directory \instances\instance_name\web directory.
b. If the Integration Server package for the web application already exists, place the copy in the Integration Server_directory \instances\instance_name\packages\packageName\web\WEB-INF directory of the package. If the Integration Server package does not exist, include the webm-taglib.tld file in your war file.
c. Update the web.xml file for the web application (which should also be in the WEB-INF directory) to identify the location of the webMethods tag library (webm-taglib.tld).
To update the web.xml file, add the following <taglib> section:
<taglib>
<taglib-uri>http://webm-taglib.tld</taglib-uri>
<taglib-location>/WEB-INF/webm-taglib.tld</taglib-location>
</taglib>
3. Place the war file for the web application in the Integration Server_directory \instances\instance_name\web\webapps directory.
Be sure to retain the appropriate directory structure for the JSPs and their supporting files, as described in
The Integration Server Package Directory Structure. In the war file, do not include the \web directory itself. Include only the files and subdirectories that reside beneath the \web directory.
4. Execute the wm.tomcat.admin:hotDeploy service.
The wm.tomcat.admin:hotDeploy service is automatically executed if you created a user task to have
Integration Server regularly execute the
wm.tomcat.admin:hotDeploy service. No further action is needed. After placing the war file in the
Integration Server_directory \instances\
instance_name\web\webapps directory, the next time the
wm.tomcat.admin:hotDeploy service executes, the
hotDeploy service deploys the web application.
Manually execute the wm.tomcat.admin:hotDeploy service if you did not create a user task to execute the service. To manually execute the service do the following:
i. From the Integration Server Administrator, in the Packages menu of the navigation panel, click Management.
ii. In the list of packages, click WmTomcat.
iii. Click Browse services in WmTomcat.
iv. Click wm.tomcat.admin:hotDeploy.
v. Click Test hotDeploy.
vi. Click Test (without inputs).
