Table of Contents
Advertisement
When the package begins installing, the referenced files are downloaded to the target machine's TEMP
directory, and then processed by the .msi.
Referencing License Files
The use of license files in the package command line options varies between applications. Some can be
referenced in a shared location, using the system environment variables described above, or included in a
.bat file, while others may be applied on a user-by-user basis. Consult the product publisher's
documentation for the application for which you are creating a package to determine how you can include
the information in the package.
Prerequisites
Installation and removal files are accessible to Package Studio users.
Optional pre- and post-command scripts are accessible to Package Studio users.
Procedure
1. Click the Files tab.
2. In the Select Files to Import area, click Select Folder. The Browse for Folder dialog box appears.
3. Browse to the folder containing the files to include in the package. Click OK. The file path is added to
the text box.
4. Click Import Files Into Project. The contents of the folder specified in the file path text box are added
to the project and the file and sub-folders are displayed in the Project Data Directory area.
5. In the Project Data Directory area, you may have the following options:
To add, remove, or rename the files in the folder, click the Folder button. The folder contents are
n
displayed. When the folder contents are properly organized, close the window.
To update the displayed files, click the Refresh button.
n
6. Configure the commands and arguments for installing the package. In the process type drop-down
list, located above the Pre-Command File label, select Installation.
7. (Optional) To specify a script to run before installation, for example, to shut down a service, click Add
on the Pre-Command File line. Browse to the location of the pre-command executable file type. The
file required by Package Studio begins preinst*.*. To see all files, type *.* in the File name text box.
Click Open to select the file. The file is renamed preinst.<extension> and is displayed after the Pre-
Command File label.
8. If the command used to run the installation is displayed in the Project Data Directory, select the .exe or
.msi, and then click Set Command. You may also type the command in the text box. The Command
text box must display the name of the command to be run, it does not have to be a command from the
file list.
9. In the Arguments text box, type the arguments you want to apply to the installation process when it is
run. Separating the arguments from the command allows for consistent behavior and better tracking
of results.
10. (Optional) To specify a script to run after installation, for example, to restart a service, click Add on the
Post-Command File line. Browse to the location of the post-command executable file type. The file
required by Package Studio begins postinst*.*. To see all files, type *.* in the File name text box. Click
Open to select the file. The file is renamed postinst.<extension> and is displayed after the Post-
Command File label.
VMware, Inc.
Using Package Studio to Create Software Packages and Publish to Repositories
31
Advertisement
Table of Contents
