Add a deployment plan step using the Command plugin
This topic describes how to handle a simple case by executing a remote shell command on a server.
This topic describes how to handle a simple case by executing a remote shell command on a server.
This topic describes how to specify multiple orchestrators for each deployment to achieve complex use cases.
With Deploy modular architecture you can change and extend components while maintaining a consistent system.
This topic explains how to disable rules in Deploy by modifying the xl-rules.xml file
An orchestrator combines the steps for the individual component changes into an overall deployment workflow.
This topic helps you to get started with Deploy rules.
Deploy is a model-driven deployment solution. Users declaratively define the artifacts and resources that they need to deploy in a package, which is a ZIP file with a deployit-manifest.xml file, and Deploy figures out how to install the components in a target environment using rules. Rules are used to teach the Deploy execution engine how to generate your deployment steps in a scalable, reusable, and maintainable way.
This topic covers how satellite servers affect a deployment plan.
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.
This topic describes the steps and step lists in Deploy.
When you use the Preview option of the deployment plan, you can also see the Stitch preview for it, by using the toggle button to switch between two views. After clicking on the Stitch preview toggle, you can also browse and view Stitch invocation details.
In Deploy, an orchestrator combines the steps for individual component changes into an overall deployment or provisioning workflow.
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.
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.
A script rule adds steps and checkpoints to a plan by running a Jython script that calculates which steps and checkpoints to add.
The Deploy rules system enables you to use XML or Jython to specify the steps that belong in a deployment plan and how the steps are configured.