CH
A
P
T
E
R
9-1
User
Guide
for
the
Cisco
Application
Networking
Manager
5.2
OL-26572-01
9
Configuring
Stickiness
Date:
3/
28/12
This
chapter
describes
how
to
configure
stickiness
on
the
Cisco
Application
Control
Engine
(ACE)
using
Cisco
Application
Networking
Manager
(ANM).
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
Stickiness,
page
9-1
•
Sticky
Types,
page
9-2
•
Sticky
Groups,
page
9-6
•
Sticky
Table,
page
9-6
•
Configuring
Sticky
Groups,
page
9-7
Information
About
Stickiness
When
customers
visit
an
e-commerce
site,
they
usually
start
out
browsing
the
site.
The
site
may
require
that
the
client
become
“stuck”
to
one
server
once
the
connection
is
established,
or
once
client
starts
to
build
a
shopping
cart.
In
either
case,
once
the
client
adds
items
to
the
shopping
cart,
it
is
important
that
all
of
the
client
requests
get
directed
to
the
same
server
so
that
all
the
items
are
contained
in
one
shopping
cart
on
one
server.
An
instance
of
a
customer’s
shopping
cart
is
typically
local
to
a
particular
web
server
and
is
not
duplicated
across
multiple
servers.
E-commerce
applications
ar
e
not
the
only
types
of
a
pplications
that
require
stickiness.
Any
web
application
that
maintains
client
information
may
require
stickiness,
such
as
banking
applications
or
online
trading.
Other
uses
include
FTP
and
HTTP
file
transfers.
