Cisco Cisco 3350 Mobility Services Engine Developer's Guide
C
ISCO
MSE
API
S
PECI FICATI ON
G
UIDE
–
C
ONTEXT
A
W ARE
S
ERVICE OF
MSE,
R
EL EASE
7.4
.
P
A G E
164
O F
227
Each trigger defines a parameter that is matched on. The parameter can be as specific or general
as required.
as required.
For example, a parameter can define a specific or wild-card version of:
MAC address
Asset Name
Asset Group
Asset Category
You should have a soap listener tool/program running on the client machine and should listen
to localhost and the port number you have configured while registering these events through
AddTrackGroup API call.
to localhost and the port number you have configured while registering these events through
AddTrackGroup API call.
12.1 Definitions
12.1.1
Track Info
It defines the configuration and monitoring parameters for the tracking system.
trackQueueLimit
—
Defines the event queue maintained in the server for pending
events to be fired. Once the queue limit is reached, events will be dropped by the
MSE. The number of dropped events is counted and is monitorable by reading
trackEventsDropped.
MSE. The number of dropped events is counted and is monitorable by reading
trackEventsDropped.
trackRateLimitInMsecs
—
Defines the time gap in milliseconds between events that
should be kept for firing events out of the MSE. By default, 0, indicates fire the
events as fast as they occur.
events as fast as they occur.
refreshTimeInMins
—
The time period that must pass before events that have
recurring triggers are fired. For example, if this parameter is set to 5 mins, but an
event trigger would cause an event to fire every 30 secs then the event will be fired
X times every 5 mins where X is retryCount + 1.
event trigger would cause an event to fire every 30 secs then the event will be fired
X times every 5 mins where X is retryCount + 1.
retryCount
—
Defines the number of retries an event should be fired during a
refresh period. Default is 1.
Class
AesTrackInfo