MCRE Configuration Parameters

This section describes the configuration parameters required by, and the WebSphere® Application Server parameters that need to be updated for, the MCRE task.

Table 1 shows the configuration parameters required by the MCRE task.
Table 1. MCRE Task Configuration Parameters
Parameter Required Default Description
Target directory Yes None The path to which MCRE file sets are saved. If Gateway is installed, this path must be the Gateway outbound source directory. For example, the Gateway outbound source path would be install_directory\check\v409\Gateway\outgoing\source.
Working directory Yes None The path of the working directory. This directory is used as a temporary repository while the extract file is created. An example path would be install_directory\check\v409\Distribution\mcre\working.
Transmission Definition Yes None The name of the transmission definition to use for this task. If the transmission definition includes a maximum size, use a value greater than 1,000,000 bytes.

For more information about creating transmission definitions, see Transmission Definitions Management.
Record size in bytes No The size of the extracted detail data The logical record size, in bytes, of the output file. If specified, it must be larger than or equal to the size of the extracted detail data.
State No RELEASED Specifies the state (TRANSMITTED or RELEASED) of outbound batch (ICL) files to include in the data file.
Business categories No All Specifies the business day categories to include in the output data file. This is a list of the individual categories to extract, separated by commas. The value All is used to extract all of the categories.
Bank numbers No All The bank numbers to include in the data file. A value of All extracts all banks. Insert commas to separate specific banks. All bank numbers specified must exist in the bank table of the FTM database.
User exit class name No None The fully qualified name of an optional user exit. For example, samples.SampleUserExit
Repost on maximum output file size exceeded No false Indicates if the task should request a re-post of the extract when the data file reaches the maximum size specified in the transmission definition. The valid values are true or false.
Note:
  1. When the task is running end of day and this parameter is set to true, an output file that would exceed the maximum file size is split into multiple, smaller output files.
  2. When the task is running end of day and this parameter is set to false, an output file that would exceed the maximum file size is not extracted. This causes the execution to fail and the remaining batches (ICLs) must be extracted by restarting the task.
Data file extension No .dat The file extension used to create the data file. After running the MCRE task, a data file is created with the specified extension.
Route file extension No .rte The file extension used to create the route file. After running the MCRE task, a route file is created with the specified extension.
Trigger file extension No .eof The file extension used to create the end-of-file file. After the MCRE task completes running, the end-of-file file is created to notify Gateway that the file set is completed.
End of day file extension No .eod The file extension used to create the end-of-day file. At the end of the day, the MCRE task creates a file with a list of all extracted MCRE files for the business day.
Trackable interval Timeout No 5 The interval, in minutes, used when creating a file expected event entry for the extracted data file. A value of zero (0) is used to disable the file tracking process.
Small file maximum No 300 Defines, for performance monitoring purposes, the maximum number of bytes in a small file.
Medium file maximum No 20000 Defines, for performance monitoring purposes, the maximum number of bytes in a medium file.
Presentment work threads No 2 The number of threads used to process batches (ICLs).
Note:
  1. The value of this parameter must be greater than 0. To improve processing performance, the value of this parameter should be greater than 2.
  2. Depending on the availability of resources, setting this parameter to a very high value may result in degradation of the overall system performance.