Ga7 8 0 Installation Guide
Ga7 8 0 Installation Guide
Guide
Version 7.8.0
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.
202504221131
Table of Contents
Firewall Recommendations 46
Database Overview 51
Clustering Overview 52
Upgrading GoAnywhere 56
Uninstalling GoAnywhere 58
Please note that GoAnywhere MFT will be referred to as simply “GoAnywhere” throughout
this guide.
GoAnywhere can be used for a variety of file transfer needs including workflow
automation, ad-hoc file transfers and document collaboration. It can simplify system-to-
system, user-to-system and user-to-user file transfers.
Workflow Automation
l Provides a graphical interface for creating multi-step workflows; no scripting or
programming required.
l Includes an integrated scheduler for running workflows and file transfers at future
dates/times.
l Triggers workflows based on events, such as an upload/download event or the
presence of a new file in a folder.
l Provides APIs and commands for running workflows from customer applications
and 3rd party schedulers.
l Encrypts, signs, verifies and decrypts files using the Open PGP encryption
standard.
l Accesses files and directories on network shares with support for UNC, NFS, SMB
and CIFS.
l Connects to popular database servers including DB2, SQL Server, Oracle, Informix,
MySQL/MariaDB, and PostgreSQL.
l Translates data to/from Excel, XML, Delimited text and Fixed Width file formats.
l Calls customer programs and scripts as part of an overall workflow.
l Connects to enterprise messaging systems including Websphere MQ, SonicMQ,
ActiveMQ and SwiftMQ
l Compresses and extracts files using ZIP, GZIP and TAR standards.
l Supports large files with auto-resume and integrity checks to help guarantee
delivery.
l Allows workflow jobs to be prioritized and segmented with job queues and run
priorities.
l Sends email alerts and text messages for failed and completed transfers.
Administration
Authorized users can utilize GoAnywhere's browser-based Administrator to perform
configuration and monitoring within the product.
23 FileCatalyst Service
Browser Compatibility
The GoAnywhere Administrator and Web Client interface's require modern internet
browsers that support HTML 5. Popular browsers are supported including Internet
Explorer*, 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.
A Windows installation wizard is provided for GoAnywhere which installs the product files
into the directory of your choice. GoAnywhere will be implemented as a Windows Service
which will automatically start (by default) when Windows starts.
Requirements
Operating Systems Windows Server 2012®
supported
Windows Server 2012 R2®
Windows 8®
Windows 10®
Windows 11®
2. Download the GoAnywhere installer .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.
3. Execute the downloaded .EXE file and follow the prompts on the screens.
4. If you did not choose to start the GoAnywhere application server within the
installer, then you can manually start this server by following these instructions:
5. The installation and startup of GoAnywhere is complete. Now you should proceed
to the Initial Configuration instructions.
NOTE:
2. Open the command prompt and use the cd command to navigate to the directory
Parameters that begin with -V must be specified as a key=value pair. Separate each -V
parameter with a space.
EXAMPLE:
[installer file name].exe -q -Vgoanywhere.adminPort=8005 -
Vgoanywhere.httpsPort=8443
For parameters for silent install on Windows, see the Parameters table.
A graphical installation wizard is provided for GoAnywhere which installs the product files
into the directory of your choice.
Requirements
Disk space 500 MB for product (does not include user data)
During installation, you will be prompted to specify the ports required (FTP, SFTP, HTTPS,
etc) by GoAnywhere. Although Linux requires root level access to bind to privileged ports
(1-1024), it is recommended to configure GoAnywhere to bind to non-standard ports so
that root level access is not required to install and run GoAnywhere.
GoAnywhere Gateway is a reverse proxy that can be used in front of GoAnywhere MFT
that allows binding to privileged ports without allowing root access to the file system. If
GoAnywhere Gateway is not used, GoAnywhere MFT may need to be installed and
running as root to use standard FTP, FTPS, SFTP and HTTP/S ports.
1. Create or designate a non-root user on the system that will be used to install and
run the GoAnywhere application. This user will be the owner of all files created
during installation as well as files written to the file system during use.
3. Download the GoAnywhere Linux installer file from the URL provided by Fortra.
4. If needed, set the Executable bit on the file (e.g. chmod 755 gax_x_x_linux.sh).
5. If you have a graphical desktop for Linux, execute the downloaded installer file and
follow the prompts on the screens. Otherwise, execute the downloaded installer file
with a -c option (e.g. installer_filename.sh -c) and follow the prompts.
7. The installation and startup of GoAnywhere is complete. Now you should proceed
to the Initial Configuration instructions.
NOTE:
You can setup GoAnywhere so it starts automatically when the Linux system is
booted. Please refer to your operating system manual for more details on setting up
auto-start services. You can execute goanywhere.sh from your startup scripts.
[installer_filename].sh -q
Parameters that begin with -V must be specified as a key=value pair. Separate each -V
parameter with a space.
EXAMPLE:
[installer file name].sh -q -Vgoanywhere.adminPort=8005 -
Vgoanywhere.httpsPort=8443
For parameters for silent install on Linux, see the Parameters table.
1. Create or designate a user with root or sudo privileges on the system that will be
used to install and run the GoAnywhere application. This user will be the owner of
all files created during installation as well as files written to the file system during
use.
3. Download the GoAnywhere Linux RPM installer file from the URL provided by
Fortra.
4. Execute the downloaded installer file by running sudo yum install <rpm_file> and
follow the prompts.
6. The installation and startup of GoAnywhere is complete. Now you should proceed
to the Initial Configuration instructions.
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.
An installation wizard is provided for GoAnywhere which installs the product files into the
directory of your choice.
Requirements
Disk space 400 MB for product (does not include user data)
Installing GoAnywhere
Perform the following steps to install GoAnywhere onto a UNIX server.
1. Create or designate a non-root user on the system that will be used to install and
run the GoAnywhere application. This user will be the owner of all files created
during installation as well as files written to the file system during use.
3. Download the GoAnywhere UNIX installer file from the GoAnywhere Customer
Portal at my.goanywhere.com.
5. Change the directory to where the installer file was downloaded (e.g. cd
/root/Desktop).
6. If needed, set the Executable bit on the file (e.g. chmod 755 gax_x_x_unix.sh).
8. The installer will attempt to find a compatible JDK (Java Development Kit) for the
installation process. Follow the steps below if the installer cannot find a compatible
JDK:
b. Clear the Installer cache by removing the file named .install4j from your
home directory
(e.g. rm /root/.install4j).
11. The installation and startup of GoAnywhere is complete. Now you should proceed
to the Initial Configuration instructions.
NOTE:
You can setup GoAnywhere so it starts automatically when the system is booted.
Please refer to your operating system manual for more details on setting up auto-start
services. You can execute goanywhere.sh from your startup scripts.
To perform a silent install of GoAnywhere on AIX, HP-US, Solaris or non x86-based Linux
systems (UNIX):
[installer_filename].sh -q
Parameters that begin with -V must be specified as a key=value pair. Separate each -V
parameter with a space.
EXAMPLE:
[installer file name].sh -q -Vgoanywhere.adminPort=8005 -
Vgoanywhere.httpsPort=8443
For parameters for silent install on UNIX, see the Parameters table.
Requirements
Operating System IBM i V7R3 or higher
Disk Space 400 MB for product (does not include user data)
The following IBM i licensed programs are prerequisites to the installation of GoAnywhere,
which are dependent on IBM i release and your choice of supported Java version.
5770SS1 30 QShell
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.
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.
The following components will be installed onto the IBM i by the GoAnywhere installation
process:
n A IBM i library will be created, which will contain the GoAnywhere commands and
program objects. The default library name is GOANYWHERE, which can be
changed during installation.
n An IFS folder will be created, which will contain the GoAnywhere software
components. The default IFS folder name is /fortra/goanywhere, which can be
changed during installation.
1. Sign on to the IBM i with the QSECOFR user profile OR with a profile which has
*ALLOBJ authority.
2. Create a temporary Save file on your IBM i by executing the following IBM i
command:
CRTSAVF FILE(QGPL/GOANYWHERE)
3. The GoAnywhere software needs to be uploaded to your IBM i using FTP. Before
proceeding, ensure the FTP server is running on the IBM i. To start the native FTP
server on the IBM i, you can issue the IBM i command of
STRTCPSVR SERVER(*FTP).
4. Download the GoAnywhere installer (for IBM i) from the Customer Portal at
my.goanywhere.com.
5. Extract the files from the installer ZIP file into a new temporary folder on your
workstation. One of the extracted files will be named GOANYWHERE.SAVF.
6. FTP the extracted GOANYWHERE.SAVF file from your PC to the Save file on the
IBM i (that was created in step 2). Listed below are instructions for a Windows
user:
b. Enter the DOS command FTP <hostname>, where <hostname> is the host
name or IP address of your IBM i.
c. Login with your IBM i user id and password, then enter the following
highlighted FTP commands:
7. Restore the installation objects into QTEMP by executing the following IBM i
command:
RSTOBJ OBJ(*ALL) SAVLIB(QTEMP) DEV(*SAVF) SAVF
(QGPL/GOANYWHERE)
8. Delete the temporary Save file by executing the following IBM i command
(optional):
DLTF FILE(QGPL/GOANYWHERE)
9. If QTEMP library is not in your library list, then add it by executing the following IBM
i command:
ADDLIBLE LIB(QTEMP) POSITION(*FIRST)
10. Prompt (F4) the command QTEMP/INSTALLGA for installing GoAnywhere. The
following screen appears.
Parameter descriptions:
Install IFS directory The directory to contain the GoAnywhere product files.
The specified directory name must not already exist.
Administration port The port number that the GoAnywhere Administrator runs
under (using HTTP). Default is 8000. *
Secure administration The port number that the GoAnywhere Administrator runs
port under (using HTTPS). Default is 8001. *
HTTPS service port The port number to run the HTTPS/AS2 service under (for
trading partner file transfers). Default is 443. *
FTP service port The port number to run the FTP service under (for trading
partner file transfers). Default is 21. *
FTPS service port The port number to run the FTPS service under (for
trading partner file transfers). Default is 990. *
SFTP service port The port number to run the SFTP service under (for
trading partner file transfers). Default is 22. *
GoFast service port The port number to run the GoFast service under (for
accelerated trading partner file tranfers). Default is 8010.*
Shutdown port The port number which the GoAnywhere will listen to for
shutdown requests. Default is 8005. *
* To check if the port number is already in use, run the IBM i command of NETSTAT
and select option 3. Then press F14 to see the numeric port numbers.
11. After reviewing and/or modifying the parameters on the INSTALLGA command,
press enter to start the installation process.
12. Prompt (F4) the command GOANYWHERE/STRGA for starting the GoAnywhere
subsystem. The following screen will be displayed.
For the Server User Profile parameter, keep the default of *CURRENT if you want
to run the GoAnywhere application under your user profile. Otherwise, specify a
different user profile to run the GoAnywhere application server under.
NOTE:
The user profile specified on the STRGA command must be enabled on the
IBM i. This profile must have *USE authority to the STRSBS command and
*RWX authority to the IFS folders where GoAnywhere is installed.
For security purposes, you may want to create a new user profile and consistently
use that profile on the STRGA command. Then you would only have to grant
authority for the GoAnywhere installation IFS folders to that user profile. There are
certain user profiles that you cannot use to start the GoAnywhere subsystem. These
are: 'QSECOFR', ‘QSPL', 'QDOC', 'QDBSHR', 'QRJE', 'QSYS', 'QLPAUTO',
'QLPINSTALL', 'QTSTRQS' or 'QDFTOWN'
13. Press enter on the STRGA command to start the GoAnywhere subsystem.
14. Execute the WRKACTJOB (Work with Active Jobs) command to confirm that the
GoAnywhere subsystem is running. You should find a subsystem which has the
same name as the library name that was specified on the INSTALLGA command in
step 10 (named GOANYHWERE by default). This subsystem should contain two
jobs, one is for the GoAnywhere application, and the other is for the JVM.
15. The installation and startup of GoAnywhere is complete. Now you should proceed
to the Initial Configuration instructions.
NOTE:
CL example:
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.
Installation − Docker
GoAnywhere can be installed using Docker containers. The GoAnywhere Docker image
provided by Fortra is based on CentOS Linux and uses the built in Azul Zulu Java SE 11
Java Development Kit (JDK). The image is installed in the /opt/Fortra/GoAnywhere
directory and runs as a non-root user (GAMFT instead of ROOT). GoAnywhere
installations must be licensed after they are started.
NOTE: Fortra recommends using Docker Compose instead of the docker run command
to install GoAnywhere since Docker Compose provides the best admin user
experience.
Requirements
Disk space 250 MB for product (does not include user data)
NOTE:
Port Numbers
Each GoAnywhere Docker image is configured to use the default ports, with the exception
of the HTTPS/AS2 (8443), FTP (8021), FTPS (8990), and SFTP (8022) Services. When
creating a new container, you must use the --publish (-p) attribute to map the default ports
in the container to ports that the host will use to send communication to GoAnywhere. An
install example below includes example port mappings.
For passive FTP, passive FTPS, and GoFast services, the GoAnywhere Docker image
has 200 ports set up for each service by default. If you need additional ports, or need to
modify the default ports on the Docker host, you will need to modify the corresponding
service settings and modify your docker-compose or docker run command to match.
When running GoAnywhere MFT in a cluster, the ports used must be unique and must
match the ports used in the service set up. For non-default ports, you will need to modify
the service settings to match your docker-compose or docker run command.
Volumes
Volumes are the preferred mechanism for persisting data that is generated by and used by
Docker containers. For GoAnywhere MFT, you will need to create a volume for the
following 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/Fortra/GoAnywhere directory.
NOTE: [config_dir] refers to the location of the GoAnywhere configuration files. For the
official GoAnywhere Docker image, this location is the /etc/Fortra/GoAnywhere
directory.
Creating these volumes will ensure that your configuration and userdata persist through
upgrades. For more information on volumes, see the Docker documentation
at: https://docs.docker.com/storage/volumes/.
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
IMPORTANT: For the multi-instance Docker configuration, the value of the cluster_dir
variable must be the full relative path of: /opt/Fortra/GoAnywhere/userdata/cluster.
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
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.
Perform the following steps to download and run GoAnywhere from the official Docker file
hosted on Docker Hub.
3. Download the GoAnywhere Docker image from Docker Hub using the following
command:
docker pull fortrallc/goanywhere-mft
4. You can verify the image has been downloaded correctly by using the following
command:
docker images
EXAMPLE:
The following command starts GoAnywhere MFT in a container and maps all the default
GoAnywhere ports to port numbers that will be used by the host.
docker run --detach \
--publish 9000:8000 --publish 9001:8001 --publish 9005:8005 \
--publish 9006:8006 --publish 9009:8009 --publish 9010:8010 \
--publish 9443:8443 --publish 9021:8021 --publish 9022:8022 \
--publish 32001-32300:32001-32300 \
--volume userdatadir:/opt/Fortra/GoAnywhere/userdata/ \
--volume upgraderdir:/opt/Fortra/GoAnywhere/upgrader/ \
--volume configdir:/etc/Fortra/GoAnywhere/config/ \
--volume tomcatserver:/etc/Fortra/GoAnywhere/tomcat/ \
--volume tomcatlogsdir:/opt/Fortra/GoAnywhere/tomcat/logs/ \
--volume ghttpsrootcustomdir:/opt/Fortra/GoAnywhere/ghttpsroot/custom/ \
fortra/goanywhere-mft:latest
7. Once the Docker container is running, you can access the administrator by opening
a browser window on your host and connecting to localhost: port where port number
is the mapped port number used in step 5. For example, the admin port 8000 was
mapped to port 9000. To access the administrator, you would use localhost:9000.
docker-compose up -d
4. Complete steps 1-3 under the section titled Setting up the First System in the
Cluster in the GoAnywhere MFT User Guide to set up the first system in your
cluster.
5. Complete the steps under the section titled Setting up Additional Systems in the
Cluster in the GoAnywhere MFT User Guide to configure online licenses.
6. Restart the Docker containers to apply database changes with the following
command:
docker-compose restart.
7. Log into MFT for Container1 and finish the cluster setup by completing step 4
under the section titled Setting up the First System in the Cluster in the
GoAnywhere MFT User Guide.
docker-compose up -d
10. Verify that Container1 was properly setup and is working for the cluster.
a. Copy the database.xml file from Container1 to the Docker host with the
following command:
docker cp <container1ID>:/etc/Fortra/config/database.xml .
b. Copy the database.xml file from the Docker host to additional Docker
container(s) using the following command:
docker cp database.xml
<containerID>:/etc/Fortra/GoAnywhere/config/database.xml .
12. Update the docker-compose.yml file by adding the environment variable MFT_
CLUSTER=true for any additional container(s).
docker-compose up -d
14. In a browser, log into MFT for all additional nodes and verify they are set up for
clustering.
To start GoAnywhere:
To stop GoAnywhere:
To start GoAnywhere:
To stop GoAnywhere:
The STRGA and ENDGA commands are located in the GoAnywhere installation library,
which is named GOANYWHERE by default.
Docker Instructions
Example: https://myserver:8001
Example: http://myserver:8000
2. The License Server page appears. Click the Get License button and follow the on
screen prompts to license the server.
3. Once the server is licensed, You are prompted to create an administrator account
for GoAnywhere. This account is assigned all administrator roles with access rights
to the entire GoAnywhere application. After this account is created, other Admin
User accounts can be created from the Users > Admin Users page.
If you want to change the location of the GoAnywhere config files after installing or
upgrading GoAnywhere, you will need to add the new path to the system.properties file
and manually move the config files to the user defined directory.
To create a user defined directory and to manually move the GoAnywhere config files,
complete the following steps:
com.linoma.config.directory=C:\\ProgramData\\Fortra\\GoAnywhere\\
NOTE:
All backslash ('\') characters need to be escaped in a given file path with an
additional backslash as noted in the example above.
3. Move the following GoAnywhere config files from the install directory into the user
defined config folder:
l agent.xml
l cluster.xml
l database.xml
l ftp.xml
l ftps.xml
l gateway.xml
l gofast.xml
l https.xml
l sftp.xml
l security.xml
l log4j2.xml
l filecatalyst.xml
4. After moving the GoAnywhere config files to the user defined directory, create a
'tomcat' folder in the user defined directory and create a 'conf' subfolder.
5. Locate the server.xml file in the [install_dir]\tomcat\conf folder and move it to the
user defined conf subfolder.
NOTE:
On Linux systems, you will need to modify directory permissions before installation for
non-root users if they choose a restricted directory (/etc., /var/lib) for their config files.
The user who has permissions to access the directory needs to be the user that
installs and runs GoAnywhere MFT.
n 8000 is the default HTTP port which users can connect (from their browsers) for
performing administration in GoAnywhere.
n 8001 serves the same function as port 8000, but uses a HTTPS (SSL-protected)
connection.
n 8005 is the default port for requesting a shutdown of GoAnywhere from a remote
system.
You can change these port numbers within the GoAnywhere browser-based administrator
interface, or by using the CFGGA command for IBM i or by making direct changes to a
GoAnywhere configuration file.
2. From the main menu bar, select the System > Admin Server.
5. Specify the new port number and click on the Save button.
6. The GoAnywhere server must be restarted for the changes to take effect.
4. Under the Port Information section, edit the port numbers as needed by choosing
option 2.
5. You may also want to change the URL under the Run Project Defaults section to
match the port number to the new Server Port.
6. Save the settings and restart GoAnywhere by running the STRGA command.
3. Change the port number for the HTTP or HTTPS connectors. Example:
<Connector port="8000" />
Memory Allocation
GoAnywhere runs in a JVM (Java Virtual Machine) instance, which is allocated 1024 MB
of memory by default when the product is installed. This memory is utilized for all features
in GoAnywhere including administration functions and file transfer activity.
Typically 1024 MB of memory is sufficient for most installations, though 2048 is ideal. If
you anticipate high loads (e.g. several thousand file transfers per day), then it is
recommended to allocate more memory for the GoAnywhere JVM. Depending on your
operating system, follow the instructions below to change this memory allocation.
For Windows:
1. Navigate to the directory of [Install_Dir]/tomcat/bin, where [Install_Dir] is the
installation directory for GoAnywhere.
NOTE:
3. Click on the Java tab and edit the Maximum memory pool setting. Specify 2048 for
2GB of memory, 3072 for 3GB of memory, 4096 for 4GB of memory, etc…
5. To restart GoAnywhere for the changes to take effect, click on the General tab and
choose to Stop and then Start the service.
4. The setting –Xmx1024m is the max memory setting, which is set to 1024 MB by
default. Change this setting to Xmx2048m for 2GB of memory, -Xmx3072 for 3GB
of memory, Xmx4096 for 4GB of memory, etc…
Do not change the MaxPermSize value. For example:
Firewall Recommendations
If you want to make GoAnywhere available to external clients over the internet, it is
important that you only open certain port numbers to the machine in which GoAnywhere is
installed. This can be controlled through your firewall settings. The firewall settings will
depend on whether if the GoAnywhere software is installed in your DMZ (Demilitarized
Zone) or the Private (internal) network, and whether if it is used in conjunction with Fortra
GoAnywhere Gateway product.
The following diagrams show the firewall settings to use if the default port numbers were
used during the installation of GoAnywhere.
Please note that the IP addresses shown are for demonstration purposes only.
Firewall configuration:
In order to administer GoAnywhere from any workstations in the private network, ports
8000 and 8001 will need to be opened (through the back-end firewall) from the private
If external trading partners need access to the file transfer protocols (e.g. SFTP, FTP,
HTTPS, AS2, FTPS, GoFast) in GoAnywhere, those port numbers (e.g. 21, 22, 443, 990,
8009, 8010) need to be opened through the front-end firewall to GoAnywhere in the DMZ.
Additionally, if employees (on the private network) need to access those file transfer
protocols in GoAnywhere, the port numbers will need to be opened through the back-end
firewall from the private network to GoAnywhere in the DMZ.
If trigger events in GoAnywhere need to call Remote Projects , then ports 8000 and 8001
need to be opened (through the back-end firewall) from GoAnywhere to another
GoAnywhere server in the private network.
3. On the System Info tab, verify the Java Version and the Java Home values.
l If the Java Home is configured to [INSTALL_DIR]/jre you are using the
embedded JDK. Use the Upgrade instructions below to upgrade your
embedded JDK.
l If the Java Home is configured to any other directory, you are using an
external JDK.
Even if GoAnywhere MFT is using an external JDK, it is possible than an embedded JDK
still exists within the application. HelpSytems recommends that you remove the
[INSTALL_DIR]/jre folder, or rename the [INSTALL_DIR]/jre to something like [INSTALL_
DIR]/jre.old.
The JAVA_HOME environment variable needs to be set to the appropriate location for
Java 11. To set the Java version used to run GoAnywhere MFT on Linux, run the following
command before executing the GoAnywhere MFT upgrade script.
export JAVA_HOME='/path/to/jdk'
The JAVA_HOME environment variable needs to be set to the appropriate location for
Java 11. To set the Java version used to run GoAnywhere MFT on Windows, run the
following command before executing the GoAnywhere MFT upgrade script.
1. Open the Control Panel and navigate to System And Security > System.
3. On the Advanced tab, select Environment Variables, and then edit JAVA_HOME to
point to where the JDK software is located, for example, C:\Program
Files\Java\jdk1.11.0.
4. 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.
5. Navigate to the Help > About page and verify Java has been has changed to your
selected version.
NOTE:
The IP addresses shown are for demonstration purposes only.
Firewall configuration:
If external trading partners need access to the file transfer protocols (e.g. SFTP, FTP,
HTTPS, AS2, FTPS, GoFast) in GoAnywhere, those port numbers (e.g. 21, 22, 443, 990,
8009, 8010) need to be opened through the firewall to GoAnywhere in the private network.
NOTE:
The IP addresses shown are for demonstration purposes only.
Firewall configuration:
The port numbers (e.g. 21, 22, 23, 443, 990, 8010 and 30000-32100) for the desired file
transfer protocols (e.g. FTP, SFTP, FileCatalyst, HTTPS, FTPS, AS2, GoFast) need to be
opened through the front-end firewall to GoAnywhere Gateway in the DMZ.
Database Overview
By default, GoAnywhere stores its configuration settings and application data in an
embedded Derby database. This database includes almost everything GoAnywhere needs
to operate, including user-defined settings, user account information, permissions, server
configuration information and more. The database also stores the audit log entries for
Project Workflows and each of the file transfer protocols.
Operational Considerations
The embedded Derby database is ideal for trial purposes and standalone instances such
as sandbox or development environments. Customers who use the embedded Derby
database on production systems should be aware of the following limitations:
l The embedded Derby database does not support GoAnywhere clustering, and as
such, the database is only ideal for small operations where high availability is not
needed.
l GoAnywhere is unavailable during backups and database tuning of the embedded
database, which halts all file transfer and workflow tasks. Externalizing the
database is the preferred method if 24/7 availability is required.
l The embedded Derby database is not accessible to 3rd party database reporting
and monitoring tools.
TIP:
Fortra highly recommends customers externalize the GoAnywhere database.
Complete database instructions can be found in the GoAnywhere MFT User Guide in
the System > Database Configuration section.
Clustering Overview
Clustering allows two or more GoAnywhere installations (systems) to work together to
provide file transfer services for the enterprise. This provides greater scalability by
allowing workloads to be distributed horizontally across multiple GoAnywhere systems.
If one GoAnywhere system fails, the remaining systems in the cluster will automatically
continue to process workloads and file transfer requests.
This active-active clustered environment also provides the best high availability option for
handling potential system failures. If one GoAnywhere system fails, the remaining
systems in the cluster will automatically continue to service the trading partners.
To learn more about clustering in GoAnywhere, see the GoAnywhere MFT User Guide
and navigate to System > Clustering.
The IBM i commands can be found in the installation library, which is GOANYWHERE by
default. Listed below is an alphabetical listing of the commands:
SFTPGET Get file over SFTP Retrieves one or more files over a SFTP
connection
SFTPPUT Put file over SFTP Sends one or more files over a SFTP
connection
UNZIP UnCompress file with Unzips files that were compressed with ZIP
ZIP standard
NOTE:
Before the SFTP, OpenPGP, ZIP and Email native commands can be utilized, their
underlying Projects (to process these commands) must be first created in
GoAnywhere. To perform this initial Project creation, select option 1 from GAMENU4
(which will execute the command CRTCMDPRJ). The Projects will be created in the
GoAnywhere folder of \CommandLineProjects.
Upgrading GoAnywhere
New versions of GoAnywhere can be downloaded from the GoAnywhere Customer Portal
at my.goanywhere.com. A GoAnywhere MFT Upgrade Guide is released for each new
software version, and contains detailed upgrade considerations and instructions. The
upgrade guide is also available on the GoAnywhere Customer Portal.
If your organization uses a Proxy Server, then you need to configure those proxy settings
in GoAnywhere before you can retrieve web updates:
1. From the main menu, select System and then Global Preferences.
2. Click the HTTP Proxy tab near the right end of the tab set.
3. Specify the type of proxy to use. DIRECT, HTTP, or SOCKS. DIRECT represents a
direct connection, or the absence of a proxy. HTTP represents proxy for high-level
protocols such as HTTP or FTP. SOCK represents a SOCKS (V4 or V5) proxy.
6. Specify the username to use in order to connect to the proxy server. This is only
necessary if the proxy server requires authentication.
7. Specify the password to use in order to connect to the proxy server. This is only
necessary if the proxy server requires authentication.
Upgrade Process
Upgrading GoAnywhere requires that you first download the updates from the portal at
my.goanywhere.com. Then you will need to stop its corresponding service/subsystem,
apply the updates, and then restart GoAnywhere.
You can check for software updates by following the instructions below:
2. From the main menu, select Help and then choose the Check for Updates option.
3. If updates are found, the page will display the new version number, the release notes,
and brief instructions on how to download and install the new version. Detailed
upgrade instructions for the new version can be found in the GoAnywhere
MFT Upgrade Guide.
WARNING:
All GoAnywhere configurations, resources and project definitions will be deleted
during the uninstall process.
2. Change the working directory to the directory where GoAnywhere was installed
(for example, cd /usr/local/Fortra/GoAnywhere).
2. Verify that there are no locks on the GoAnywhere library. Default library name is
GOANYWHERE.
WRKOBJLCK OBJ(GOANYWHERE) OBJTYPE(*LIB)
4. Delete the GoAnywhere folder from the IFS. The default main folder name is
/fortra/goanywhere.
RMVLNK OBJLNK('/fortra/goanywhere/*.*')
RMVDIR DIR('/fortra/goanywhere')
2. Determine the name or ID of the container you want to delete using the following
command:
docker ps -a
5. Delete the GoAnywhere image from Docker using the following command:
docker rmi image name