How do I run GoAnywhere on JAVA 1.6?

View some of the Frequently Asked Questions to our support staff. Included are some tips and tricks making this forum ideal for users getting started with GoAnywhere Director. Note: Users can reply to existing topics but only our support staff can add new topics to this forum.

How do I run GoAnywhere on JAVA 1.6?

Postby Support_Mary » Tue Nov 20, 2012 4:52 pm

The instructions for running GoAnywhere on JAVA (JDK or JRE) version 1.6 is dependent on your operating system.

Instructions for IBM i Customers:

For IBM i customers on V5R3 of the operating system:
IBM does not allow JRE 6 (JDK 6) to be installed on V5R3. To take advantage of future releases of GoAnywhere, you will need to upgrade to IBM i OS version V5R4 or higher and install JDK 6 (1.6).

For IBM i customers on V5R4 of the operating system:
You will need to install IBM’s licensed program 5722JV1 options 10 or 11 to get JDK 6 (1.6). (Linoma recommends you install Option 11). Optionally, you can order the special PTF of SI30432 from IBM. Group PTF SF99291 (minimum level of 17) is required to run GoAnywhere. Running on lower level has been known to cause issues with GoAnywhere in certain scenarios and is not recommended. Use the command WRKPTFGRP to verify that the required group PTFs are applied.

For IBM i customers on V6R1 of the operating system:
JDK 6 (1.6) is included on IBM i operating system version of V6R1. Group PTF SF99562 (minimum level of 23) is required to run GoAnywhere. Running on lower level has been known to cause issues with GoAnywhere in certain scenarios and is not recommended. Use the command WRKPTFGRP to verify that the required group PTFs are applied.

For IBM i customers on V7R1 of the operating system:
JDK 6 (1.6) is included on IBM i operating system version V7R1. Group PTF SF99572 (minimum level of 12) is required for GoAnywhere. Running on lower level has been known to cause issues with GoAnywhere in certain scenarios and is not recommended. Use the command WRKPTFGRP to verify that the required group PTFs are applied.

To configure your installation of GoAnywhere Director to use JDK 6 (1.6) on IBM i:
Please note above requirements before changing your configuration

  1. Make sure the GoAnywhere Director installation library is in your library list
  2. From the Command Line, type CFGGA and press <ENTER>
  3. Take option 2 next to the “Java Home” item
  4. Change the value to "/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit" and press <ENTER>
  5. Take option 2 next to the “Java Version” item
  6. Change the value to "1.6" and press <ENTER>

Once these changes have been made, GoAnywhere Director will need to be restarted by following these instructions:
  1. From the Command Line, execute ENDGA
  2. Make sure the GoAnywhere Director Subsystem has ended
  3. From the Command Line, execute STRGA (changing the run UserID as needed)
  4. Verify the GoAnywhere Director Subsystem has started

To configure your installation of GoAnywhere Services to use JDK 6 (1.6) on IBM i:

  1. Make sure the GoAnywhere Services installation library is in your library list
  2. From the Command Line, type CFGGAS and press <ENTER>
  3. Take option 2 next to the “Java Home” item
  4. Change the value to "/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit" and press <ENTER>
  5. Take option 2 next to the “Java Version” item
  6. Change the value to "1.6" and press <ENTER>

Once these changes have been made, GoAnywhere Services will need to be restarted by following these instructions:
  1. From the Command Line, execute ENDGAS
  2. Make sure the GoAnywhere Services Subsystem has ended
  3. From the Command Line, execute STRGAS (changing the run UserID as needed)
  4. Verify the GoAnywhere Services Subsystem has started

Instructions for Linux Customers:
If you installed GoAnywhere with the executable shell script specific to your system’s architecture (i.e. x64 or x86) then a JRE was shipped with the application and no further action is needed.

If you did not, or are unsure, you can verify the Java Home setting in the GoAnywhere admin screens by going to Help->About->System Info tab. If the Java Home is pointed to [INSTALL_DIR]/jre, where [INSTALL_DIR] is the folder location where GoAnywhere is installed, then you are using the JRE that is shipped with the GoAnywhere Installer. The 4.3.0 upgrade of GoAnywhere Director will install an updated JRE if required.

If this location is different, and the JRE version is 1.5, then you must configure GoAnywhere to use a newer JRE. Follow the Instructions for Switching the JRE on Linux/Unix based Operating Systems below.

Instructions for UNIX, AIX, HP-UX and Solaris Customers:
The installer for UNIX, AIX, HP-UX and Solaris operating systems do not include a JRE. Confirm you are using JRE 1.6 (or later) by going to the Help->About->System Info tab in the GoAnywhere administrator. If the Java Version is 1.5.x, you need to update the JRE used by GoAnywhere. Follow the Instructions for Switching the JRE on Linux/Unix based Operating Systems below.

Instructions for Switching the JRE on Linux/Unix based Operating Systems:
The JAVA_HOME environment variable needs to be set to the appropriate location for JRE 1.6. If you do not have JRE 1.6 (or later) installed on your system, then you must first have it installed before proceeding.

To set the JRE used to run GoAnywhere, run the following command before executing the GoAnywhere startup script.

  1. export JAVA_HOME='/path/to/jre'
    [i]'/path/to/jre' is the absolute path to the jre. i.e. export JAVA_HOME='/usr/lib/jvm/java-6-sun-1.6.0.26/jre'

