Classic IEG Targets

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:

importieg - This target imports all IEG files in a specified directory to the database. This command takes two parameters - directory and overwrite.
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.

importiegscript - This target imports an IEG script from a file system to the database. This command takes two parameters - IEG file and overwrite.
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.

importiegcomponent - This target imports all IEG data (IEG scripts and question groups) from the ieg subdirectory of a specified component to the database. This command takes two parameters - component and overwrite.
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.

importiegsubdirs - This target imports all IEG data (IEG scripts and question groups) from the ieg subdirectory of subdirectories of a specified directory to the database. This command takes two parameters - directory and overwrite. This target is used when it is required to import IEG data from multiple components.
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.

importquestiongroup - This target imports an IEG question group from a file system to the database. This command takes two parameters - IEG file and overwrite.
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.
exportiegscript - This target exports a script definition (.sx file) from a database to the file system. This command takes two parameters - scriptid and component. Exported scripts will be saved and named as [specified rulesetid].sx in the <SERVER_DIR>/components/[specified component]/ieg folder.
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).
exportiegscripttodir - This target exports a script definition (.sx file) from a database to the file system. This command takes two parameters - scriptid and exportdirectory. Exported scripts will be saved and named as [specified rulesetid].sx in the specified export directory.
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).
exportfulliegscript - This target exports a specific script definition (.sx file) and its associated group definitions(.gx files) from the database to the file system. If any of the files exported are read only, a warning will be reported and the file will not be overwritten. The exportfulliegscript command takes two parameters - scriptid and component. The exported script is named as [specified scriptid].sx and the associated question groups are saved and named as [associated questiongroupid].gx in the <SERVER_DIR>/components/[specified component]/ieg folder.
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).
exportfulliegscripttodir - This target exports a specific script definition (.sx file) and its associated group definitions(.gx files) from the database to the file system. If any of the files exported are read only, a warning will be reported and the file will not be overwritten. The exportfulliegscripttodir command takes two parameters - scriptid and exportdirectory. The exported script is named as [specified scriptid].sx and the associated question groups are saved and named as [associated questiongroupid].gx in the specified export directory.
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).
exportquestiongroup - This target exports a question group definition (.gx file) from database to the file system. This command takes two parameters - groupid and component. Exported question groups will be saved as [specified rulesetid].gx in <SERVER_DIR>/components/[specified component]/ieg folder.
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).
listiegscripts - Produces a list of all the IEG scripts available in the database.
listquestiongroups - Produces a list of all the question groups available in the database.
migrateiegscript - Migrate a Classic IEG script definition to an IEG2 script definition (use -Dscriptfilename= -Dinputdir= -Doutputdir=).
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.
validatealliegscripts - Validates the IEG scripts.