Service Manager Architecture
Last modified on 2023/08/03 11:42
Contents
The Service Manager application is made up of the following:
- The Service Engine Back Office with an interface specifically designed for operational teams and software administrators.
- The Service Apps Front Office with a portal providing services and Web apps specifically designed for end users.
Servers used by Service Manager
Three types of servers are used by Service Manager:
- Apache Web servers (Web Front End): In charge of processing the HTTP requests of users and of returning HTML Web pages.
- Application servers: In charge of processing business requests and providing the data required for the Web server based on the logged-in user ccount and authorizations.
- Database servers (SQL Server): In charge of storing data.
Service Manager databases
Our recommendations on database backups are provided to ensure service restoration in the event of component failure.
Database (schema) | Description | Backup recommendations | ||
---|---|---|---|---|
EVO_ADMIN | This contains the technical configuration of the installation performed, e.g. location of data, number of accounts used. | Perform a daily backup and, at the very least, after each installation or major version upgrade. | ||
EVO_BACKOFFICE | This contains the activity logs and temp tables used for integrations. | Perform a daily backup and, at the very least, after each installation or major version upgrade. | ||
EVO_CONFIGxxxxx | This contains the configuration of the customer environment and interface, e.g. configuration of screens, filters, or views, for the xxxxx account.
|
|||
EVO_DATAxxxxx | This contains customer data, e.g. equipment, users, incidents, or workflows, for a given environment.
|
Recommended backup frequency:
|
||
EVO_REFERENCE | This contains references common to the account, namely certain default values that are required for the application to work correctly. | Perform a daily backup if you have the Discovery module, and, at the very least, after each installation or major version upgrade. |
EasyVista services
EasyVista services are Windows services available on the application server.
- Their names include the prefix Smo (for smart object).
- They are made up of three distinct and independent groups: Application Kernel, Back Office and Monitoring.
- The services in each group can be stopped and started without affecting the other groups.
- The restarting of Back Office and Monitoring services will not affect users.
Description of EasyVista services
Application Kernel
Service | Description | Notes | ||
---|---|---|---|---|
EasyvistaServer | Manages communication between Service Manager and Service Apps and displays infotips in Service Manager |
|
||
SmoASTPlugin | Manages emails sent to inboxes dedicated to the Technical Support Agent for each platform environment |
|
||
SmoAuthenticate | Manages LDAP authentication with bind for REST Web services and end users |
|
||
SmoBroker |
|
|
||
SmoExtendedService | Encrypts SSO information |
|
||
SmoMail | Manages the routing of platform emails |
|
||
SmoPrintServer | Manages report output (printers in the web interface) |
|
||
SmoScheduler | Manages non-externalized scheduled tasks |
|
||
SmoServer | Main service (application engine) |
|
||
ZMO EZV Restart Services | Starts/restarts the application after all components required for the starting or restarting of the platform have been verified |
|
Back Office
Service | Description | Notes | ||
---|---|---|---|---|
SmoBackoffice | Manages data integration, i.e. loading of raw data in specific tables and formatting via SQL scripts prior to integration |
|
Monitoring
Service | Description | Notes | ||
---|---|---|---|---|
SmoMonitoring | Used for application maintenance |
|
Recommended order for stopping and restarting EasyVista services
StopRestartEasyVistaServices
- When stopping services:
- net stop SmoScheduler
- net stop SmoASTPlugin
- net stop SmoPrintServer
- net stop SmoMonitoring
- net stop EasyvistaKernel
- net stop EasyvistaServer
- net stop SmoServer
- net stop SmoBroker
- When restarting services:
- net start SmoBroker
- net start SmoServer
- net start EasyvistaServer
- net start EasyvistaKernel
- net start SmoMonitoring
- net start SmoPrintServer
- net start SmoASTPlugin
- net start SmoScheduler