User manual SYMANTEC PACKAGER V 1.3 IMPLEMENTATION GUIDE

[. . . ] SymantecTM Packager Implementation Guide 2 SymantecTM Packager Implementation Guide The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Documentation version 1. 3 Copyright Notice Copyright © 2004 Symantec Corporation. Any technical documentation that is made available by Symantec Corporation is the copyrighted work of Symantec Corporation and is owned by Symantec Corporation. The technical documentation is being delivered to you AS-IS, and Symantec Corporation makes no warranty as to its accuracy or use. [. . . ] A Build Status window appears, which provides information about the progress of the build and logs any problems that have occurred. If the build is successful, the last line in the Build Status window reads as follows: Product was built successfully. In the Build Status window, click Close. 3 Configuring custom products Building and testing custom products 45 Testing custom products The product module files and product configuration files that are provided by Symantec are designed to help you create a buildable, installable product. You should test whether your feature selections and installation options are appropriate for your users. It is important that you test your custom products on all supported platforms before you include them in a package or deploy them to end users. The following applications must be installed on the test system or error messages will appear when you attempt to run the product . msi file: ISScript. msi If you are using only Symantec pcAnywhere with Symantec Packager, you do not need to install ISScript. msi. Windows Installer 2. 0 To test custom products 1 2 3 On the Windows taskbar, click Start > Run. In the Run dialog box, type the following: explorer. exe In Windows Explorer, navigate to the Configure Products data folder. If you encounter error messages when you double-click a product . msi file, verify that ISScript. msi and Windows Installer 2. 0 are installed on the test computer. Follow the on-screen installation instructions to complete testing the product. After installation, use the product to verify that your feature selections meet your users' needs. 4 5 6 46 Configuring custom products Building and testing custom products Chapter 6 Configuring custom commands This chapter includes the following topics: About configuring custom commands Working with custom commands Configuring custom commands Building and testing custom commands About configuring custom commands Symantec Packager lets you create custom commands to include in your packages. Examples of custom commands include installations of unsupported products, batch files, third-party executables, command-line arguments, or simple file copies. Custom commands let you simplify application deployment by including multiple tasks in one package. When you create a custom command, Symantec Packager creates a command configuration file. A command configuration file is a generic product configuration file that does not reference a product template file. Therefore, custom commands do not depend on the Import Products phase. The build process for custom commands creates a self-extracting executable (. exe) file, which can be tested before including it in a package. 48 Configuring custom commands About configuring custom commands Custom commands let you do the following: Execute a command on the target computer. Combine these two so that you copy files to the target computer and execute a command on the target computer. Figure 6-1 shows the Configure Products tab, which lets you view product configuration and custom command files. Figure 6-1 Configure Products tab showing a custom command Product configuration (. pcg) files Command configuration (. pcg) file Creating a custom command involves the following process: Create a custom command file. See "Specifying command-line parameters and switches" on page 52. See "Specifying operating system support" on page 55. Configuring custom commands Working with custom commands 49 Build the custom command. See "Testing custom commands" on page 57. Working with custom commands In the Symantec Packager main window, the Configure Products tab lists the custom commands that you have created and provides information about when they were last modified and built. [. . . ] These files are self-extracting executable (. exe) files that can be deployed through Symantec Packager or other deployment tools that support deploying . exe files. Symantec Packager lists product . msi files on the Deploy Packages tab if they are supported and if you configured the Symantec Packager Preferences to show supported . msi files. You can use the Web-based Deployment Tool that is supplied by Symantec or an industry-standard, third-party deployment tool to deploy the pcAnywhere . msi file. The Symantec Packager Deployment Tool does not support deployment of . msi files. [. . . ]