UrbanCode Deploy has four main components:
For performance and other reasons, the UrbanCode Deploy controller servers do not do deployment work. All deployment activities including moving files, adjusting configuration, starting and stopping, interacting with load balancers, and interacting with ALM and ITSM tools is performed by Agents.
Many organizations require deployments and availability across multiple data-centers. IBM UrbanCode Deploy is architected to match the requirements of these organizations.
The Plugin System evolved from the realization that much of the value of an automation engine comes from the integrations with other systems. Without integrations, an automation system can simply execute scripts and thus becomes a distributed scheduler. Worse, those scripts must be kept up to date on the all the target servers.
UrbanCode Deploy Agents do work by executing plugin steps. Many plugins are available from IBM directly and clients are encouraged to build their own as well. The controller server sends the Agent instructions by telling it to run a plugin step, with information including:
- The plugin to run
- The name of the step from the plugin
- The required version of the plugin
- Parameters to pass to the plugin