TIBCO MDM Customization Guide - TIBCO Product Documentation

Using FileWatcher| 151DataServiceUpdate actionsMetadata from the system is exported in the form of JAR, ZIP, or XML files. Suchexport files are used as input to the FileWatcher 'DataServiceUpdate' action.While processing DataSerivceUpdate, FileWatcher extracts the contents of the fileinto a directory such as:MQ_COMMON_DIR/Work/year/month/day/hour/unique_dir_name(where unique_dir_name is a directory created by the system with unique ID).Sample Jar File EntriesThe following are the contents of a sample jar file to be used as input to theDataServiceUpdate action. At the root of the jar is the command XML -request-response.xml. It also contains 2 attachments referred by the commandfile, data.csv, and DataCustodian.xml.• request-response.xml• $MQ_COMMON_DIR/Work/2004/Nov/19/16/55224-0888234/data.csv• $MQ_HOME/config/rules/DataCustodian.xmlThe above entries may get extracted into the following directories:• $MQ_COMMON_DIR/Work/2004/Nov/19/16/1MDNU41Q3G8TJAJT/request-response.xml• $MQ_COMMON_DIR/Work/2004/Nov/19/16/1MDNU41Q3G8TJAJT/commondir/Work/2004/Nov/19/16/55224-0888234/data.csv• $MQ_COMMON_DIR/Work/2004/Nov/19/16/1MDNU41Q3G8TJAJT/mqhome/config/rules/DataCustodian.xmlError ReportingWhen there is an error (including credential/validation errors), FileWatcher sendsa message to the address, specified in the Configurator > Email > Email ReceiverAddress for Errors.This email address should be routed to someone who accesses his or her mail on aregular basis.Note that the errors reported to this email address are technical errors, that is,configuration errors. This does not include email generated by initiatedworkflows.The Application does not start if there is an error in FileWatcher initialization. AllDataSets and users referred in the configuration should exist.TIBCO MDM Customization Guide