All versions of this manual
X
Welcome to Linkurious administration manual v4.2.1. Use the menu to access other documentations.
  1. Introduction
  2. FAQ
  3. Getting started
    1. Version support policy
    2. Release notes
    3. Client requirements
    4. Graph DB Feature Map
  4. Deploying on premise
    1. Technical requirements
    2. Downloading
    3. Installing
    4. Starting Linkurious
    5. Stopping Linkurious
    6. Cluster mode
  5. Configuring
  6. Troubleshooting
    1. Checking Linkurious status
    2. Reading the logs
    3. Getting support
    4. Managing licenses
    5. Vulnerabilities
  7. Importing graph data
    1. Neo4j
    2. Memgraph
    3. Amazon Neptune
    4. Cosmos DB
    5. Spanner Graph
    6. Updating your graph data
  8. Updating Linkurious
    1. Checking for updates
    2. Backing up your data
    3. Update procedure
  9. Configuring data-sources
    1. Neo4j
    2. Amazon Neptune
    3. Memgraph
    4. Google Spanner
    5. Cosmos DB
    6. Alternative IDs
    7. Merging data-sources
    8. Advanced settings
  10. Resource management
    1. Managing spaces
    2. Managing tags
  11. Search index
    1. Search Option Comparison
    2. Neo4j Search
    3. Elasticsearch
    4. OpenSearch for Amazon Neptune
    5. Azure Search
    6. Incremental Indexing
    7. Numerical/Date search
  12. User-data store
    1. Migrating to an external database
    2. Backing-up your store
  13. Web server
  14. Authentication
    1. Getting started
    2. LDAP / Active Directory
    3. SSO with Azure
    4. SSO with Google
    5. SSO with OpenID Connect
    6. SSO with SAML2 / ADFS
    7. Configuration
  15. Access control
    1. Managing users
    2. Managing groups
    3. Standard access-rights
    4. Property-key access-rights
  16. Guest mode
    1. Guest mode
  17. Data Schema
    1. Property types
    2. Hiding data
    3. Strict mode
  18. Alerts
    1. Configuration
  19. Entity resolution
    1. Requirements
    2. Installing
    3. Configuring
    4. Accessing Entity Resolution
    5. Managing mappings
    6. Running Entity Resolution
    7. Viewing Results and explanations
    8. Node Grouping and Collapsing
    9. Managing the license
    10. Troubleshooting tips
  20. Email Notifications
    1. Configuration
  21. Visualizations appearance
    1. Default styles
    2. Default captions
    3. Default properties order
    4. Geographic tiles
  22. Audit trail
    1. Log format
  23. Webhooks
  24. Observability
  25. Plugins
  26. Deep link
 

Entity resolution: Requirements

This section describes the technical requirements to install and run Entity Resolution in Linkurious Enterprise.

Technical overview

Entity Resolution is a separate service that runs independently of the Linkurious Enterprise server. The Entity Resolution server is powered by Senzing and communicates with the Linkurious Enterprise server through a configured HTTP endpoint.

To use Entity Resolution:

  1. Install and start the Entity Resolution server as a Docker container. See "Installing" section.
  2. Configure Linkurious Enterprise to connect to the Entity Resolution service via URL. See "Configuring" section.

Requirements & prerequisites

Before using Entity Resolution, make sure your environment meets the following requirements:

  • The version of Linkurious Enterprise must be v4.1.12 or later
  • The data-source must be Neo4j
  • The data-source must not be in read-only mode
  • The APOC plugin must be enabled on the Neo4j database
  • The Entity Resolution feature must be enabled and configured in Linkurious Enterprise's global configuration
  • A valid Entity Resolution license must be included in your Linkurious Enterprise license file

If any of the above conditions are not met, Entity Resolution will not be available in the UI. Users will be shown a contextual explanation (e.g., unsupported vendor, read-only mode, or missing configuration).

Example of "unsupported data-source vendor" message.

Entity Resolution server: hardware requirements

For a local testing environment:

  • Any OS with Docker installed
  • At least 4 GB of RAM.

For production environment:

  • Linux with Docker
  • At least 7 GB of RAM.
  • At least 4 CPU Cores.
  • Connection to a MySQL or MsSQL database server that uses Solid State Drives or NVMe storage (provision approximately 1GB of storage per 50K records).
  • You also need to fine-tune your database to get decent performance, please read this article

For more details, please refer to Senzing's technical documentation: