Deploying Applications


This page is about the deployment process in Appian and the different ways you can deploy updates to your applications. To learn how to deploy your applications and patches, see Deploy to Target Environments.

The Deployment Process

Deploying packages is how you release your application updates to end users and deliver value. To deploy, you select and package the objects you want to deploy, and then move those changes from a source to a target environment.

Import Export Packages

There are three methods for deploying a package in Appian:

  • Compare and Deploy - Guided push-button deployment of applications and patches across environments.
  • Export and Import - Manually import and export applications and patches.
  • Customized Deployment - Tailor your deployment process and integrate with third-party systems with this tool.

Appian allows you to deploy different types of packages:

  • Applications: Deploy an application when you are introducing a completely new business solution into the target environment.
  • Patches: Deploy a patch when you are introducing a new update to an existing application in the target environment. You can also deploy bulk patches to multiple applications.
  • Admin Console Settings: Deploy Admin Console settings only when you want to make changes to the Admin settings in the target environment.

Make sure you understand object-specific behavior before importing or exporting packages for deployment.

Your packages may depend on other files or scripts such as:

  • Import customization file: When your deployment includes environment specific values, such as usernames and passwords, Appian generates an import customization file for you automatically. You can then modify the file to include the appropriate values for the target environment.
  • Database scripts: You can directly deploy database scripts alongside your application changes or allow Appian to manage your database structure. In addition, you can always manually deploy database scripts to a specific environment, following change management best practices.
  • Plug-ins: Plug-ins allow developers to extend Appian functionality. On Cloud sites, system administrators can deploy Cloud-approved plug-ins to an environment through the Admin Console. On self-managed sites, plug-ins can be hot deployed by placing the jar in the specified directory.

Direct Deployment

Direct deployments are an out-of-the-box approach to simpler deployments, with fewer manual steps and predictable outcomes. This supports continuous delivery by allowing you to deploy packages frequently and reliably.

For those looking for a streamlined deployment process with minimal setup effort, Appian recommends using compare and deploy.

Post-Deployment Processes

A post-deployment process is a process that automatically runs after a direct deployment has finished on an environment. From this process, you'll be able to access key information about the relevant deployment.

Post-deployment processes provide flexibility, which allows you to automate tasks, leverage third-party tools, and customize your workflow. Automating your post-deployment steps helps you reduce manual tasks and errors.

Customized Deployment

Appian offers a set of tools that helps organize your deployment processes and further reduces manual steps: the Automated Deployment Manager.

The Automated Deployment Manager consists of two tools:

  • Automated Versioning Manager: Integrates with version control systems, such as Git, to manage changes for Appian applications.
  • Automated Import Manager: Automates application and patch deployments, including database scripts and Admin settings.

These tools are best used in conjunction to enhance your deployment process.

For more information about the full benefits of continuous delivery through automated deployment, see the DevOps Quick Start Guide.

Open in Github Built: Wed, Aug 17, 2022 (01:05:05 PM)

On This Page