GoAnywhere MFT Upgrade

Guide
Version 7.5.1
Copyright Terms and Conditions

Copyright © Fortra, LLC and its group of companies. All trademarks and registered trademarks are the property of their respective
owners.
The content in this document is protected by the Copyright Laws of the United States of America and other countries worldwide. The
unauthorized use and/or duplication of this material without express and written permission from Fortra is strictly prohibited. Excerpts and
links may be used, provided that full and clear credit is given to Fortra with appropriate and specific direction to the original content.
202404081248
 Table of Contents

Upgrade Process 5 Global File Buffer Size 11

Before You Begin 6 Changes to Custom Tasks 11

Backup External Database 6 System Requirements 13

Important Version Updates 7 Windows Requirements 13

7.5.0 7 Linux Requirements 13

Database Connection Pool Update 7 UNIX, AIX, HP-UX, Solaris

Requirements 14
Derby Database Resources 7
IBM i (iSeries) Requirements 14
7.4.2 8
Mac OS X 15
Docker Image Permissions 8
Browser Compatibility 16
7.4.0 8
Upgrade File Download 17
FTP Client 8
Windows Upgrade Instructions 19
SMB Network Share
Authentication 9 Linux/UNIX/AIX/HP-UX/Solaris
Upgrade Instructions 22
Network Shares Monitors 9
Linux RPM Upgrade Instructions 24
Updated Project Variables on
Monitors 9 IBM i Upgrade Instructions 25

7.3.1 10 Docker Upgrade Instructions 29

Java Max Memory 10 Upgrading a Cluster Environment 34

7.3.0 10 Post Upgrade Notes 35

Importing Secure Forms 10 Starting GoAnywhere MFT in

Clustered Environments 35
7.2.0 11

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 3

Table of Contents

Enable Schedules, Monitors, and

Triggers 35

Changes to Resource Passwords 35

Changes to Key Locations 36

Downgrading GoAnywhere MFT 37

Downgrading GoAnywhere MFT on

IBM i 39

page: 4 www.goanywhere.com GoAnywhere MFT Upgrade Guide

 Upgrade Process /

Upgrade Process
An upgrade script (program) is available which will perform all the necessary steps to
upgrade GoAnywhere MFT. See the Upgrade File section to determine which upgrade
script you require. Download the appropriate upgrade script by visiting the GoAnywhere
Customer Portal at my.goanywhere.com.

1. Ensure you have a backup of GoAnywhere MFT including the database (i.e. a
snapshot) so you can restore your instance if needed.

2. Review the Important Version Updates section for information on the GoAnywhere
version you are upgrading to.

3. Verify your system meets the minimum requirements for the upgrade.

4. Ensure you have obtained the correct upgrade file.

5. Follow the steps for the installed platform:

l Windows
l Linux/UNIX
l IBM i
l Docker

6. Review the Post Upgrade section.

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 5

 Before You Begin / Backup External Database

Before You Begin

This guide outlines the steps required for upgrading GoAnywhere MFT to the latest
version.

n Check if there are any updates available for GoAnywhere MFT by logging in to its
browser interface as a user with the Product Administrator role. From the main
menu bar, point to Help and then click Check for Updates. The system checks for
updates and provides you with further upgrade options. The Check for Update
process provides guidance to upgrade GoAnywhere MFT to the latest version.
n Since GoAnywhere MFT must be restarted to apply the updates, it is important that
you perform the upgrade process when no projects or file transfers are active in
GoAnywhere MFT. Also, no other external processes must be running against the
database that GoAnywhere is running on (such as a database backup).
n It is recommended that you clean up the temporary workspace by deleting the older
files and subfolders from under the folder named
[installfolder]/userdata/workspace.
n Create backups or VM snapshots of any GoAnywhere MFT or Gateway servers.
n Consider testing an upgrade in your development environment prior to upgrading
your production environment.

Backup External Database

If you are using an external database, such as MySQL/MariaDB, SQL Server, Oracle, DB2
on IBM i, PostgreSQL, or Derby in network mode, you will want to ensure the database is
backed up before you begin the upgrade.

NOTE:
GoAnywhere MFT automatically backs up the embedded Derby database during the
upgrade.

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 6

Important Version Updates / 7.5.0

Important Version
Updates
7.5.0
Database Connection Pool Update
With 7.5.0, GoAnywhere MFT has updated its database connection pooling library. With
the inclusion of the improved connection pool, it is suggested that your GoAnywhere
MFT’s Maximum Pool Size amount be reviewed before upgrading. The new connection
pool is more aggressive during its initialization which can result in all connections being
consumed on the database server if the Maximum Pool Size for MFT does not align with
what is configured for your database.

You can configure GoAnywhere MFT’s Maximum Pool Size by navigating to System >
Database Configuration > Edit Configuration.

Derby Database Resources

As of GoAnywhere MFT 7.5.0, the JDBC Driver type
org.apache.derby.jdbc.AutoloadedDriver is no longer supported. Any Projects or
Resources that connect to a Derby database using the affected JDBC Driver will need to
be updated to use the new driver type org.apache.derby.jdbc.ClientDriver. For
information on how to change the JDBC Driver types in their respective locations, please
refer to the Database Servers Resource and SQL Task topics within the GoAnywhere MFT
User Guide.

page: 7 www.goanywhere.com GoAnywhere MFT Upgrade Guide

 Important Version Updates / 7.4.2

