Skip to main content
Close announcements banner

Administering Qlik Data Catalyst

Administration features provide a centralized console for operations and services around single server or cluster maintenance, configuration, performance monitoring, integration with Active Directory Network Services, and registration and management of Qlik Sense Connectors for QVD Ingest.

Access Administration functions by clicking on the Admin tab in the top-right navigation ribbon accessible from all Qlik Data Catalyst screens.

Maintenance Services

System maintenance and cleanup services are scheduled and tracked through a calendar and task enablement/prioritization menu.

Application Logs

Application and Server logs are administration-level system diagnostic tools that provide Garbage Collector, Qlik Data Catalyst, and high-level Catalina server health indicators without having to manually navigate into Apache Tomcat logs.

Active Directory integration

Qlik Data Catalyst enables enterprises to dynamically sync Qlik Data Catalyst-managed security with Active Directory (AD) identity services and domain management. LDAP protocol is used to connect to and obtain information from AD.

Data Meter

Data Meter enables administrators to view the size of data ingested to HDFS Receiving Directory and data transformed in Prepare.

Table Meter

Table Meter measures and reports status and compliance for customers with a contractual limit on the number of tables (registered & managed) in Qlik Data Catalyst.

Database driver registration

Users must register drivers for all JDBC source databases. Administration provides a wizard for the modular registration of databases.

System Settings: Level Control

Level Control allows users to control the level at which specified data is managed while retaining a metadata catalog.

QlikView Data (QVD) file import

Qlik Data Catalyst allows users to import QVDs from a mapped instance of Qlik Sense.

Refresh Core_Env.Properties file

Users can refresh the core environment properties. This saves users from having to restart Tomcat Server when changes are made to core_env.properties file.