Glossary

This glossary provides terms and definitions for the IBM® UrbanCode Release software and products.

The following cross-references are used in this glossary:
  • See refers you from a nonpreferred term to the preferred term or from an abbreviation to the spelled-out form.
  • See also refers you to a related or contrasting term.

For other terms and definitions, see the IBM Terminology website (opens in new window).

A C D E G L P R S

A

agent
A program that runs on a remote computer and communicates with the IBM UrbanCode Deploy server. Agents run processes on deployment target systems.
application
One or more computer programs or software components that provide a function in direct support of a specific business process or processes.

C

component
A representation of deployable items and the user-defined processes that operate on them, usually by deploying them.

D

deployment
A multistage process that retrieves the output of a build, packages the output, and moves the package to another location so it can be tested or run.
deployment plan
The segments and segment-related tasks in a deployment.

E

environment
A user-defined collection of resources that hosts an application.

G

gate
A requirement that must be met before an application can move on to the next phase.

L

lifecycle
The phases in a release. A lifecycle is a template for the stages of work in a release.

P

phase
A specific team's work on the applications in a release.

R

release
A collection of applications that are deployed together. An application can be part of any number of releases.

S

segment
A period of time in a deployment plan. Deployment plans can group tasks into segments to specify when tasks are run relative to each other.
snapshot
A collection of specific versions of components. Typically, a snapshot represents a set of component versions that are known to work together.

Feedback