http:\/\/winmerge.org\/<\/a><\/p>\nExpect new line items in the config files if upgrading to a new version of Ephesoft Transact.<\/p>\n
Adjust customized settings as found.<\/p>\n
Examples of lines you would not change would be completely new config lines that exist in new config files but not in old ones. These configuration files are primarily the *.properties files that are found in:<\/p>\n
<Ephesoft Installation Directory>:\\Ephesoft\\Application\\WEB-INF\\classes\\META-INF\\<\/strong><\/p>\nAn example of acceptable differences between files would be changes to paths of the database, SharedFolder<\/strong>, or computer names (if you moved these parts of the environment to various locations).<\/p>\nAn example of a configuration that may have changed is the imagemagick.properties<\/strong> file, which contains different compression settings for TIF and PDF files. If these were previously changed from the default values, they may have reverted back to the default settings.<\/p>\nIn some config files, such as user-connectivity properties, config entries that used to have separate lines for LDAP and AD may have consolidated config lines that are now used for both. In these cases, careful consideration should be made before making changes.<\/p>\n
For clustered environments, closely check the workflow and reporting properties files against the backup files for consistency across cron expressions.<\/p>\n
Restore any custom Tomcat memory settings.<\/p>\n
<\/p>\n","protected":false},"featured_media":0,"parent":28328,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","doc_tag":[],"yoast_head":"\n
Ephesoft Transact 2019.1 Upgrade Guide - Single-Server - for Linux | Ephesoft Docs<\/title>\n\n\n\n\n\n\n\n\n\n\n\n\t\n