V6 Deployment Details

This document is used in all transfer, distribution, creating a package, import or export functions of Dollar Universe V6 objects.

Copying or not copying the object from its source location to the destination location can also be managed by the user. In any case, the object is never deleted from the source location.

Source

Type

Select the deployment source. If this document is opened after you select « Send to… » the selected objects in the original document will be preselected in this section.
Package

Check this option to extract package objects. The objects list contains a list of existing packages on the node. Check one or more boxes to extract the package objects selected.
Objects from local node

Check this option to extract objects from a local node.
- Area: Select the original Area of the objects. Transfers from one Area to another are possible regardless of the Area's origin and destination. For the objects common to all Areas (resources, applications ...), only the selection of an Area is required.
- Type: Click on the arrow to select the type of object to deploy.
Objects

The object list contains a list of objects selected on the local node and the selected Area. Check the boxes next to the objects to be deployed. The following buttons can be used to facilitate this selection:
- Select All: Selects all the lines (visible and not visible).
- Unselect All: Unselects all the lines (visible and not visible).
- Select Filtered: Selects all the visible filtered lines.
- Unselect Filtered: Unselects all the visible filtered lines.
If the Unselect All button is not activated, the previous filter selection will be combined with the current filter selection.
Translation Table

Click the down arrow to select a translation table among the existing ones. Or click New to create a new translation table. The user will then have the choice to create a saved table or a temporary table (not saved in the translation tables list, which will be used for this particular deployment, but which could not be reused nor reviewed later). For more details, please refer to section Translation Table Details - Actions.

Destination

A deployment can be requested on one of the following three destinations:

A Package
A Node
A Management Unit

Check the destination chosen.

Package
- New: Enter the new package name which will be created at the end of the deployment.
- Existing: Enter the existing package name or click on the arrow to select it in the local node packages list.
Node
- Node group selection: Enter the name of the node group defined on the local node or click on the arrow to select it in the list. If you want to select a single node, leave the field blank.
- Nodes List: This list displays all the DUAS V6 nodes known to the Univiewer Management Server or if the Selection by nodeview was filled, all the nodes from the node group.
  
  Check the boxes next to the nodes to be used as a deployment destination; the Select All / Select None buttons can be used to facilitate this selection.
  
  This list can be filtered; the Select filtered/Deselect filters buttons can be used to facilitate the selection.
- Area: Click the arrow to select the deployment destination Area; if the objects to deploy are common to all Areas (resources, applications ...), selecting any Area will work.
Management Unit

This destination must be used for object template distribution which must become operational on the targeted management units, calendar and Task template, and for job chain creations from Business Views.
- Management Unit List: This list displays all the Dollar Universe Management nodes.
  
  Check the boxes next to the nodes to be used as a deployment destination; the Select All/Select None buttons can be used to facilitate this selection.
  
  This list can be filtered; the Select filtered/Deselect filters buttons can be used to facilitate the selection.
- Area: Click on the arrow to select the deployment destination Area; if the objects to deploy are common to all Areas (resources, applications ...), selecting any area will work.

Enable the following:

The template becomes a non-template and is associated with the MU
The destination is calculated according to the MU
Job Chains are created based on the Business Views

Check this box so the templates are distributed as non-templates (so that tasks and calendars are operational) on the selected Management Units and to create Job Chains based on Business Views.

If this box is cleared, the objects will be distributed as a template and Job Chains will not be created.

Use the MU / Template name field of Tasks. If the corespondent MU doesn’t exist please select an MU in the list or the Task won’t be deployed:

When creating a template task, once the Template task option is selected, a field called Template name appears. To associate an existing MU with a template task, enter the name of the MU in this field. Then, during deployment, select this option.
This option allows the user to deploy without selecting a MU. It will consider the data provided in the task.
If a task is deployed with its specific tasks, the destination MU of the specific task is calculated regarding the session. And this even if the specific task is a template (the template name of a specific task is not used). If the session has an HDP for this specific task, it will be deployed on all the MU of the HDP.

Click Next to continue the deployment steps one by one or click Send to launch the deployment process using the default options.

The combination of options for deploying template and non-template tasks are described in the following table:

Task Type	Target	Enable the Following	Use MU/ Template name	Task Type after deployment	The task is deployed on... Description
Template	Node	N/A	N/A	Template	On the node / area
Template	MU	Not selected	Not selected	Template	On the selected MU
Template	MU	Selected	Not selected	Non-template	On the selected MU.
Template	MU	Selected	Selected	Non-template	On the MU entered in the template name field. If this does not correspond to an actual MU, the user will be prompted to select one.
Non-template	Node	N/A	N/A	Template	On the MU that was initially assigned to it.
Non-template	MU	Not selected	Not selected	Template	On the MU that was initially assigned to it.
Non-template	MU	Selected	Not selected	Non-template	On the selected MU
Non-template	MU	Selected	Selected	Non-template	On the selected MU and the MU that was initially assigned to it

If the target MU cannot be located, a pop-up window will appear notifying the user to select an existing MU.

