Jump to: navigation, search

The HTTP Interface

This page pertains only to Stat Server that operates in cluster mode. Specifying the HTTP protocol for Stat Server that operates in regular mode is not currently supported.

In order for the SIP Cluster Solution to receive information about the state of a regular DN or to receive information about performance data about each Stat Server node within a Stat Server cluster, you can configure one or more Stat Server applications within a Stat Server cluster to use an HTTP interface.

Using the HTTP Interface for Feature Server

One manner in which Feature Server (a SIP Cluster server) sends call forwarding and DND requests from a particular DN to T-Controller is triggered through the activity that is transmitted through an HTTP interface. (Other manners are described in the SIP Cluster Solution Guide.) Stat Server operating in cluster mode can provide DN state information via this interface when it is configured to do so. When requested through the HTTP interface, Feature Server sends the TCallSetForward, TCallCancelForward, TSetDNDOn, or TSetDNDOff request, as appropriate, to the appropriate T-Controller that is in charge of the DN within the SIP Cluster.

Configuring an HTTP Listening Port

Within Genesys Administrator, you configure an HTTP listening port at the Server Info tab of an application’s properties. Refer to the Genesys Administrator Help for more information. This listening port is specific to a particular Stat Server—you do not configure an HTTP listening port at the Stat Server solution level for all components to share. However, you can designate as few as one HTTP listening port within one Stat Server node to provide DN state information for all nodes within a Stat Server cluster.

The default protocol that Stat Server uses when you specify no connection protocol is an internal proprietary simple protocol.

Internal Performance Counters

Through the HTTP interface, Stat Server also supplies performance measurements to T-Controller for the events that Stat Server receives and sends. To provide server performance information, you must configure an HTTP listening port for every Stat Server node that must supply this information. Such configuration is required because the performance measurements that Stat Server provides will differ based on the object that initiated the request. The table below lists the performance measurements that Stat Server provides.

Stat Server Performance Counters

Request / Input Output
Configuration Server events Rate of Configuration Server events per second calculated for the last checkpoint interval. (The default checkpoint interval is internally set at 30 seconds.)

Rate of Configuration Server events per second calculated for the entire time since startup.

Maximum rate of Configuration Server events per second calculated for the checkpoint interval.

Configuration Server delayed events Number of delayed Configuration Server events during the last checkpoint interval
T-Server events Rate of T-Server events per second calculated for the last checkpoint interval.

Rate of T-Server events per second calculated for the entire time since startup.

Maximum rate of T-Server events per second calculated for the checkpoint interval.

T-Server delayed events Number of delayed T-Server events during the last checkpoint interval.
Requests from Stat Server clients Rate of events per second calculated for the last checkpoint interval.

Rate of events per second calculated for the entire time since startup.

Maximum rate of events per second calculated for the checkpoint interval.

Events sent to Stat Server clients Rate of events per second calculated for the last checkpoint interval.

Rate of events per second calculated for the entire time since startup.

Maximum rate of events per second calculated for the checkpoint interval.

Samples published to shared memory Number of samples during the latest checkpoint interval.
Subscriber notifications from shared memory Number of subscriber notifications during the latest checkpoint interval.

You can also get response within an html browser by issuing the following string in the URL:

http://<StatServer HTTP listener host name>:<listener port>/genesys/statserver/<path to specific resource>

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on September 2, 2015, at 04:13.