Start the Extractor Process

The <extractor-name> parameter in the EXTRACTOR Configuration contains a symbolic server name. This name is defined by the SERVER token in the DEFSSRV and UDEFSSRV files which are located in the <Prognosis_Home>\Server\Configuration folder path. The SERVER token (e.g. #FSCOL) is the logical server name applied to the collector.

Each instance of an Extractor server configures itself according to the EXTRACT statements in the EXTRACTOR Configuration.

The DEFSSRV entry for the default Extractor server is shown below.

SERVER #FSCOL
OBJECT IRADICOL.EXE*
CPU -1
PROMGR_AWARE FULL
DEBUG NO
END_SERVER

* This will be IRADICOL.EXE for Windows and IRADICOL for UNIX and IREXTCOL for HPE NonStop

The DEFSSRV file defines the symbolic name for the default Extractor server as #FSCOL; therefore related EXTRACT statements in the EXTRACTOR Configuration must have FSCOL as their first parameter to be effective.

When a large number of extractor scripts are being run it can be advantageous to divide the load over multiple Extractor servers. This can be done by creating a UDEFSSRV text file in the <Prognosis_Home>\Server\Configuration folder path and adding the required server information.

Example;

SERVER #FSCOL2
OBJECT IRADICOL.EXE
CPU -1
PROMGR_AWARE FULL
DEBUG NO
END_SERVER

The UDEFSSRV file is simply a text file, all parameters, as shown above, should be entered exactly as shown with the only change being the Server field which should be amended to show a new server name, e.g. #FSCOL2.

Only add new servers to the UDEFSSRV file and not to the DEFSSRV file and do not duplicate server names within or between these files.

This mechanism allows multiple concurrent extractions to be defined in two (non-exclusive) ways:

  • A single Extractor server instance can process more than one extraction by having multiple EXTRACT statements using its server name in the configuration.

  • Multiple Extractor servers can be defined in the UDEFSSRV file with one or more extractions defined for each in the configuration by EXTRACT statements matching the symbolic server name of each server.

Provide feedback on this article