Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

There is currently no support for upgrading an older Gateway to its latest release. However, for easing the migration, it is possible to configure an existing Gateway to connect to our Bologna Data Centre. This can be achieved by editing your "gateway/conf/ecmwf.properties" configuration file and apply the following changes:

Configure the Gateway to connect to our Data Center in Bologna:

[Login]
ecaccessServer=boaccess.ecmwf.int

Comment out the "telnet" plugin to deactivate it:

[PluginList]
#telnet=...

Force the TLS version 1.2 protocol:
[Security]
SSLVersion=TLSv1.2

Comment out the "cipherSuites" to allow TLS cipher negotiation:
[ProxySocket]
#cipherSuites=...

This page describe the procedure which allow to upgrade an existing ECaccess Gateway on the same platform. If you wish to install a new ECaccess Gateway on a new platform then please install the ECaccess Gateway from scratch on the new platform and then follow the procedure described in ECtrans Associations Export - Import to migrate the ECtrans Association from the existing Gateway to the new Gateway.

Before to follow the procedure, please first download the upgrade script.

Please note this script will only work if you have a valid installation of Java 8 on your platform. Your existing Gateway might run with a different version of Java but Java 8 must be available on the platform as well. If this is the case then please enter the absolute path of the Java 8 binary file when prompted.

We are currently running the following version of Java for our local Gateways at ECMWF:

  • java version "1.8.0_60"
  • Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
  • Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)

Although it should work with any release of Java 8 please note we have only tested the Gateway with the release mentioned above.

This script will upgrade any Gateway from v2.0.1-v4.0.0 to v4.2.0. The configuration will be imported from the initial installation. It is a safe upgrade, the initial ECaccess installation is not altered and the start-up scripts are not modified (to be done manually). If this is required the script can also handle simultaneously a Java upgrade (the Database is converted and the script also deals with the Java keystore conversion).

To do the upgrade simply:

  • Copy this script to the "bin" directory of your existing Gateway (e.g. ecaccess-v<version>/gateway/bin).
  • Run this script as the UID under which the Gateway is running.

The new ECaccess Gateway will be installed in the parent directory of the existing Gateway (ecaccess-v4.2.0 will be at the same level as ecaccess-v<version>).

Once the update has been completed successfully, please update the following script with the absolute path for ECACCESS_HOME and the absolute path for your Java binary:

  • "ecaccess-v4.2.0/gateway/bin/gateway"

Then make a copy of this script in your "init.d" directory.

Please use your standard procedure to start the new ECaccess gateway, usually through:

#./gateway start

Also, refer to the Administrator's Manual for further details.

...