|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.
Enabling Database Access
You configure database access points (DAPs) to specify the database connection parameters and other options that Genesys Info Mart uses to access source and target databases. This page provides general information about DAPs in your Genesys Info Mart deployments.
For information about configuring the DAPs for Genesys Info Mart use, see Configuring Required DAPs.
You must configure DAPs to access the applicable source and target databases in your environment, in order to extract, transform, load, aggregate (if applicable), and maintain all types of data.
The number and type of DAPs that you need depends on your particular deployment topology. For a description of Genesys Info Mart–supported topologies, see Supported Topologies.
At a minimum, you must configure the following DAPs:
- DAPs to access the IDBs from which Genesys Info Mart extracts data. In this document, these DAPs are referred to as extraction DAPs. You must configure one extraction DAP for each IDB.
- One DAP to access the Info Mart database. In this document, this DAP is referred to as the Info Mart DAP.
Genesys Info Mart Server and the jobs that extract, transform, and load data use Java Database Connectivity (JDBC) to access all databases. The DAPs that the Interaction Concentrator server (ICON) uses to connect to IDB are non-JDBC DAPs that are associated with a DB Server.
To simplify your deployment, you can reuse the non-JDBC DAPs in your deployment and make these DAPs suitable for Genesys Info Mart to access the same databases. In other words, you can reuse the existing DAPs that enable ICON(s) to access IDB(s), to enable Genesys Info Mart to access the same IDBs.
Minimal additional configuration is required for you to reuse non-JDBC DAPs, if all of the following conditions are true:
- DB Server is running on the same host as the DBMS server
- the port of the DBMS listener is the default
- (for Oracle) the TNS name and the SID name are identical
Otherwise, jdbc-* options, which you configure in the [gim-etl] section on the Options tab of the DAP application object, enable you to specify the required JDBC connection parameters.
For more information about the JDBC options that you can configure on the non-JDBC DAPs to enable Genesys Info Mart to reuse these DAPs, see Configuring a non-JDBC extraction DAP.
If you have a high availability (HA) deployment topology, you must create additional DAPs. See Enabling High Availability for more information.