![]() ![]() If needed, add your custom Certificate Authority (CA).If needed, force users to use HTTPS (see forceHttps: true in Web Server configuration).If needed, configure external authentication.This service account should be the only user on the system to have read and write access to the linkurious/data directory.Make sure Linkurious Enterprise runs under a service account.Ready Linkurious Enterprise itself for production MariaB: replication overview, setting up replicationĤ.If you need high-availability, set up replication Make sure your user-data-store database is secure Schedule regular backups of the user-data store: SQLite is not recommended for production environment: switch to MySQL/MariaDB/MSSQL instead. Ready your user-data store for productionīy default, SQLite is used for the user-data store. Make sure your have the right hardware for Elasticsearchģ.If you are using Linkurious Enterprise with Elasticsearch ![]() Keep in mind that Linkurious Enterprise can be used without Elasticsearch, see search options. Make sure that your graph database is secure: Neo4j: sizing and hardware guide, clustering guide. ![]() Ready your graph database for productionĬonsult with your vendor to make sure that your graph database is installed on appropriate hardware and configured for better performances: The data layer supports several graph databases, as well as indexation engines.įAQ Going to production What should I do before going to production? 1. Multiple external authentication providers are supported (LDAP, Microsoft Active Directory, Microsoft Azure Active Directory, Google Suite, OpenID Connect, SAML2 / ADFS). It can be connected to multiple graph databases at the same time and offers high-level APIs for collaborativeĮxploration of graphs: users can create, share and publish graph visualizations,Īdministrators can control it from its REST API for easy automation and deployment. It implements also a security layer with modular authentication that enables role-based access control policies. It provides a unified REST API to read, write and search into graph databases from multiple vendors The logic layer is a NodeJS-based server. The presentation layer communicates with the logic layer via a JSON-based REST API.Ĭustom presentation layer application can be developed on top of the logic layer. It also provides a user interface to enable data administration and collaboration among end users. It uses our graph visualization library, Ogma, to allow rich interactions with the graph. The presentation layer is a Web application. Linkurious Enterprise is a three-tier application. This documentation will help you install, run and customize Linkurious Enterprise. Welcome to the Linkurious Enterprise administrator documentation. ![]()
0 Comments
Leave a Reply. |