Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - NETWORK DISCOVERY DATABASE STRUCTURE, Руководство системного администратора

Страница: 61 / 374

System Variables
4
61
n
ov
do
cx (e
n)
16
Ap
ril 20
10
4
System Variables
System variables let you define variables that can be used to replace paths, names, and so forth as
you enter information in ZENworks
®
Control Center.
You can define system variables at three levels:
Š Management Zone: The system variables are inherited by all device folders, devices, and
bundles.
Š
Device Folder: The system variables are inherited by all devices contained within the folder or
its subfolders.
Š
Device or Bundle: The system variables apply only to the device or bundle for which they are
configured.
The following sections contain more information:
Š
Section 4.1, “Understanding System Variables,” on page 61
Š
Section 4.2, “Adding System Variables,” on page 62
Š
Section 4.3, “Removing System Variables,” on page 63
Š
Section 4.4, “Editing System Variables,” on page 63
Š
Section 4.5, “Using System Variables,” on page 63
4.1 Understanding System Variables
The following examples illustrate some uses of system variables:
Š
Specifying Paths and Filenames in Actions: When you create an Edit INI File action, for
example, you specify a
.ini
file and configure the changes to be performed on that file. During
the creation process, you can specify the full path to the file (for example,
C:\Program
Files\OpenOffice.org 2.0\program\setup.ini
).
Instead of specifying the entire path and filename, you can create a system variable. For
example, the name of the variable can be OpenOffice INI and the value can be the full path to
the file. Now, instead of specifying the full path and filename when you create the action, you
can type
${OpenOffice INI}
in the Filename field.
An advantage of using a system variable rather than typing the full path and filename is that
you can specify this particular
.ini
file in many different types of actions. Suppose that the
location of the
.ini
file changes. Instead of editing the path in each action, you can edit the
path in the system variable and all the actions still point to the correct path.
You can generalize the path even more by creating a system variable named ProgramFiles with
the value of
C:\program files
. In the future, when you specify a path, you can type
${ProgramFiles}
and then specify the remaining path to the specific file. For example,
${ProgramFiles}\OpenOffice 2.0\program\setup.ini
. Again, if the path to the
C:\program files
directory changes in the future, you only need to change the path in the
system variable, rather than in each bundle that uses that location in a path.