HighQ Appliance provides a range of connectors that communicate with key systems, for example, Microsoft SharePoint, Active Directory, SQL Server.
Please check the hardware and software requirements for HighQ Appliance, please note there are additional requirements for certain connectors.
Managing connectors
Each type of connection is governed by a separate connector. You can purchase Collaborate and Publisher connectors that permit:
- Active Directory integration (Publisher or Collaborate)
- iSheet integration (Collaborate only - external SQL database, RSS and XML feed)
- Importing content to the Events module (Collaborate only)
- Importing content to the Blog module (Collaborate only)
- File sync using CMIS for Sharepoint and network file share (Collaborate only)
HighQ Appliance is subject to a separate licensing agreement, and is not included with Collaborate or Publisher. Please contact your HighQ Account Manager for more information.
Please contact your HighQ account manager for information on connectors that are not described here.
Please note that Enterprise Key Management (EKM) and the Hybrid storage connector have been replaced with a BYOK solution. Please contact your HighQ representative for more information.
Log in to the HighQ Appliance to see and manage all enabled connectors (connector settings are grouped in 'modules').
Deployment and configuration
Normally, when HighQ Appliance is first deployed, it is pre-configured as specified with your HighQ Account Manager and purchased connectors/modules will be enabled. Further configuration, such as user management, the addition of new modules, or matching updates to your system, can only be performed by an administrator.
HighQ Appliance components and glossary
This illustration shows the structure of HighQ Appliance modules (connectors) and interactions:
Module
A module represents the integration of an external application with HighQ Collaborate, to consume services from external applications. The module works as a manager for the external application integration ('connector') and it holds the integration point mappings and the schedule, under which the specific services are consumed.
External driver
The module uses an external driver to pull in content and services from the external application(s). An external driver is tightly coupled with the external application and the integration method is dependent on the services provided by the external application. If the application supports a web service or web standard way of exposing content and services, then a standard-compliant integration can be developed, which works by using interfaces and is loosely coupled to support version upgrades on either end. A database-based integration will be tightly coupled with the client application and any change in the database for the client application will force an upgrade to our external driver.
Internal driver
An internal driver provides an interaction interface with HighQ applications and because the interface is within HighQ development control, it is easier to make it modular and loosely coupled. A mapping interface exposes the fields to be populated for internal applications.
Driver mapping
To transfer contents from an external to an internal application, a mapping interface defines how the fields are mapped from the external application to the internal application.
Actions
Each module is built to fulfill certain tasks and these tasks are associated with the module as actions. Therefore, predefined actions implement business logic. Actions are specific to the module and the external application that is integrated, e.g. pulling SQL data to an iSheet or users and groups from the active directory.
Schedules
Content resides in the external application and to sync content from external applications, different sync schedules are required to make sure that the system is not overloaded and the applications are synced at an acceptable time interval.
Reports
The dependency on external applications and the installation of the HighQ Appliance within the client network requires effective reporting to ensure that any exceptions or issues can be tracked effectively in the smallest amount of time possible. The reports are generated with the scheduled run of actions and executed against the drivers.
