Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added Events Service version information

...

You must upgrade manually if either of the two following conditions applyyou:

...

  • Do not use the Enterprise Console to deploy the Events Service

...

  • Upgrade Events Service nodes hosted on remote Windows machines

...

  • . The Enterprise Console does not support remote operations on Windows.

Before Upgrading

...

For on-premises deployments, 4.5.2 is the latest version of the Events Service. If you

...

upgrade to a version of the Events Service other than the latest, run the Enterprise Console installer for the desired Events Service version

...

Info

For SaaS deployments upgrading to Events Service version 4.5.3 or later,

...

 modify your data field

...

names to conform to the latest

...

requirements, as described here.

...

Before Upgrading

  1. Download and install the new Enterprise Console.
  2. Plan the order in which to upgrade platform components (not just Events Service).
  3. Modify the events-service-api-store.properties file.
    • Replace the absolute path APPLICATION_HOME property in the file with an actual path.
    • This is required because while performing a discover and upgrade job, the Enterprise Console is unable to migrate the data directory for custom environment variables in the file. Failure to modify the file causes the upgraded Events Service to start with a new, blank data set.
  4. Back up your events-service.vmoptions file.
    • This is required because the events-service.vmoptions file is not maintained when the Events Service is upgraded. After the upgrade completes, merge your backup copy of events-service.vmoptions into the new file.

...

  1. Run the upgrade Events Service command. 
  2.  Discover the Events Service nodes using the Enterprise Console.

...