Release Notes v8.0.2
*************** IMPORTANT ****************
1. All product documentation is now available at http://knowledgebase.coviantsoftware.com/.
2. All Diplomat Cloud Connector sites MUST BE UPGRADED when upgrading to Diplomat MFT v8.0.x from versions earlier than Diplomat v7.1.
3. If you are upgrading from any Diplomat MFT v5.x or v6.x EARLIER than v6.2:
. BEFORE STARTING THE UPGRADE, be sure you know the domain, username and password for the network account associated with the Diplomat MFT Service. On Windows systems, this account is referenced in the Log On tab of the Properties page associated with the Diplomat MFT Service.
. IF YOU ARE USING CUSTOM PORTS, you must update the server.xml file typically located at C:\Program Files\Coviant Software\Diplomat-j\tomcatWebserver\conf. See http://knowledgebase.coviantsoftware.com/customer/en/portal/articles/1557024-changing-diplomat-services-port-numbers-v6-0 for details on how to change port numbers.
4. Upgrading directly from v4.x or earlier of Diplomat Transaction Manager to Diplomat MFT v6.0 or later is not supported, please contact Coviant Software Support before proceeding.
5. The web.xml file is replaced during the Diplomat v5.x installation. The current web.xml file is renamed web.xml.old. If you believe that you have made changes to any settings in the web.xml file, please contact Coviant Software Support before proceeding.
6. The web.xml file is NOT replaced during an upgrade from Diplomat v5.x to Diplomat v6.x, v7.x or v8.x.
7. In Diplomat MFT Standard and Enterprise Editions v6.2 through v7.0, jobs using File Monitoring can stop monitoring unexpectedly. No notifications are sent when the monitoring stops, so the Diplomat administrator is unaware of the problem. At this time, we strongly recommend that you DO NOT USE the File Monitoring feature for critical file transfer jobs, especially if you have seen this problem with your Diplomat implementation.
*************** IMPORTANT ****************
Version 8.0.2 bug fixes
. Fixed problem introduced in v8.0.1 where encrypt, decrypt, sign and verify settings were lost from partners and transactions when restoring backup files
Version 8.0.1. bug fixes
. Fixed display of geographic location data when using the Test button on FTP, FTPS, SFTP, HTTP and HTTPS partner profiles.
. Fixed problem where saving a transaction while it was executing would cancel the executing job. The job would appear to complete with no errors, but only some of the files would be processed.
. When a transaction is saved make sure the values in the encrypt, decrypt, sign and verify fields are coordinated with the key definitions in the partner profiles. Also, automatically correct this problem during a merge or restore.
Version 8.0 enhancements:
. When using search/move features for keys, partners or transactions, leaving the 'containing phrase' field blank displays an unfiltered list of objects.
. Enter 'Accelerate' into the 'containing phrase' field when All Fields is selected to identify any SFTP partners that have 'Accelerate transfers' selected.
. Added Reset with accelerator CTRL-R to the top level menus for Public Keys, Key Pairs, SSL Certificates, Partners (Enterprise only) and Transactions.
. Added accelerators for the Search/Move items of Partners (Enterprise only) and Transactions - CTRL-P and CTRL-T.
. Added support for Windows Server 2016.
. Added ability to add Integrity Protected Packets to PGP-encrypted files.
STANDARD AND ENTERPRISE ONLY
. Add initialization error messages to server startup email going to IT Support email addresses.
. Added ability to zip source files before transferring and unzip destination files after transferring. New PRE_ZIP and POST_ZIP fields added to SQL audit database to summarize zip process in particular jobs.
. Added ability to start Diplomat Service in 'safe startup mode' with all transactions suspended. Right-click on the Transactions folder to unsuspend any transactions that were not suspended before the Diplomat Service restart.
. If in use, the SQL audit database is updated to add multiple columns to the JOB_AUDIT and JOB_AUDIT_ARCHIVE tables the first time the Diplomat Service is started after an upgrade to v8.0. No data conversion is done, but the SQL audit database can no longer be used by earlier versions of Diplomat MFT.
. Added fields for API and FILE_MONITORING to SQL audit database to indicate how jobs were initiated.
. Added support for shared folders in Citrix Sharefile partner profiles.
Version 8.0 bug fixes:
. Ensure that the AEK field is cleared when 'Encrypt' is not selected, which resolves a problem that occurred when attempting to restore a backup file with a record containing an AEK, but 'Encrypt' was not selected.
. Ensure that Email Settings can be saved with either or both of the sending and receiving email servers/accounts being undefined.
. Do not allow transactions or partners with no names or just blank spaces for names.
. Ensure that SMB partner profiles that are defined with a non-blank Directory field can successfully overwrite destination files.
. Ensure that default diplomat.lic licenses under Program Files folder are deleted after initial Diplomat Service start-up.
. Do not delete anonymous partner profiles with no matching transactions on 'safestart' or if errors occurred during Diplomat database initialization.
. Ensure log entries are made when an anonymous partner is deleted from the database on Diplomat Service startup.
. Corrected error that occurred when attempting to recover a previously deleted private key pair.
. Added missing user information to 'Last Updated' information on some screens, including the Job Queue Settings pop-up.
. Changed scheduling so that previously defined 'excluded days' are not considered when the Recurrence Type is Weekly.
. Corrected scheduling error that occurred when scheduling window spanned midnight. Jobs do not stop at midnight, but now run until the end of the scheduling window.
. Support RIPEMD-160 as a hash algorithm.
. Added new columns to the job table of the audit database to capture when jobs were initiated by an API request or file monitoring.
. Corrected problem when expand/collapse folders in left navigation tree was not working reliably.
. Instead of adding Run Now jobs to the back of the queue with all other scheduled jobs, run the job immediately even if the "maximum number of jobs" limit has been reached.
. Fixed error in getting correct file modified date when using subfolders in the source file name field.
. When a Diplomat Scripting Agent request gets a connection error, wait 5 seconds and then try again up to a total of 3 times before failing the job.
. Changed names of .jnlp files (used by Diplomat Web Launch) created during a Diplomat install to start with "sample" to avoid overwriting existing .jnlp files. Users should rename the files to remove "sample" when using Diplomat Web Launch.
. Resized pop-up dialogs, including Search/Move, such that fields are visible upon opening.
. Removed some Java exception messages from the audit database.
. Fixed problem generating reports when using a Diplomat Client opened by Web Launch.
. Corrected problem where the post-command working directory field was displaying the pre-command working directory field content.
. Corrected a problem where a Run Now dialog would not display the summary information at the end of the job if the associated transaction was saved while the job was running.
. Corrected problem where a second job based on a transaction would start while an earlier job based on the transaction was still running.
. Corrected problem where attempts to create new sub-folders on FTP, FTPS and SFTP destinations were not occurring.
. If multiple debug files are created because of FTP failures during a file transfer job, ensure that all debug files are added to the troubleshooting zip file.
. Increased length of the FILE_STATUS_REASON field in the FILE_AUDIT and the FILE_AUDIT_ARCHIVE tables in SQL audit database from 128 to 255 characters to reduce the number of times the field is truncated.
. A bug introduced in v7.3.x caused the SQL audit database version number not to be written to the database. Starting with Diplomat MFT v8.0, a missing database version number will be treated as if it were v7.3.x.
. If a left-nav item is selected and the user scrolls it so that it is not visible, the left nav will not scroll back to the selected left-nav item when the display refreshes.