CH
A
P
T
E
R
4-1
User
Guide
for
the
Cisco
Application
Networking
Manager
5.2
OL-26572-01
4
Using
Application
Template
Definitions
Date:
3/
28/12
This
chapter
describes
how
to
use
Cisco
Application
Networking
Manager
(ANM)
application
template
definitions
for
configuring
ACE
virtual
contexts.
Note
This
chapter
uses
the
terms
“virtual
context”
and
“device”
interchangeably.
Note
When
naming
ACE
objects
(such
as
a
real
server,
virtual
server,
parameter
map,
class
map,
health
probe,
and
so
on),
enter
an
alphanumeric
string
of
1
to
64
characters,
which
can
include
the
following
special
characters:
underscore
(_),
hyphen
(-),
dot
(.),
and
asterisk
(*)
.
Spaces
ar
e
not
al
lowed.
If
you
are
using
ANM
with
an
ACE
module
or
ACE
appliance
and
you
configure
a
named
object
at
the
ACE
CLI,
keep
in
mind
that
ANM
does
not
support
all
of
the
special
characters
that
the
ACE
CLI
allows
you
to
use
when
configuring
a
named
object.
If
you
use
special
characters
that
ANM
does
not
support,
you
may
not
be
able
to
import
or
manage
the
ACE
using
ANM.
This
chapter
includes
the
following
sections:
•
Information
About
Application
Template
Definitions
and
Instances,
page
4-1
•
Managing
Application
Template
Instances,
page
4-3
•
Managing
Application
Template
Definitions,
page
4-15
Information
About
Application
Template
Definitions
and
Instances
The
ANM
application
template
definitions
allow
you
to
quickly
configure
one
or
more
ACE
virtual
contexts
(or
devices)
with
a
complex
configuration
for
well-known
or
c
ustom
in-house
applications.
A
template
is
defined
by
an
XML
template
definition
file,
which
contains
the
configuration
that
is
deployed
to
a
device
with
place
holders
for
variable
replacement.
The
template
variables
are
presented
to
the
user
in
the
ANM
GUI.
The
two
types
of
application
template
definitions
are
as
follows:
•
System
t
emplates—Defined
by
Cisco
and
i
ncluded
in
ANM
for
major
applications.
You
can
edit
a
system
file
to
customize
it
if
needed.
