Default Value: 1000
Valid Values: Positive integers less than 4294967296 (232)
Changes Take Effect: After restart
Related Options: reg-dns-chunk-delay
Specifies the number of DNs that Stat Server submits in a single registration request to T-Server. Instead of trying to register for all configured DNs at once, Stat Server divides the DN registration among several requests, each for the specified number of DNs.
In a large configuration environment, use this option in conjunction with reg-dns-chunk-delay to optimize DN registration at Stat Server startup.
Default Value: 10
Valid Values: Positive integers less than or equal to 2147483
Changes Take Effect: After restart
Related Options: reg-dns-chunk-volume
Specifies the interval, in seconds, between two subsequent registration requests. Stat Server waits for the specified interval before sending a request to T-Server to register a subsequent set of DNs, thus allowing T-Server to process the previous request.
In a large configuration environment, use this option in conjunction with reg-dns-chunk-volume to optimize DN registration at Stat Server startup.
Configuring a Stat Server Application
You must configure a Stat Server Application object before you install it. To configure Stat Server, Configuration Server must be running.
Note: To use secure Transport Layer Security (TLS) connections between Stat Server and its clients, or between Stat Server and Configuration Server, you must configure such connections manually following the procedures described in the Genesys Security Deployment Guide.
You can configure a Stat Server 8.5 Application object manually within Genesys Administrator/GAX. Refer to the Genesys Administrator/Genesys Administrator Extension Help file for more information. You use the Stat Server application template to accomplish this. This template is located in the templates directory of the Real-Time Metrics Engine CD and is named Stat_Server_851.apd. You should import this file into your configuration environment before configuring Stat Server application.
In the templates directory of the Real-Time Metrics Engine CD—Stat_Server_851.xml file—contains the metadata that defines the default and valid values for most of the Stat Server configuration options that are available to you in the 8.5.x release. (The listing of configuration options is located in the RTME Options Reference.) To use this metadata, you must import it into the Stat Server application template. As you configure a Stat Server application within Genesys Administrator, Genesys Administrator validates the values that you specify for configuration options against this metadata.
Refer to the Genesys Administrator/Genesys Administrator Extension Help file for instructions on how to import and use metadata and for instructions on how to configure applications.
For Stat Server operating in cluster mode, you must select auto-restart.The Stat Server applications that function within a Stat Server cluster ignore the stat type definitions that are defined at the application level.
Configuring Stat Server as Part of a SIP Cluster
Topic Configuring a Stat Server Cluster Solution will have you adding Stat Server applications to a Stat Server solution for the purposes of servicing a SIP Cluster. The Stat Server solution is the core object that controls when its components are started and what common statistical options all Stat Server applications share. This collection of Stat Server applications forms a Stat Server cluster where the nodes of the Stat Server cluster are paired in some capacity with nodes in the SIP Cluster.
You can add other nonnodal applications to the Stat Server solution (including other Stat Server applications that are not paired to any SIP Cluster node at all). Refer to Configuring the Components of a Stat Server Solution for additional information. Contact your Genesys representative for information about SIP Cluster architecture.
Adding SIP Server Applications to Stat Server Configuration
On the Connections tab of a Stat Server application, add all of the SIP Server applications that each node is to monitor.
- If a particular Stat Server node must connect to both the Interaction Proxy and T-Controller interfaces of SIP Server, then leave the Connection Protocol field blank. With Interaction Proxy and T-Controller listening ports properly provisioned within the SIP Server application, Stat Server will retrieve that information and open connections to both Interaction Proxy and T-Controller ports.
- If a particular Stat Server node must connect to the Interaction Proxy interface only of SIP Server, configure the connection by selecting IPport in the Port ID field and by typing IProxy in the Connection Protocol field.
- If a particular Stat Server node must connect to the T-Controller interface only of SIP Server, configure the connection by selecting TCport in the Port ID field and by typing TController in the Connection Protocol field.
How Stat Server Pairs Its Nodes to SIP Server Nodes
A Stat Server node connects to the SIP Server applications in the Connections tab according to the following rules:
TController Connection Protocol. If the server connection is configured with TController as the connection protocol and the SIP Server has a port ID of TCport, then Stat Server connects to this SIP Server as to a T-Controller.
IProxy Connection Protocol. If the server connection is configured with IProxy as the connection protocol and the SIP Server has a port ID of IPport, then Stat Server connects to this SIP Server as an Interaction Proxy.
No Specified Connection Protocol. If no connection protocol is specified, then Stat Server connects to SIP Server both as a T-Controller and an Interaction Proxy if the corresponding ports are specified within SIP Server configuration.
Configuring Stat Server in High Availability mode
A high-availability (HA) architecture implies the existence of redundant applications: a primary and a backup. These applications are configured so that if one fails, the other can take over its operations without significant loss of data or impact to business operations.
Stat Server supports both types of redundancy in Genesys software:
- Warm Standby
- Hot Standby. For more information see the Hot Standby (HA) topic in Stat Server User's Guide and HA specific configuration options in RTME Options Reference Manual.
Configuring Secure Connections in an HA Environment
Stat Server connects to server applications by reading the properties of its own Application object in Configuration Server and connecting to each of the servers that are listed under the Connections tab in Genesys Administrator/GAX. Each connected application, in turn, has its own properties and advanced transport parameters—for example, TLS mode, client-side port definition (CSPD), IP address, security certificate signatures, backup servers—that define how connections are to be made.
In warm standby mode, Stat Server tries to connect to the backup application only after repeated attempts to connect to the primary application have failed. The backup application does not have to be listed among Stat Server connections in order for these attempts to take place. In this scenario, however, Stat Server uses the connection parameters that are specified within the properties of the primary application to connect to the backup application. This propagation of parameters to the backup application is the default behavior.
Starting with release 8.5.109, Stat Server supports hot standby mode.
But, what if you want Stat Server to use instead those parameters that are specified within the application properties of the backup application—a different CSPD, for instance? When both TLS and HA are enabled and you require individual security settings for each connection, you must add the backup application explicitly to Stat Server’s connections list in order for Stat Server to read its properties.
This configuration will cause Stat Server to generate the error; however, selecting Yes to continue the assignment will yield the desired effect without Stat Server inadvertently launching the backup server when it is not needed.
To set client-side ports for each connection, refer to the “Client-Side Port Definition” chapter of the Genesys Security Deployment Guide and to all of the chapters within the “Communications Integrity–Transport Layer Security” part of this document for further information.
Configuring Stat Server on Slow Networks
For a big configuration environment on a slow network we recommend to:
- Set up an ADDP connection between Stat Server and Configuration Server with longer timeout.
- Set the packet-size Configuration Server option to lower value to decrease a maximum size of packets sent by Configuration Server. (See Framework 8.5 Configuration Options Reference Manual on the Management Framework page for more information).