smoBackOffice is a system scheduling tool used or running processing referenced in a configuration file, such as Discovery or Network data integration or preimport tasks.
Each type of processing is enabled or disabled depending on customer requirements.
The scheduling tool launches each process referenced in the configuration file, in the listed order and depending on the execution scheduled time.
Note: Priority will be given to the ongoing tasks that will not be interrupted. The new tasks will be queued.
smoBackOffice is shipped as an executable in the <Easyvista>\tools\ folder.
You should not confuse the smoBackOffice system scheduler with the scheduler used to run scheduled tasks, e.g. to run integration models, calculate trends and alerts, send scheduled reports and purge archives.
The preimport task is a preliminary process run before third-party data is integrated in the database. It is used to automate processing that cannot be performed using an integration model.
1. Third-party data sources (e.g. CSV file, database or directory) are read using the connection settings defined in .ini configuration files.
2. Data are stored in work tables.
3. The processing referenced and scheduled in the .ini configuration files is run.
4. All of the data processed is stored in the final tables. You can filter the tables to retrieve only data that is new or modified since the previous processing.
Preimport processing to run SQL scripts before running the model, e.g. data formatting, deletion, normalization, delta differencing.
Preimport task for integrating data using the SCCM gateway.
Preimport task to synchronize third-party data with EasyVista, e.g. incidents.
A preimport task can read and process different third-party data sources.
Each preimport task can be run regularly based on the frequency defined in .ini configuration files.
The scripts for creating or deleting objects must always be run in the SQL Server database before running the preimport task.
You should schedule preimport tasks to be run whenever possible outside platform production periods, i.e. at night, during weekends, or during periods when 24/7 platforms are accessed by the least number of users.
Optimize data processing time and load by performing incremental integration instead of running full integration.
This is the general scheduler for the preimport process.
It indicates the paths of all .ini configuration files used by the process and determines the processing sequence.
It must be placed in the /Preimport/ folder in smoBackOffice.
The third-party data sources used and the connection settings to each of them.
The different processing to be run and their sequence.
They must be placed in the /Preimport/ folder in smoBackOffice.
SQL scripts must be placed in a subfolder in the /Preimport/ folder, e.g. /Preimport/CUSTOMERNAME.
This section lists the SQL scripts to be run before reading or loading data. These are usually queries for purging tables.
Run scripts found in CUSTOMERNAME. Note: Remember to add the symbol = that marks the end of an instruction.
This section lists SQL scripts to be run for loading raw data in work tables. They depend on the third-party data source and can be used to populate new work tables.
Run a script in the CUSTOMERNAME folder. Note: Remember to add the symbol = that marks the end of an instruction.
This section lists SQL scripts to be run for data loaded in work tables.
Standard scripts for standardizing data.
Data normalization scripts that can be customized by each customer, for integration gateways.
Scripts for populating the final tables. These are run after prior processing. Note: You can insert a WHERE clause within the script if certain minor processing is required.
smoBackOfficeClient is a tool for running preimport tasks whenever required autonomously, without using the smoBackOffice system scheduler.
It requires the definition of command lines indicating the configuration files to be run. These can be added to a Batch or PowerShell script and run at a scheduled time using an external scheduler or third-party application.
Nexthink integration enables you to integrate 48 health metrics related to equipment in . As a general rule, it is run every 30 minutes.
==> To be able to ensure this frequency, smoBackOfficeClient is used. Integration is immediately run instead of being placed in the smoBackOffice system scheduler queue.
smoBackOfficeClient is shipped as an executable in the <Easyvista>\tools\ folder.
When you run a task using the smoBackOfficeClient tool, it must no longer be run using the smoBackOffice system scheduler.
You should reduce the number of tasks run simultaneously by smoBackOfficeClient.
You should schedule tasks to be run whenever possible outside platform production periods, i.e. at night, during weekends, or during periods when 24/7 platforms are accessed by the least number of users.
You can define a preimport task to run immediately using smoBackOfficeClient followed by immediate data integration using smoIntegration. To do this, add the two command lines to a Batch or PowerShell script.
2. Go to the <Easyvista>\tools\smoBackOffice folder.
2. Duplicate the file called smoBackOffice.cfg.
3. Rename the file smoBackOfficeClient.cfg.
1. Open a command prompt window.
2. Enter the following command line.
Replace <subfolder> by the subfolder where the the .ini configuration file for the preimport task is located.
Replace <file.ini> by the name of the .ini configuration file for the preimport task.