**NOTE**
This command may vary depending on the exact flavor of your OS, so please refer to your Operating System documentation for more information.

Instructions for Windows Customers:
The Windows installers for GoAnywhere are shipped with an appropriate JRE, and in most cases, no further action is required. If you modified your install to use an alternate JRE, or are unsure, you can verify the Java Home setting in the GoAnywhere admin screens by going to Help->About->System Info tab. If the Java Home is pointed to [INSTALL_DIR]/jre, where [INSTALL_DIR] is there folder location where GoAnywhere is installed, then you are using the JRE that is shipped with the GoAnywhere Installer. The 4.3.0 upgrade of GoAnywhere Director will update the application to use a newer 1.6 version of the JRE in all cases. If you wish to continue using an alternate JRE after upgrading to GoAnywhere Director 4.3.0, you will need to manually update the Windows service again, following the steps outlined below.

Follow the directions below to change the JRE used by GoAnywhere.

  1. cd [INSTALL_DIR]\tomcat\bin
    where [INSTALL_DIR] is the folder where GoAnywhere is installed
  2. Double click on the file [SERVICE_NAME]w.exe
    where [SERVICE_NAME] is the name chosen for the Windows Service during installation of GoAnywhere

    This launches the service configuration tool (see below):
    GAD Properties.PNG

  3. Navigate to the ‘Java’ tab and click the ellipsis "…" button on the Java Virtual Machine field.
  4. Navigate to and select the file [JRE]\bin\server\jvm.dll
    i.e. An alternate JRE path may look like C:\Program Files\Java\jre6\bin\server\jvm.dll
  5. Click OK and restart the windows service.

Log in to the administrator and view the Help->About->System Info tab to confirm that GoAnywhere is running on the new JRE.

GoAnywhere Director and SQL Server database connections:
If you have GoAnywhere Director projects that make connections to a SQL Server database, or are running GoAnywhere Director on a SQL Server database, then you will need to upgrade the SQL Server JDBC driver when you make the switch to JRE 1.6. Send a request to the Support team at Linoma Software (support@linomasoftware.com) to receive information on obtaining the JRE 1.6 compatible SQL Server JDBC driver, and follow the steps in this section to install the updated JDBC driver within GoAnywhere Director. Failure to do so will result in the following error message when making SQL Server database connections:

Code: Select all
Java Runtime Environment (JRE) version 1.6 is not supported by this driver. Use the sqljdbc4.jar class library, which provides support for JDBC 4.0.

If you are not making database connections to SQL Server, you do not need to perform these steps and the SQL Server JDBC driver will automatically be upgraded in the required release of GoAnywhere Director.

NOTE: The upgrade of GoAnywhere Director from 4.2.x to 4.3.0 will automatically handle the upgrading of the SQL Server JDBC driver (if required). Only if you are manually updating your JRE to 1.6 on a GoAnywhere Director version prior to 4.3.0 will you need to update the SQL JDBC driver manually.

Follow the directions below to update the SQL Server JDBC driver to a JRE 1.6 compatible version. Note that this update must be done at the same time GoAnywhere Director is updated to run on JRE 1.6. The new SQL Server JDBC driver is not compatible with JRE 1.5.

  1. Obtain the JRE 1.6 compatible SQL Server JDBC driver: sqljdbc4.jar. Contact Support at Linoma Software for more information.
  2. Shutdown GoAnywhere Director
  3. Navigate to the [INSTALL_DIR]/lib folder, where [INSTALL_DIR] is the installation directory of GoAnywhere Director.
  4. Delete the existing driver file: sqljdbc.jar. You may also move it to a folder outside the GoAnywhere Director installation directory, but note that simply renaming the file in the same directory will not be sufficient. It MUST be removed from this folder.
  5. Move the compatible JDBC driver (sqljdbc4.jar) into this folder.
  6. Start GoAnywhere Director (once it is configured to run on JRE 1.6) and test the database connection to ensure the connection is working properly.

Below is a compatibility matrix for the SQL Server JDBC driver and the JRE versions they support.

Driver and JRE compatibility
JRE 1.5 - sqljdbc.jar
JRE 1.6 - sqljdbc4.jar
JRE 1.7 - sqljdbc4.jar

GoAnywhere Director 4.2.x and under - NVARCHAR and NCHAR data types
If you are updating GoAnywhere Director 4.2.x or below to JRE 1.6, and you have project that work with SQL Server tables containing NVARCHAR and NCHAR data types, your queries may run into failures after making the JRE switch. This section does not apply to GoAnywhere Services.

Cause
In JRE 1.5 with JDBC 3.0, NVARCHAR and NCHAR data types were not supported and the type returned from the JDBC driver was simply VARCHAR and CHAR. In the later JDBC 4.0 version, the new data types were added. This is the reason for requiring the new sqljdbc4.jar driver file for SQL Server when running on JRE 1.6.

Options
  1. You can workaround these issues by explicitly selecting the VARCHAR data type on all columns that working with NVARCHAR and NCHAR fields in your GoAnywhere Director projects.
  2. If you do not want to update your projects, or are concerned you may run into these issues, you can upgrade to GoAnywhere Director 4.3.0 which adds support for these data types and requires JRE 1.6.
Support_Mary
Support Specialist
 
Posts: 9
Joined: Tue Feb 09, 2010 11:16 am

Return to Knowledge Center

Who is online

Users browsing this forum: No registered users and 0 guests

cron