WAN Traffic Manager
315
n
ov
do
cx (e
n)
22
Ju
n
e 20
09
LOCAL INT L1 :=10;
LOCAL INT L2;
LOCAL TIME L3;
LOCAL BOOLEAN L4 :=TRUE, L5 :=FALSE;
LOCAL NETADDRESS L6;
The required and optional declarations are specific to a particular traffic type. Policies that do not
contain the required variables will not run. The optional declarations must have a value to provide a
default if none is passed in. WAN Traffic Manager provides system symbols (predefined variables)
for use with all traffic types.
Each declaration consists of three parts:
Scope
Type
List of names/optional value pairs
Scope
Valid scopes are listed in the following table.
Type
Valid types are listed in the following table.
Scope
Description
REQUIRED
Variables defined as REQUIRED in scope can be used in multiple sections, but only
once within the Declaration section.
No values can be defined for a REQUIRED scope variable. Its value must come from
the GetWanPolicy request.
OPTIONAL
Variables defined as OPTIONAL in scope can be used in multiple sections of a policy,
but only once within the Declaration section.
OPTIONAL scope variables are assigned to a default value. These values are not
initialized. They are set only if a value is not passed. If a WAN policy request does not
pass a new value to the parameter that matches in both name and type, the value
defined in the Declaration is used when processing the policy.
You must assign a value to variables defined as OPTIONAL in scope. Therefore,
because TIME and NETADDRESS types cannot be initialized in the Declaration
section, do not use an OPTIONAL scope with these variable types.
LOCAL
Variables defined as LOCAL in scope can be used in multiple sections, but only once
within the Declaration section.
LOCAL scope variables exist only for a particular policy; that is, their values are not
returned to the calling client.
All parameter types can be defined. However, because TIME and NETADDRESS
types cannot be initialized in the Declaration section, do not assign values to these
types.
SYSTEM
Variables defined as SYSTEM in scope can be used in multiple sections, but only
once within the Declaration section.
Summary of Contents for EDIRECTORY 8.8 SP5
Page 4: ...4 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 72: ...72 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 118: ...118 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 130: ...130 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 188: ...188 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 222: ...222 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 240: ...240 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 264: ...264 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 290: ...290 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 322: ...322 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 540: ...540 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 548: ...548 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
Page 616: ...616 Novell eDirectory 8 8 Administration Guide novdocx en 22 June 2009...
