Network Locations for Framework Components
This section provides basic data and makes recommendations that will help you select the optimal components for your specific needs, choose a computer for each component, and define the optimal location for each component on the network.
A separate section presents the information for each layer of Framework.
The Configuration Layer is a mandatory part of any Genesys CTI installation. You cannot configure and run any other layers of Framework-or any solutions-unless Configuration Layer components are running.
This section provides recommendations for planning and installing the Configuration Layer components.
The Configuration Database stores all configuration data.
- Never add, delete, or modify any data in the Configuration Database, except through applications developed by Genesys, or through applications instrumented with the Genesys Configuration Server application programming interface (API). If you have compelling reasons for accessing the database directly, consult Genesys Customer Care before you do so.
- Configuration Server treats its information and checks integrity constraints in a case-sensitive manner. Therefore, your SQL database must be installed and configured in case-sensitive mode. Refer to your SQL Server Administrator documentation for additional information.
Configuration Server provides centralized access to the Configuration Database, based on permissions that you can set for any user to any configuration object. Configuration Server also maintains the common logical integrity of configuration data and notifies applications of changes made to the data.
Configuration Server Proxy
To support a large number of clients and/or distributed installations, Configuration Server can operate in Proxy mode. In this document, a Configuration Server that operates in Proxy mode is called Configuration Server Proxy. For more information about Configuration Server Proxy, see Solution Availability.
Genesys Security Pack on UNIX
Genesys Security Pack on UNIX, an optional component of the Configuration Layer, provides the components, such as shared libraries, which are used for generation of certificates and their deployment on UNIX computers on which Genesys components are installed. For more information, refer to the ''Genesys 8.1 Security Deployment Guide''.
The exact configuration of the Management Layer depends on which of the following management functions you would like to use. Genesys recommends that you use all of these capabilities to optimize solution management.
If you intend to use one or more of the Management Layer capabilities, plan to install the components required for each capability, as outlined below. Refer to the ''Framework 8.5 Management Layer User's Guide'' for descriptions of, and recommendations for, these components.
Management Layer Components
This section provides recommendations for planning and installing the Management Layer components.
Local Control Agent
Solution Control Server
Centralized Log Database
As with any historical database, the size of the Centralized Log Database grows with time. When you are planning your installation, keep in mind that:
- The maximum allowable record size is 1 KB.
- The size of the Centralized Log Database depends on:
- The number of applications in the system.
- The log level you have set for the network output for each application.
- The required time the log records should be kept in the database. The following table provides general timing recommendations:
|Logging Level||Supported Call Volume||Recommended Storage Time|
|STANDARD||100 calls/sec||10 days|
|INTERACTION||10 calls/sec||1 day|
|TRACE||5 calls/sec||1 day|
SNMP Master Agent
When planning your installation, Genesys recommends that you use SNMP Master Agent only if both of these conditions apply:
- You want to access the Management Layer functions via an NMS interface; or you have another SNMP-enabled Genesys application and want to access its features via an NMS interface.
- You don't have another AgentX-compatible SNMP master agent in place.
User Interaction Layer (Genesys Administrator)
Install the Genesys Administrator web server preferably in close proximity with Configuration Server. You can then install as many web browsers as required, from which you can access and use Genesys Administrator.
For every switch that you plan to make a part of your interaction management solution, install at least one T-Server application.
T-Server provides an interface between traditional telephony systems and Genesys applications.
Services Layer (Stat Server)
Although StatServer is considered an element of Framework, it is logical to install it when you install the solution that it will serve.
Stat Server tracks real-time states of interaction management resources and collects statistics about contact center performance. Genesys solutions use the statistical data to more "intelligently" manage interactions. Use Genesys Reporting to generate real-time and historical contact center reports based on data that Stat Server collects.
For specific recommendations on Stat Server installation, refer to Stat Server documentation.