Symantec 14541094 Implementation Guide - Page 50

Viewing custom command details, Deleting custom commands, New Custom Command, Display Details

Get Symantec 14541094 - pcAnywhere Host & Remote PDF manuals and user guides
UPC - 037648640480
View all Symantec 14541094 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 50 highlights

50 Configuring custom commands Working with custom commands This procedure details the minimum steps required to create a custom command file. You can customize the command configuration file. To create a custom command 1 In the Symantec Packager window, on the Configure Products tab, on the File menu, click New Custom Command. 2 In the Command Editor dialog box, on the Parameters tab, do one or both of the following: ■ Type the command-line parameters for your custom command, and then click OK. ■ Include files and specify their target locations. 3 In the Command Editor dialog box, click OK. 4 In the Save As dialog box, type a file name for the custom command, and then click Save. The command configuration file appears on the Configure Products tab. Viewing custom command details Symantec Packager lets you view the details of a custom command file without opening the file. A summary of the custom command specifications is available using the Display Details option. To view custom command details 1 In the Symantec Packager window, on the Configure Products tab, select the custom command file that you want to view. 2 On the File menu, click Display Details. 3 Click OK to close the Details window. Deleting custom commands Deleting a custom command removes its configuration file, which contains the configuration settings that are needed to build the custom command. If you delete the command configuration file that is included in a package definition file, you break the package definition file. However, if you delete a command configuration file, it does not affect installation packages that were previously built and stored on the Deploy Packages tab.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
50
Configuring custom commands
Working with custom commands
This procedure details the minimum steps required to create a custom command
file. You can customize the command configuration file.
To create a custom command
1
In the Symantec Packager window, on the Configure Products tab, on the File
menu, click
New Custom Command
.
2
In the Command Editor dialog box, on the Parameters tab, do one or both of
the following:
■
Type the command-line parameters for your custom command, and
then click
OK
.
■
Include files and specify their target locations.
3
In the Command Editor dialog box, click
OK
.
4
In the Save As dialog box, type a file name for the custom command, and
then click
Save
.
The command configuration file appears on the Configure Products tab.
Viewing custom command details
Symantec Packager lets you view the details of a custom command file without
opening the file. A summary of the custom command specifications is available
using the Display Details option.
To view custom command details
1
In the Symantec Packager window, on the Configure Products tab, select the
custom command file that you want to view.
2
On the File menu, click
Display Details
.
3
Click
OK
to close the Details window.
Deleting custom commands
Deleting a custom command removes its configuration file, which contains the
configuration settings that are needed to build the custom command. If you
delete the command configuration file that is included in a package definition
file, you break the package definition file. However, if you delete a command
configuration file, it does not affect installation packages that were previously
built and stored on the Deploy Packages tab.