Jump to: navigation, search

Configuration Database

After you have created a database in your DBMS (see Databases), you can populate the tables of the Configuration Database manually (using your DBMS tools).

Setting Up the Configuration Database

If you install Configuration Server and the Configuration Database separately, you must install and configure an SQL Server client for your database type on the same host where Configuration Server is running. Please refer to the Framework Database Connectivity Reference Guide for recommendations on environment settings for your database client.
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.
  1. In the directory in which Configuration Server is installed, open the sql_scripts folder.
  2. Open the folder that matches your database type.
  3. Load and execute the initialization script that corresponds to your DBMS and your environment (enterprise or multi-tenant), as listed in the table below.
  4. Tip
    If you are using the DB2 DBMS, Genesys recommends using the DB2 Command-Line Processor to run Genesys SQL scripts. [+] Show steps
    DBMS Enterprise Script Name Multi-Tenant Script Name Multi-language Script Name (see Note)
    DB2 init_single_db2.sql init_multi_db2.sql Enterprise:

    Microsoft SQL init_single_mssql.sql init_multi_mssql.sql Enterprise:

    Oracle init_single_ora.sql init_multi_ora.sql Enterprise:

    PostgreSQL init_single_postgre.sql init_multi_postgre.sql Enterprise:

    Note: Use the multi-language scripts if you are setting up Configuration Server in multi-language mode.
  5. Load and execute the script that loads the CfgLocale table into the initialized database, depending on your database type, as shown in the table below.
  6. Tip
    If you are using the DB2 DBMS, Genesys recommends using the DB2 Command-Line Processor to load and execute the script, as follows: [+] Show steps
    DBMS Script Name
    DB2 CfgLocale_db2.sql
    Microsoft SQL CfgLocale_mssql.sql
    Oracle CfgLocale_ora.sql
    PostgreSQL CfgLocale_postgre.sql

About the Initialized Configuration Database

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 Technical Support before you do so.

The Configuration Database contains the following predefined objects, which allow initial access to the database through Genesys Administrator:

  • A User object with user name set to default, and password set to password. Use this Master Account to log in to the Configuration Layer for the first time. A user logged on through this Master Account has all possible privileges with respect to objects in the Configuration Database. The Master Account is not alterable in any way, and you should not use it to perform regular contact center administrative tasks. Rather, it exists as a guarantee that, no matter what happens to the regular accounts, you will always be able to access the Configuration Database.
    Genesys recommends changing the default user name and password of the Master Account during the first session, securing these login parameters, and using the Master Account for emergency purposes only. For regular operations, create a real working account and add it to the access group Super Administrators. (By default, this Access Group has the same privileges as the Master Account.) Use this real working account for any subsequent sessions.
    For instructions on creating new configuration objects, and working with existing configuration objects, refer to ''Framework 8.1 Genesys Administrator Help''.
  • Four Application Template objects, as follows:
    • Configuration Server
    • Configuration Manager
    • Genesys Administrator
    • Genesys Administrator Server
  • Five Application objects, as follows:
    • confserv object of type Configuration Server.
    • default object of type Configuration Manager.
    • Genesys Administrator object of type Genesys Administrator.
      Consider changing the name of this application during the first session.
    • Genesys AdministratorServer object of type Genesys Administrator Server.
    • Installation Configuration Utility Application object with the name set to ITCUtility. This utility supports configuration updates during installation processes for Genesys components. No additional configuration is needed..
  • The default Access Groups objects: Users, Administrators, and Super Administrators. For more information, refer to Security Considerations.
  • Folders for all types of objects managed by the Configuration Layer.

The Configuration Database also contains a number of other predefined objects (for example, Alarm Conditions) that help you set up some Genesys functionality as you deploy other Framework and solution components.

This page was last modified on May 20, 2014, at 12:26.


Comment on this article:

blog comments powered by Disqus