7.4.2
Docker Image Permissions
In 7.4.2, the GoAnywhere MFT Docker image was updated to prevent the default gamft
user that runs MFT from escalating permissions via the Linux sudo command. This change
was added to the Docker container as a security enhancement. Customers who map
internal Docker ports to privileged ports (ports below 1024) will experience issues binding
to these ports.

NOTE: This change only affects customers who have modified the internal Docker ports
from their defaults. For information on how to change these ports, please see the Port
Numbers topic in the Installation - Docker section within the GoAnyhwere Installation
Guide.

7.4.0
FTP Client
As of 7.4.0, the Apache Commons Net jar has been upgraded to remediate a known
vulnerability within FTP. This has changed the default behavior of passive FTP.

When using a passive FTP or FTPS connection, the FTP client no longer trusts the
address returned from the server in the passive (PASV) mode reply. Instead, the FTP client
will connect back to the address used for the control channel. This may lead to a
connection failure.

In the instance of a connection failure, you may see a log message similar to the following:
[Replacing site local address "passiveIPAddress" with "newPasssiveIPAddress"].

The above message is not new. There are other potential reasons for it to appear in past
releases. However, if you are experiencing a new FTP/FTPS connection failure and this
message has appeared when it has not been present in the past, it could be related to the
upgrade.

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 8

Important Version Updates / 7.4.0

To revert to trusting the host from the passive response, add

org.apache.commons.net.ftp.ipAddressFromPasvResponse=true to
config\system.properties.

WARNING: Fortra only recommends adding the above variable to

config\system.properties if absolutely necessary. If FTP client connections are
failing, you should determine if the address sent to you for connecting to the passive
channel should be different than that used for the control channel.

SMB Network Share Authentication

In GoAnywhere MFT 7.4.0, behavior of SMB Network Share connections has changed.
The JNQ library has been upgraded to version 2.4.0. As of this update, JNQ will now
always attempt a Kerberos connection first. If this fails, then JNQ will try to connect over
NTLM. If NTLM fails, the connection will fail. Prior to 2.3.0, JNQ defaulted to NTLM and
only used Kerberos if explicitly configured.

Network Shares Monitors

Upgrading to GoAnywhere MFT 7.4.0 will fail if you have active monitors that use an SMB
(version all) resource AND whose event type is File Created or Modified or File Modified.
Once the upgrader fails, you will be notified that in order to upgrade you need to disable
these monitors and re-enable them once you have upgraded.

Updated Project Variables on Monitors

The 7.4.0 GAMFT upgrade fixes an issue where editing a Monitor did not synchronize
existing Monitor variables with Project variables. Before upgrading, it is suggested that
you evaluate all Monitors that may have Monitor variables matching Project variables, and
update them to Project variables following the steps below:

1. Edit the Monitor and navigate to the Project tab.

2. For all Monitor defined variables that match a Project variable, take note of the
value if specified.

page: 9 www.goanywhere.com GoAnywhere MFT Upgrade Guide

 Important Version Updates / 7.3.1

a. Monitor variables are variables created and managed by the Monitor

definition. You can identify these variables by looking at the Name column. If
the Name column is editable, or has a red X next to the name field, the
variable is a Monitor variable.

b. Project variables are defined at the Project level but can be overwritten by a
Monitor. You can identify these variables by looking at the Name column. If
the Name column is not editable the variable is a Project variable.

3. Change the Project field to a different project than what is currently selected.

a. You may select a different Project with the project selector or by simply typing
into the field itself.

4. Reselect the original Project.

5. The Project’s variables should now be applied below under Variables.

6. Apply the values noted in step 2 to the Project variables.

7.3.1
Java Max Memory
As of 7.3.1 you can set the JAVA_MAX_MEMORY value. This is an optional variable that
determines the maximum amount of memory, in megabytes (MB), allocated for the Java
Virtual Machine. By default, this value is 1024 MB. You can set this value when Installing
GoAnywhere MFT using Docker or Docker Compose. See the Docker Upgrade
Instructions section in this guide for more information.

7.3.0
Importing Secure Forms
When importing a Secure Form into version 7.3.0 or later that was exported in a version
previous to 7.1.0, users will have to re-enter the password that was previously stored. To
do this:

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 10

Important Version Updates / 7.2.0

1. Import the form as normal.

2. Once imported, edit the Secure Form.

3. Click on the Project tab, then select the Change Password link to re-enter the
password.

NOTE: For Secure Forms that were exported from version 7.1.0 and later, no action is
necessary.

7.2.0
Global File Buffer Size
The default setting for the global file buffer size has been changed to 512 KB so users can
gain a performance improvement. This is also due to the need to consolidate multiple
system properties related to buffer sizes in different contexts. We advise customers
concerned with memory usage and performance tuning in GoAnywhere to evaluate the
new global buffer size setting and adjust it to their requirements.

More information about the global file buffer size setting can be found in the GoAnywhere
MFT User guide.

Changes to Custom Tasks

The 7.2.0 update includes the following change to Custom Task functionality:

l User validation - The com.linoma.dpa.ValidationException package path

has been changed to
com.linoma.commons.exception.ValidationException.

In addition to the above change, all Custom Tasks will need to be rebuilt using the 7.2.0
Custom Task jar files. To do this:

page: 11 www.goanywhere.com GoAnywhere MFT Upgrade Guide

 Important Version Updates / 7.2.0

1. Upgrade MFT to version 7.2.0 or later.

2. Rebuild the Custom Task using the updated MFT jar files. If you are unsure of how
to do this, please refer to step 2 in the GoAnywhere MFT Custom Task Guide.

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 12

 System Requirements / Windows Requirements

