Dime.Scheduler is built with performance and scalability in mind. Therefore, it is based on a loosely coupled architecture that separates the main planning application from the connected plugins (responsible for interacting with external applications).
The following components will be installed:
- Dime.Scheduler SQL database: Storage of the planning data.
- Dime.Scheduler website: The main planning application, including the multi back office web service, for communication from the back office application(s).
- Dime.Scheduler Service Bus: Publishes messages to all registered plugins.
- Dime.Scheduler Back Office Plugin database: Storage of the data needed for sending data back to the back office application(s).
- Dime.Scheduler Back Office Plugin Windows service: Plugin for sending data back to the back office application(s).
- Dime.Scheduler Back Office Plugin website: Application for monitoring and reprocessing data sent to the back office application(s).
All components can be installed on different servers but to keep deployment of the application simple we recommend to only split the application components from the database components. This manual will assume a setup including 1 application server and 1 database server. For more complex scenarios please contact us.
Dime.Scheduler's modular and distributed architecture has many upsides, but it also means there are multiple nodes to be installed. This chapter will guide you through all of the following: