GoAnywhere Director to GoAnywhere MFT Upgrade Guide. Version: Publication Date: 07/09/2015

Transcription

1 GoAnywhere Director to GoAnywhere MFT Upgrade Guide Version: Publication Date: 07/09/2015

2 Copyright 2015 Linoma Software. All rights reserved. Information in this document is subject to change without notice. The software described in this document is furnished under a license agreement and may be used only in accordance with the terms of that agreement. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or any means electronic or mechanical, including photocopying and recording for any purpose other than the purchaser's personal use without the written permission of Linoma Software. GoAnywhere and the GoAnywhere logo are trademarks of Linoma Software, Inc. Other trademarks shown are the property of their respective owners. Linoma Software 103 South 14th Street Ashland, NE United States This document was published on 7/9/2015. GoAnywhere Director Upgrade Guide 2

3 Contents Welcome 4 Before You Begin 4 Browser Compatibility 4 Menu Enhancement 4 Custom Task Prerequisite 5 License Prerequisite 6 Upgrade Process 7 System Requirements 8 Windows Requirements 8 Linux/Unix Requirements 8 IBM i (iseries) Requirements 8 Download the Upgrade File 10 Upgrading the Java Virtual Machine (JRE) 11 Windows Upgrade Instructions 13 Linux/UNIX Upgrade Instructions 14 IBM i Upgrade Instructions 15 Upgrading a Cluster Environment 16 Downgrading GoAnywhere Director 17 About Linoma Software 19 Contacting Linoma Software 19 GoAnywhere Director Upgrade Guide 3

4 Welcome Welcome This guide outlines the steps required for upgrading GoAnywhere Director to GoAnywhere Managed File Transfer (MFT) on your server. GoAnywhere MFT is the next evolution in Managed File Transfer, which merges workflow automation capabilities (adapted from GoAnywhere Director) with secure FTP server and collaboration features (adapted from GoAnywhere Services). Both GoAnywhere Director and GoAnywhere Services products have been superseded by the GoAnywhere MFT solution. Before You Begin If you are upgrading from a version older than 3.6.1, you must follow the upgrade process until you install version or later. Due to licensing restrictions, upgrade versions less than will no longer process FTP and SFTP transfers. Since GoAnywhere Director must be restarted to apply the updates, it is important that you perform the upgrade process when no projects are running in GoAnywhere Director. 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. Browser Compatibility The GoAnywhere MFT Administrator interface requires modern internet browsers that support HTML 5. Popular browsers are supported including Internet Explorer, 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. Menu Enhancement The menu structure in GoAnywhere Director has been reorganized in GoAnywhere MFT. Notable changes include: Resources are now found in the Resources menu. Projects, Scheduler, Monitors, Triggers, Job Queue Manager, Queued Jobs, Active Jobs, and Completed Jobs are now found in the Workflows menu. The SSL Certificate Manager, SSH Key Manager, Open PGP Key Manager, FIPS Compliance, and Encrypted Folders Manager are now found in the Encryption menu. System configuration settings, such as Global Settings, Database Configuration, Cluster Manager, Custom Tasks, and IP Filter are now found in the System menu. The GoAnywhere MFT license is now managed in the Help menu. View the GoAnywhere Managed File Transfer User Guide for more information. GoAnywhere Director Upgrade Guide 4

5 Custom Task Prerequisite Custom Task Prerequisite Customer's who have created Custom Tasks in GoAnywhere Director must re-install their custom task imports and extend the 'CustomTask' class after the upgrade to GoAnywhere MFT. For more information, see the GoAnywhere MFT Custom Task Guide. New CustomTask Class Example (Changes in Red) package com.example; import com.linoma.ga.projects.customtask; import com.linoma.ga.projects.taskcontainer; public class CopyTask extends CustomTask { public CopyTask(TaskContainer parent) { super(parent); } } GoAnywhere Director Upgrade Guide 5

