34 docs tagged with "package"

This topic explains how to add a package to Deploy.

Artifacts are the physical files that make up a specific version of an application.

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 details how Deploy manages archive artifacts (like ZIP files) and folders, highlighting specific characteristics.

This topic covers creating a package retention policy (policy.PackageRetentionPolicy) to manage package retention based on a regular expression

This topic describes how to fetch artifacts from a Maven repository. You can access artifacts stored in a Maven repository using the fileUri property of Deploy artifacts. To use this feature, you must configure the Maven repositories that Deploy will search for artifacts.

In Digital.ai Deploy, a copy strategy is the mechanism used to transfer file.Folder artifacts to target hosts using the overthere.Host library.

This topic describes how to create a Deploy package using Ant by utilizing the jar task.

To enable continuous integration, Deploy can work with Jenkins CI server through the Jenkins Deploy plugin.

To enable continuous deployment, the Deploy Maven plugin enables you to integrate Deploy with the Maven build system.

You can use the command line to create a deployment package (DAR file) that can be imported into Deploy. This example packages an application called PetClinic that consists of an EAR file and a resource specification.

Customize file.Folder deployments to control how Deploy handles empty folders, performance optimization (isForceArchive), legacy behavior, connection retry logic, and debug logging.

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

This topic provides information about the Deploy concepts for using Deploy.

The manifest file included in a deployment package (DAR file) describes the contents of the archive for Deploy. When importing a package, the manifest is used to construct CIs in Deploy's repository based on the contents of the imported package. The format is based on XML.

This topic explains the Deploy repository in XL Deploy, detailing its role in storing and managing deployment packages, configurations, and artifacts essential for the deployment process.

This topic provides information about Deployables and deployeds.

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 disable placeholder scanning in Deploy during package import.

This topic covers how to export a deployment package (DAR file) from Deploy using both the GUI and the command line.

Artifacts are the physical files that make up a specific version of an application.

A file.Folder configuration item (CI) in Digital.ai Deploy allows you to deploy a directory structure either as an exploded folder or from an archive onto a target host. The source for a file.Folder can be a directory, a TAR, ZIP, or other supported archive format. During deployment, the contents are extracted and copied to the destination host as a folder, using the most appropriate copy strategy for performance and correctness.

This topic covers how Deploy checks application dependencies.

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:

This topic emphasizes that when creating a Deployment Package in Deploy, the name field is mandatory.

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.

This topic covers the process of resolving properties during application updates in Digital.ai Deploy.

This topic provides some helpful tips and tricks to use when managing deployment packages.

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.

Placeholders are configurable entries in your application that will be set to an actual value at deployment time. This allows the deployment package to be environment-independent and reusable. At deployment time, you can provide values for placeholders manually or they can be resolved from dictionaries that are assigned to the target environment.

This topic provides information on the Deploy Manifest Editor, an open-source, stand-alone tool for Microsoft Windows that helps you create valid deployit-manifest.xml files for your deployment packages..

This guide explains the process of deploying files to z/OS systems using the new SSH-SFTP connection. Previously, deployments required manual ASCII to EBCDIC (CP1047) transcoding when using SCP or SFTP, making the process more complex and time-consuming. With the new SFTP-only approach, text files are automatically converted to EBCDIC (CP1047) during transfer, simplifying deployments.

Objective