Application environments

An environment is a user-defined collection of resources that hosts an application.

An environment is the application's mechanism for bringing together components with the agent that actually deploys them. Environments are typically modeled on some stage of the software project lifecycle, such as development, QA, or production. A resource is a deployment target, such as a database or Java™ Platform, Enterprise Edition container. Resources are usually found on the same host where the agent that manages them is located. A host can be a physical system, virtual machine, or be cloud-based.

Environments can have different topologies, for example: an environment can consist of a single system; be spread over several systems; or spread over clusters of systems. Environments are scoped to applications. Although multi-tenant systems can be the target of multiple applications, most IT organizations use application-specific environments. Additionally, approvals are generally scoped to environments.

IBM® UrbanCode Deploy maintains an inventory of every artifact that is deployed to each environment and tracks the differences between them.

Environment properties can be created with the environment's Properties pane (Applications > [selected application] > Environments > [selected environment] > Properties).

A value that is set on a component environment overrides a value with the same name set directly on an environment property. Component environment properties enable you to centralize properties, tracking type and default values, for instance. Environment properties provide ad hoc lists of property=value pairs.

Referenced: ${p:environment/propertyName}.


Feedback