System Requirements
You must meet the minimum system requirements before upgrading GoAnywhere MFT on
your server.

Windows Requirements
Operating Systems supported Windows Server 2012®

Windows Server 2012 R2®

Windows Server 2016®

Windows Server 2019®

Windows Server 2022®

Windows 8®

Windows 10®

Windows 11®

Disk space 500 MB for product (does not include user data)

Memory 1024 MB minimum

Linux Requirements
Disk space 500 MB for product (does not include user data)

Memory 1024 MB minimum

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 13

System Requirements / UNIX, AIX, HP-UX, Solaris Requirements

UNIX, AIX, HP-UX, Solaris

Requirements
Disk space 400 MB for product (does not include user data)

Memory 1024 MB minimum

JRE (Java Runtime Environment) The following JREs can be used:

l OracleJava SE 11
l Azul Zulu Java SE 11
l IBM Java SE 11

IBM i (iSeries) Requirements

Operating System IBM i V7R3 or higher

Disk Space 400 MB for product (does not include user data)

Memory 1024 MB minimum

Required Licensed Programs

The following IBM i licensed programs are prerequisites to the installation of GoAnywhere
MFT, which are dependent on the IBM i release and your choice if supported Java version.

IBM i Release Licensed Program Product Description

Option

V7R3, V7R4, 5770JV1 19 Java SE 11 64 bit

V7R5
5770SS1 30 QShell

5770SS1 33 Portable App

Solutions
Environment

page: 14 www.goanywhere.com GoAnywhere MFT Upgrade Guide

 System Requirements / Mac OS X

To check if the licensed programs (listed above) are installed on your IBM i, execute the
command GO LICPGM and select option 10 to display the installed licensed programs.
Press F11 twice from that screen to display the Product Options.

If these licensed programs are not loaded on your IBM i, they may be available on the IBM
software CDs that came with your IBM i. Otherwise, you will have to request those
licensed programs from IBM, which are normally provided at no charge.

Required PTFs

The following IBM i Program Temporary Fixes (PTFs) and Group PTFs are prerequisites to
installing GoAnywhere MFT.

V7R3 Group PTF SF99725

V7R4 Group PTF None required

Use the command DSPPTF to verify that the required individual PTFs are applied. Use the
command
WRKPTFGRP to verify that the required group PTFs are applied.

Mac OS X
Operating Systems supported Mac OS X

Disk space 400 MB for product (does not include user data)

Memory 1024 MB minimum

JRE (Java Runtime Environment) 11 must be installed prior to the installation.

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 15

 Browser Compatibility /

Browser Compatibility
The GoAnywhere MFT Administrator and Web Client interface's require modern internet
browsers that support HTML 5. Popular browsers are supported including Microsoft Edge,
Chrome, Firefox and Safari. Please note that some HTML 5 advanced features, such as
drag and drop, will not work in older versions of browsers.

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 16

 Upgrade File Download /

Upgrade File Download

Visit the GoAnywhere Customer Portal to download software updates, check the status of
a support case, and manage your GoAnywhere MFT license. You must create an account
in order to use the portal.

The portal can be accessed by using your internet browser and navigating to
my.goanywhere.com

Depending how old your current GoAnywhere MFT version is, you may need to repeat the
upgrade process until you are upgraded to the current version of 7.5.1. The versions must
be upgraded in the order listed below to maintain database integrity. For example, if you
have GoAnywhere 6.0.1 currently installed, you would first download and upgrade to
version 6.0.4, followed by 7.0.3, then 7.1.3 before upgrading to the latest released version.

NOTE:
Your current installed version can be found by pointing to the Help menu and then
clicking About.

Installed Version Upgrade Version

5.0.0 Upgrade to GoAnywhere MFT 5.0.1 using the ga_upgrade5_

0_1.jar that is available on the Customer Portal.

5.0.1 - 6.0.3 Upgrade to GoAnywhere MFT 6.0.4 using the ga_upgrade6_

0_4.jar that is available on the Customer Portal.

6.0.4 - 7.0.2 Upgrade to GoAnywhere MFT 7.0.3 using the ga_upgrade7_

0_3.jar that is available on the Customer Portal.

7.0.3 - 7.1.2 Upgrade to GoAnywhere MFT 7.1.3 by downloading the ga_7_

1_3.zip file that contains the ga_upgrade.jar, upgrade.sh, and
upgrade.bat files. Unzip the .jar file into the appropriate
upgrader folder, replacing the old scripts, and run the required
update script.

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 17

Upgrade File Download /

Installed Version Upgrade Version

7.1.3 Upgrade to GoAnywhere MFT 7.5.1 by downloading the ga_

upgrade7_5_1.jar that is available on the Customer Portal.

page: 18 www.goanywhere.com GoAnywhere MFT Upgrade Guide

 Windows Upgrade Instructions /

Windows Upgrade
Instructions
Prior to upgrading, make sure to see the Before you Begin section for best-practice
recommendations, including backing up your existing systems.

There are two ways of upgrading GoAnywhere MFT on Windows. The following includes
instructions on how to upgrade your installation of GoAnywhere MFT by running either the
upgrader .EXE file or the upgrader .JAR file available at my.goanywhere.com.

WARNING:
Do not use a GoAnywhere installer to upgrade. Use only the above mentioned
upgrader files. The procedure for installing GoAnywhere MFT is different than
upgrading. See the GoAnywere MFT Install Guide for more information.

