Adobe 65021566 Deployment Guide - Page 9

CS4 Deployment Packages

Get Adobe 65021566 - Creative Suite 4 Design Premium PDF manuals and user guides
UPC - 883919163796
View all Adobe 65021566 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 9 highlights

CS4 Deployment Packages CS4 Deployment Packages An Adobe CS4 deployment package is an encapsulation of an invocation of a CS4 product install program which could be done by hand in a laborious and error-prone process. It provides an automated way of invoking a CS4 install program to perform an enterprise install - a silent, customized install. Each package can install just one CS4 product. You create packages with the CS4 deployment toolkit. When creating a package, one of the first things you do is point the toolkit at the product install folder for the product you are packaging. The toolkit scans this folder and presents you with a list of applications and components that can be installed, from which you make your choices. You can also set a number of options that affect the behavior of the install program and of the installed applications. All of these choices are recorded in the package. When you save a newly created package, what you have is a folder containing four things:  Two executable programs - AdobeUberInstaller and AdobeUberUninstaller;  Two configuration files - AdobeUberInstaller.xml and AdobeUberUninstaller.xml. The executables do what their names suggest: they install and uninstall a particular Adobe product. The executables are called the Uber programs; the XML files are called the package files. When you execute a package, you invoke one of the Uber programs. The Uber program in turn invoke the Adobe install program, Setup. Deployment packages are always executed on the target systems. "Executing a package" means invoking one of the Uber programs. When the AdobeUberInstaller program is invoked:  It uses the information in the AdobeUberInstaller.xml file to construct files that Setup uses when it runs;  It adds or modifies system configuration files that Setup uses when it runs;  It invokes Setup with appropriate command line arguments so that the install happens as you configured it in your package.  When Setup completes, AdobeUberInstaller cleans up after it, removes the product install folder from the target systems if so specified in the package, and terminates. Document Version 1.0 Sep 2009 9

  • 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
CS4 Deployment Packages
Document Version 1.0
Sep 2009
9
CS4 Deployment Packages
An Adobe CS4 deployment package is an encapsulation of an invocation of a CS4 product install program
which could be done by hand in a laborious and error–prone process. It provides an automated way of
invoking a CS4 install program to perform an enterprise install – a silent, customized install. Each package
can install just one CS4 product.
You create packages with the CS4 deployment toolkit. When creating a package, one of the first things you
do is point the toolkit at the product install folder for the product you are packaging. The toolkit scans this
folder and presents you with a list of applications and components that can be installed, from which you
make your choices. You can also set a number of options that affect the behavior of the install program
and of the installed applications. All of these choices are recorded in the package.
When you save a newly created package, what you have is a folder containing four things:
Two executable programs — AdobeUberInstaller and AdobeUberUninstaller;
Two configuration files — AdobeUberInstaller.xml and AdobeUberUninstaller.xml.
The executables do what their names suggest: they install and uninstall a particular Adobe product. The
executables are called the
Uber programs
; the XML files are called the
package files
. When you execute a
package, you invoke one of the Uber programs. The Uber program in turn invoke the Adobe install
program, Setup.
Deployment packages are always executed on the target systems. “Executing a package” means invoking
one of the Uber programs. When the AdobeUberInstaller program is invoked:
It uses the information in the AdobeUberInstaller.xml file to construct files that Setup uses when it
runs;
It adds or modifies system configuration files that Setup uses when it runs;
It invokes Setup with appropriate command line arguments so that the install happens as you
configured it in your package.
When Setup completes, AdobeUberInstaller cleans up after it, removes the product install folder from
the target systems if so specified in the package, and terminates.