6 License Prerequisite License Prerequisite GoAnywhere MFT requires a new license key which is issued through the GoAnywhere Customer Portal. During the upgrade, you will be presented with a base 64 encoded license bundle (example below) that will be used to upgrade your existing license. Follow the instructions on the screen to activate your license. Once your license is activated on the Customer Portal, download the license to your workstation by clicking the Download button. You can also download the license at any time by expanding the Active license row and clicking the Download button under the license key. Once the gamft.lic file is downloaded, copy the file to the installation directory on the GoAnywhere server that produced the license activation request. Windows Example Installation Directory: C:\Program Files\Linoma Software\GoAnywhere License File Location: C:\Program Files\Linoma Software\GoAnywhere\gamft.lic Linux/Unix Example Installation Directory: /usr/local/linoma_software/goanywhere License File Location: /usr/local/linoma_software/goanywhere/gamft.lic IBM i Example Installation Directory: /local/goanywhere License File Location: /local/goanywhere/gamft.lic The activated license exclusively belongs to the GoAnywhere installation that produced the activation request. It cannot be used to upgrade or run any other install of GoAnywhere. GoAnywhere Director Upgrade Guide 6

7 Upgrade Process Upgrade Process Typically the upgrade process will only take a few minutes to run. It is important that you perform the upgrade process when no jobs are running in GoAnywhere Director since it must be shut down during the upgrade. An upgrade script (program) is available which will perform all the necessary steps to migrate GoAnywhere Director to GoAnywhere MFT. Download the latest upgrade script by visiting the GoAnywhere Customer Portal at my.goanywhere.com. 1. Verify you meet the minimum system requirements. 2. Obtain the correct upgrade file. 3. Follow the steps for the installed platform: Windows Linux/UNIX IBM i GoAnywhere MFT 4.3.x and higher requires Java Virtual Machine (JRE) version 1.6 or later. Follow the instructions here to upgrade the JRE version for GoAnywhere Director. GoAnywhere Director Upgrade Guide 7

8 System Requirements System Requirements You must meet the minimum system requirements before upgrading GoAnywhere Director on your server. Windows Requirements Operating Systems supported Windows Server 2003 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Windows XP Windows Vista Windows 7 Windows 8 Disk space Memory 300 MB for product (does not include user data) 512 MB minimum Linux/Unix Requirements Disk space Memory 300 MB for product (does not include user data) 512 MB minimum IBM i (iseries) Requirements Operating System Disk Space Memory IBM i V6R1 or higher 250 MB for product (does not include user data) 512 MB minimum Required Licensed Programs The following IBM i licensed programs are prerequisites to the installation of GoAnywhere Director, which are dependent on the IBM i release. IBM i Release Licensed Program Product Option Description V6R1 5761JV1 11 Java SE 6 32 bit 5761SS1 30 QShell 5761SS1 33 Portable App Solutions Environment GoAnywhere Director Upgrade Guide 8

9 IBM i (iseries) Requirements V7R1 5761JV1 11 Java SE 6 32 bit 5770SS1 30 QShell 5770SS1 33 Portable App Solutions Environment V7R2 5770JV1 11 Java SE 6 32 bit 5770SS1 30 QShell 5770SS1 33 Portable App Solutions Environment GoAnywhere Director Upgrade Guide 9

10 Download the Upgrade File Download the Upgrade File The GoAnywhere Customer Portal is where you can create support requests, check the status of a support case, download software updates and documentation, 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 To check if there are any updates available for GoAnywhere Director, login to its browser interface as a user with the Product Administrator role. From the main menu bar, point to Administration 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 Director to the latest version. GoAnywhere Director 4.3.x and higher require Java Virtual Machine (JRE) version 1.6 or later. Follow the instructions here to upgrade the JRE version for GoAnywhere Director. Depending how old your current GoAnywhere Director version is, you may need to repeat the upgrade process until you are upgraded to the current version of The versions must be upgraded in the order listed below to maintain database integrity. Installed Version Upgrade Version Upgrade to Upgrade to Upgrade to Upgrade to Upgrade to Upgrade to Upgrade to Upgrade to Upgrade to Upgrade to Upgrade to Upgrade to GoAnywhere MFT Your current installed version can be found by pointing to the Help menu and then clicking About. GoAnywhere Director Upgrade Guide 10

11 Upgrading the Java Virtual Machine (JRE) Upgrading the Java Virtual Machine (JRE) Depending on the operating system, GoAnywhere Director may use a JRE that is bundled with the application or it may use an existing JRE which is already installed. Follow the steps below to determine which JRE is being used and then take the appropriate upgrade steps. For more information, visit the GoAnywhere Support Forum Determine Java (JRE) version and Location 1. From the menu bar, point to Help, then click About. 2. In the About window, click the System Info tab. 3. On the System Info tab, verify the Java Version and the Java Home values. Java 1.8 If GoAnywhere Director is using JRE version 1.8, it must be at least Java 1.5 or Earlier If GoAnywhere Director is already using a JRE that is version 1.6 or later, then you can skip this section. Windows and Linux When upgrading, GoAnywhere Director uses a bundled JRE if a suitable Java installation is not detected. Solaris and other Unix/Linux Installations JCE Policy Files Before GoAnywhere Director can be started or upgraded using the new JRE, it requires installation of the unlimited strength JCE policy files. To use the unlimited strength policy files, copy the JCE policy files to the JRE s (Java Runtime Environment) security folder. Copy the US_export_policy.jar file and the local_policy.jar file from the jce_policy_files/sun folder (located in the GoAnywhere Director installation folder) to the jre/lib/security folder (located in the JRE's installation directory). Changing Java Home The JAVA_HOME environment variable needs to be set to the appropriate location for Java 1.6 (or later). If you do not have Java 1.6 installed on your system, it must be installed before proceeding. To set the Java version used to run GoAnywhere Director and the upgrade, run the following command before executing the GoAnywhere Director upgrade script. export JAVA_HOME='/path/to/jre' '/path/to/jre' is the absolute path to the JRE, for example: '/usr/lib/jvm/jdk6/jre' GoAnywhere Director Upgrade Guide 11

12 Upgrading the Java Virtual Machine (JRE) Alternate Java Installations Platforms such as IBM i, AIX, and Mac OS use a version of the JRE supplied by the platform manufacturer. Ensure GoAnywhere Director is running on Java 1.6 or later before upgrading. The upgrade will fail if the system is not running the correct Java version. IBM i Installations Required PTFs The following Group PTFs are prerequisites to run GoAnywhere Director 4.3.x and later on Java 1.6. Use the command WRKPTFGRP to verify that the required group PTFs are applied. V6R1 Group PTF SF99562 (minimum level of 23) V7R1 Group PTF SF99572 (minimum level of 12) Changing Java Home AIX Installations 1. Run GOANYWHERE/CFGGA and select option 2 on Java Home and Java Version. 2. Change the Java Home value from /QOpenSys/QIBM/ProdData/JavaVM/jdk50/32bit to /QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit and then press ENTER to save. 3. Change the Java Version value from 1.5 to 1.6 and then press ENTER to save. 4. Run GOANYWHERE/CPYPOLICY to copy the JCE unlimited strength policy files into the JVM used by GoAnywhere Director. JCE Policy Files Before GoAnywhere Director can be started or upgraded using the new JRE, it requires installation of the unlimited strength JCE policy files. To use the unlimited strength policy files, copy the JCE policy files to the JRE s (Java Runtime Environment) security folder. Copy the US_ export_policy.jar file and the local_policy.jar file from the jce_policy_files/ibm folder (located in the GoAnywhere Director installation folder) to the jre/lib/security folder (located in the JRE's installation directory). Changing Java Home The JAVA_HOME environment variable needs to be set to the appropriate location for Java 1.6 (or later). If you do not have Java 1.6 installed on your system, it must be installed before proceeding. To set the Java version used to run GoAnywhere Director and the upgrade, run the following command before executing the GoAnywhere Director upgrade script. export JAVA_HOME='/path/to/jre' '/path/to/jre' is the absolute path to the JRE, for example: '/usr/lib/jvm/jdk6/jre' GoAnywhere Director Upgrade Guide 12

13 Windows Upgrade Instructions Windows Upgrade Instructions Prior to beginning the upgrade, Linoma Software suggests that you move any previous backup files (e.g. backup 2, backup 3, etc.) out of the [installfolder/backup] folder (where [installfolder] is the location where GoAnywhere Director is installed). 1. Rename the downloaded upgrade file to ga_upgrade.jar 2. Copy the downloaded upgrade file to [installfolder]\upgrader, where C:\Program Files\Linoma Software\GoAnywhere is the default installation directory of GoAnywhere Director. 3. 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. Rename and move the most recent logs to a folder outside the [installfolder] location. 4. Sign into the GoAnywhere Director browser-based Administrator and verify there are no active jobs before proceeding. 5. Login to the Windows system as an administrator. a. If the GoAnywhere Director 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 Director service, select Properties, and then click the Log On tab. 6. Stop the GoAnywhere Director 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. 7. If the GoAnywhere Director 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. 9. Run the upgrade.bat file to start the upgrade process. When complete, a message indicates the upgrade was successful. The first time you run the GoAnywhere MFT upgrade for each installation of GoAnywhere, you will be presented with a License Activation request (see License Prerequisite). Use this request to activate and install your GoAnywhere MFT license. Once installed, run the upgrade again. 10. Start the GoAnywhere Director 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 Director service, its status should be updated to Started. 11. Before logging into the upgraded version of GoAnywhere Director, each user should press CTRL + F5 from their browser to clear the cache. Due to a licensing issue with a third party API, you must upgrade to at least version in order to use the FTP, SCP, FTPS or SFTP functionality in GoAnywhere Director. It is recommended to repeat the upgrade process until you are at the current release of GoAnywhere Director. GoAnywhere Director Upgrade Guide 13

14 Linux/UNIX Upgrade Instructions Linux/UNIX Upgrade Instructions Prior to beginning the upgrade, Linoma Software suggests that you move any previous backup files (e.g. backup 2, backup 3, etc.) out of the [installfolder/backup] folder (where [installfolder] is the location where GoAnywhere Director is installed). 1. Rename the downloaded upgrade file to ga_upgrade.jar 2. Copy the downloaded upgrade file to [installfolder]/upgrader, where /usr/local/linoma_software/goanywhere is the default installation directory of GoAnywhere Director. 3. Sign into the GoAnywhere Director browser-based Administrator and verify there are no active jobs before proceeding. 4. Login to the system as a root user and open a terminal window. 5. Stop the GoAnywhere Director service: a. Change the working directory to the directory where GoAnywhere Director is installed. For example: cd /usr/local/linoma_software/goanywhere b. Stop the GoAnywhere Director application server by executing the following shell script:./goanywhere.sh stop 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 Director database is configured to run on a database other than the embedded Derby database, make a backup of that external database before continuing. 8. Change the directory to [installfolder]/upgrader. 9. Run the upgrade.sh file to start the upgrade process. When complete, a message indicates the upgrade was successful. The first time you run the upgrade for each installation of GoAnywhere, you will be presented with a License Activation request (see License Prerequisite). Use this request to activate and install your GoAnywhere MFT license. Once installed, run the upgrade again. 10. Start the GoAnywhere Director service: a. Change the working directory to the directory where GoAnywhere Director is installed. For example: cd /usr/local/linoma_software/goanywhere b. Start the GoAnywhere Director application server by executing the following shell script:./goanywhere.sh start 11. Before logging into the upgraded version of GoAnywhere Director, each user should press CTRL + F5 from their browser to clear the cache. Due to a licensing issue with a third party API, you must upgrade to at least version in order to use the FTP, SCP, FTPS or SFTP functionality in GoAnywhere Director. It is recommended to repeat the upgrade process until you are at the current release of GoAnywhere Director. GoAnywhere Director Upgrade Guide 14

15 IBM i Upgrade Instructions IBM i Upgrade Instructions 1. Rename the downloaded upgrade file to ga_upgrade.jar. 2. Copy the downloaded upgrade file to [installfolder]/upgrader on the IFS, where /linoma/goanywhere/ is the default installation directory of GoAnywhere Director. If GoAnywhere Director is installed in a different directory, substitute with that directory. 3. Sign into the GoAnywhere Director browser-based Administrator and verify there are no active jobs 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 Director 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 Director subsystem is completely shutdown before proceeding. 6. Verify there are no locks on the GoAnywhere Director 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. 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. 8. 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. 9. If the GoAnywhere Director database is configured to run on a database other than the embedded Derby database: Version 3.5.x and 3.6.x - Backup the external database before continuing. Version and later - The SAVPRD command provides a parameter to backup the GoAnywhere Director external database library when running on DB2. Other database types require a manual backup. 10. Apply the upgrade by executing the UPGRADEGA command. The UPGRADEGA command is located in the installation library, which is named GOANYWHERE by default. The first time you run the upgrade for each installation of GoAnywhere, you will be presented with a License Activation request (see License Prerequisite). Use this request to activate and install your GoAnywhere MFT license. Once installed, run the upgrade again. 11. The user profile starting the subsystem must have *RWX permission to the GoAnywhere Director installation folder and the entire directory tree. On V6R1 and later, a command is provided to change the authority on an entire directory tree. In this example '/linoma/goanywhere' is the installation directory and PGUSER will be the user profile that will be starting the subsystem. CHGAUT OBJ('/linoma/goanywhere') USER(PGUSER) DTAAUT(*RWX) OBJAUT(*ALL) SUBTREE(*ALL) 12. Start the GoAnywhere Director subsystem by executing the IBM i command of STRGA. The STRGA command is located in the installation library, which is named GOANYWHERE by default. 13. Before logging into the upgraded version of GoAnywhere Director, each user should press CTRL + F5 from their browser to clear the cache. Due to a licensing issue with a third party API, you must upgrade to at least version in order to use the FTP, SCP, FTPS or SFTP functionality in GoAnywhere Director. It is recommended to repeat the upgrade process until you are at the current release of GoAnywhere Director. GoAnywhere Director Upgrade Guide 15

16 Upgrading a Cluster Environment Upgrading a Cluster Environment The following steps will ensure a successful upgrade when upgrading GoAnywhere Director 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. Each server in the cluster will need a new license when upgrading to GoAnywhere MFT. 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 Director 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. Windows Upgrade Instructions Linux/Unix Upgrade Instructions IBM i Upgrade Instructions 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 Director subsystem or service on the server after it is upgraded. If this is the first server to be upgraded, it will assume the coordinator role. 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 Director Upgrade Guide 16

17 Downgrading GoAnywhere Director Downgrading GoAnywhere Director When an upgrade is performed, the upgrade process makes a backup of folders and files that could be changed during upgrade. These files are placed in [installfolder]/backup (where [installfolder] is the location where GoAnywhere Director is installed). If the backup folder already exists when an upgrade starts, the existing backup directory will be renamed to backup 2, backup 3, etc. The most recent backup will always be in the base backup directory. If the upgrade fails before the backup directory is successfully created, then no changes will be made and you can restart GoAnywhere Director. The upgrade creates an upgrade log, which displays the location of the backup folder. Example of the upgrade log: Installed Version: Upgrading to: Checking the server status... GoAnywhere Server appears to be down. Okay to upgrade. Backing up currently installed files Created the backup directory: /linoma/goanywhere/backup Backup was created in: /linoma/goanywhere/backup 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 rollback is performed. The rollback returns GoAnywhere Director 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 MFT subsystem or service. 2. Make a copy of the [installfolder] for archive purposes. 3. Make note of the folders in the [installfolder]/backup location and remove the corresponding folders from the [installfolder] location. If using an external database, restore that database to the backup made just prior to upgrading GoAnywhere Director. If rolling back from GoAnywhere Director 3.5.x to 3.2.1, delete the [installfolder]/lib folder. This folder did not exist in versions prior to and will cause issues when you run the upgrade again. When restoring, verify the permissions and ownership of the files and folders in the [installfolder] /backup folder match those of the [installfolder]. 4. Copy the contents of the [installfolder]/backup folder to the [installfolder]. 5. If using the embedded Derby database and rolling back from GoAnywhere Director 3.6.x thru 4.7.x, copy the contents of the [installfolder]/backup/database to [installfolder]/userdata/database/goanywhere. If using the embedded Derby database and rolling back from GoAnywhere MFT 5.0, copy the contents of the [installfolder]/backup/userdata/database/goanywhere to [installfolder]/userdata/database/goanywhere. 6. Navigate to the [installfolder]/tomcat/work folder and delete all files present in that folder. 7. Start the GoAnywhere Director subsystem or service. GoAnywhere Director Upgrade Guide 17

18 Downgrading GoAnywhere Director Additional Steps for Windows Server Downgrades from GoAnywhere Director 4.1.x to 4.0.x: 1. Make note of any special configuration changes to the GoAnywhere Director service. 2. Stop the GoAnywhere Director service. 3. From a command prompt, navigate to the [installfolder]\tomcat\bin folder. 4. Run the following command: service.bat remove 5. When complete, run this command: service.bat install 6. Start the GoAnywhere Director service. GoAnywhere Director Upgrade Guide 18

19 About Linoma Software About Linoma Software Linoma Software provides innovative technologies for protecting sensitive data and automating data movement. Linoma Software has a diverse install base of over 3,000 customers around the world including Fortune 500 companies, non-profit organizations and government entities. Linoma Software s success has been built on being very responsive to our customer s requirements. If you have suggestions on how we can improve our products to better serve your organization, please let us know. Contacting Linoma Software Online Sales Support Web Site Sales@GoAnywhere.com Support@GoAnywhere.com Phone Toll-free (800) Outside USA (402) Fax (402) Mail Linoma Software 103 South 14th Street Ashland, NE United States GoAnywhere Director Upgrade Guide 19