Upgrading with .EXE file

1. Login to the target Windows system as an administrator.

a. If the GoAnywhere MFT database is configured to run on Microsoft SQL

Server with integrated security, you must login as the same user that runs the
GoAnywhere Windows Service. The user can be identified by right-clicking on
the GoAnywhere MFT service, select Properties, and then click the Log On
tab.

2. Download the GoAnywhere MFT upgrader .EXE file from the GoAnywhere
Customer Portal at my.goanywhere.com.

NOTE:
If you have a 64-bit operating system, make sure to download the 64-bit version.

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 19

Windows Upgrade Instructions /

3. Stop the GoAnywhere MFT service.

a. From the Control Panel, open Administrative Tools and then click Services.

b. In the Services window, right-click the GoAnywhere service and select Stop.

4. If the GoAnywhere MFT database is configured to run on a database other than the
embedded Derby database, make a backup of that external database before
continuing.

5. Execute the downloaded upgrader .EXE file and follow the prompts on the screens.

6. Start the GoAnywhere MFT service.

a. From the Control Panel, open Administrative Tools and then click Services.

b. In the Services window, right-click the GoAnywhere service and select Start.
Within seconds after starting the GoAnywhere MFT service, its status should
be updated to “Running”.

7. The upgrade of GoAnywhere MFT is complete.

Upgrading with .JAR file

1. Rename the downloaded upgrade file to ga_upgrade.jar.

2. Copy the downloaded upgrade file to [installfolder]\upgrader, where C:\Program

Files\Fortra\GoAnywhere is the default installation directory of GoAnywhere MFT.

3. Sign into the GoAnywhere MFT browser-based Administrator and verify there are
no active jobs or transfers before proceeding.

4. Login to the Windows system as an administrator.

a. If the GoAnywhere MFT database is configured to run on Microsoft SQL

Server with integrated security, you must login as the same user that runs the
GoAnywhere Windows Service. The user can be identified by right-clicking on
the GoAnywhere MFT service, select Properties, and then click the Log On
tab.

5. Stop the GoAnywhere MFT service.

a. From the Control Panel, open Administrative Tools and then click Services.

b. In the Services window, right-click the GoAnywhere service and select Stop.

page: 20 www.goanywhere.com GoAnywhere MFT Upgrade Guide

 Windows Upgrade Instructions /

6. Check the [installfolder]/tomcat/logs folder for stdout_[date].log and stderr_

[date].log files. Remove all but the most recent files based on the date appended to
each log file.

7. If the GoAnywhere MFT database is configured to run on a database other than the
embedded Derby database, make a backup of that external database before
continuing.

8. Open a Command Prompt window and change the directory to

[installfolder]\upgrader.

NOTE:
You must run the Command Prompt window as administrator to run the Upgrade.bat
file.

9. Run the upgrade.bat file to start the upgrade process. When complete, a message
indicates the upgrade was successful.

10. Start the GoAnywhere MFT service.

a. From the Control Panel, open Administrative Tools and then click Services.

b. In the Services window, right-click the GoAnywhere service and select Start.
Within seconds after starting the GoAnywhere MFT service, its status should
be updated to “Running”.

11. Before logging into the upgraded version of GoAnywhere MFT, each user should
press CTRL + F5 from their browser to clear the cache.

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 21

 Linux/UNIX/AIX/HP-UX/Solaris Upgrade Instructions /

Linux/UNIX/AIX/HP-
UX/Solaris Upgrade
Instructions
Prior to upgrading, make sure to see the Before you Begin section for best-practice
recommendations, including backing up your existing systems.

WARNING:
Do not use a GoAnywhere installer to upgrade. Use only upgrader files. The procedure
for installing GoAnywhere MFT is different than upgrading. See the GoAnywere MFT
Install Guide for more information.

1. Rename the downloaded upgrade file to ga_upgrade.jar.

2. Copy the downloaded upgrade file to [installfolder]\upgrader, where [installfolder]

is the default installation directory of GoAnywhere MFT.

3. Sign into the GoAnywhere MFT browser-based Administrator and verify there are
no active jobs or transfers before proceeding.

4. Login to the system as the same user profile used to start GoAnywhere MFT and
open a terminal window.

5. Stop the GoAnywhere MFT service:

a. Change the working directory to the directory where GoAnywhere MFT is

installed. For example:
cd /usr/local/Fortra/GoAnywhere

b. Stop the GoAnywhere MFT application server by executing the following bash
shell script:
./goanywhere.sh stop

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 22

Linux/UNIX/AIX/HP-UX/Solaris Upgrade Instructions /

6. Check the size on the [installfolder]/tomcat/logs/catalina.out file. If it is larger than

5 megabytes, rename the file and move it to a different folder outside the
[installfolder] location.

7. If the GoAnywhere MFT database is configured to run on a database other than the
embedded Derby database, make a backup of that external database before
continuing.

8. Run the upgrade.sh file to start the upgrade process.

a. Change the directory to [installfolder]/upgrader.

b. Start the upgrade by executing the following bash shell script:

./upgrade.sh

When complete, a message indicates the upgrade was successful.

9. Start the GoAnywhere MFT service:

a. Change the working directory to the directory where GoAnywhere MFT is

installed. For example:
cd /usr/local/Fortra/GoAnywhere

b. Start the GoAnywhere MFT application server by executing the following

bash shell script:
./goanywhere.sh start

10. Before logging into the upgraded version of GoAnywhere MFT, each user should
press CTRL + F5 from their browser to clear the cache.

