Adobe 65019371 Deployment Guide - Page 15

Choosing a Deployment Configuration Identifying the Package You Need 1. Will you distribute and place the package and the product install folder together or independently? By together, we mean that the package and product install folder are on the same disk drive or volume on a computer, or on the same portable disk medium, such as a DVD, flash drive, or movable disk. An answer of "together" leads to three very similar configuration choices (TT, TM, and TS in the following figure). An answer of "independently" leads to a second question. 2. Will you physically place the product install folder on each target or on one or more servers? Your choice is influenced by the disk capacity of the target machines to which you will deploy the package as well as by your network bandwidth. An answer of "on the targets" leads to two similar configurations (IT and IM in the following figure). An answer of "on servers" leads to a sixth configuration (IS in the following figure). These six basic deployment configurations are shown below. In this picture the term "package" is abbreviated to 'Pkg" and the term "product install folder" is abbreviated to "PIF". How are the Package & Product Install Folder Placed? TOGETHER INDEPENDENTLY Pkg & PIF on same drive on TARGET TT Pkg & PIF on PORTABLE STORAGE MEDIUM TM Pkg & PIF on same drive on SERVER TS Where is the Product Install Folder? ON TARGET ON SERVER Pkg anywhere PIF on TARGET on different drive IT Pkg anywhere PIF on PORTABLE STORAGE MEDIUM IM Pkg anywhere PIF on SERVER IS As already explained, the path from a newly created package to its product install folder is always an absolute path. Some of the above configurations either preclude the use of an absolute path or make some other path type more desirable. For configurations TT, TM, and TS, the only sensible choice is a relative path from the package to the product install folder. Configurations IT, IM, and IS require an absolute path. Certain instances of configuration IS may require an explicit network path. These path forms are defined in Table 1. Table 2 lists the valid path form(s) for each deployment configuration. The rest of this section contains a detailed description of each configuration. Document Version 1.0 Sep 2009 15