Adobe 65019371 Deployment Guide - Page 16

Table 1: Path Forms for the Package-to-Product Install Folder Link, Table 2

Page 16 highlights

Choosing a Deployment Configuration Identifying the Package You Need Table 1: Path Forms for the Package-to-Product Install Folder Link Relative Path Relative paths are used to locate the product install folder relative to the location of the package that references it, i.e. relative to the current working directory of the Uber program when it runs. Relative paths are recommended in cases where the package and the product install folder are located together on the same drive or volume on a system or on the same movable storage medium. A relative path on Windows contains a path component that does not begin with either a slash or backslash ( / or \). A relative path on the Mac is any path that does not start with a slash( / ). ..\Mystery Files\Follow Me Mystery Files/Follow Me Absolute Path Absolute paths are used to locate the product install folder relative to the target machine, independent of where the package is located. An absolute path can resolve to either a local directory or a network location. You cannot determine for certain whether an absolute path is a local path or a network path just by looking at it, although you can in some instances make an educated guess. For example, on the Mac, network mounts are often made under the /Volumes folder. On Windows, network mounts are often done on drive letters near the end of the alphabet. An absolute path on Windows begins with a drive letter and colon followed by a slash or backslash ( / or \ ). For example: H:\CS4_Apps\PIFs\WebPremium An absolute path on the Mac begins with a single slash ( / ). For example: /CS4_Apps/PIFs/WebPremium Explicit Network Path An explicit network path denotes a specific server, a mountable volume on that server, and optionally a path on that volume. Explicit network paths are useful when the product install folder is remote to the target, especially when it cannot be mounted on the target before deployment. Explicit network paths are easily recognizable. On Windows, you must use UNC (Universal Naming Convention) paths, which begin with two backslashes ( \\ ) or two quoted slashes ( "//" ) and whose first path element is the name of a server. For example: \\fileserver.company.com\transfer\CS4-Apps\PIFs\WebPremium On Mac, you must use AFP (Apple Filing Protocol) paths of the form afp://server-name/volume-name/path. For example: afp://fileserver.company.com/transfer/CS4-Apps/PIFs/WebPremium Table 2: Path Forms Required for Deployment Configurations Config Package Product Install Folder TT Together on same drive on TARGET TM Together on PHYSICAL MEDIUM mounted on target TS Together on same drive on SERVER IT ANYWHERE IM ANYWHERE IS ANYWHERE On different drive on TARGET On PHYSICAL MEDIUM mounted on target On SERVER, mounted on target before deployment On SERVER, mounted on target during deployment Path Type Relative Relative Relative Absolute local Absolute local Absolute network Explicit Network Document Version 1.0 Sep 2009 16

  • 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
16
Table 1: Path Forms for the Package–to–Product Install Folder Link
Relative Path
Relative paths are used to locate the product install folder relative to the location of the package that references it, i.e.
relative to the current working directory of the Uber program when it runs. Relative paths are recommended in cases
where the package and the product install folder are located together on the same drive or volume on a system or on the
same movable storage medium.
A relative path on Windows contains a path component that does not begin with either a slash or backslash ( / or \).
A relative path on the Mac is any path that does not start with a slash( / ).
..\Mystery Files\Follow Me
Mystery Files/Follow Me
Absolute Path
Absolute paths are used to locate the product install folder relative to the target machine, independent of where the
package is located. An absolute path can resolve to either a local directory or a network location.
You cannot determine for certain whether an absolute path is a local path or a network path just by looking at it,
although you can in some instances make an educated guess. For example, on the Mac, network mounts are often made
under the
/Volumes
folder. On Windows, network mounts are often done on drive letters near the end of the alphabet.
An absolute path on Windows begins with a drive letter and colon followed by a slash or backslash ( / or \ ).
For example:
H:\CS4_Apps\PIFs\WebPremium
An absolute path on the Mac begins with a single slash ( / ).
For example:
/CS4_Apps/PIFs/WebPremium
Explicit Network Path
An explicit network path denotes a specific server, a mountable volume on that server, and optionally a path on that
volume. Explicit network paths are useful when the product install folder is remote to the target, especially when it
cannot be mounted on the target before deployment.
Explicit network paths are easily recognizable. On Windows, you must use UNC (Universal Naming Convention) paths,
which begin with two backslashes ( \\ ) or two quoted slashes ( “//” ) and whose first path element is the name of a server.
For example:
\\
fileserver.company.com
\transfer\CS4-Apps\PIFs\WebPremium
On Mac, you must use AFP (Apple Filing Protocol) paths of the form
afp://
server-name
/
volume-name
/
path
.
For example:
afp://
fileserver.company.com
/transfer/CS4-Apps/PIFs/WebPremium
Table 2:
Path Forms Required for Deployment Configurations
Config
Package
Product Install Folder
Path Type
TT
Together on same drive on TARGET
Relative
TM
Together on PHYSICAL MEDIUM mounted on target
Relative
TS
Together on same drive on SERVER
Relative
IT
ANYWHERE
On different drive on TARGET
Absolute local
IM
ANYWHERE
On PHYSICAL MEDIUM mounted on target
Absolute local
IS
ANYWHERE
On SERVER, mounted on target before deployment
On SERVER, mounted on target during deployment
Absolute network
Explicit Network