Adobe 65019371 Deployment Guide - Page 37

Creating Packages Using the Deployment Toolkit Creating Packages Using the Deployment Toolkit In order to create packages, you need a number of things:  You need the document Enterprise Deployment Toolkit Guide which contains directions for invoking and using the toolkit.  You need to know where the toolkit is installed on the admin machine.  You need planning sheets #2 and #3 for each package you plan to create. If someone other than yourself planned the packages, you need to get these planning sheets from the planner at this time. You are now ready to invoke the deployment toolkit and create all of your packages, using the configuration choices on planning sheet #2 for each package. Do this now. When you are finished creating the packages, come back to this document at this point. Editing Package Files Once all packages have been created, check planning sheet #3 for each package to see if the package-to-product install folder path for the package is OK as it is, or if you need to edit the package files to change it. NOTE: Configuration IS with EXPLICIT NETWORK PATH ON COMMAND LINE chosen does not require package editing.  Configurations TT, TM, and TS always require package editing, as they use a relative path between the package and the product install folder. Replace the value of the InstallerLocation element in the package files with the relative path specified on planning sheet #3 in the PACKAGE-TO-PRODUCT INSTALL FOLDER PATH field.  Configurations IT, IM, and IS with ABSOLUTE NETWORK PATH chosen may or may not require package editing. Compare the path on planning sheet #2 in the MEDIA FILES LOCATION FIELD to the path on planning sheet #3 in the PACKAGE-TO PRODUCT INSTALL FOLDER PATH field. If they are the same, you do not need to edit the package. If they are not the same, replace the value of the InstallerLocation element in the package files with the path specified on worksheet #3.  Configuration IS with EXPLICIT NETWORK PATH IN PACKAGE chosen requires package editing. Replace the value of the InstallerLocation element in the package files with the explicit network path specified on planning sheet #3 in the PACKAGE-TO PRODUCT INSTALL FOLDER PATH field. Remember, you can do this only on Windows, and only if you are sure that the users who will invoke the Uber program have permission to perform network mounts. While you are in the package files, check the value of the deleteInstallationImage attribute of the DeploymentInfo element to make sure its setting matches that specified on planning sheet #3. Document Version 1.0 September 2009 37