Glossary

This glossary provides terms and definitions for theIBM® UrbanCode Deploy 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 B C D E F G I L P R S V

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.
agent relay
A communication proxy for agents that are located behind a firewall or in another network location.
application
One or more computer programs or software components that provide a function in direct support of a specific business process or processes.
application process
A process that is associated with an application. Unlike a component or generic process, an application process is created from application-level steps. Typically, an application process invokes component processes, and orchestrates multi-component deployments. See also component process, generic process, process.
artifact
A deployable item such as a file, image, database, configuration material, or anything else that is associated with a software project. By default, artifacts are stored in CodeStation repository.

B

blackout
A setting that prevents deployments and snapshots from being scheduled. Blackouts solely affect the environment and application that they are applied to.

C

CodeStation
The artifact repository for IBM UrbanCode Deploy. CodeStation tracks artifact versions as they change and maintains an archive for each artifact.
component
A representation of deployable items and the user-defined processes that operate on them, usually by deploying them.
component inventory
A list of all of the resources on which a component is deployed. See also environment inventory, resource inventory.
component process
A series of user-defined steps that operate on component artifacts. See also application process, generic process, process.

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.

E

environment
A user-defined collection of resources that hosts an application.
environment inventory
A list of all of the component versions that are deployed to an environment. See also component inventory.

F

full version
A component version that contains all of the artifacts in the component, as opposed to an incremental version. See also incremental version, version.

G

generic process
Processes that are designed to run outside typical component or application processing. See also application process, component process, process.

I

incremental version
A component version that contains only the artifacts that are different from the previous version, as opposed to a full version. See also full version, version.

L

lifecycle model
A template for managing dependencies, artifacts, and deployments associated with every build of a given project. Lifecycle models can be reused for separate projects.
lock
A means of preventing uncommitted changes made by one application process from being perceived by another application process and for preventing one application process from updating data that is being accessed by another process. A lock ensures the integrity of data by preventing concurrent users from accessing inconsistent data.

P

process
Automated tasks that run on agents. See generic processes, component processes, and application processes. See also application process, component process, generic process.

R

relay servers
A proxy that can be used to access agents behind a firewall. Relay servers enable network-to-network communication.
resource
A user-defined construct that is based on the architectural model of IBM UrbanCode Deploy. A resource represents a deployment target.
resource inventory
A list pf all of the components that are deployed to an agent resource. See also component inventory.
role
A job function that identifies the tasks that a user can perform and the resources to which a user has access. A user can be assigned one or more roles.

S

snapshot
A collection of specific versions of components. Typically, a snapshot represents a set of component versions that are known to work together.

V

version
A group of resources that represent a particular version of a component. See also full version, incremental version.

Feedback