IBM BJ0NJML Integration Guide - Page 148

JMS Queues Parameter ENTERPRISESERVICE FILENAME USEREXITCLASS TARGETENABLED Description A required parameter value that identifies the enterprise service name that the cron task uses to process all files that are located in the source directory. An optional parameter value that determines whether the cron task data load process selects source files based on its file name. An optional custom processing class value that defines additional cron task capability (for example, file load order). A required Boolean flag value that determines whether the cron task runs in a specific application server. The default value is 0 (false). When set to a value of 1, the application server where the cron task was created is defined as a dedicated server for that particular cron task instance. All XML files that are available in the source directory are associated with a specific external system - enterprise service when you add a value to the EXTERNALSYSTEM, SOURCEDIRECTORY, and the ENTERPRISESERVICE parameters. These XML files also are loaded into the integration framework. The files that match the cron task file name property are associated with a specific external system - enterprise service and are loaded into the system when you add a value to the EXTERNALSYSTEM, SOURCEDIRECTORY, ENTERPRISESERVICE, and FILENAME parameters XMLFILECONSUMER Cron Task Processing Properties Keep in mind the following cron task processing properties for inbound messages: T File processing order - The order in which files are loaded on to the server that is determined by the XML file time stamp. The cron task user exit class can be used to overwrite the inbound message processing logic. T File split - Multi-noun files that are processed by the XMLFILECONSUMER cron task are split before they are written to the queue. The cron task identifies if the file that is loaded is a multi-noun XML file. If the XML file is a multi-noun file, the integration framework uses the split tag value and XML schema (when default schema is not being used) to identify the node in which the file split occurs. T Queue processing - The XMLIN cron task identifies the queue in which the XML file is loaded. The location is based on the queue (continuous or sequential) specified at the external system and enterprise service level. The cron task creates an index file (recovery_filename.txt) that contains a reference to the last successfully processed noun when you process a multi-noun file. The entry in the index file is updated when the noun is successfully 134 Integration Guide