Jump to: navigation, search

Interaction Database

Also known as IDB. The database that stores data about contact-center interactions and resources at a granular level of detail.
See also Interaction Concentrator.



Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Database Access Point

Also known as a DAP. An object that provides the interface between an application in the Genesys installation and the databases to which the application requires access. Refer to the Framework Database Connectivity Reference Guide for more information about configuring and using DAPs.



Glossary

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

default-schema

Section: gim-etl
Default Value: No default value
Valid Values: Any valid database owner or schema name
Changes Take Effect: For an extraction DAP, at the next run of the extraction job for the particular data domain; for the Info Mart DAP, on restart of the Genesys Info Mart Server.


Specifies the database schema or owner name, if it is different from the database user ID. If you do not specify this option, the database tables and other database objects are assumed to be owned by the user name that you specify on the DB Info tab.

Note for PostgreSQL: Genesys recommends that you use lower case for all schema names. If you cannot do so, specify the value in case-sensitive mode by surrounding the value with a set of double quotes.

Database Privileges

Genesys Info Mart requires access to source and target databases to perform a variety of operations. This page describes the types of database users and privileges Genesys Info Mart requires.

Database Object Owners and User IDs

Logically, there are four types of users for which you must provision user accounts:

  • Info Mart — The user’s account that is used by Genesys Info Mart jobs to access the Info Mart database schema for the purposes of:
    • Creating and modifying the Info Mart database schema
    • Extracting data from IDB — Applicable only to Microsoft SQL Server when the Info Mart and IDB databases are on the same server or when IDB is on a linked server (db link).
    • Processing the extracted data and storing it in the Info Mart database schema
    • Maintaining the Info Mart database schema
  • ICON — The user’s account that is used by Genesys Info Mart jobs to access the IDB schemas for the purposes of:
    • Modifying the IDB schemas to work with Genesys Info Mart
    • Extracting data from IDB
  • Tenant Admin — The user’s account that is used by a Tenant Administrator to access the Info Mart database schema and Tenant User schema(s) for the purposes of:
    • Creating and dropping the Tenant User schema(s) and views
    • Granting privileges to the read-only tenant users to access tenant-specific views in the Info Mart database schema through the Tenant User schema(s)
  • Tenant User — The user’s account that is used by a read-only tenant user to view tenant-specific data in the Info Mart database schema through views in the Tenant User schema.

Each User ID must have the necessary privileges to perform the required operations against the applicable database. For information about the required privileges, see Required Database Privileges.

In principle, the User ID that you specify to connect to each database does not need to be the same as the Owner ID. You can create the database objects in a schema that is different from the User ID that accesses them, provided that the User ID has the required privileges, with the following exceptions:

  • In PostgreSQL deployments using Genesys Info Mart releases earlier than 8.5.009, the name of the Tenant User schema must be the same as the name of the corresponding tenant User ID.
  • In PostgreSQL deployments that include Reporting and Analytics Aggregates (RAA), the Info Mart schema name must either be public or else be the same as the User ID.

Limitation

For new deployments, Genesys strongly recommends that you follow the Recommendations for User Accounts shown in the table below. Given the range of possible account setups, Genesys does not guarantee that Genesys Info Mart will function with all other user/owner account configurations that might be employed. Furthermore, internal changes in Genesys Info Mart processing over time might mean that, after migration, other user accounts that used to work no longer enable Genesys Info Mart jobs to access IDB or the Info Mart schema for certain purposes.

Refer to the Database User Account Recommendations in the Genesys Info Mart 8.5.x Release Note for information about possible workarounds if you encounter permissions-related issues after deployment.

Important
In Microsoft SQL Server, all database objects are contained in schemas, instead of being owned by a database owner. The SQL Server logins are mapped to database users, who can own objects in the various schemas. In addition, a default schema is configured for each database user, to contain unqualified database objects. In this document, for Microsoft SQL Server, the term Owner ID refers to the database user who owns the object — for example, the database user who created a view.
Recommendations for User Accounts
RDBMS For Database Recommendations
Microsoft SQL Server Info Mart and IDB
  • The Info Mart database should have one Info Mart schema. IDB should have one ICON database schema.
  • If the Info Mart schema is not dbo, contact Genesys Customer Care before executing any SQL scripts and before migration.
Oracle Info Mart and IDB
  • User Name: <Database schema owner>
  • default-schema (DAP option): <Database schema owner>
PostgreSQL Info Mart and IDB
  • The Info Mart database should have one Info Mart schema. IDB should have one ICON database schema.
  • See above for specific requirements for the Info Mart schema name in deployments that include RAA.

Identifying the owner and user accounts that you will use in your Genesys deployment is an important step in your deployment and installation planning. After you have identified the accounts that you will use, record the IDs and passwords on the applicable worksheet that is provided on the Database Worksheets page. You will need this information to create the database schemas and to specify connection parameters when you configure the DAP(s).

Required Database Privileges

The following table summarizes the user account privileges that are required for the respective source and target database schemas.

Important
Genesys recommends that you explicitly grant the required privileges to the respective users. Do not assume that granting DBA privileges will be sufficient to enable the user account to perform all required operations.
Required User Account Privileges
User Account Database Required Privilegesa
Info Mart IDB
  • SELECT on all tables and views (for example, include this user in the db_datareader role in IDB)

Note: This user account on IDB is required only for Microsoft SQL Server when Info Mart and IDB databases are on the same server or IDB is on a linked server (db link).

Info Mart schema
  • CREATE, DROP, and ALTER tables, views, indexes, procedures, and, if applicable, partitions
  • SELECT on all tables and views
  • INSERT, UPDATE, and DELETE on all tables
  • RDBMS-specific privileges that are required to truncate tables
  • CREATE and EXECUTE on all stored procedures
  • (For Oracle only) EXECUTE on DBMS_LOCK
  • (For databases that implement partitioning) RDBMS-specific privileges that are required to CREATE, DROP, and ALTER tables, indexes, and partitions
  • (For PostgreSQL only, if tenant views are used) Tenant view owner permissions
Tenant User schema(s) (For PostgreSQL only, if tenant views are used)
  • In releases earlier than 8.5.010, Schema owner permissions
  • Starting with release 8.5.010, Tenant User role

ICON

IDB
  • SELECT on all tables and views
  • CREATE and DROP tables, views, and indexes
  • INSERT, UPDATE, and DELETE on all IDB tables
Tenant Admin Info Mart schema
  • EXECUTE on all stored procedures
  • CREATE, SELECT, and INSERT on all tables
  • CREATE, DROP, and SELECT on all views and sequences
  • GRANT access to views for Tenant users
Tenant User schema(s)
  • CREATE and DROP views
Tenant Userb Info Mart schema
  • SELECT on the tenant-specific view in the applicable Tenant User schema

Note: Privileges for the Tenant User to access views in the Info Mart schema are granted by the Tenant Admin when the make_gim_view_for_tenant.sql script is run.

Tenant User schema
  • SELECT on all views

a. Privileges are called permissions in Microsoft SQL Server.

b. Applicable only for read-only views, which are strictly required only for multi-tenant deployments.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on June 26, 2018, at 08:05.