This page is intentionally hidden from navigation but remains accessible via direct link. It is retained for internal reference purposes only and may contain outdated or transitional content.
Regenerating Data
Regenerate_data is a script that lets you regenerate generated data types from the archive. It inserts them into the data structure and reaggregates the summarized data.
You need support's assistance to do this. Please coordinate with them to make sure everything goes smoothly.
Requirements
- Open iT Core Server
- Administrative rights
Running regenerate_data
- Windows
- Unix
-
Open a command prompt with Administrator level privileges.
-
Go to the bin directory, which is by default in
C:\Program Files\OpeniT\Core\bin
, run the command:Examplecd C:\Program Files\OpeniT\Core\bin
-
Run the command:
Command Syntaxregenerate_data <parameter 1> <parameter 2> ... <parameter n> <from> <to>
NOTEIf no
--datatype
or--archtype
is given, regeneration for archive typelicpoll2
is assumed.Required Parameters:
Parameter Description <period start>
Use this to specify the date ( YYYY-MM-DD
) for which to start the processing.<period end>
Use this to specify the date ( YYYY-MM-DD
) for which to end the processing. Not required if you will only regenerate data from a single day.Required Parameters for Running Regenerate_data
Optional Parameters:
Parameter Description --archtype <type>
Use this parameter to regenerate data from a specific archive type. --datatype <number>
Use this parameter to regenerate data from a specific data type. Specify the corresponding number of the data type you want to regenerate. --filter <details>
Written as: <key1> = <value1>
This is case-sensitive. Globbing is allowed. See Examples.
Runningregenerate_data
with this parameter saves the regenerated data in the merge directory, which is inC:\ProgramData\OpeniT\Data\incoming\merge
by default.--method <schedule/direct>
Use this parameter to specify what you want to happen to the regenerated data. Choose from: schedule
(default) - does the same as the regular server. Jobs (.spec
) files will be created and placed inC:\ProgramData\OpeniT\Data\temp\LoadManager\pending
by default, where they will be picked up by the normal processing daemon (loadmanager
).direct
- processes jobs by running the filtrator and will not create jobs forloadmanager
. When the generation is done, it will also trigger loading (check_and_split
andadd
).
--bin_dir
Use this parameter to specify the path to the openit_filtrator
application if not in the default directoryC:\Program Files\OpeniT\Core\bin
.--config_file
Use this parameter to specify an alternative filtrator
config file if not in the defaultC:\Program Files\OpeniT\Core\Configuration\filtrator.conf
.--incoming_dir
Use this parameter to specify an alternative directory for the regenerated data if not in the default C:\ProgramData\OpeniT\Data\incoming
.--pending_dir
Use this parameter to specify an alternative directory for the jobs ( .spec
) files created if not in the defaultC:\ProgramData\OpeniT\Data\temp\LoadManager\pending
. Useful with--method schedule
.--nocommit
Use this parameter to generate new data in the default C:\ProgramData\OpeniT\Data\incoming
, but skip loading (check_and_split
andadd
). Relevant with--method direct
.--debug <args>
Use this parameter to get debug information. --verbose
Use this parameter to get verbose debug information. --version
Use this parameter to display the script version information. --dryrun
Use this to show (not execute) the filtrator commands. --help
Use this parameter to display the help text. Optional Parameters for Running Regenerate_data
-
Optional: If you used the
--filter
parameter, the regenerated data are saved in the merge directory, which is inC:\ProgramData\OpeniT\Data\incoming\merge
by default. To continue, you need to move the files from the merge directory to the incoming directory, which is inC:\ProgramData\OpeniT\Data\incoming
by default.
-
Go to the bin directory, which is by default in
/opt/openit/bin
, run the command:Examplecd /opt/openit/bin
-
Run the command:
Command Syntax./regenerate_data <parameter 1> <parameter 2> ... <parameter n> <from> <to>
NOTEIf no
--datatype
or--archtype
is given, regeneration for archive typelicpoll2
is assumed.Required Parameters:
Parameter Description <period start>
Use this to specify the date ( YYYY-MM-DD
) for which to start the processing.<period end>
Use this to specify the date ( YYYY-MM-DD
) for which to end the processing. Not required if you will only regenerate data from a single day.Required Parameters for Running Regenerate_data
Optional Parameters:
Parameter Description --archtype <type>
Use this parameter to regenerate data from a specific archive type. --datatype <number>
Use this parameter to regenerate data from a specific data type. Specify the corresponding number of the data type you want to regenerate. --filter <details>
Written as: <key1> = <value1>
This is case-sensitive. Globbing is allowed. See Examples.
Runningregenerate_data
with this parameter saves the regenerated data in the merge directory in the incoming directory in your defined data_dir ($ROOT_DATA_DIR
) upon Open iT server installation.--method <schedule/direct>
Use this parameter to specify what you want to happen to the regenerated data. Choose from: schedule
(default) - does the same as the regular server. Jobs (.spec
) files will be created and placed in/var/opt/openit/temp/LoadManager/pending
by default, where they will be picked up by the normal processing daemon (loadmanager
).direct
- processes jobs by running the filtrator and will not create jobs forloadmanager
. When the generation is done, it will also trigger loading (check_and_split
andadd
).
--bin_dir
Use this parameter to specify the path to the openit_filtrator
application if not in the default directory/opt/openit/bin
.--config_file
Use this parameter to specify an alternative filtrator
config file if not in the default/var/opt/openit/etc/filtrator.conf
.--incoming_dir
Use this parameter to specify an alternative directory for the regenerated data if not in the default incoming directory in your defined data_dir ( $ROOT_DATA_DIR
).--pending_dir
Use this parameter to specify an alternative directory for the jobs ( .spec
) files created if not in the default/var/opt/openit/temp/LoadManager/pending
. Useful with--method schedule
.--nocommit
Use this parameter to generate new data in the incoming directory, but skip loading ( check_and_split
andadd
). Relevant with--method direct
.--debug <args>
Use this parameter to get debug information. --verbose
Use this parameter to get verbose debug information. --version
Use this parameter to display the script version information. --dryrun
Use this to show (not execute) the filtrator commands. --help
Use this parameter to display the help text. Optional Parameters for Running Regenerate_data
-
If you used
--filter
in runningregenerate_data
, the regenerated data will be put in the merge directory in the incoming directory in your defined data_dir ($ROOT_DATA_DIR
) upon Open iT server installation.
To continue, you need to move the files from the merge directory to the incoming directory.
Examples
This section shows examples when running regenerate_data
with the --filter
parameter.
- Windows
- Unix
Regenerating data with a specific product
-
The
regenerate_data
script assumes you want to filter product(s) if a key is not specified.Exampleregenerate_data --archtype licpoll2 --filter "server035;sentinel" 2023-09-11 2023-10-11
This example will regenerate data with product server035;sentinel from archive type licpoll2 from September 11, 2023 to October 11, 2023.
-
--filter "product=<product>"
Exampleregenerate_data --datatype 102 --filter "product=server175,server370,server75;dsls" 2024-01-12
This example will regenerate data with product server175,server370,server75;dsls from data type 102 from January 12, 2024.
Regenerating data with a specific feature
--filter "feature=<feature>"
regenerate_data --datatype 75 --filter "feature=StandardEngine" 2023-05-01 2023-09-01
This example will regenerate data with feature StandardEngine from data type 75 from May 1, 2023 to September 1, 2023.
Regenerating data with a specific license manager
--filter "license_manager=<license manager>"
regenerate_data --datatype 102 --filter "license_manager=Altair" 2024-02-27
This example will regenerate data with Altair license manager from data type 102 from February 27, 2024.
Regenerating data with a specific daemon
--filter "daemon=<daemon>"
regenerate_data --archtype licpoll2 --filter "daemon=MLM" 2023-06-01 2023-12-31
This example will regenerate data with daemon MLM from archive type licpoll2 from June 1, 2023 to December 31, 2023.
Regenerating data with a specific product and feature
--filter "product='<product>'&feature=<feature>"
Make sure that the feature specified is active for the indicated product.
regenerate_data --archtype flexlog2 --filter "product='server356;arcgis'&feature=Viewer" 2023-05-01 2023-06-01
This example will regenerate data with product server356;arcgis and feature Viewer from archive type flexlog2 from May 1, 2023 to June 1, 2023.
Regenerating data with specific products
--filter "<product 1>|<product 2>|<product n>"
regenerate_data --datatype 102 --filter "server078;sentinel|server965,server966,server967;dsls|server036,server037,server038;altair" 2023-07-01 2024-01-01
This example will regenerate data with product server078;sentinel, server965,server966,server967;dsls, and server036,server037,server038;altair from data type 102 from July 1, 2023 to January 1, 2024.
Regenerating data with specific features
--filter "feature=<feature 1>|<feature 2>|<feature n>"
regenerate_data --archtype licpoll2 --filter "feature=HyperWorks|SolverInApp|GlobalZoneAP|GlobalZoneEU" 2022-01-01 2022-04-01
This example will regenerate data with features HyperWorks, SolverInApp, GlobalZoneAP, and GlobalZoneEU from archive type licpoll2 from January 1, 2022 to April 1, 2022.
Regenerating data with specific products and features
--filter "product=<product 1>|<product 2>|<product n>&feature=<feature 1>|<feature 2>|<feature n>"
Make sure that the features specified are active for the indicated products.
regenerate_data --datatype 75 --filter "product=server758;adskflex|server06v;slbsls|server03v;arcgis&feature=DataReViewer|MultiFlash_Asphaltene|" 2023-05-01 2023-06-30
This example will regenerate data with products server758;adskflex, server06v;slbsls, and server03v;arcgis, and features DataReViewer and MultiFlash_Asphaltene from data type 75 from May 1, 2023 to June 30, 2023.
Regenerating data with a specific product
-
The
regenerate_data
script assumes you want to filter product(s) if a key is not specified.Example./regenerate_data --archtype licpoll2 --filter "server035;sentinel" 2023-09-11 2023-10-11
This example will regenerate data with product server035;sentinel from archive type licpoll2 from September 11, 2023 to October 11, 2023.
-
--filter "product=<product>"
Example./regenerate_data --datatype 102 --filter "product=server175,server370,server75;dsls" 2024-01-12
This example will regenerate data with product server175,server370,server75;dsls from data type 102 from January 12, 2024.
Regenerating data with a specific feature
--filter "feature=<feature>"
./regenerate_data --datatype 75 --filter "feature=StandardEngine" 2023-05-01 2023-09-01
This example will regenerate data with feature StandardEngine from data type 75 from May 1, 2023 to September 1, 2023.
Regenerating data with a specific license manager
--filter "license_manager=<license manager>"
./regenerate_data --datatype 102 --filter "license_manager=Altair" 2024-02-27
This example will regenerate data with Altair license manager from data type 102 from February 27, 2024.
Regenerating data with a specific daemon
--filter "daemon=<daemon>"
./regenerate_data --archtype licpoll2 --filter "daemon=MLM" 2023-06-01 2023-12-31
This example will regenerate data with daemon MLM from archive type licpoll2 from June 1, 2023 to December 31, 2023.
Regenerating data with a specific product and feature
--filter "product='<product>'&feature=<feature>"
Make sure that the feature specified is active for the indicated product.
./regenerate_data --archtype flexlog2 --filter "product='server356;arcgis'&feature=Viewer" 2023-05-01 2023-06-01
This example will regenerate data with product server356;arcgis and feature Viewer from archive type flexlog2 from May 1, 2023 to June 1, 2023.
Regenerating data with specific products
--filter "<product 1>|<product 2>|<product n>"
./regenerate_data --datatype 102 --filter "server078;sentinel|server965,server966,server967;dsls|server036,server037,server038;altair" 2023-07-01 2024-01-01
This example will regenerate data with product server078;sentinel, server965,server966,server967;dsls, and server036,server037,server038;altair from data type 102 from July 1, 2023 to January 1, 2024.
Regenerating data with specific features
--filter "feature=<feature 1>|<feature 2>|<feature n>"
./regenerate_data --archtype licpoll2 --filter "feature=HyperWorks|SolverInApp|GlobalZoneAP|GlobalZoneEU" 2022-01-01 2022-04-01
This example will regenerate data with features HyperWorks, SolverInApp, GlobalZoneAP, and GlobalZoneEU from archive type licpoll2 from January 1, 2022 to April 1, 2022.
Regenerating data with specific products and features
--filter "product=<product 1>|<product 2>|<product n>&feature=<feature 1>|<feature 2>|<feature n>"
Make sure that the features specified are active for the indicated products.
./regenerate_data --datatype 75 --filter "product=server758;adskflex|server06v;slbsls|server03v;arcgis&feature=DataReViewer|MultiFlash_Asphaltene|" 2023-05-01 2023-06-30
This example will regenerate data with products server758;adskflex, server06v;slbsls, and server03v;arcgis, and features DataReViewer and MultiFlash_Asphaltene from data type 75 from May 1, 2023 to June 30, 2023.