This document provides an overview of UrbanCode Deploy v6.1 from IBM. It begins with an introduction and objectives for the module. It then covers key concepts like applications, environments, processes, blueprints, approvals, notifications, properties and more. Screenshots with annotations are provided to demonstrate how to create and configure these different elements in the tool. Best practices, examples and further resources are also included at the end. The goal is to teach users how to properly scope applications, create environments and processes, use approvals/notifications, properties and blueprints to orchestrate deployments with UrbanCode Deploy.
Per Thomas Hudson: Application process steps do not come from plug-ins. Component process steps come from plug-ins. Users cannot add application process steps the way they can add or create plug-ins. Application processes run on the server; component processes run on an agent. So, nothing operates on plug-ins. Component processes (created from plug-in steps) operate on plug-ins. Application processes can call component processes.