# Configuring LicensePredictor

The LicensePredictor allows administrators to analyze trends and usage patterns according to the expected usage level. LicensePredictor also sends an email alert to update the administrators about the detected anomalies for products and features.

To configure the email settings of the LicensePredictor:

This scheduler file runs a python script that creates usage forecasts for the configured data types.

1. Open core_forecast.oconf in the scheduler directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\scheduler.

2. Locate and set active value to true to activate forecasting.

   ...
    7|    forecast
    8|    {
   ...
   16|        active
   17|        {
   18|          type=bool
   19|          value=true
   ...

3. Save the changes.

Specify special dates in forecast-config.json to customize holidays and special dates for the forecast model.

1. Open forecast-config.json in the Configuration directory, which is by default in C:\Program Files\OpeniT\Core\Configuration.

2. Specify the values for each pair.

   • holiday_dates - list of dates separated by comma/s (,). Enclose the values with double quotations (""). The format of the date is [mm/dd/yyyy] (e.g. ["4/21/2019", "12/25/2019"]).

   • holiday_name - a descriptive name for the purpose of the item.

   • upper_window - the number of days after the specified date to include in the occurrence.

   • lower_window - the number of days before the specified date to include in the occurrence.

      1|{
      2|   "Holidays": [
      3|      {
      4|         "holiday_dates": ["12/25/2019","12/25/2022","12/25/2021"],
      5|         "holiday_name": "Christmas",
      6|         "lower_window": -1,
      7|         "upper_window": 0
      8|      }
      9|   ]
     10|}

   To add a new date, add a comma ( , ) after the closing bracket ( } ) and copy the attribute-value pairs. Specify the values for this set of pairs.

   The attribute-value pair order is not strict; on the Easter example, "holiday_name" is placed before "holiday_dates". This will not cause any problem.

3. Save the changes.

This example specifies to ignore Christmas, Easter, and Houston Rodeo as holidays by forecast:

1|{ 
2|   'Holidays': [  
3|      {
4|         'holiday_name' : "Christmas",
5|         'holiday_dates' : ["12/25/2019","12/25/2022","12/25/2021"],
6|         'upper_window' : 0,
7|         'lower_window' : -1
8|      }, 
9|      {
10|         'holiday_name' : "Easter",
11|         'holiday_dates' : ["4/21/2019","4/12/2022","4/4/2021"],
12|         'upper_window' : 1,
13|         'lower_window' : -3
14|      }, 
15|      {
16|         'holiday_name' : "Houston Rodeo",
17|         'holiday_dates' : ["2/27/2019","3/3/2022","3/2/2021"],
18|         'upper_window' : 19,
19|         'lower_window' : 0
20|      }
21|   ] 
22|}

The upper_window and lower_window values are used to extend the holiday to a range of days, from lower_window days to upper_window days around each date in holiday_dates.

Either positive of negative numbers can be used to wither place. However, the number of lower_window must be less than the number for the upper_window (which will naturally be the case). Usually, users should desire to enter a negative number for lower_window, since that is extending the holiday_dates earlier, and a positive number for the upper_window since it is extending the holiday_dates later.

On the example above, to include Christmas Eve in addition to Christmas, the value of lower_window is -1, and the upper_window is 0. To include Black Friday in addition to Thanksgiving, make lower_window=0 and upper_window=1.

The FORECAST_CPU_COUNT is a new Open iT directive that can be configured in the openit.cfg file, which is by default in C:\Program Files\OpeniT\Core\Configuration. This directive is exclusively applicable on Windows systems since there is no LicensePredictor support in Unix.

The value assigned to this directive will be employed by the LicensePredictor to determine the quantity of subprocesses it will spawn during forecast processes. Essentially, it regulates the number of subprocesses the LicensePredictor will initiate.

The default value is set to 7. It is recommended to set the value to the maximum CPU count of the Core Server host minus one.

For instance, if the Core Server host possesses 64 CPUs, the recommended value would be 63.