📄️ Tips and Tricks for Deployment Packages
This topic provides some helpful tips and tricks to use when managing deployment packages.
📄️ Package Version Handling
When you create a Deployment Package, name is a mandatory field. It can take various formats depending on the need but it is recommended to follow a standard naming convention so that the Deploy application can sort them the way you want.
📄️ Add a Package to Deploy
To deploy an application with Deploy, you must supply a deployment package. It contains the files (artifacts) and middleware resources that Deploy can deploy to a target environment.
📄️ Improve file.Folder Deployment Performance
Suppose you are doing a deployment where one of the deployables is a file.Folder or any type derived from this. 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.
📄️ 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
When importing a package, Deploy scans the artifacts contained in the package for placeholders that need to be resolved during a deployment. You can turn off placeholder scanning using one of the following methods described in this topic.
📄️ Preparing Your Application for Deploy
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. For example, an application binary, configuration files, or web content. When adding an artifact to a deployment package, you can either:
📄️ Add an Externally Stored Artifact to a Package
Artifacts are the physical files that make up a specific version of an application. For example, an application binary, configuration files, or web content. When adding an artifact to a deployment package, you can either:
📄️ 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
The Deploy Manifest Editor is 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
Export a deployment package (DAR file) using the Deploy GUI
📄️ Resolving Properties During Application Updates
When you update a deployed application, Deploy resolves the properties for the deployeds in the application in the same way that it does for the initial deployment of the application. This means:
📄️ 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
Creating a Deploy package via Ant is possible using 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. The plugin supports:
📄️ Create a Deployment Package Using Maven
To enable continuous deployment, the Deploy Maven plugin enables you to integrate Deploy with the Maven build system. For more information, see Deploy Maven plugin.