|Maintenance Notice - PDF Generation|
|Dynamic PDF generation for web-based content is temporarily unavailable. This maintenance affects dynamic PDF files that are generated from either the HTML-based page or manual that you are viewing. Links that normally allow this functionality have been hidden, and will reappear as soon as the feature is restored.
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.
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.
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.
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.
|Microsoft SQL Server||Info Mart and IDB||
|Oracle||Info Mart and IDB||
|PostgreSQL||Info Mart and IDB||
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.
|User Account||Database||Required Privilegesa|
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||
|Tenant User schema(s)||(For PostgreSQL only, if tenant views are used)
|Tenant Admin||Info Mart schema||
|Tenant User schema(s)||
|Tenant Userb||Info Mart schema||
|Tenant User schema||
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.