page: 23 www.goanywhere.com GoAnywhere MFT Upgrade Guide

 Linux RPM Upgrade Instructions /

Linux RPM Upgrade

Instructions
Prior to upgrading, make sure to see the Before you Begin section for best-practice
recommendations, including backing up your existing systems.

1. Sign into the GoAnywhere MFT browser-based Administrator and verify there are
no active jobs or transfers before proceeding.

2. Login to the system as the same user profile used to start GoAnywhere MFT and
open a terminal window.

3. Download the GoAnywhere MFT Linux RPM installer file from the URL provided by
Fortra.

4. Execute the downloaded installer file by running sudo yum upgrade <rpm_file>
and follow the prompts.

5. Start GoAnywhere MFT by following these instructions:

a. Open a Terminal window.

b. Start GoAnywhere MFT by executing the following shell script:

sudo service goanywhere-mft start

c. Before logging into the upgraded version of GoAnywhere MFT, each user
should press CTRL + F5 from their browser to clear the cache.

NOTE:
You can setup GoAnywhere so it starts automatically when the Linux system is booted
by running sudo service goanywhere-mft enable. Please refer to your operating
system manual for more details on setting up auto-start services.

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 24

 IBM i Upgrade Instructions /

IBM i Upgrade Instructions

Prior to upgrading, make sure to see the Before you Begin section for best-practice
recommendations.

If using an external database (DB2), the database user profile must have the *ALLOBJ
authority to make changes to the database during the upgrade.

In some cases, the upgrade may remove columns from tables in the external database.
The *USE authority must be given to ADDRPYLE and RMVRPYLE commands to
complete this change.

If you are using an external GoAnywhere Database Library, it is highly recommended that
you disable any High Availability (HA) software prior to starting the upgrade. HA software
similar to Mimix, Itera, Maxava, etc. has been known to lock tables during an upgrade
causing the upgrade to fail when a table is affected by consecutive operations.

To determine if you are using an external Database Library, login to GoAnywhere MFT and
navigate to System > Database Configuration and review the Database driver and
URL information.

Contact your system or HA software administrator to ensure this process has been
disabled.

WARNING:
Do not use a GoAnywhere installer to upgrade. Use only the above mentioned
upgrader files. The procedure for installing GoAnywhere MFT is different than
upgrading. See the GoAnywere MFT Install Guide for more information.

Upgrade IBM i
1. Rename the downloaded upgrade file to ga_upgrade.jar.

2. Copy the downloaded upgrade file to [installfolder]/upgrader on the IFS, where

/Fortra/goanywhere/ is the default installation directory of GoAnywhere MFT. If
GoAnywhere MFT is installed in a different directory, substitute with that directory.

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 25

IBM i Upgrade Instructions /

3. Sign into the GoAnywhere MFT browser-based Administrator and verify there are
no active jobs or transfers before proceeding.

4. Sign on to an IBM i session with the QSECOFR user profile or with a profile that
has *ALLOBJ authority.

5. Stop the GoAnywhere MFT subsystem by executing the IBM i command of

ENDGA. The ENDGA command is located in the installation library, which is
named GOANYWHERE by default. Wait until the GoAnywhere MFT subsystem is
completely shutdown before proceeding.

6. Verify there are no locks on the GoAnywhere MFT installation library or objects. Do
not proceed with the upgrade until all locks are released. Run the following
command to check for locks (assuming GOANYWHERE is the install library):
WRKOBJLCK OBJ(GOANYWHERE) OBJTYPE(*LIB)

7. If you have externalized your GoAnywhere database to IBM i DB2, use the
WRKOBJLCK command to check for any locks on the database objects.

8. Check the size on the [installfolder]/tomcat/logs/catalina.out file. If it is larger than

5 megabytes, rename the file and move it to a different folder outside the
[installfolder] location.

9. Run the SAVPRD command in the installation library. This saves the installation
library to a save file, saves the matching folder to a save file, then saves both of
those to a third save file, the name and location of which will be requested when
you prompt the SAVPRD command. Specify a location to save the file in a library
outside the installation library.

10. If the GoAnywhere MFT database is configured to run on a database other than the
embedded Derby database, make a backup of that external database before
continuing. The SAVPRD can be used to backup the external database library
when running on DB2/400. Other database types require a manual backup.

11. Apply the upgrade by executing the UPGRADEGA command. The UPGRADEGA
command is located in the installation library, which is named GOANYWHERE by
default.

page: 26 www.goanywhere.com GoAnywhere MFT Upgrade Guide

 IBM i Upgrade Instructions /

12. The user profile starting the subsystem must have *RWX permission to the
GoAnywhere MFT installation folder and the entire directory tree. On V7R3 and
later, a command is provided to change the authority on an entire directory tree. In
this example '/Fortra/goanywhere' is the installation directory and PGUSER will be
the user profile that will be starting the subsystem.
CHGAUT OBJ('/Fortra/goanywhere') USER(PGUSER) DTAAUT
(*RWX) OBJAUT(*ALL) SUBTREE(*ALL)

13. Start the GoAnywhere MFT subsystem by executing the IBM i command of STRGA.
The STRGA command is located in the installation library, which is named
GOANYWHERE by default.

14. Before logging into the upgraded version of GoAnywhere MFT, each user should
press CTRL + F5 from their browser to clear the cache.

