eMuseum
Have an Idea?Contact SupportGo to Prism docsChoose a Product
Overview
Overview
  • Overview
  • Versions
  • License Tiers
  • System Requirements
  • Architecture
  • Upgrade Guide
  • HTTPS Setup
  • eMuseum API
  • Knowledge Base Articles
    • Adding Google Analytics
    • Email and Logging
    • Creating Custom Groups
  • Webinars
Powered by GitBook
On this page

Was this helpful?

Export as PDF

Architecture

PreviousSystem RequirementsNextUpgrade Guide

Last updated 1 year ago

Was this helpful?

Starting with eMuseum 6, data and media transfers to eMuseum are done on the application level. No direct database connection from eMuseum to TMS is required anymore. For this, the utility application is required on the TMS side to collect the data and media and push both to eMuseum via HTTPS.

The following diagram shows the architecture of eMuseum with network connections between eMuseum, Prism, and TMS:

Arrows indicate the direction of access, not the direction of data-flow. There is no access against the direction of an arrow. For example, the eMuseum server does not initiate a connection to the Prism server.

Prism
Architecture Overview of TMS, Prism and eMuseum.
Drawing