Description

The information below, shows the default parameter values that are set for the SegmentDataCreatorReceiver and XMLSegmentMergeV2Receiver. When GenRocket auto-assigns the SegmentDataCreatorReceiver and XMLSegmentMergeV2Receiver, it sets default parameters that should allow Scenarios to generate segment data and the resulting merged XML documents in specific subdirectories under the base directory pulled a user's resource.output.directory. 


Default Settings for SegmentDataCreatorReceiver

Each Domain created to represent an XSD complexType is automatically assigned a SegmentDataCreatorReceiver with the following parameter defaults.

  • outputPath - Defines the location to store the generated segment file.
  • subDirectory - Defines the subdirectory name under the outputPath.
  • fileName - Defines the name of the generated segment file (e.g. a Domain named, Organization, gets OrganizationSegment.xml).
  • filePerDirectory - Defines the number of files to be generated per output sub-directory.
  • recordsPerFile - Defines the number of segments to be generated per file.



Default Settings for XMLSegmentMergeV2Receiver

Only one Merge Domain is created and is assigned the XMLSegmentMergeV2Receiver with the following parameter defaults.

  • outputPath - Defines the location to store the newly generated nested XML file(s).
  • outputSubDirectory - Defines the prefix name of subdirectories that are auto created under the outputPath and then appended with a number.
  • configPath - Defines the base directory where the configuration file and XSD file are to be stored.
  • configSubDir - Defines the subdirectory under the configPath directory where configuration file and XSD file are to be stored.
  • configName - Defines the name of the configuration file.
  • filesPerOutputSubDir - Defines the number of files to be generated per output subdirectory.
  • segmentPath - Defines the path to the Segment directory where all segment subdirectories can be found.
  • segmentSubDirectory - Defines the subdirectory under the segmentPath where segment files can be found.