Purge and Archive FAQs

The Purge and Archive parameters can be set in the W_PA_SETTINGS variable in /eagle_ml-2-0_custom_cm/w_config_custom.inc file OR in the PurgeArchiveParams taskParameter node of the initial Control Message.

The PurgeArchiveParams taskParameter node may be missed or empty in control message. In this case, Purge and Archive parameters will be taken from the W_PA_SETTINGS variable in the /eagle_ml-2-0_custom_cm/w_config_custom.inc file. This also means that the value of the PurgeArchiveParams taskParameter has higher priority than the W_PA_SETTINGS variable value.

The Purge and Archive mode can be set in the W_PA_MODE variable in /eagle_ml-2-0_custom_cm/w_config_custom.inc file OR in the PurgeArchiveMode taskParameter node in the initial Control Message.

The PurgeArchiveMode taskParameter node may be missed or empty in CM. In this case the mode setting for Purge and Archive will be taken from the W_PA_MODE variable in the /eagle_ml-2-0_custom_cm/w_config_custom.inc file. This also means that the value of the PurgeArchiveMode taskParameter has higher priority than the W_PA_MODE variable value.

Yes. In this case, the Purge and Archive parameters will be read from the W_PA_SETTINGS variable in the /eagle_ml-2-0_custom_cm/w_config_custom.inc file. If the initial CM and W_PA_SETTINGS variable do not contain Purge and Archive parameters then this functionality will be disabled. But, if at the same time the eagle_ml-2-0_custom_cm/w_config_custom.inc file contains old W_CONFIG_FTP_*parameters then the older version of Purge and Archive will be activated.

You can group a lot of commands by the pipe ‘|’ delimiter.

For example, in the w_config_custom.inc file:

<COL TAG="W_PA_SETTINGS"EXPRESSION="'FTP;FOLDER;/CMW/inbound_tst;*;PURGRE;;;0|FILE;FOLDER;cmw/reply;*.xml;PURGE;;;48|'"/>

<taskParameter>
    <name>PurgeArchiveParams</name>
    <dataType>S</dataType>
    <value>
        FILE;ALLMCSTREAMFOLDERS;processing;*;ARCHIVE;data/msgcenter/cmw/custom_ack/;N;72|
        FTP;FOLDER;CMW/inbound_tst;*;PURGE;;;0|
        FTP;FOLDER;CMW/outbound;*;ARCHIVE;data/msgcenter/archive/outbound;Y;72|
        FILE,MCSTREAMFOLDER,cfs_flow_control/outgoing,*.csv,ARCHIVE,data/msgcenter/archive,N,24|
    </value>
</taskParameter>

If you set [clean_type]=ARCHIVE and [is_need_compress]=Y then the archive file will be generated only if there are files to process (so if no files have been selected, the archive file will not be created).

The archive filename will be generated according to the following model:

Replace([path_to_process],’/’,’_’)+’__’+Convert( Today(), 'yyyymmdd' ) +'_' +Convert( CurrentTime(), 'hhmmss' ) + iif(GetPlatform() = 'WIN','.zip','.gz').

For example, in the CMW/outbound folder on a Unix OS box:

CMW_outbound_20140915_010341.gz

For example, in the cfs_flow_control/outgoing folder on a Windows OS box:

cfs_flow_control_outgoing_20140915_010341.zip

For example in all processing folders when [clean_option]=ALLMCSTREAMFOLDERS on a Unix OS box. several archive files will be created for each “processing” stream folder:

cfs_flow_control_processing_20140915_010341.gz

…

eagle_ml-2-0_default_cm_control_message_processing_20140915_010342.gz

eagle_ml-2-0_default_cm_purge_archive_20140915_010342.gz

…

If the archive folder defined in the [archive_folder] parameter doesn’t exist, it will be created.

If the server rules support the older version of Purge and Archive, then to run it the W_PA_SETTINGS variable should be removed (or empty value set to this variable) and then the CM of older version run.

Yes. It is important to make sure that the [path_to_process] does not contain control characters such as “@”, “$”, “#”, “‘”. In this case the path will be ignored. For paths containing “!” an error will be generated.