Simple Architecture of Mail & Deploy

Understand the Mail & Deploy architecture. 



Mail & Deploy consists of two main components; server and client. In a typical Mail & Deploy installation, there is one server and one or more clients.

Server 

Each Mail & Deploy environment has at least one Mail & Deploy Server component which manages repositories, executes tasks, provides an interface for Mail & Deploy Clients and hosts Mail & Deploy Hub, which is a web-interface that allows on-demand requests and subscription of reports. You can get more detailed information about the server in the section Server.


Repository

A repository is a database that contains users, user groups, data sources, reports and tasks. Mail & Deploy supports a theoretically unlimited number of repositories, you can organize your report data by splitting it up into multiple repositories if required. Repositories are stored and organized by Mail & Deploy Server. 

Example: If you want to distribute IT reports and Controlling reports in Mail & Deploy, it makes sense to create one repository for each category and allows IT users to access the IT repository only and the Controlling users to access the Controlling repository only.


Client 

Mail & Deploy Clients are used to connecting to a Mail & Deploy Server, open a repository and edit data in that repository by managing users and data sources, designing reports and setting up tasks. The number of clients is not limited you can install as many as you want in your Mail & Deploy environment. Clients communicate with Mail & Deploy Server via the network using a port that you can configure (see Server Configuration). You can get more detailed information about clients in section Client.

T
Team is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.