NOTE:
When upgrading the GoAnywhere Library on an iSeries, backups are created for
upgraded config files. For example, restoring the GACONFIG object [RSTOBJ] during
an upgrade will result in the creation of a GACONF0001. These objects can be
removed after the system has been thoroughly tested with the new objects.

Adding Fonts on IBMi

The recommended way to add fonts on the IBMi is to install licensed program 5770SS1
Option 43 (Additional Fonts). An alternate way to add fonts is to create a fonts folder and
reference that folder via the JAVA_FONTS environment variable. Follow the steps below to
enable Java 11 to discover and use fonts on IBMi operating systems using the alternate
method. Arial, Courier and Time New Roman TTF files have been known to work.

1. Copy the desired font’s TTF file(s) from the Windows Fonts folder (the default
location: is C:\WINDOWS\Fonts) to the designated fonts folder in your IBMi
Integrated File System.

2. Ensure the JAVA_FONTS environment variable is exposed to the application. To

do this, execute one of the following commands:

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 27

IBM i Upgrade Instructions /

a. To set the fonts folder for the entire system:

i. ADDENVVAR ENVVAR(JAVA_FONTS) VALUE('/fonts:/fonts2')
LEVEL(*SYS)

b. To set the fonts folder for only the GoAnywhere application:

i. Run GOANYWHERE/CFGGA and select option 2 under Java Fonts.

ii. Specify the fonts folder.

NOTE: Visit this page for more detail on adding custom fonts to IBMi:
https://www.ibm.com/support/pages/how-add-fonts-ibm-technology-java-j9-jdks-ibm-i

page: 28 www.goanywhere.com GoAnywhere MFT Upgrade Guide

 Docker Upgrade Instructions /

Docker Upgrade
Instructions
Prior to upgrading, make sure to see the Before you Begin section for best-practice
recommendations, including backing up your existing systems.

If you are upgrading using the GoAnywhere Docker image provided by Fortra, file
ownership will be migrated from the root to a non-root user (GAMFT instead of ROOT). The
following services will be migrated from the default ports to the ports listed:

l HTTPS/AS2 - 8443
l FTP - 8021
l FTPS - 8990
l SFTP - 8022

Verify that the following volumes are setup in Docker to preserve the GoAnywhere MFT
directories:

l [config_dir]/config
l [config_dir]/tomcat
l [install_dir]/tomcat/logs
l [install_dir]/ghttpsroot/custom
l [install_dir]/userdata
l [install_dir]/upgrader

NOTE: [install_dir] refers to the file path of the GoAnywhere installation directory within
the Docker image. For the official GoAnywhere Docker image, the application is
installed in the /opt/HelpSystems/GoAnywhere directory.

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 29

Docker Upgrade Instructions /

NOTE: [config_dir] refers to the location of the GoAnywhere configuration files. For the
official GoAnywhere Docker image, this location is the
/etc/HelpSystems/GoAnywhere directory.

For more information on how to setup volumes in Docker, see the Docker documentation
at: https://docs.docker.com/storage/volumes/.

Upgrade Docker

Use the following instructions to upgrade Docker, be sure to complete each step before
proceeding:

1. Ensure that a previous version of Docker is running on a non-derby database.

2. Update the docker-compose.yml file or the docker run command.

a. Add a new volume to handle the migration of config/user files (e.g.,

migrationdir:/etc/HelpSystems/GoAnywhere/migration)

3. Start the new version of the containers using the following command: docker-
compose up -d

4. Navigate into the started GoAnywhere MFT container by running docker exec -it
<container_id> bash

a. Copy all of the config/user files into the migration directory.

i. Use the migration script located here:

https://my.goanywhere.com/public/goanywhere/mft/docker/upgrade/mi
gration-backup.sh

b. Modify the permissions on the migration-backup.sh file to allow for

execution.

c. Copy migration-backup.sh into the container using the command: docker cp

<path-to-migration-script>/migration-backup.sh:/usr/bin/migration-
backup.sh

d. Run the following command: /usr/bin/migration-backup.sh -d <path to

migration volume above>

page: 30 www.goanywhere.com GoAnywhere MFT Upgrade Guide

 Docker Upgrade Instructions /

i. This will copy the config, userdata, custom web branding, tomcat logs,
and existing MFT license to that location.

e. Exit the container.

5. Update the docker-compose.yml file or docker run command.

a. Modify GoAnywhere MFT to use the newer image.

b. Add an entry point override (e.g., entrypoint: ["sh", "-c", "sleep infinity"]).

i. This is necessary to keep the container from restarting repeatedly.

c. Update volumes to point to the new path by changing HelpSystems to Fortra

in the paths.

i. DO NOT change migration volume path.

6. Start the new version of the containers using the following command: docker-
compose up -d

7. Go into the GoAnywhere MFT container by running the following command: docker
exec -it <container_id> bash

a. Copy all config/user files from the migration directory back to source and
update paths in files.

b. Remove any bind mounts for all config/user files.

c. Run the following command: /usr/bin/migration-restore.sh -d <path to

migration volume above>

i. This will copy the backup files into the new dir structure and update
paths inside config files.

d. Exit the container.

8. Update the docker-compose.yml file or docker run command.

a. Remove the added migration volume.

b. Remove the entrypoint override.

c. Return any bind mounts removed in previous steps.

9. Start the new containers and verify that GoAnywhere MFT starts without any errors.

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 31

Docker Upgrade Instructions /

Setting JAVA_MAX_MEMORY in Docker Compose

The following snippet demonstrates how to set the JAVA_MAX_MEMORY value in your
Docker Compose YAML file. See the single instance and multi-instance examples below
for full sample files that you can modify.

