Deploy Concepts

ISPW Deploy uses various concepts to manage the deployment of software.

Deploy Concepts

The preceding figure shows an example of the Deploy concepts that will be explained in this section:

Deploy System

A Deploy System identifies a particular system image on which many different products may be implemented. This refers to some physical computer system, although for operating systems such as z/OS, it may be a logical system image (LPAR).

In the preceding figure, there are four Deploy Systems: z/OS LPARs 1 through 4.

Deploy Environment

A Deploy Environment represents the logical execution environment where a specific version of one or more software products is implemented. A software product may physically require its components to be implemented in execution environments that are on disparate platforms and systems. However, where this all forms a single software product, it can be defined as one logical Deploy Environment.

In the preceding figure - Deploy Concepts, there are two Deploy Environments:

Training
Production

Deploy Sub-Environment

The Deploy Sub-Environment represents the physical execution environment(s) where a software product’s components need to be deployed.

For example, a software product may contain some components that need to be deployed to a z/OS CICS system and other components that need to be deployed to a z/OS IMS system. Each of these would be defined as separate Sub-Environments.

In the preceding figure - Deploy Concepts, there are three Sub-Environments defined for the Deploy Environment “Production”:

CICS
IMS
z/OS

Sub-Environments may also be used to separate the major components of a product, even when they are deployed on the same system. The only absolute requirement to use them is when components of a product are being deployed to disparate systems.

Deploy Target

Sub-Environments contain combinations of various Deploy Types (such as Load modules, DBRMs, etc.) and Deploy Systems. Where each Sub-Environment is implemented on a Deploy System, it is called a Deploy Target.

In the preceding figure - Deploy Concepts, an example of a Deploy Target would be the definition data required to implement Sub-Environment “CICS” to System “z/OS CICS System”.

Defining Deploy Targets

Defining Deploy Targets involves specifying the actual system images where the Sub-Environment is to be deployed. In other words, a Deploy Target is the instance of a deployment definition between a Sub-Environment and System.

Some product implementations require deployment onto multiple system images to meet performance or service level agreements. In this case, the deployment on each system image is exactly the same. The Deploy Target concept supports this requirement.

In the preceding figure - Deploy Concepts, an example is the definition of a second Target for Sub-Environment “z/OS Executables” to System “z/OS LPAR 1”.

Another Deploy Example

The following example shows a Deploy Environment called “Production” that includes two physical Sub-Environments: A and B.

Deploy Environment PRODUCTION

Each of these Sub-Environments contains a combination of various Systems and Types (CICSLOAD, DBRM, etc.). For instance, these Sub-Environments may represent:

SubEnv A—CICS and Batch components (two Targets on a z/OS System)
SubEnv B—IMS components (one Target on a z/OS System).

Deploy Requests

A Deploy Request is an instruction to deploy one or more software component parts into a Deploy Environment.

A Deploy Request contains a request header, which holds basic details about the request, and one or more Deploy Packages.

Deploy Packages

A Deploy Package is used to group together all the software component parts that are destined for the same Deploy Sub-Environment and have the same Deploy Category. A Deploy Package contains one or more Deploy Package Items.

Deploy Package Items

A Deploy Package Item specifies a software component part that is to be deployed. It will be deployed to all Deploy Targets that are defined for the Sub-Environment specified on the Deploy Package that contains the item.

Deploy Request Contents

An example of a Deploy Request is shown in the following figure.

Deploy Request Contents