Express Batch

Express Batch processing can significantly improve NA batch performance; in this mode NA batch skips additional configurations provided by Engage One Server during delivery channel definition, thus reducing I/O operations. Resources such as Keymaps, Journals and, Lookup Tables can be assigned to the template in Designer or defined/overridden via OPS settings in EngageOne Server as described below.

  • Express Batch processing applies to non-interactive templates created in EngageOne Designer. Refer to Publishing for EngageOne in Designer and the Designer User's Guide for further information.

  • File assignments for the template can be made, in the EngageOne Server environment for resources such as:
    • Active content
    • Message content
    • Keymaps
    • Lookup tables

    Assignments can be made either through the EngageOne Administration or, at NA-batch execution using an OPS (override) file. Refer to Using overrides for further information.

  • The XML processing file used for Express Batch processing allows you to specify the OPS file used for the NA batch run. Refer to XML processing file for further information

  • You can dynamically define parameters used in your OPS file using symbols either on the NA batch command line or, within the OPS file. Refer to XML processing file for further information.

Points to note when running NA-batch:

  • Processing restrictions - to allow for the enhanced NA-batch performance, The following features are not available :
    • Splitting of input data,
    • sorting criteria,
    • inclusion conditions,
    • recipient processing,
    • user defined report processing.
  • Output variable support - only the following output variables are allowed:
    • ${SYSTEM_TIME},
    • ${SYSTEM_DATE},
    • ${INCREMENT}.

  • Missing resources - Where templates are missing resources, a symbol is used in the EngageOne Administration application to flag this, as shown below:

    In this case, we are missing Lookup Table resources. The missing resources must be exclusively resolved either through EngageOne Administration application or at NA-batch runtime using OPS setting. Note that settings defined in the OPS file take precedence over those made in the Administration application.

  • Multiple template processing - where multiple templates are published in EngageOne Designer, only the name of the first template will be shown in Template Management. You must specify this template name in the XML configuration used by NA-batch. On successful completion of the batch run output for all templates will be generated.

  • Multiple output device processing - a delivery channel must be specified for each output device selected when the template was published in EngageOne Designer, for example:

    A template is published using the Express Batch processing option with one PDF and one AFP output device in EngageOne Designer. In this scenario, one PDF delivery channel and one AFP delivery channel must be specified in the EngageOne Administration application.

  • Journals for Publishable Active Content - Only the Structured XML Journal is supported in Publishable Active Content used with Express Batch processing templates. Any other journal type entries will not appear in the output.

  • Output path and file name configuration - You can set the output path and file name via the OPS file or in the Administration application. It is important to note that assignments made in the OPS file take precedence over those set in the Administration application.