Upgrading to v8.x

Every effort has been made so that upgrading to v8 is a seamless and painless as possible. There are however a few caveats that should be taken into account depending on the starting version that you are upgrading from.

The following summarises the differences between v6, v7 and v8:

• In both v7 and v8, Security is enabled by default. In v6, security is disabled by default.

• In v8 it is mandatory to configure an admin user for the API. In v7 it was optional and in v6 the API didn't exist.

• In v7.1.0, the jGroup libraries where upgraded, which means managers running versions prior to 7.1.0 will not communicate with managers running 7.1.0 or later (including 8+)

• v8, like v7 enables full security by default, so the disable-security-controls flag will default to false when not specified.

  In addition this property also enables encrypted communication to the database. Setting this value to false, or leaving omitted, translates to the following settings being applied:

  file-protection-level=0027
  rmi-ssl=true
  thl-ssl=true
  rmi-authentication=true
  jgroups-ssl=true
  datasource-enable-ssl=true
  connector-ssl=true

If you are running v6 and wish to upgrade to v7, then you should follow the steps in the v7 upgrade documentation, see "Upgrading to v7.x"

If you are upgrading from v6 directly to v8, you should step through all of the sections of this upgrade document, taking note of specific steps and decisions to be made along the way with regards to security.

If you are upgrading from v7 and do not wish to make any changes to your configuration you should go straight to "Steps to upgrade using tpm"