Home
Administration
Administering HCL Discover involves configuring and integrating the HCL Discover client framework with your web applications or mobile native applications, installing and administering the databases used by HCL Discover, defining event objects and configuring events, hit attributes, dimensions, and other object attributes used by HCL Discover to monitor mission-critical metrics of your web application's performance.
HCL Discover Administration Manual
Database Administration
The HCL Discover datastore runs on top of a set of four Microsoft™ SQL Server databases.
Troubleshooting Discover databases
If you are experiencing an access or performance-related issue with your installed Discover SQL database, review the troubleshooting tips in this section, which may help to resolve your issue.
SQL Server configuration
Topics in this section describe ways to correct issues with SQL Server configuration.
Failure to install due to model database size mismatch
During installation of the Discover databases, the Discover Database Manager may report a failure because of a mismatch between the configured database sizes in Discover and the model database sizes that are configured in SQL Server Management Studio.

Administration
Administering HCL Discover involves configuring and integrating the HCL Discover client framework with your web applications or mobile native applications, installing and administering the databases used by HCL Discover, defining event objects and configuring events, hit attributes, dimensions, and other object attributes used by HCL Discover to monitor mission-critical metrics of your web application's performance.
- HCL Discover Administration Manual
  - Discover Admin Overview
    This section is an overview to the Discover system and its components.
  - Discover System Monitoring
    Discover provides several mechanisms for monitoring the health of the Discover system and Discover user activities. This section provides access to the various tools available in the Discover system for monitoring it and its users.
  - Portal Management
    This section contains administration topics for managing the Discover Portal and features available through it.
  - Discover Management System
    The Discover Management System (Manage Services) centralizes configuration management for Discover systems on Windows™-based hosts.
  - Database Administration
    The HCL Discover datastore runs on top of a set of four Microsoft™ SQL Server databases.
    - SQL Server authentication
      This page contains information about the authentication methods and login permissions that are required by Discover for accessing the SQL Server databases.
    - Configuring the Discover Data Service
      The Discover Data Service manages connections between Discover components and services and the databases they are querying. This service allows database connectivity to be managed as a Windows™-based service for security, reliability, and control.
    - Databases
      This section provides some overview information on each of the HCL Discover databases.
    - Database backup strategy
      Your Discover databases should be backed up regularly for recovery and performance reasons. Without valid backups, Discover may be unable to recover customer data in the event of a system failure or data corruption.
    - Troubleshooting Discover databases
      If you are experiencing an access or performance-related issue with your installed Discover SQL database, review the troubleshooting tips in this section, which may help to resolve your issue.
      - SQL Server configuration
        Topics in this section describe ways to correct issues with SQL Server configuration.
        Unable to connect to SQL Server
        If Discover is unable to connect to the SQL Server database, try the following steps:
        Failure to install due to model database size mismatch
        During installation of the Discover databases, the Discover Database Manager may report a failure because of a mismatch between the configured database sizes in Discover and the model database sizes that are configured in SQL Server Management Studio.
        Configuring use of SQL Server dynamic ports
        Discover does not natively support use of dynamic ports when accessing SQL Server. If possible, Discover recommends disabling use of dynamic ports.
        Migrating to a new SQL Server
        If you are migrating to a new instance of SQL Server, there are more steps that are required.
        Poor SQL Server performance on 64-Bit operating systems
        Follow this procedure to correct poor SQL Server performance on 64-Bit operating systems.
        SuperSocket information: (SpnRegister): error 1355 in Windows application event log
        If the SQL Server is unable to register a Service Principal Name (SPN), a SuperSocket information: (SpnRegister): error 1355 message is thrown.
        SQL Server blocks access to procedure sys.sp_OAGetProperty
        In some environments, the following error may be displayed in the SQL Server error log:
        Setting the recovery model and logging levels for Discover databases
        To properly maintain the Discover databases, control their size, and improve performance, Discover recommends using the Simple Recovery Model for SQL Server and compressing the log files.
      - Discover database configuration
        Topics in this section describe ways to correct issues with Discover database configuration.
      - Configuration issues
        Use the information in this section to troubleshoot database configuration and data collection issues.
  - Report Access Permissions
    Users whose accounts contain the proper permissions may administer Discover reports. Depending on the type of report, permissions to administer individual reports of that type are configured in the report definition.
  - Managing User Agents
    Through Discover, you can monitor the different types of user agents that contact your web application. Through a provided set of data objects, Discover can identify the type of traffic that is requesting resources from your web application and then monitor counts and other information that pertains to the type of user agent. These objects can be used as the source data for developing a useful set of user agent-related reports, enabling you to closely monitor the composition of traffic to your site.
  - Configuring User Agent Detection
    This section describes how to acquire and maintain the configuration files necessary for parsing of fixed and mobile user agents and how to prepare those files for use in the HCL Discover platform.
  - Configuring User Agent Events
    To use the data that is injected into the [ExtendedUserAgent] section by the Discover SessionAgentTLTRef, a Discover administrator must create events that create charts for this data.
  - User Agent Tools
    These external utilities can be used to monitor and update user agent configuration data that is required by Discover.
  - bot Detection
    Most commercial enterprise web applications are subjected to significant traffic from web crawling bots. Short for "robot," a bot is a software agent that navigates websites to extract information about them. Some bots are used by search engines for indexing pages.
  - Discover Reference Information
    Use the links below to access reference information on file formats, common standards, and more in use by the Discover system.
  - Integrating HCL Discover and Unica Journey
    HCL Discover and Unica Journey integration works with CEP configuration. The CEP configuration enables the event to be sent to CEP and the external systems. Unica Discover-Unica Journey integration is supported from version 12.1.0.3 onwards.
  - Integrating HCL Discover and Unica Interact
    HCL Discover and Unica Interact integration works with CEP configuration. The CEP configuration enables the event to be sent to CEP and the external systems. Unica Discover-Unica Interact integration is supported from version 12.1.0.3 onwards.
  - Selective Deletion
    You can delete sessions and session fragments from the HCL Discover system with the Selective Deletion tool.
  - Using the ArchiveConfig utility
    Run the ArchiveConfig utility to configure and execute Selective Archiving.
  - ELK Configurations
    Before configuring ELK on HCL Discover, there are some prerequisites:
  - Securing Interprocess Communication
    Discover 12.1.8 and above supports the use of a new SSL certificate based mechanism for securing all inter-process communication between the Discover servers. This is important in a distributed environment with multiple servers, as the components of Discover communicate with each other over the network, using a variety of ports.
  - Support for Okta
    From version 12.1.12, HCL Discover supports Okta authentication for customers who wish to use Okta instead of Microsoft Windows NT Authentication.
- HCL Discover Data Export for Data Analysis Administration Manual
- Session Archiving Guide

Failure to install due to model database size mismatch

During installation of the Discover databases, the Discover Database Manager may report a failure because of a mismatch between the configured database sizes in Discover and the model database sizes that are configured in SQL Server Management Studio.

About this task

In rare cases, a customer may change the size of the model database size in their SQL Server installation from the default value of 50 MB. SQL Server Management Studio does not allow databases to be installed below the model database size. For example, if the model database size is set to 250MB, when the Discover Database Manager attempts to install the Discover databases, some installations fail because they are smaller than this minimum limit.

The solution is to do one of the following:

Procedure

Reconfigure the model database size in SQL Server Management Studio to 50MB. For more information, consult the documentation that was provided with your SQL Server product.
Reconfigure the database sizes in Discover Database Manager to be slightly larger than the model database size in SQL Server Management Studio. For the above example, you could set the database size to 260MB.
- Database sizes must be configured through individual filegroups for each database.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box.