Integration Server 10.3 | Microservices Runtime Guide | Automatic Package Deployment | Considerations for Auto Deployment of Packages
 
Considerations for Auto Deployment of Packages
Before you configure automatic package deployment in Microservices Runtime, keep the following behavior limitations and considerations in mind.
*You cannot cancel an in-progress automatic package deployment operation.
*If the watt.server.autodeploy.alwaysUseHotDeployment parameter is set to true. Microservices Runtime performs hot deployment for the installation of any custom package regardless of whether it is a new package or an upgraded package. For more information on hot deployment, see Enabling and Configuring Automatic Package Deployment.
*If you are deploying new package and it has new dependent packages, you have to deploy all at once in the autodeploy folder.
*If you use hot deployment for automatic package deployment, all of the hot deployment considerations apply to automatic package deployment as well. For more information about hot deployment considerations, see Enabling and Configuring Automatic Package Deployment.
*When hot deployment is used for automatic package deployment, Microservices Runtime uses the configured hot deployment values. For more information about configuring hot deployment, see Enabling and Configuring Automatic Package Deployment.