Our aim here at Coviant is to improve the usability and flexibility of secure file transfer workload automation, while lowering your operational costs. We’ve been busy on our latest release, Diplomat MFT 8.2. This post takes you through the main changes – many of which are based on your input – and details of how to upgrade.
Five new features for file transfer workload automation
With the new Diplomat MFT 8.2, we’ve accomplished quite a bit beyond the usual bug fixes. We have expanded our capabilities to increase our value to you. I’ll highlight a few notable items here:
- AS2 – We’ve now added the ability to send files using AS2. You can securely send files (messages) to a destination AS2 server over the internet. We support strong cryptography and digitally signed synchronous receipts for non-repudiation. If you’ve dealt with AS2 before, you know how complex it can be. We’ve made it as simple as possible, and we’ve tested against a host of AS2 endpoints to ensure you can hit the ground running.
This new capability is available for all customers running Enterprise Edition, and as an optional component with Standard Edition. If you would like to add AS2, or if you’re running Basic and would like to see what upgrading to Standard can do for you, just let us know. We’re always happy to help.
- Trigger Files – Diplomat already provides you with a wide range of “file ready” conditions to ensure you can easily accommodate your unique processes. We’ve expanded that to include detailed trigger file matching per file, in addition to a single trigger file for all matching source files. Together with flexible variables and the rest of the filtering and conditions, we’ve got you covered.
- Post-transaction File Move – We have long offered you the option to delete a source file after a fully successful transaction. It’s a great feature that helps keep the source directory neat and clean and keeps jobs simple. Based on your input we’ve now added the option to move those source files elsewhere on the source server. This allows the source server to keep a copy of the file without cluttering up your source folder. This is great if you don’t have delete permissions to the source server. Does your business process require that a copy be retained? Solved!
- Transfer Order – We really do listen when you give us feedback! You told us you needed it, so we added the ability for you to choose the order in which matching source files are transferred. By default we still transfer whichever we found first, but now you can choose to transfer them in alphabetical order or by timestamp. Choose whichever option works best for you.
- Ad-hoc REST API – We are committed to continually expanding our REST API. We believe that making Diplomat even more extensible and friendly to our DevOps users can only help increase our value to you and reinforce a foundation we can build on for years to come. In this most recent expansion, we added a new “RunAdHoc” endpoint. API consumers can run any arbitrary transfer job without having to have it predefined. We support JSON payloads and responses for this endpoint. For those who can leverage it, it’s a big deal, and we’re proud of this innovation. As a reminder, we make the REST API available to both our Enterprise and Standard editions.
Beyond these, we have provided numerous additional enhancements:
- Supporting client-side SSL certificates and exporting SSH client private keys.
- We made the interactive version of our Scripting Agent even better.
- For our high-demand customers we optimized folder monitoring using the SMB transport, transaction connection logic, and email notification queues.
- We added options to run the Job History database entirely in memory.
- You can run the scheduler in a new High Frequency mode, too.
- We even created a new ability to export a sanitized version of your configuration (no passwords included). We hope this eases any concerns about providing your configuration to our Support team.
If you’re running a version from 2018 or older, we strongly recommend updating to 8.2 as soon as you can. Version 8.1.1 brought numerous security enhancements, of course, but we also made foundational updates due to licensing changes at Oracle. Updating will eliminate risks associated with this.
Furthermore, you should update Diplomat MFT to v 8.1.1 or higher due to licensing changes with the SFTP and FTPS library formerly used by our software, which was made by JSCAPE. Diplomat MFT versions older than 8.1.1 are no longer considered to be in compliance with JSCAPE licensing.
We’re proud of this new version, and we hope you like it, too. We’re continuing to push forward to make Diplomat continually better into next year and beyond. Do you have any questions or have you encountered any issues? Do you have your own suggestions for improving your particular file transfer automation? Please don’t hesitate to let us know.