Integration Server 10.7 | Microservices Runtime Guide | Automatic Package Deployment | How Automatic Package Deployment Works
 
How Automatic Package Deployment Works
In automatic package deployment, the packages that you want Microservices Runtime to deploy automatically are placed in a location that Microservices Runtime periodically scans for new or updated custom packages. Microservices Runtime executes a system task named “Auto Package Deployer” that scans the folder and checks for new or updated custom packages. When Microservices Runtime finds new or updated custom packages, Microservices Runtime does one of the following:
*For a new package, Microservices Runtime installs, archives, and activates the package.
*For an updated custom package, Microservices Runtime does one of the following:
*If hot deployment is enabled for automatic package deployment, Microservices Runtime uses the block-and-wait approach employed by hot deployment to deploy the package. This ensures that Microservices Runtime assets are available for processing without any noticeable downtime. For more information about how hot deployment works, see webMethods Integration Server Administrator’s Guide
*If hot deployment is not enabled, Microservices Runtime unloads the existing package information from memory and loads the new version of the package and its contents into memory. While the package is being upgraded, it is possible that some assets might be unavailable for some time. This could cause serious issues such as denial of service or disruption of the in-flight tasks.
Hot deployment is enabled for automatic package deployment if either of the following is true:
*Hot deployment is enabled globally for the Microservices Runtime. Hot deployment is enabled globally when the Enabled field is set to Yes on the Settings > Hot Deployment page.
*Hot deployment is enabled for automatic package deployment when the watt.server.autodeploy.alwaysUseHotDeployment server configuration parameter is set to true.
By default, the automatic package deployment feature is disabled in Microservices Runtime. To enable automatic package deployment or configure other aspects of hot deployment, such as the system task execution frequency, see the section Enabling and Configuring Automatic Package Deployment Enabling and Configuring Automatic Package Deployment .