Deploy Request Packages – Composite View

Selecting a Deploy Request displays the Deploy Request Packages screen, which has three views: Composite, Summary, and System. The first view displayed is the Composite view, shown in the following figure. The view being displayed can be changed by placing the cursor on the desired View name and pressing Enter.

Deploy Request Packages Screen – Composite View

This screen can be scrolled to the right. Note that the column order may vary for different users. The column order can be changed using the VP command.

Logical and Physical Packages

This screen is called the Composite view because it shows both the Logical and Physical packages. The Logical Package is identified on the line with the Package ID (PkgId). Each line below that containing a different System represents a separate Physical Package.

Important

A Logical Package represents the deployment of a set of component parts to one or more Targets. The Physical Package represents the deployment of those components to one Target System only. Because most sites will probably deploy to a single Target, this concept can easily be missed.

The following table describes the columns on the Composite view of the Deploy Request Packages screen (preceding figure):

Column	Description
PkgId	Unique ID that identifies a Package
Sub	Deploy Sub-Environment.
System	Target System
Date Strt	Date that the Package began deployment
Time Strt	Time that the Package began deployment
Date End	Date that the Package successfully ended deployment.
Time End	Time that the Package successfully ended deployment.
DplyCat	Deploy Category
Status	The Logical Package status is derived from the individual Physical Package statuses. These statuses are described later in this section.
Date/Time Impl	Date/Time that the Deployment Implementation is to begin.
Date/Time Actv	Date/Time that the Deployment Activation (if any is defined) is to begin.

Logical Package Statuses

This status is derived from the statuses of all the Physical packages and can have the following values:

Value	Description
Blank	No processes have yet been identified.
Staged	All deployable parts are staged onto their respective Target systems
Implemented	This Package undergoes Activation, and the Implementation processes are complete.
Completed	All Deploy processes are complete (i.e. if both Implementation and Activation are defined then both are completed successfully. If only Implementation is required then this has completed successfully).
Failed	One or more Physical Packages has failed.

Physical Package Statuses

The Physical Package Status is constructed of two parts:

XX:Status

where XX is a two-character representation of the process that the status relates to.

Status Processes and their various statuses are listed in the following table.

Physical Package Statuses

Process	Status	Description
STStaging	Wait Time	This status is not commonly seen for Staging because there is no specific Date/Time constraint for the Staging process. A Physical Package can have this status for 30 seconds or less due to the internal Deploy Scheduler.
	Ready	All conditions have been met for the Staging Process to begin. This status could indicate that the Target CT Task is not running.
	Dispatched	CT Task has been awakened to start Staging.
	Executing	CT Task is performing the Staging process.
	Complete	Staging is complete.
	Failed	Staging has failed.
	Terminated	Overall Request was terminated for Packages that were not Complete or Failed when the Terminate was issued.
IMImplementing and ACActivating	Wait Time	Implementation is waiting on the Implementation Time, or Activation is waiting on Activate Time.
	Ready	All conditions have been met for the Implement or Activate process to begin. This status could indicate that the Target CT Task is not running.
	Dispatched	CT Task has been awakened to start the process.
	Held	Process has been started in a HELD status – option not currently supported.
	Wait External	An External process has been defined, and ISPW is waiting for it to start.
	Executing	Implementation/Activation is executing.
	Complete	Implementation/Activation process is complete.
	Failed	Implementation/Activation process has failed.
	Terminated	Indicates that the overall Request was terminated for Packages that were not Complete or Failed when the Terminate was issued.

Package Operations

The following operations are valid against a Logical Package:

S—Select Package to list Items.
M—Select Package details for viewing.

Sections later in this chapter describe each of these operations.