📄️ Tips and Tricks for Deployment Packages
This topic provides some helpful tips and tricks to use when managing deployment packages.
📄️ Package Version Handling
This topic emphasizes that when creating a Deployment Package in Deploy, the name field is mandatory.
📄️ Add a Package to Deploy
This topic explains how to add a package to Deploy.
📄️ Improve file.Folder Deployment Performance
This topic provides information about deploying a file.Folder or any type derived from it in Deploy. As part of the deployment, placeholders will be replaced in each of the files contained in the folder, and then the files are transferred to a temporary directory on the target host before moving them to their final deployment destination.
🗃️ z/OS Deployment
2 items
📄️ Using Placeholders in Deployments
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.
📄️ Disable Placeholder Scanning
This topic explains how to disable placeholder scanning in Deploy during package import.
📄️ Preparing Your Application for Deploy
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.
📄️ Extend the External Artifact Storage Feature
Artifacts are the physical files that make up a specific version of an application.
📄️ Add an Externally Stored Artifact to a Package
Artifacts are the physical files that make up a specific version of an application.
📄️ Configure Deploy to Fetch Artifacts From a Maven Repository
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.
📄️ Using the Deploy Manifest Editor
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..
📄️ Deploy Manifest Format
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.
📄️ Export a Deployment Package
This topic covers how to export a deployment package (DAR file) from Deploy using both the GUI and the command line.
📄️ Resolving Properties During Application Updates
This topic covers the process of resolving properties during application updates in Digital.ai Deploy.
📄️ Create a Deployment Package Using the Command Line
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.
📄️ Create a Deployment Package Using Ant
This topic describes how to create a Deploy package using Ant by utilizing the jar task.
📄️ Create a Deployment Package Using Jenkins
To enable continuous integration, Deploy can work with Jenkins CI server through the Jenkins Deploy plugin.
📄️ Create a Deployment Package Using Maven
To enable continuous deployment, the Deploy Maven plugin enables you to integrate Deploy with the Maven build system.