EXAMPLE:
version:
services:
mft:
image:
container_name:
restart:
environment:
JAVA_MAX_MEMORY=2048
ports:
...
volumes:
...
volumes:
...

Example Compose YAML Files

Fortra provides two sample docker.compose.yml files that you can modify. The first
sample file contains a single GoAnywhere instance definition. The second example
contains the necessary components to run GoAnywhere in a Cluster, such as three
GoAnywhere instance definitions, a MySQL database that each instance will use as a
back end database, and a shared volume. You can download each compose file here:

l Single Instance:
https://my.goanywhere.com/public/goanywhere/mft/docker/single/docker-
compose.yml
l Multi-Instance:
https://my.goanywhere.com/public/goanywhere/mft/docker/multi/docker-
compose.yml

page: 32 www.goanywhere.com GoAnywhere MFT Upgrade Guide

 Docker Upgrade Instructions /

IMPORTANT: For the multi-instance Docker configuration, the value of the cluster_dir
variable must be the full relative path of:
/opt/HelpSystems/GoAnywhere/userdata/cluster.

To use a Compose file:

1. Ensure Docker and Docker Compose are running.

2. Download an example docker-compose.yml file from a link above.

3. Open a terminal window.

4. From the terminal window, change to the directory that contains the docker-
compose.yml file.

5. Download the GoAnywhere Docker image and all other services by using the
following command:
docker-compose pull

6. Start all the services (in the background) by using the following command:
docker-compose up -d

7. Verify the status of all services by using the following command:

docker-compose ps

8. Optionally, you can shut down all the services in your Compose file by using the
following command:
docker-compose down

If you used the multi-instance Compose file, Compose has downloaded any necessary
images (such as mySQL), created containers, mapped volumes, and started GoAnywhere
MFT. You should then use the Clustering documentation found in the GoAnywhere User
Guide to verify and complete your clustered Docker installation.

TIP:
The GoAnywhere Docker Image does not contain a text editor. You will need to install
your preferred software to modify system configuration files.

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 33

 Upgrading a Cluster Environment /

Upgrading a Cluster
Environment
Prior to upgrading, make sure to see the Before you Begin section for best-practice
recommendations, including backing up your existing systems.

The following steps will ensure a successful upgrade when upgrading GoAnywhere MFT in
a cluster environment. The whole cluster must be brought down during the upgrade as the
first system upgraded will make core changes to the external shared database. When
planning for downtime during the upgrade, you will only be down for the time it takes to
upgrade the coordinator (first system).

1. Bring down all GoAnywhere MFT instances in the cluster.

2. Run the upgrade process for your specific operating system on a server in the
cluster. During this upgrade, all required changes are made to the shared database.
l Windows Upgrade Instructions
l Linux/Unix Upgrade Instructions
l IBM i Upgrade Instructions
l Docker Upgrade Instructions

NOTE:

After the first upgraded server has made the required changes to the shared
database, each additional server will detect the updated database and only
update its file system with the necessary changes.

3. Start the GoAnywhere MFT subsystem or service on the server after it is upgraded.
l If this is the first server to be upgraded, it will assume the coordinator role.
l If this is not the first server to be upgraded, verify the server has joined the
cluster.

4. Repeat steps 2 and 3 for each additional server in the cluster.

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 34

 Post Upgrade Notes /

Post Upgrade Notes

Starting GoAnywhere MFT in Clustered
Environments
All systems in the cluster must point to the same set of shared folders for storing
documents, certificates and other user files. Participants in the cluster will not start if the
Coordinator is configured to use relative paths. New shared folder locations were added
during the upgrade from GoAnywhere Director or Services to GoAnywhere MFT 5.0.1.
These folder locations must be configured to use a shared folder, even if you are not
licensed for the feature that accesses these folders.

The shared folder locations can be found in the GoAnywhere MFT Install Guide's "Setting
up the First System in the Cluster"section.

Enable Schedules, Monitors, and Triggers

In GoAnywhere MFT version 5.2.0 and later, Schedules, Monitors, and Trigger engines are
now enabled from the Admin Server page in GoAnywhere. If you disabled the Scheduler,
Monitors, or Triggers prior to upgrading from 5.1.x to a later version, you must enable them
by navigating to System > Admin Server, and then click the Start button next to each
engine.

Changes to Resource Passwords

In GoAnywhere MFT version 5.4.0 and later, A new feature in GoAnywhere MFT 5.4.0
improves the ability for Admin Users with the Resource Manager Role to recover Resource
passwords. For more information on this enhancement, open the Help within the
GoAnywhere application and navigate to Resources > Recover Resource Passwords.

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 35

Post Upgrade Notes /

Changes to Key Locations

In GoAnywhere MFT 5.6.0, an all new Key Management System was implemented to
manage SSL certificates, SSH keys, and OpenPGP keys. Your existing keys will now be
found in the legacy File Based Keys manager, which is located under the Encryption >
File Based Keys menu. For more information, open the Help within the GoAnywhere
application and navigate to the Encryption topic.

page: 36 www.goanywhere.com GoAnywhere MFT Upgrade Guide

 Downgrading GoAnywhere MFT /

Downgrading
GoAnywhere MFT
When an upgrade is performed, the upgrade process makes a backup of folders and files
that are changed during upgrade. These files are placed in
[installfolder]/backups/backup_[fromVersion]_[toVersion] (where [installfolder] is the
location where GoAnywhere MFT is installed). The backup folder names contain the
existing and new version numbers of GoAnywhere. For example, the 'backup_543_to_552'
folder contains the files that were backed up when GoAnywhere MFT was upgraded from
version 5.4.3 to version 5.5.2.