From Dollar Universe 6.2, if a template task is deployed to an MU without the “Enable the following” option selected, the task will be associated with the target MU.

The options for deploying template, specific and general calendars are described in the following table:

Calendar Type	Target	Enable the Following	Use MU/ Template name	Calendar Type after deployment	The calendar is deployed on… Description
Template	Node	N/A	N/A	Template	On the node / area
Template	MU	Not selected	N/A	Template	The template name is the selected MU
Template	MU	Selected	N/A	Specific	On the selected MU
Specific	Node	N/A	N/A	Specific	MU or MU type entered in the “Specific Destination” field of the calendar
Specific	MU	Not selected	N/A	Template	MU or MU type entered in the “Specific Destination” field of the calendar
Specific	MU	Selected	N/A	Specific	On the selected MU
General	Node	N/A	N/A	General	On the node/area
General	MU	Not selected	N/A	General	This action is not possible.
General	MU	Selected	N/A	Specific	This action is not possible.

The options for deploying triggers with their associated tasks are described in the following table. Only the deployment options for the trigger will change the deployed task. The options for the task are ignored. If a trigger is deployed without the associated task(s), a task with the same name, Management Unit and nature must exist already on the deployment destination.

Target	Enable the Following	Use MU/ Template name	Task Type after deployment	The task is deployed on... Description
Node	N/A	N/A	Template	On the node / area with the same MU as the task of the source trigger.
MU	Not selected	Not selected	Template	The destination MU
MU	Selected	Not selected	Non-template	The destination MU.
MU	Selected	Selected	Non-template	On the task MU.

Objects and dependencies

This list displays the objects to be deployed and some dependent objects.

Application: Domains, application directories
Uproc: Application (not its dependencies), conditioning Uprocs, conditioning resources, incompatibility classes
Session: Uprocs of the session, used MU. If the session is developed (this occurs in the case where a task is deployed onto an MU: Uprocs are created on the node of the execution context and on the node of parent Uproc execution context, the session is created on all nodes)
MU: MU dependencies, MU directories, MU variables
Task: Session and its dependencies, specific tasks
DQM Queue: Physical queues for a logical queue
Trigger: Task if needed
Business View: Tasks and their dependencies

If deployed without using the template name: The Uprocs and their sessions are added.

Expand

Activated on an object in the list, the Expand button will add the dependent objects of the first level:
- Application: Domains, application directories
- Uproc: Application and its dependencies, conditioning Uprocs, conditioning resources, incompatibility classes
- Session: Session Uprocs and their dependencies, used MU and their dependencies
- MU: MU dependencies (and their dependencies), MU directories (and their dependencies: application and its dependencies), submission account by default, MU variables
- Task: Session and its dependencies, specific tasks and their dependencies, destination MU (if needed) and its dependencies, submission account, calendar, DQM queue and its dependencies, resource for a watcher task
- DQM Queue: Physical queues for a logical queue
- Trigger: Task (if needed) and its dependencies
- Business View: Tasks and their dependencies (and the dependencies of their dependencies)
If we deploy without using template task names: Uprocs and Sessions are added.

To include all dependency levels of an object (for example conditioning Uprocs of an Uproc of a task of a Business View), the user has to click the Expand button many times. When the list is stable, all dependencies have been explored and included in the package / deployment.

Update

For each object, the conflict resolution column indicates the action to be carried out if the object already exists on the target. To change this resolution select the row and click Update (or double click the line).

Depending on the object type, the possible resolutions are the following:

	Skip Node	Overwrite	Complete
Application	X	X
Business View	X	X
Calendar	X	X
Job Chain	X	X	X
Uproc Class	X	X
Submission account *	X	X
Domain	X	X
Runbook	X	X
Management Unit dependencies	X	X
Queue	X	X
Resource	X	X
Rule	X	X
Application Directory	X	X
Management Unit Directory	X	X
Session	X	X
Task	X	X
Management Unit	X	X
Uproc	X	X
Trigger	X	X

Skip node: This object’s deployment is abandoned on this node.
Overwrite: The existing object on the target node is replaced by the one deployed.
Append: (for job chains only) the new job chain Tasks from the Node of origin (or the new Tasks in the Business View of origin) are appended to the destination job chain.)

Set Password

If a submission account (on Windows, other than LocalSystem) must be deployed on a node, the user must enter the password (associated with this system user account) for the creation of the corresponding Windows user service.

Only the objects where the check boxes are selected are deployed. Click on Next at the bottom of the window to continue with the deployment steps.

Summary

This document lists all the objects that will be deployed. Select a line and click:

Add: The V6 Deployment Details window is displayed to add a new object to this list.
Update: Modify the conflict resolution policy, the Management Unit destination, object template characteristics.
Delete: to not deploy the object selected.

At the bottom of the window, click on:

Send: to launch the deployment process.
Cancel: to abandon this process.

The process is synchronous. A message box "Loading Data" is displayed when the deployment is in progress. At the end of deployment, the "List of deployments" document is displayed again.