Versions Compared

Version Old Version 1 New Version 2
Changes made by

Silvia Neag (Unlicensed)

Silvia Neag (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.



...

Image Removed
Contents
OS Virtualization
1.1 Activities
1.1.1 Connect To PVS
1.1.2 Disconnect From PVS
1.1.3 Add vDisk
1.1.4 Append vDisk To Device
1.1.5 Set vDisk Build Version
1.1.6 Set Access Mode vDisk
1.1.7 Remove vDisk From Device
1.1.8 Remove vDisk
1.1.9 Create Device
1.1.10 Set Device
1.1.11 Add Device To Domain
1.1.12 Remove Device
1.1.13 Get vDisk Info
1.2 Workflow
1.3 Parameters
1.3.1 General Guidelines
1.3.2 Connect To PVS
1.3.3 Disconnect From PVS
1.3.4 Add vDisk
1.3.5 Set Device
1.3.6 Set vDisk Build Version
1.3.7 Set Access Mode vDisk
1.3.8 Append vDisk To Device
1.3.9 Remove vDisk From Device
1.3.10 Remove vDisk
1.3.11 Create Device
1.3.12 Get vDisk Info
1.4 On Execution Workflow
This section deals with all Citrix Provisioning Server 5.0 related Activities.

...

Table of Contents
indent2


  
Image Added
 
 
 

Anchor
_Toc331166145
_Toc331166145
Activities

 

Anchor
_Toc331166146
_Toc331166146
Connect To PVS


This activity connects to a Provisioning Server host.

Anchor
_Toc331166147
_Toc331166147
Disconnect From PVS


This activity disconnects from a Provisioning Server host.

Anchor
_Toc331166148
_Toc331166148
Add vDisk


This activity imports and adds a vDisk with a given name.

Anchor
_Toc331166149
_Toc331166149
Append vDisk To Device


This activity adds a vDisk to an existing Device on Provisioning Server farm.

Anchor
_Toc331166150
_Toc331166150
Set vDisk Build Version


This activity sets a new value for the Build property of the specified vDisk.

Anchor
_Toc331166151
_Toc331166151
Set Access Mode vDisk


This activity sets a new value for the Access Mode property of the specified vDisk.

Anchor
_Toc331166152
_Toc331166152
Remove vDisk From Device


This activity removes the specified vDisk from the existing Device on Provisioning Server farm.

Anchor
_Toc331166153
_Toc331166153
Remove vDisk


This activity removes the specified vDisk from the Provisioning Server farm.

Anchor
_Toc308515303
_Toc308515303
Anchor
_Toc331166154
_Toc331166154
Create Device


This activity creates a new device on the Provisioning Server farm.

Anchor
_Toc308515304
_Toc308515304
Anchor
_Toc331166155
_Toc331166155
Set Device


This activity sets new parameters for an existing device.

Anchor
_Toc308515305
_Toc308515305
Anchor
_Toc331166156
_Toc331166156
Add Device To Domain


This activity adds the device to the specified domain.

Anchor
_Toc331166157
_Toc331166157
Remove Device


This activity removes a specified device from Provisioning Server Farm.

Anchor
_Toc308517348
_Toc308517348
Anchor
_Toc331166158
_Toc331166158
Get vDisk Info


This activity returns a collection with the specified vDisk properties and their correspondent values on Provisioning Server farm.

Anchor
_Toc331166159
_Toc331166159
Workflow


Workflow name: OSVirtualization_workflow
Workflow description:

Activities are the building blocks of WF , they are a unit of work in WF. Activities can be composed together into larger Activities. When an Activity is used as a top-level entry point, it is called a "Workflow".
In WF4, the root activity is called „Sequence". This activity is added by default in WF Designer panel when a new workflow is created. All activities that are placed inside of a sequence are called child activities


...

Variables and Arguments
In general terms of parameters in WF4, there are two main concepts: Variables and Arguments. The definitions for each are that Variables are used to store data within a workflow and Arguments are used to passing data in/out of a workflow. The concept of „binding" parameters has been replaced with the usage of variables and arguments.
Variables are to be used in a workflow whenever the need to store data is limited to the current workflow and the output/input of the workflow is not used anywhere else (for example in Admin Suite).
Arguments are to be used whenever the input parameters of an activity are given by the user using for instance a web-based application, (for example when running a workflow in Admin Portal) and if the output of an activity is to be returned and used outside of DesignStudio application . (for example Admin Portal)
All parameters that have an Expression editor in Activity Properties panel can be used for value storage and passing, through variables and arguments.
Example: Collection From String activity
Image Removed
Defined IN arguments, with default value to be filled in by the user when running the workflow:
Image Removed
Defined variables to store the output of the Collection From String activity:
Image Removed
Parameters with different editors, like Folder editors or ComboBox cannot be bound to variables nor arguments.
Activity Properties
In general terms of activities properties, there are two main concepts: „Stop On Error" and „Enabled".
Image Removed
The concept of „Stop on error" and „Enabled"mechanisms are defined for runtime purposes.
Image Removed
„Stop on error" Property
On runtime (nn. Start button), if the Stop on error property is set to Yes for an activity and an error or exception is thrown, the execution of the workflow stops on the activity that caused the error /exception to be thrown.
Image Removed
Image Removed
If set to No, the error message is displayed in Tracking Data panel, but the execution of the workflow continues.
Image Removed
Image Removed
„Enabled" Property
On runtime, if the Enabled property is set to Yes for an activity,the activity is executed.
Image Removed
Image Removed
If set to No, the activity will not be executed on runtime.
Image Removed
WF Designer panel view:
Image Removed
Tracking Data panel view:
Image Removed

Activities Parameters

Anchor
_Toc331166162
_Toc331166162
Connect To PVS


The SiteIP,Username and Server Domain parameters may be given by the user via IN arguments.
The Password Binding parameter has no default value because its value must be given encrypted when run outside the Design Studio (for example Admin Portal).
The Password parameter is a Password editor type. When clicked, the Password editor opens and the user may specifiy the desired password.
The Protocol parameter is a combobox, when clicked it displays a drop down list and the user may choose the desired option.


The output returned by this activity is stored to variable Connection:

Anchor
_Toc331166163
_Toc331166163
Disconnect From PVS


The input parameter Connection takes the value stored in the variable Connection, which contains the result of Connection To PVS activity.

Anchor
_Toc331166164
_Toc331166164
Add vDisk


All parameters besides Connection are given by the user via IN arguments defined in the Parameters Area from WF Designer panel.
The Connection parameter takes the value stored in the variable defined for Connect To PVS activity.


The output returned is stored in two variables:

Anchor
_Toc331166165
_Toc331166165
Set Device


The Connection parameter takes the value stored in the variable defined for Connect To PVS activity.
All parameters besides Connection and Boot From are given by the user via IN arguments defined in the Parameters Area from WF Designer panel.




The output returned is stored in one variable:

Anchor
_Toc331166166
_Toc331166166
Set vDisk Build Version


The Connection parameter takes the value stored in the variable defined for Connect To PVS activity.


The output returned is stored in the variable setBuildVersion_output.

Anchor
_Toc331166167
_Toc331166167
Set Access Mode vDisk


The Connection parameter takes the value stored in the variable defined for Connect To PVS activity.
All parameters besides Connection and Access Mode are given by the user via IN arguments defined in the Parameters Area from WF Designer panel.




The output returned is stored in the variable setAccessModevDisk_output.

Anchor
_Toc331166168
_Toc331166168
Append vDisk To Device



The Connection parameter takes the value stored in the variable defined for Connect To PVS activity.
All parameters besides Connection and Remove existing vDisk are given by the user via IN arguments defined in the Parameters Area from WF Designer panel.



The output returned by this activity is stored in the variable Append_status.

Anchor
_Toc331166169
_Toc331166169
Remove vDisk From Device


The Connection parameter takes the value stored in the variable defined for Connect To PVS activity.
All parameters besides Connection and Target Device Name are given by the user via IN arguments defined in the Parameters Area from WF Designer panel.


Anchor
_Toc331166170
_Toc331166170
Remove vDisk



The Connection parameter takes the value stored in the variable defined for Connect To PVS activity.
All parameters besides Connection and Delete From Disk are given by the user via IN arguments defined in the Parameters Area from WF Designer panel.


The output returned by this activity is stored in the variable RemovevDisk_status.

Anchor
_Toc331166171
_Toc331166171
Create Device


The Connection parameter takes the value stored in the variable defined for Connect To PVS activity.
All parameters besides Connection are given by the user via IN arguments defined in the Parameters Area from WF Designer panel.



The output returned is stored in the variable CreateDevice_status.

Anchor
_Toc331166172
_Toc331166172
Get vDisk Info


The Connection parameter takes the value stored in the variable defined for Connect To PVS activity.
All parameters besides Connection are given by the user via IN arguments defined in the Parameters Area from WF Designer panel.



The output returned by this activity is stored into variables:


Remove Device





Anchor
_GoBack
_GoBack

Anchor
_Toc331166173
_Toc331166173
On Execution Workflow



Execution Result: