When running the extractor from the command line, all input parameters
should be passed using the -D option, i.e. -D<parameter
name>=<parameter value>.
Mandatory Parameters:
- component - the name of the destination component folder
where the extractor output is written (e.g. 'custom'). If this folder
does not exist in SERVER_DIR/components the extractor will report an
error.
- serverDir - this parameter is automatically set (from the
SERVER_DIR variable) when running the extractor from the command line.
It must be specified if running the extractor from Eclipse, and defines
the location of the 'EJBServer' folder.
- lowerKey - specifies the lower or the starting key for the
key range used to generate replacement primary keys for extracted
database records.
- upperKey - specifies the upper or the end key for the key
range used to generate replacement primary keys for extracted database
records.
Parameters defining the Evidence Type extraction strategy, i.e. which
evidence types to extract. At least one of these parameters has to be
specified or the extractor will report an error:
- extractAll - if this parameter is provided with a value of
'true', all Active Dynamic Evidence Types on the system (in the
EvidenceTypeDef table) will be extracted. This parameter
overrides the other extraction strategy parameters. If it is absent or
its value is not 'true' the subsequent parameters will be
considered.
- etExtractionList - specifies a list of Dynamic Evidence Types
to be extracted. The list must contain one or more Evidence Type logical
names separated by semicolons (no white space allowed). This parameter
overrides the etCodePrefix parameter.
- etCodePrefix - specifies a Dynamic Evidence Type code prefix,
e.g. 'DET'. Dynamic Evidence Types with codes beginning with the
specified prefix will be extracted. The code prefix is a customizable
application property (curam.dynamicevidence.type.code.prefix in Dynamic
Evidence – located in the configuration section of the administration
application).
Optional Parameters:
- extractProductLinks - enables extraction of Dynamic Evidence
Type links to Products. If set to true the relevant records from
ProductEvidenceTypeDefLink entity will be extracted.
- extractICLinks - enables extraction of Dynamic Evidence Type
links to Integrated Cases. If set to true the relevant records from
AdminICEvidenceTypeDefLink entity will be extracted.
- datamanagerDir - name of the directory where datamanger (DMX,
blob, clob) files are to be written. This directory is located in the
destination component directory and it is automatically created if it
does not exist. The default directory name is 'data'.
- dmxDir - name of the directory where DMX files are written.
This directory lives in the datamanagerDir directory and it is
automatically created if it does not exist. The default directory name
is 'initial'. Inside this folder, the tool creates directories for blob
and clob files.
- codetableDir - name of the directory where codetable (CTX)
files are written. This directory is located in the destination
component folder and it is created automatically if it does not exist.
The default directory name is 'codetable'.
- tabDir - name of the directory where section configuration
(SEC) files are written. This directory is located in the destination
component folder and it is created automatically if it does not exist.
The default directory name is 'tab'.
- preserveRangeKeys - This parameter specifies a list of Range
Keys. Primary keys of extracted database records will remain unchanged
if the key falls inside one of the rangeKeys specified in this property.
If not withing any range specified the primary key will be generated
based on the upperKey and lowerKey properties specified. Specify as
follows:- -DpreserveRangeKeys="20000-20999,23000-23999"