Run an execution profile
How you run an execution profile depends on whether you are using Install Capture, Self-Provisioning, or Forward Path. This topic provides instructions for all of these.
To run an execution profile using Install Capture
Note: Install Capture uses a virtual machine configuration to store all of the information that AppDNA requires to connect to and manage the virtual machine.
On the Install Capture tab in the Import Applications screen, click Browse, Search, or Import from List on the toolbar to select the .exe or other installation file that you want to import.
Ensure that you specify the files using a UNC path (such as \\192.168.50.20\Source\application.exe or \\MachineName\Source\application.exe).
In the list of applications on the Install Capture tab, select the check box to the left of the application against which you want to run the execution profile.
On the toolbar in the Install Capture tab, select the virtual machine configuration that you want to use.
The virtual machine configuration specifies the details of the virtual machine on which the execution profile will run. This virtual machine must be set up appropriately for the execution profile. For example, the App-V 5.1 Sequencer execution profile requires Microsoft Application Virtualization 5.1 Service Pack 1 to be installed.
In the list of applications on the Install Capture tab, click the + to the left of the application name to open the application’s options panel. Then in the first drop-down list, select the execution profile that you want to run.
On the toolbar in the Install Capture tab, click Import. This starts the Install Capture processing, as defined by the selected execution profile and on the virtual machine specified in the virtual machine configuration. When the capture finishes, the application is automatically imported into AppDNA.
Note: If you have customized execution profiles, customized versions won’t be upgraded. The built-in versions of the execution profiles will be upgraded. You may want to consider refreshing your customized profiles. For more information, see Execution Profiles.
To run an execution profile using Self-Provisioning
Self-Provisioning provides a mechanism for the application capture to be driven by an expert end user who does not have access to AppDNA itself. In summary, the procedure is as follows:
The administrator uses the Self-Provisioning tab in the main AppDNA Import Applications screen to set up the instructions for the capture.
During this procedure, the administrator selects the execution profile to be used in a similar way to selecting the execution profile for Install Capture.
The administrator arranges for the Self-Provisioning client machine to be set up for the specific execution profile.
For example, the App-V 5.1 Sequencer execution profile requires Microsoft Application Virtualization 5.1 to be installed.
The administrator sends the instructions to the end user who then runs the capture on the Self-Provisioning client machine.
For more information, refer to Self-Provisioning.
To run an execution profile using Forward Path
Forward Path is controlled by scenario and task scripts. A Forward Path task script can run an execution profile. To do this, call the ProductionManager.RunExecutionProfile function in the task script. This function has the following syntax:
Public Shared Sub RunExecutionProfile ( _ controller As IActionController, _ profile As ExecutionProfileBuilder, _ profile_replaceable_values As Dictionary(Of String, String), _ vm_config_name As String _ )
|controller||This object is automatically passed into the script when it runs and provides access to information about the current application, for example.|
|profile||Use to pass the name of the execution profile.|
|profile_replaceable_values||Use to pass a list of replaceable name and value pairs.|
|vm_config_name||Use to pass the name of the virtual machine configuration to use.|
Dim replaceables As New Dictionary(Of String, String) ' Set the SequenceName replaceable replaceables.Add("SequenceName", controller.Application.Name) ' Activate auto-clicker replaceables.Add("UseAutoClick", "--use-autoclick") ProductionManager.RunExecutionProfile(controller, _ "App-V 5.1 Sequencer", replaceables, "App-V VM Configuration")
See Forward Path for more information.