Server Wide Variables
No edit summary
No edit summary
Line 3: Line 3:
[[File:2020-11-20 10h53 19.png|none|thumb|536x536px]]
[[File:2020-11-20 10h53 19.png|none|thumb|536x536px]]


If you want to access to your Server Wide Variables you have add the variables with same name to your serverside viewmodel. When the serverside viewmodel runs the server will find the matching variable on name. In your ServerSide ViewModel the Server Wide Pre EAL will execute before the rest of your job actions.
When you want to access your Server Wide Variables you have add the variables, with same name as Server Wide Variables, to your serverside viewmodel. When the serverside viewmodel runs the server will find the matching variable on name. In your ServerSide ViewModel the Server Wide Pre EAL will execute before the rest of your job actions.


This is a practical way to give your jobs information that are environment specific.
This is a practical way to give your jobs information that are environment specific.

Revision as of 15:05, 28 March 2022

In the MDrivenServer you can declare Server Wide Variables. This is useful if you want access to gobal variables in your serverside viewmodels for different purpose. Remeber to click Submit to save your Server Wide Variables.

2020-11-20 10h53 19.png

When you want to access your Server Wide Variables you have add the variables, with same name as Server Wide Variables, to your serverside viewmodel. When the serverside viewmodel runs the server will find the matching variable on name. In your ServerSide ViewModel the Server Wide Pre EAL will execute before the rest of your job actions.

This is a practical way to give your jobs information that are environment specific.

The normal use case is to clearly give information to jobs that this is a Production environment and every action can be executed, or this is NOT a production environment and thus you may want hold of exporting data och maybe export data to a different external system than what you use in production.

Special variables - vServerRestartedTime and vSkipQueryAndSkipJob

If you declare a variable vServerRestartedTime:DateTime this will be set to the time where the system was most recently restarted - because of a model evolve or some external event that killed the application. Use this as flag to execute a job depending on if this value is new to what you saw before - or log restarts of your system.

If you declare a Serverside ViewModel variabel named vSkipQueryAndSkipJob:Boolean - and this happen to evaluate to true - the PS-query for the job is skipped.

2020-11-26 14h17 51.png

This new variables would make it possible to execute a job only 1 time after system start - consider this for Job EAL code:

vSkipQueryAndSkipJob:=SysSingleton.oclSingleton.LastTimeTheInitJobWasExecuted>vServerRestartedTime  -- remember to set SysSingleton.oclSingleton.LastTimeTheInitJobWasExecuted in the initjobb to DateTime.Now
This page was edited 98 days ago on 02/10/2024. What links here