NOTE:
If the upgrade fails before the backup directory is successfully created, then no
changes will be made and you can restart GoAnywhere MFT.

The upgrade creates an upgrade log, which displays the location of the backup folder.
Example of the upgrade log:

Installed Version: 5.5.2

Upgrading to: 5.5.9
Checking the server status...
GoAnywhere Server appears to be down. Okay to upgrade.
Backing up currently installed files
Created the base backups directory: C:\Program
Files\Fortra\GoAnywhere\backups
Created the backup directory: C:\Program
Files\Fortra\GoAnywhere\backups\backup_552_to_559

If you choose to downgrade GoAnywhere MFT, any changes to projects, resources, or any
other GoAnywhere MFT configuration settings made after the upgrade will be lost when the

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 37

Downgrading GoAnywhere MFT /

rollback is performed. The rollback returns GoAnywhere MFT to the state it was just before
the upgrade was performed.

If the new version of GoAnywhere MFT is deemed unfit, a rollback can be performed using
the following steps:

1. Stop the GoAnywhere subsystem or service.

2. Make a copy of the [installfolder] for archive purposes.

3. To ensure no library conflicts are introduced during the rollback, delete the
contents of [install_dir]/lib.

4. Navigate to the backup folder and with the exception of the userdata folder (do not
delete the userdata folder), perform the following for each folder:
l If the folder exists in the [install_dir]/backups folder, delete the
corresponding folder in the install directory.

NOTE: If you are using the embedded Derby database, deleting the
[install_dir]/userdata/database/goanywhere folder and replacing it with
the [backup_dir]/userdata/database/goanywhere folder will downgrade
your embedded database to the backup taken during the upgrade
process.

l Copy the folder from the backup directory to the install directory.
l If folders exist in the backup folder that do not exist in the install folder, copy
them to the install folder.

5. Any individual files in the backup folder not contained in a folder should also be
copied to the install folder.

6. Reverse any steps taken to upgrade to Java if applicable.

7. If using an external database (MySQL/MariaDB, SQL Server, Oracle, DB2 on IBM

i, PostgreSQL, or Derby in network mode) restore that database to the backup
made just prior to upgrading GoAnywhere MFT.

page: 38 www.goanywhere.com GoAnywhere MFT Upgrade Guide

 Downgrading GoAnywhere MFT / Downgrading GoAnywhere MFT on IBM i

8. On IBM i, you must also restore the save files created by the SAVPRD command
that was used to install or upgrade GoAnywhere. The first file is named
GOANYWHERE. The second file is typically named GADATA. The second file is
required if GoAnywhere is using the external DB2 database. Further instructions for
IBM i are provided below.

9. Ensure the user profile used to start GoAnywhere has ownership authority to the
restored files. On IBM i and Unix/Linux systems, ensure the user profile used to
start GoAnywhere has execute permission to all shell scripts (*.sh).

10. Navigate to the [installfolder]/tomcat/work folder and delete all files present in that
folder.

11. Start the GoAnywhere MFT subsystem or service.

Downgrading GoAnywhere MFT on IBM i

When upgrading GoAnywhere on an IBM i, you were instructed to run the
SAVPRD command which saves the installation library. The library specified in the
SAVPRD step is where the save file (*SAVF) is located. This save file contains 2-3 save
files, containing the GoAnywhere library, The GoAnywhere IFS folder, and (if it exists) the
GADATA library.

Example of the SAVPRD screen, prior to the upgrade:

1. Rename the existing GOANYWHERE library and IFS Folder. The folder is located
in either the /Linoma, /HelpSystems, or /Fortra directory on the IFS. This will

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 39

Downgrading GoAnywhere MFT / Downgrading GoAnywhere MFT on IBM i

preserve the libraries and check for necessary authority. Ensure these libraries are
renamed before moving to the next step.

NOTE:
If you have an IBM i data library (GADATA), you will need to save the library and
delete it because of journaling.

2. To confirm the names of the primary save files, use the command DSPSAVF
mylibrary/gamftsavf (use the actual library and file name specified when the
SAVPRD command was run). The following image illustrates the results of the
command:

3. Restore the temporary save files using the following command:

RSTOBJ OBJ(*ALL) SAVLIB(QTEMP) DEV(*SAVF) SAVF([mylibrary]/

[gamftsavf]).

You should see the message “3 Objects Restored…”

4. If using the DB2 Database Library, use this command. Note: If downgrading GA
Services, the SAVLIB would be GASDATA.

RSTLIB SAVLIB(GADATA) DEV(*SAVF) SAVF(QTEMP/SDATAGA)

5. Restore the IFS Folder.

RST DEV('/qsys.lib/qtemp.lib/sifsga.file') OBJ(('/fortra/goanywhere'))

6. Finally, restore the GoAnywhere program library. Note: If downgrading GA

Services, the SAVLIB would be GASERVICES.

page: 40 www.goanywhere.com GoAnywhere MFT Upgrade Guide

 Downgrading GoAnywhere MFT / Downgrading GoAnywhere MFT on IBM i

RSTLIB SAVLIB(GOANYWHERE) DEV(*SAVF) SAVF(QTEMP/SLIBGA)

GoAnywhere MFT Upgrade Guide www.goanywhere.com page: 41