Integration Server 11.1 | Integration Server Administrator's Guide | Managing Packages | Automatic Package Deployment | How Automatic Package Deployment Works
 
How Automatic Package Deployment Works
In automatic package deployment, the packages that you want Integration Server to deploy automatically are placed in a location that Integration Server periodically scans for new or updated custom packages. Integration Server executes a system task named “Auto Package Deployer” that scans the folder and checks for new or updated custom packages. When Integration Server finds new or updated custom packages, Integration Server does one of the following:
*For a new package, Integration Server installs, archives, and activates the package.
*For an updated custom package, Integration Server does one of the following:
*If hot deployment is enabled for automatic package deployment, Integration Server uses the block-and-wait approach employed by hot deployment to deploy the package. This ensures that Integration Server assets are available for processing without any noticeable downtime. For more information about how hot deployment works, see Hot Deployment of Packages.
*If hot deployment is not enabled, Integration Server 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 Integration Server. 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 Integration Server. 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.