The Classic Intelligent Evidence Gathering Guide provides an introduction to scripts and question groups within Classic IEG. The database can be populated by using the Classic IEG editor to define these scripts. However, support is also provided for representing the groups and scripts as xml data. Although the files are consistent with well and fully formed xml, the file extensions are modified to denote the contents as script (.sx) and question group(.gx). These xml data files can be created and manipulated directly to allow for the synchronization between these files, and the database. A number of extra targets have been introduced to enable this:
directory - This parameter denotes the directory from which IEG scripts and question groups are imported.
overwrite (Optional) - This is an optional flag with the default value as false, indicating whether the database should be overwritten if an imported script or group already exists.
For example:
build importieg
-Ddirectory=
<
SERVER_DIR>/components/core/ieg
-Doverwrite=true
Where <SERVER_DIR>/components/core/ieg denotes the path to the import directory and true denotes the flag to overwrite the database if a file already exists.
ieg.file - This parameter denotes the full path of the IEG script to be imported.
overwrite (Optional) - This is an optional flag with the default value as false, indicating whether the database should be overwritten if the script already exists.
For example:
build importiegscript
-Dieg.file=
<
SERVER_DIR>/components/core/ieg/PRODUCT_1.sx
-Doverwrite=true
Where <SERVER_DIR>/components/core/ieg/PRODUCT_1.sx denotes the path of the script definition file and 'true' denotes the flag to overwrite the database if the question script already exists.
component - This parameter denotes the component from which to import all IEG data to the database.
overwrite (Optional) - This is an optional flag with the default value as false, indicating whether the database should be overwritten if the IEG data already exists.
For example:
build importiegcomponent -Dcomponent=core -Doverwrite=true
Where core denotes the path of the component and 'true' denotes the flag to overwrite the database if the question script already exists.
directory - This parameter denotes the directory whose subdirectories will be searched for IEG data to import to the database.
overwrite (Optional) - This is an optional flag with the default value as false, indicating whether the database should be overwritten if the IEG data already exists.
For example:
build importiegsubdirs -Ddirectory=<SERVER_DIR>/components -Doverwrite=true
Where <SERVER_DIR>/components denotes the path of the directory and 'true' denotes the flag to overwrite the database if the IEG data already exists.
ieg.file - This parameter denotes the full path of the IEG question group to be imported.
overwrite (Optional) - This is an optional flag with the default value as false, indicating whether the database should be overwritten if IEG import data already exists.
For example:
build importquestiongroup
-Dieg.file=
<SERVER_DIR>/components/core/ieg/
PRODUCT_1.gx
-Doverwrite=true
Where <SERVER_DIR>/components/core/ieg/PRODUCT_1.gx denotes the path of the question group definition file and true denotes the flag to overwrite the database, if the question group already exists.
scriptid - Identifier of the script that is to be exported from the database.
component - Name of the component to which the script has to be exported (copied).
For example:
build exportiegscript -Dscriptid=PRODUCT_1 -Dcomponent=core
Where 'PRODUCT_1' denotes the identifier of the script that is to be exported from the database and 'core' denotes the name of the component to which the script has to be exported (copied).
scriptid - Identifier of the script that is to be exported from the database.
exportdirectory - Full path of the directory to which the script has to be exported (copied).
For example:
build exportiegscripttodir -Dscriptid=PRODUCT_1 -Dexportdirectory=C:/exportedscripts
Where 'PRODUCT_1' denotes the identifier of the script that is to be exported from the database and 'C:/exportedscripts' denotes path to the directory to which the script has to be exported (copied).
scriptid - Identifier of the script that is to be exported from the database.
component - Name of the component to which the script has to be exported (copied).
For example:
build exportiegscript -Dscriptid=PRODUCT_1 -Dcomponent=core
Where 'PRODUCT_1' denotes the identifier of the script that is to be exported from the database and 'core' denotes the name of the component to which the script and its associated question groups has to be exported (copied).
scriptid - Identifier of the script that is to be exported from the database.
exportdirectory - Full path of the directory to which the script has to be exported (copied).
For example:
build exportfulliegscripttodir -Dscriptid=PRODUCT_1 -Dexportdirectory=C:/exportedscripts
Where 'PRODUCT_1' denotes the identifier of the script that is to be exported from the database and 'C:/exportedscripts' denotes the path to the directory to which the script and its associated question groups has to be exported (copied).
groupid - Identifier of the question group that is to be exported from the database.
component - Name of the component to which the rule set has to be exported (copied).
For example:
build exportquestiongroup -Dgroupid=PRODUCT_1 -Dcomponent=core
Where 'PRODUCT_1' denotes the identifier of the question group that is to be exported from the database and 'core' denotes the name of the component to which the question group has to be exported (copied).
scriptfilename - denotes the name of the file to import.
inputdir - denotes the directory to import from.
outputdir - denotes the directory to write the migrated script to.