52 docs tagged with "deployment"

This topic describes how to handle a simple case by executing a remote shell command on a server.

This topic describes dependencies among different versions of different applications.

This topic describes how to define dependencies among different versions of applications in Deploy.

This topic describes how to use Deploy with AWS CodePipeline.

This topic describes how to specify multiple orchestrators for each deployment to achieve complex use cases.

This topic describes how to add and remove an extension on JBoss Plugin using Deploy server. It assumes you have the JBoss Domain plugin installed.

This topic describes how to configure and deploy the application by logging subsystem enabled on JBoss server using Deploy.

You can configure the following advanced Deploy client settings in /centralConfiguration/deploy-client.yaml.

This topic describes how to configure system properties on JBoss server using Deploy.

This topic provides information about how to configure task execution engine.

This topic covers the creation of rules in Deploy, which define the steps to be included in a deployment plan. Each rule in the xl-rules.xml file specifies a number of steps to add to the deployment plan.

This topic describes how to configure an environment for running batch application and manage batch using the Batch-Jberet subsystem in JBoss DM plugin.

This topic outlines the steps to connect Deploy to IBM WebSphere Application Server (WAS) and deploy a sample application.

This tutorial describes how to deploy an application on Apache Tomcat.

This tutorial describes how to deploy an application on GlassFish.

This tutorial describes how to deploy an application on JBoss EAP 6 or JBoss AS/WildFly 7.1+.

This topic provides a guide for setting up and deploying a sample application using Deploy and the Microsoft IIS plugin.

This tutorial describes how to deploy an application on Oracle WebLogic.

This topic outlines the process for deploying an application using the Deployment Wizard in Deploy, including options for managing and troubleshooting deployments.

This topic describes how to use the Deploy command-line interface (CLI) to deploy an artifact from a Maven repository such as Artifactory or Nexus.

This topic provides information about Deploy Microsoft IIS configuration elements and attributes.

This topic describes a deployment that consists of all actions needed to install, configure, and start an application on a target environment.

This topic explains how to download and interpret usage reports from the Dashboard tab in Reports.

An orchestrator combines the steps for the individual component changes into an overall deployment workflow.

This topic covers tasks in Deploy, which are activities with steps for deploying, updating, or managing applications that can be scheduled, recovered, and manually archived post-execution.

This topic covers how Deploy checks application dependencies.

This topic covers how satellite servers affect a deployment plan.

This topic describes using a CI tool plugin to interact with Deploy. However, as a preferred alternative starting with version 9.0, you can utilize a wrapper script to bootstrap XL CLI commands on your Unix or Windows-based Continuous Integration (CI) servers without having to install the XL CLI executable itself. The script is stored with your project YAML files and you can execute XL CLI commands from within your CI tool scripts. For details, see the following topics:

You can use the Deploy rules system and a PowerShell script to find and update the value of a previously deployed property with a new deployed property value.

You can use the Deploy health REST endpoint (/deployit/ha/health) with a GET or a HEAD request to check if the Deploy node is up and accessible.

This topic describes the monitoring section in the Deploy user interface, which provides an overview of deployment tasks that are not archived.

This topic describes the issues caused by concurrent deployments in Deploy when using custom microservices deployment technologies. Middleware limitations may restrict the target environment to performing only one deployment at a time, leading to potential conflicts.

This topic explains how Deploy uses the Unified Deployment Model (UDM) to structure deployments. In this model, deployment packages are containers for complete application distribution. These include application artifacts (EAR files, static content) and resource specifications (datasources, topics, queues, and others) that the application requires to run.

When you set up an initial deployment or an update, you can use the Preview option to view the deployment plan that Deploy generated based on the deployment configuration. As you map deployables to containers in the deployment configuration, the Preview will update and show changes to the plan.

When you define an XML or script rule in Deploy, you use expressions or scripts to define its behavior. These are written in Jython, a combination of Python and Java.

Using Deploy, you can schedule deployment tasks for execution at a specified moment in time.

This topic describes how to schedule or reschedule tasks in Deploy for execution at a specified date and time. You can schedule or reschedule tasks that are in a PENDING or SCHEDULED state.

Deploy can stage artifacts to target hosts before deploying the application. Staging is based on the artifact Checksum property, and requires that the plugin being used to deploy the artifact supports staging.

This topic describes the steps and step lists in Deploy.

This topic provides information on how to stop, abort, or cancel a deployment in Deploy.

The rules system works with the Deploy planning phase. You can use XML or Jython to specify the steps that belong in a deployment plan and how the steps are configured.

In Deploy, an orchestrator combines the steps for individual component changes into an overall deployment or provisioning workflow.

This topic provides information on how to undeploy an application. To remove an application and its components from an environment, you need to undeploy the application. Similarly, to tear down a cloud-based environment provisioned by Deploy, you need to deprovision it.

The planning phase takes place when the global structure of the deployment has been determined, and Deploy needs to fill in the steps needed to deploy the application. The goal of planning is to generate a deployment plan. It uses the structured deployment generated by the orchestration phase. Plugins and rules contribute steps to the plan.

This topic provides information on updating packages in Deploy. You do not need to manually create a delta package to perform an update, as the Deploy auto-flow engine automatically calculates the delta between two packages.

This topic provides information on how to update an app (EAR/WAR) in IBM WebSphere AS.

Deploy rules enable you to use XML or Jython to specify the steps that belong in a deployment plan and how the steps are configured. Several Deploy plugins include predefined rules that you can use when writing rules. For more information on rules, see Get started with rules.

You can use the tagging feature to configure deployments by marking which deployables should be mapped to which containers. By using tagging, in combination with placeholders, you can prepare your deployment packages and environments to automatically map deployables to containers and configuration details at deployment time.

Deploy contains information about your applications, environments, infrastructure, and deployments. Using the reporting functionality, you can gain insight into the state of your environments and applications.

In Deploy you can view the deployment pipeline for an application or a deployment/provisioning package. In the deployment pipeline you can view the sequence of environments to which an application is deployed during its lifecycle. The deployment pipeline also allows you to see the data about the last deployment of an application to each environment. You must first define a deployment pipeline for each application you want to view.

Deploy uses the FreeMarker templating engine to allow you to access deployment properties such as such as the names or locations of files in the deployment package.

You can view the history of successful deployments of application versions to an environment. This is useful when you want to determine placeholder value changes between versions for an environment, determine who made a specific change, and to support deployment rollbacks.