Reference architecture - Virtual Machines
This reference architecture is intended for any infrastructure that utilises virtualisation of machines. This includes most cloud providers and on-premises environments and is particularly suitable for network isolated environments.
Topology
Components
| Component | Description |
|---|---|
| Linkage Users | The end users of the system include application administrators, data managers and linkers. Roles and permissions are configurable. |
| Application/Integration | Orchestration of LinXmart is available through the Web API and allows automation of data workflows in and out of the system. |
| Web VM | Hosts the web site that provides a front-end to the users. On a Windows machine this is typically IIS. It will require access to the database and the Envelope/File Store file share. |
| API VM | Hosts the web API that is used by client applications for automation/integration. On windows this is typically hosted by IIS. |
| Envelope/File Store | A folder that stores the raw data that is ingested into the system and can store linkage map data downloadable from the Web UI. This can be a shared folder, available to the Web and API VMs. |
| Worker VM | The linkage processing is performed on this machine and should be provided enough resources to cater for intended data sizes. |
| MS SQL Server | The primary database stores all project configuration, metadata and application settings. Additional databases are created for each linkage project, keeping project data siloed. |
| Active Directory | AD provides the authentication for the system and users must also be explicitly added to LinXmart. Authorisation is handled internally to LinXmart. |
| SMTP Relay | An optional service that provides LinXmart with the ability to send email notification to users. |