Adobe 65019371 Deployment Guide - Page 14

Choosing a Deployment Configuration

Page 14 highlights

Choosing a Deployment Configuration Identifying the Package You Need Choosing a Deployment Configuration As has already been explained, a deployment package is always associated with one product, and therefore with one product install folder. The connection between the package and the product install folder is set during package creation, when the toolkit asks for you for a Media Files Location. Because the toolkit forces you to browse for this location, the resulting path is always an absolute path and can point either to a file on the local system or on a mounted drive. When you save the package, this path is preserved in the package's two package files as the value of the InstallerLocation element. The screen shot below shows the toolkit running on a Windows system, and shows where the Media Files Location you specify in the toolkit is saved in the package files. Layout:Photoshop,Illustrator,and InDesign for the layout folks C:\CS4 Master Collection Media\Adobe CS4 Windows If you deploy the package as created, the Uber programs use this path to locate the product install folder during deployment. Given your enterprise system configuration and the way in which you plan to deploy the package, this path may not be optimal or even possible. If the original path won't do for your situation, you can provide a different path either by editing the path in the package files before deployment or by providing a path as a command line argument to the Uber program when you invoke it. In order to determine what your deployment path needs to be, you must identify your deployment configuration - the physical and logical relationship between the package and the product install folder at the time the package is executed. At this point, it might be useful to look at Enterprise Deployment Planning Sheet #3 : CS4 Deployment Configurations while you read the rest of this section, as the planning sheet summarizes the configuration descriptions which follow. When you are finished reading about the configuration options, you should fill out a planning sheet #3 for each package you are going to deploy. In order to determine which configuration option best meets your needs, you need to answer several questions: Document Version 1.0 Sep 2009 14

  • 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

Choosing a Deployment Configuration
Identifying the Package You Need
Document Version 1.0
Sep 2009
14
Choosing a Deployment Configuration
As has already been explained, a deployment package is always associated with one product, and
therefore with one product install folder. The connection between the package and the product install
folder is set during package creation, when the toolkit asks for you for a Media Files Location. Because the
toolkit forces you to browse for this location, the resulting path is always an absolute path and can point
either to a file on the local system or on a mounted drive.
When you save the package, this path is preserved in the package’s two package files as the value of the
InstallerLocation
element. The screen shot below shows the toolkit running on a Windows system,
and shows where the Media Files Location you specify in the toolkit is saved in the package files.
If you deploy the package as created, the Uber programs use this path to locate the product install folder
during deployment. Given your enterprise system configuration and the way in which you plan to deploy
the package, this path may not be optimal or even possible. If the original path won’t do for your situation,
you can provide a different path either by editing the path in the package files before deployment or by
providing a path as a command line argument to the Uber program when you invoke it.
In order to determine what your deployment path needs to be, you must identify your
deployment
configuration —
the physical and logical relationship between the package and the product install folder
at the time the package is executed.
At this point, it might be useful to look at
Enterprise Deployment Planning Sheet #3 : CS4 Deployment
Configurations
while you read the rest of this section, as the planning sheet summarizes the configuration
descriptions which follow. When you are finished reading about the configuration options, you should fill
out a planning sheet #3 for each package you are going to deploy.
In order to determine which configuration option best meets your needs, you need to answer several
questions:
<?xml version=’1.0’ encoding=’utf-8’?>
<!-- Generated by Adobe CS4 Deployment Toolkit. Place this xml
along with AdobeUberInstaller utility and then execute the
silent installation by invoking AdobeUberInstaller.exe (Win)
or AdobeUberInstaller (Mac) -->
<InstallInfo>
<PackageDescription>
Layout:Photoshop,Illustrator,and InDesign for the
layout folks
</PackageDescription>
<InstallerLocation>
C:\CS4 Master Collection Media\Adobe CS4
</InstallerLocation>
<TargetOS> Windows </TargetOS>
<DeploymentInfo processorFamily="All"
deleteInstallationImage="false"
ignoreProcesses="false">