Upgrading

Existing users of commercial editions of JSCAPE MFT Server are entitled to 1 year of free upgrades and technical support. To obtain access to the latest version please contact JSCAPE via the Help Desk.

1. If you are an existing licensed user wishing to upgrade please contact the Help Desk to obtain a valid license key for this version. Previously generated license keys may be incompatible with the current version and may result in application starting in evaluation mode.

2. The steps outlined below are for in-place upgrades. If you wish to perform an upgrade + migration, read the page 'Migrating JSCAPE MFT Server'

3. If you encounter a "HTTP ERROR 500" issue when attempting to access a domain via the web UI (HTTP/S service) after an upgrade, please follow the instructions outlined here.

4. If you are using Oracle Java, we strongly recommend you use at least Java 8 Update 161. If you are using an Oracle Java 8 patch earlier than Update 161, you need to install the JCE Unlimited Strength Jurisdiction Policy Files.

5. If you are using database logging, you need to execute the following SQL command against the database that stores the logs:

This will add the application_instance_id column, which is not added automatically during upgrades.

This process is available only to versions 6.2 and above when using GUI installer. Upgrades may only be performed against versions 5.0 or above. If you are currently using a version prior to 5.0 then you must uninstall/delete current version and reinstall/reconfigure new version.

2. When prompted where to install JSCAPE MFT Server select the same installation directory as your current installation.

3. The installer for JSCAPE MFT Server will detect that a previous version of JSCAPE MFT Server is installed and will prompt you for a directory in which the current version may be backed up.

4. Continue with the installation process as normal. Once installation is complete your server configuration settings from previous version will be automatically migrated from previous version to current version.

1. Any logos or text label settings that you have made to web interface WILL NOT be migrated during upgrade process.

2. Note, for Windows environments the JSCAPE MFT Server service will revert to using the Local System account after an upgrade. If JSCAPE MFT Server is accessing shared network resources (e.g. UNC paths) then you may need to update JSCAPE MFT Server service to use an account with access.

Upgrades may only be performed against versions 5.0 or above. If you are currently using a version prior to 5.0 then you must uninstall/delete current version and reinstall/reconfigure new version.

The steps needed for the manual process vary depending on your previous version. If your version is Pre-9.3, follow the Pre-9.3 instructions. If your version is 9.3.x and higher, follow the Post-9.3 instructions.

Note: Several Linux distributions exhibit slow response as a result of the newly introduced FIPS TLS library. To prevent this issue, please install haveged before upgrading JSCAPE MFT Server

2.	Rename/move (DO NOT DELETE) the old installation directory to a different directory (e.g. JSCAPE_MFT_Server_old)

Install the new JSCAPE MFT Server version (Note: Just do Steps 1 and 2 of the installation instructions. DO NOT run the commands for configuring/initializing the database, administrative user, administration service, etc. i.e. Don't run js-addadmin, js-database-configuration, js-web-configuration js-client-configuration, and so on.)

4.	Copy license.lic from <renamed_oldinstalldir> into <newinstalldir>/etc

5.	Copy 'users' directory from <renamed_oldinstalldir> into <newinstalldir>/

6.	Copy the '-XmxNNNm' line of the server.vmoptions file in the <renamed_oldinstalldir> to the server.vmoptions file in the <newinstalldir> if the value of that parameter in the former is bigger than the one in the latter.

7.	Copy <renamed_oldinstalldir>/libs/actions/*jar files into <newinstalldir>/libs/actions/ , if there are any.

8.	Copy <renamed_oldinstalldir>/libs/ext/*jar files into <newinstalldir>/libs/ext/ , if there are any.

Execute the following commands while INSIDE <newinstalldir>

./js-database-configuration -configure

./js-database-configuration -init
./js-db-migration -dir <renamed_oldinstalldir> -exclude-log-searches
./js-update-web-resources -dir <renamed_oldinstalldir>

NOTE: If you are upgrading from version 8.8 and earlier, you will have to configure the Web/REST settings. Run the following command:

./js-web-configuration -host [REST ip address] -port [REST port] -timeout [timeout in minutes]

10. Connect to the following web management interface URL using a browser. This is now the only way to manage the server. <rest_port> is 11880 by default.

If users are unable to connect after the successful upgrade then please open each domain and check that IP Access > IP Access page has the following "allowed" rules for the following IP Mask. If it's empty, then please manually add an allow rule for these 2 IP Masks.

Note: Several Linux distributions exhibit slow response as a result of the newly introduced FIPS TLS library. To prevent this issue, please install haveged before upgrading JSCAPE MFT Server

4.	Install updated version of JSCAPE MFT Server making sure to use same installation directory as previous install.

5.	Copy any JDBC driver JAR files you have installed from backup libs/jdbc directory to libs/jdbc directory of current installation.

6.	Copy any custom actions you have installed from backup libs/actions directory to libs/actions directory of current installation.

7.	Copy any custom authentication or 3rd party JAR from backup libs/ext to libs/ext directory of current installation.

8.	Copy data and users directories from backup into installation directory.

•	<backup>/jdbc.dat or <backup>/etc/jdbc.dat to <current installation>/etc/jdbc.dat

•	<backup>/client.cfg or <backup>/etc/client.cfg to <current installation>/etc/client.cfg

•	<backup>/ssl.cfg or <backup>/etc/ssl.cfg to <current installation>/etc/ssl.cfg

•	<backup>/ssl_ibm.cfg or <backup>/etc/ssl_ibm.cfg to <current installation>/etc/ssl_ibm.cfg

•	<backup>/license.lic or <backup>/etc/license.lic to <current installation>/etc/license.lic

•	<backup>/etc/database.properties to <current installation>/etc/database.properties

10.	Copy *.vmoptions files from backup directory to current installation directory.

11.	Run the ./js-database-configuration -update -previous-version <previous server version> command from within the installation directory.

12.

Run the ./js-update-web-resources -dir [path-to-your-backup] command from within the installation directory. This command will import and merge changes made to certain labels and logos in the user Web interface in the previous installation. You need to specify the location of the previous installation's backup in the [path-to-your-backup] parameter.