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.

Caution:

  • You must perform, at the very least, one full daily backup of the MSSQL server for the different environments, i.e. production, preproduction, etc.
  • When installing a fix, EasyVista recommends that you perform, at the very least, an incremental backup when stopping the production environment, and a backup once functional acceptance for the deployment of the fix is completed.
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.
  • xxxxx refers to a EasyVista account:
    • 40000: Demo environment (test case database)
    • 50004: Production environment
    • 50005: Development environment (sandbox database)
EVO_DATAxxxxx This contains customer data, e.g. equipment, users, incidents, or workflows, for a given environment.
  • xxxxx refers to a EasyVista account:
    • 40000: Demo environment (test case database)
    • 50004: Production environment
    • 50005: Development environment (sandbox database)
  • For each account (i.e. 40000, 50004, or 50005), the EVO_DATAxxxxx and EVO_CONFIGxxxxx databases are inseparable.
 Recommended backup frequency:
  • 40000 database: Perform a backup after each installation or major version upgrade.
  • 50004 database: Perform a full daily backup and an incremental hourly backup per worked period.

   Check the impact on platform availability when running the backup.

  • 50005 database: Perform a backup based on the modifications made during tests.
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
  • This service depends on the SmoServer service.
SmoASTPlugin Manages emails sent to inboxes dedicated to the Technical Support Agent for each platform environment
  • Service is stopped during the normal functioning of the application server.
  • This service depends on the SmoServer service.
  • There must be only one service enabled for each platform.
  • It accesses the shared file server.
  • In case of malfunction or when it is stopped, the application will still work but no incoming email will be processed.
SmoAuthenticate Manages LDAP authentication with bind for REST Web services and end users
  • This service depends on the SmoServer service.
SmoBroker
  • Performs load balancing across the different application servers
  • Counts licenses
  • Notifies all SmoServer services of modifications to the platform configuration
  • This service is not dependent on other services but requires the database server to be running in order to access data.
  • There must be only one service enabled for each platform.
  • Configuration file: smobroker.ini.
SmoExtendedService Encrypts SSO information
  • This service depends on the SmoServer service.
  • Optional service.
SmoMail Manages the routing of platform emails
  • This service depends on the SmoServer service.
SmoPrintServer Manages report output (printers in the web interface)
  • This service depends on the SmoServer service.
  • In case of malfunction or when it is stopped, the application will still work but reports will not be sent to printers.
  • Configuration file: smoPrintServer.ini for the application server.
SmoScheduler Manages non-externalized scheduled tasks
  • This service depends on the SmoServer service.
  • There must be only one service enabled for each platform.
  • In case of malfunction or when it is stopped, the application will still work but no scheduled tasks will be run.
SmoServer Main service (application engine)
  • This service depends on the SmoBroker service.
  • It accesses data, and as such, the database server must be running.
  • It accesses the shared file server.
  • Configuration files: smoserver.ini for the application server and smo_config.php for the Web server.
ZMO EZV Restart Services Starts/restarts the application after all components required for the starting or restarting of the platform have been verified
  • This service is not dependent on other services.

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
  • This service is not dependent on other services but requires the database server to be running in order to access data.
  • There must be only one service enabled for each platform.
  • The restarting of this service will not affect users.
  • Configuration file: smobackoffice.cfg.

Monitoring

Service Description Notes
SmoMonitoring Used for application maintenance
  • Service is stopped during the normal functioning of the application server.
  • This service is not dependent on other services but requires the Web server to be running.
  • The restarting of this service will not affect users.
  • Configuration files: config.cfg for the application server, and config.php, connexions.xml and destinations.xml for the Web server.

Recommended order for stopping and restarting EasyVista services

StopRestartEasyVistaServices

   Only for On-premises customers. SaaS-based customers must create a change request using MyEasyVista.com to ask the EasyVista CMC team to restart the services.

  • 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
EndStopRestartEasyVistaServices
Tags:
Powered by XWiki © EasyVista 2022