Aegis ‘Depot’ Activity – md5 File Checksum

Aegis ‘Depot’ Activity – md5 File Checksum

If you've ever dealt with files in an automated workflow, copied / moved / executed etc. how sure were you of the files integrity?   Having a workflow copy a remote file 'successfully' only to discover later on the file was modified or incomplete is an automation failure.  The md5 checksum algorithm is widely used a method to guarantee a files integrity, as the algorithm germinates a 'fingerprint' for a file which will change if any change occurs to the files such as a transmission or disk error.  md5checksums are often available when files are downloaded from the internet so you can very the files integrity once it is downloaded.  More complex algorithms exist which will also verify against malicious file changes - md5 while will detect many malicious changes cannot be guaranteed up to detect all.

So how will this work in Aegis?  Pretty simple.  Up until now i've seen a  few scripted solutions out there, this one is a simple 1 input activty, point it at the file and it will output the md5checksum.  The checksum is in the familiar format of a 32 length HEX value for example : 201e751fc09c7cfc2d806c21b3738102

At design time the activity has a file browser input so you can browse to the file, hardcoded tect, or use input builder to allow dynamic file input.

s0

 

At runtime, the output is a simple string value which can easily be compared within your workflow to a known checksum value

 

s1

As in the example, files can exist locally or remotely via UNC path.   Running the activity to a remote file however will take a long time if the file is large as the file needs to be read into the activity in order to generate the checksum.

 
Labels (1)
Attachments

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
10 of 10
Last update:
‎2020-01-09 16:45
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.