Deploying Applications

Overview

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 packages, see Deploy to Target Environments.

The deployment process

Deploying packages is how you release your application updates to end users and deliver value. A package is a collection of Appian application changes that a developer can deploy to another environment. You can use packages containing new and updated objects to enhance an application in the target environment via a deployment. Preparing a package is an important step in the deployment process and involves understanding what changes you need to deploy and how these changes will affect your target environment.

To deploy, you prepare a package with the relevant objects, and then move it from a source to a target environment.

Import Export Packages

There are three methods for deploying a package in Appian:

In addition to deploying enhancements, you can also use the following types of packages to deploy new applications and change administration settings in the target environment:

  • Applications: Deploy an application when you are introducing a completely new business solution into the target environment.
  • Administration Console Settings: Deploy Administration Console settings only when you want to make changes to the Administration 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. In addition, you can deploy plug-ins that exist in one environment to another using compare and deploy.

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.

External deployment

Appian has native deployment APIs that can be called from external tools, such as Jenkins. There are five endpoints that allow you to inspect and deploy packages, import customization files, and database scripts.

This allows you to programmatically trigger deployments and integrate your Appian release into an automated pipeline. You can configure your pipeline once and run it the exact same way for all future deployments, saving time and avoiding manual errors.

In order to programmatically deploy Administration Console settings or tightly integrate with a version control system to store and retrieve package files, use the Automated Deployment Manager. For more information on setting it up, see the DevOps Quick Start Guide.

Post-deployment processes

A post-deployment process is a process that automatically runs after a direct or external 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 reduces manual tasks and the potential for human error.

Open in Github Built: Mon, Nov 15, 2021 (03:03:53 PM)

On This Page

FEEDBACK