Retail Pro 8 ccmaintv2.exe ECM integration to prevent re-polling of data

Retail Pro 8 ccmaintv2.exe ECM integration to prevent re-polling of data

In order to use the ECM integration function of ccmaintv2.exe, you need to pass the /C: parameter. It takes lists of paths to ECM folders (i.e. those folders where Ecm.exe and EcmProc.exe are located). In the case where you have multiple ECM installs pointing to the same Retail Pro 8 data (some people do that) you need to pass those paths separated by a comma (no blank spaces in between), e.g. "/c:d:\ecm,d:\ecm_extra,d:\ecm_backup". You can surround the entire /C: parameter with quotation marks to make sure it's all parsed as a single parameter.

For each Retail Pro 8 data file scanned, this tool will also scan Polling folders in all listed ECM installs. It will go through each station and collect a list of CRC files corresponding to that data file. Then every time it changes a credit card record (either because it needs to be cleared, or because it needs to be re-encrypted with a new key) it will also calculate a new CRC for each document containing a credit card number before and after re-encryption, compare the CRCs and if they are identical it will update the CRC record in the ECM files to keep them in sync. Thus, if a document (receipt/SO/customer) was already confirmed by ECM prior to re-encryption it will stay confirmed.


1) Since re-encryption will not invalidate ECM's confirmations you need to run this tool on each remote individually, you can't just re-encrypt one side and poll all the documents by ECM (or rather, you cannot just poll differences, you have to poll ALL). On the other hand, running this tool locally is faster than re-polling all receipts, sales orders, and customers.

2) This tool can be used to re-encrypt or clean all credit cards in the case of compromised database. The old tool would only help if you wanted to clear credit card numbers. The new tool can also re-encrypt them with new keys without clearing.

3) Do not combine running this tool with any other application touching Retail Pro 8 data (e.g. make sure polling, RP8 tools etc. are not running).

4) This tool DOES NOT re-encrypt POSRes files and securedoc files, those need to be securely deleted manually.

5) This tool DOES NOT operate on the Demo folder, only on the RPRO folder.

6) If you have multiple ECM installs pointing to the same database and you want to keep confirmations intact you MUST indicate all paths in /C: parameter in the same run, because it's impossible to find out whether a document was confirmed or not after credit cards are re-encrypted and saved.

7) If you DO NOT want to keep confirmed documents and want to re-poll all modified documents by ECM - you do not need to supply the /C: parameter, but keep in mind that in this case ECM will be scanning and processing out all those documents until it gets them all confirmed through normal polling means.

8) Do not try to run two or more instances of the same tool in the same RPRO folder - it does not have exclusive mode locks (for performance reasons, since it will operate on potentially very large data set) and can corrupt files in the process.


Published on Mar 18, 2014 in Store Operations, EFT & Payments


Find Another Article