Upgrading

 Top  Previous  Next

Existing users of commercial editions of MFT Server are entitled to 1 year of free upgrades and technical support.  To obtain access to the latest version please visit the website.

 

Important Notes

 

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 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:

 

alter table log add column application_instance_id VARCHAR(255);

 

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

 

Related Topics

 

Restoring from the backup

HA considerations

Consideration for Trigger action

 

Upgrade Process - Graphical User Interface

 

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.

 

1.  Run the GUI installer for MFT Server.

 

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

 

3.  The installer for MFT Server will detect that a previous version of 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.

 

Additional Notes

 

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 MFT Server service will revert to using the Local System account after an upgrade.  If MFT Server is accessing shared network resources (e.g. UNC paths) then you may need to update MFT Server service to use an account with access.

 

 

Upgrade Process - Manual

 

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.

 

Pre-9.3

 

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 MFT Server

 

1.Stop the old MFT Server.

 

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

 

3.Install the new 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]

 

For example:

 

./js-web-configuration -host 0.0.0.0 -port 11880 -timeout 10

 

9.Start the new MFT Server
 

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.

 

http://<mft_server_host_or_ip>:<rest_port>
 

NOTE:

 

If users are unable to connect after the successful upgrade then please open each domain and check that SECURITY > 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.

 

*.*.*.*

*:*:*:*:*:*:*:*

 

[End Pre-9.3]

 
 

Post 9.3

 

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 MFT Server

 

1.Shutdown MFT Server Service and MFT Server Manager.

 

2.Backup current MFT Server installation directory.  This backup can be used for disaster recovery purposes.  Click here for details on how to restore from the backup.

 

3.Uninstall current version of MFT Server.

 

 3a. How to backup and uninstall RPM installations:

 

▪Stop the MFT Server service using command: ./stop_service.sh

 

▪Backup current MFT Server installation directory:
•mv mft_server mft_server_old (if MFT Server version >= 12.2)
•mv ActiveMFT_Server ActiveMFT_Server_old (if MFT Server version = 12.1)
•mv JSCAPE_MFT_Server JSCAPE_MFT_Server_old (if MFT Server version < 12.1)

 

▪Execute one of the following commands to discover the MFT Server installed package:
•rpm -qa | grep mft_server (if mft_server version >= 12.2)
•rpm -qa | grep activemft_server (if mft_server version = 12.1)
•rpm -qa | grep jscape_mft_server (if mft_server version < 12.1)

 

This returns PackageName, the RPM name of your MFT Server which is used to identify the install package.

 

▪Execute the following command to uninstall the product:
•rpm -ev <PackageName>                

         

 3b. How to backup and uninstall ZIP installation:

 

       You need to stop and backup the MFT Server installation directory for Zip installations.

 

▪Stop the MFT Server service using command: ./stop_service.sh

 

▪Backup the current MFT Server installation directory:
•mv mft_server mft_server_old (if MFT Server version >= 12.2)
•mv ActiveMFT_Server Active MFT_Server_old (if MFT Server version = 12.1)
•mv JSCAPE_MFT_Server JSCAPE_MFT_Server_old (if MFT Server version < 12.1)

 

4. Install the updated version of MFT Server.

 

 The directory name of the different versions of MFT Server installation are as follows:

 

▪ActiveMFT_Server (MFT Server installation directory name if the version is 12.1)
▪mft_server (MFT Server installation directory name if the version is >= 12.2)
▪JSCAPE_MFT_Server (MFT Server installation directory name if the version is < 12.1)

 

5. Copy any JDBC 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.

 

9. Copy the following files:

 

•<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.

Note: If H2 (embedded) database was used in the previous installation, check the file <backup>/libs/h2-xxx.jar. If it appears like h2-1.xx.xx.jar, copy this file to  <current installation>/libs directory and remove <current installation>/libs/h2-2.xx.xx.jar file.

 

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

    This command will update the application database. You need to specify the previous version (version of old installation) in the <previous server version> parameter.

        e.g. ./js-database-configuration -update -previous-version 12.2.0.422

 

12. Run the ./js-database-configuration -update-data-protection command from within the installation directory. This command will update the application with data encryption for sensitive data.

 

13. 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.

 

14. Restart MFT Server Service and MFT Server Manager.

 

[End Post-9.3]

 

Restoring from the backup

 

To restore from the backup directory, just copy the contents of the backup directory into a freshly installed MFT Server (having the same version as the backup). You may even copy the backup over an existing installation that is not working properly. Once the existing files get replaced with the backup files, that installation will then acquire the configurations of the backup.

 

For RPM console restore, perform the following steps:

 

•./rpm -iv <install.rpm>.

   This will install a fresh instance of MFT Server. <install.rpm> is the MFTServer rpm installer filename, the same version as the backup.

 

•rsync -a /opt/<backup directory>/ /opt/<MFT Server>/

  This will copy all contents of the backup directory into the freshly installed MFTServer. <MFT Server> is the directory name of new installation.

 

•Start the MFT Server service using command:

  ./start_service.sh

 

For Zip console restore, perform the following steps:

 

•unzip <install.zip>.

  This will unzip a fresh instance of MFT Server. <install.zip> is the MFTServer zip installer filename, the same version as the backup.

 

•rsync -a /opt/<backup directory>/ /opt/<MFT Server>/

  This will copy all contents of the backup directory into the freshly installed MFTServer. <MFT Server> is the directory name of new installation.

 

•Start the MFT Server service using command:

  ./start_service.sh

 

HA considerations:

 

For the HA environment, it is important that only one instance is using the common DB during upgrading. And for all other instances/nodes you should select a local DB first and then switch to the global DB in the UI.

 

Here are the steps:

 

▪switch all instances except one to use local DB
▪upgrade the instance which is still using the common DB
▪upgrade all other instances
▪switch other instances to use common DB

 

Consideration for Trigger actions

 

Trigger actions that have the installation path parameter hard-coded should be updated with the new directory name manually.

 

e.g.: System Configuration Backup trigger action.

 

If the parameter is referenced as a variable, then you don't need to change anything

 

 

 

 

 

 

 





Home | Company | Products | Solutions | Purchase | Support | Services | Blog

© 2023 Redwood Software, Inc.