TIBCO MDM Customization Guide - TIBCO Product Documentation

146| Chapter 6 FileWatcher You can also customize the Java class,com.tibco.mdm.workflow.engine.activities.FilesAndDirectoriesCleaner, which purges the Work directory content and Temp directory content. This classis used in the PurgeFilesThroughShellScript and PurgeTempFiles workflowactivities. A sample Java class, FilesAndDirectoriesCleaner.java, is located inthe $MQ_HOME\common\standard\samples\workflow directory.Invoking the Activity From the Standard Purge WorkflowThe isAdvanced parameter of the UpdateEvent activity is commented by default.To invoke the AdvancedPurge activity from the workflow, uncomment theisAdvanced parameter.Publish and Validate ActionsThese actions initiate a synchronization workflow for the specified catalog.Specify an existing catalog name. This works exactly the same as way assynchronizations initiated from the user interface. These actions do not requireany data to be present in the input file. The input file simply acts as a trigger andcould be 0 bytes. The most common implementation is to generate a 0-byte file byusing the UNIX command ‘touch’. Make sure the file name is unique. This triggerfile should be created in the directory identified by the URI.Note: When the action is specified as Publish, the Catalog element should refer tothe synchronization profile name.Parameter Description Valid values Mandatory DefaultMasterCatalog The repository name. Any existing repositoryname.Catalog Name. Any existing catalogname.Y -Y -Action The action to be taken. PUBLISH or VALIDATE Y -PRIM0065064183212PUBLISHMQ_COMMON_DIREAI/PrimDataTIBCO MDM Customization Guide