distributed architecture¶

a distributed insight architectured is recommended for big installations

Example for a distributed architecture:

Backend-Node: JEE-Server for backend processes (download-scheduling, indexer)
Web-UI-Node: JEE-Server for requests of web-clients
Mobile-UI-Node: JEE-Server for requests from mobile-clients
DB-Node: Database-Server
- insight-database
- Elasticsearch

DistributedArchitekture

It is strongly recommended to use separate VMs for separate nodes so that they are independent of each other i.e. downtime of a UI-Node does not affect the backend-node. If more then one JEE-Server is running on one server then please see port-offset

Its possible to install more than one Mobile-UI-Node and use loadbalancing for the UI-Requests. But only one instance of Backend-Node can be installed.

insight-middleware-config.zip does contain a config-snippet for loadbalancing with Apache. It is recommended to use caching for ProfileDB. Please also see comments for Profile DB

Description of a distributed standard maximo-installation (v2-environment):

Deployments for Backend-node:¶

crawl.war
download.war
download-roots.war
download-schedule.war
insight-auth.war
insight-change-events.war
insight-indexer.war
insight-monitoring.war
insight-profile.war
insight-properties-web.war
insight-reldb.war
insight-server.war
insight-cache.war

Deployment for Mobile-UI-node:¶

crawl.war
download.war
download-gateway.war
download-roots.war
insight-auth.war
insight-change-events.war
insight-db.war
insight-esproxy.war
insight-gateway.war
insight-profile.war
insight-profile-gateway.war
insight-properties-web.war
insight-reldb.war
insight-server.war
insight-cache.war

Deployment for Web-UI-node:¶

crawl.war
insight-auth.war
insight-change-events.war
insight-db.war
insight-esproxy.war
insight-gateway.war
insight-profile.war
insight-profile-gateway.war
insight-properties-web.war
insight-reldb.war
insight-server.war
insight-cache.war