Overview

When a new version of Evanios is released, customers are urged to upgrade to the latest version. The upgrade process is the same for Evanios Operations, Evanios Monitoring, or any Integration Package. In this article, you’ll learn how to install Evanios updates and how to update the Agent JAR files.
Most of this upgrade process requires Admin rights on the ServiceNow instance.

Installing the Update Set

Determining the Current Evanios Version

Before starting the upgrade process, it is important to be familiar with which version of Evanios is currently installed.


For Evanios Operations

  1. Navigate to Evanios Operations > Administration > Properties
  2. Check the field labeled Version of Evanios Operations (do not change)

For Evanios Monitoring

  1. Navigate to Evanios Monitoring > Administration > Properties
  2. Check the field labeled Version of Evanios Operations (do not change)

Downloading the Update Sets

Navigate to the Downloads page and download the update sets that will be required to upgrade to the newest Evanios release and unzip them. The following file is included in each zip file:

  • ServiceNow Update Set: <Evanios Application> – <release_name> – <release-type> <release_date>.xml
  • Example: Operations – Charlotte- Upgrade 01.22.2018.xml

The version of Evanios which is currently installed will determine which update sets you will need to download and install to upgrade to the latest Evanios release. Releases must be installed sequentially and can not be skipped. For example, if upgrading from Adelaide R1 to Charlotte, you will need to install the following update sets sequentially:

  1. Adelaide R2
  2. Barcelona Upgrade
  3. Barcelona R1
  4. Charlotte Upgrade

For a list of all Evanios Operations upgrade paths, check out the Evanios Operations Upgrade Path article.

Installing the Update Sets

  1. Log in to ServiceNow with an Admin account.
  2. Navigate to Retrieved Update Sets.
  3. At the bottom of the list, select Import Update Set from XML.
  4. Click Browse and select the unzipped update set that was downloaded from the Evanios web site.
  5. Once selected, click Upload and wait for the upload to finish.
  6. Select the uploaded update set from the list.
  7. Click Preview Update Set.
    • Note: If the Preview Update Set button is not available or you get a pop-up saying not allowed on this record, make sure your Domain is set to global.
  8. Once the preview has completed, select Commit Update Set.
  9. Repeat steps 2 – 8 until you have upgraded to the latest version.

NOTE: It is critically important that each version is loaded, previewed, and committed in order. Loading a newer update set before an older update set has been committed will result in a preview error.

For example, if upgrading from Adelaide R1 to Charlotte R1, the installation workflow would be as follows:

  1. Load the Adelaide R2 update set
  2. Preview the Adelaide R2 update set
  3. Commit the Adelaide R2 update set
  4. Load the Barcelona Upgrade update set
  5. Preview the Barcelona Upgrade update set
  6. Commit the Barcelona Upgrade update set
  7. Load the Barcelona R1 update set
  8. Preview the Barcelona R1 update set
  9. Commit the Barcelona Upgrade update set
  10. Load the Charlotte Upgrade update set
  11. Preview the Charlotte Upgrade update set
  12. Commit the Charlotte Upgrade update set
  13. Load the Charlotte R1 update set
  14. Preview the Charlotte R1 update set
  15. Commit the Charlotte R1 update set

Upgrading the Agent

When updating your Evanios release version, it’s important to also upgrade to the latest Evanios agent. This ensures that you can take advantage of the latest features and bug fixes. While older versions of the agent JAR may still work, they may produce errors and will not benefit from the newest Evanios Operations / Evanios Monitoring features.

Downloading the Agent

  1. Download the “EVA Consolidation Point for MID Server (multiplatform)” (file is evagent_<date>.zip) file from the Evanios download site.
  2. Unzip the JAR file.

The JAR file located on the Evanios download site will always be the most up-to-date JAR file.

Uploading the JAR to ServiceNow

After downloading and unpacking the JAR file, you will need to upload the JAR to ServiceNow.

  1. Navigate to MID Server > JAR files.
  2. Create a new JAR record.
  3. Fill out the record as in the example below. NoteSource MUST be Evanios; otherwise, it will not be available to select on the Agent Configuration page.
    • Name can be anything you would like. We suggest picking a naming convention and sticking with it.
    • Version can be anything you would like, but we suggest keeping the version here to make keeping track of versions currently uploaded easier.
    • Source MUST be Evanios. This ensures that the MID server choses the correct JAR attachment.
    • Description can be anything of your choice to help identify a particular agent record.
  4. To attach the JAR file, drag and drop the JAR file directly onto the ServiceNow record OR click the paper clip  in the top right-hand corner. Ensure that the name of the JAR file you are adding is unique and does not overwrite any other versions.
  5. Wait patiently for ServiceNow to finish uploading.
  6. Click Submit.

After the JAR record has been created and uploaded, the MID servers will download the JAR file from ServiceNow to the MID server directory. The MID servers may take some time to push out the file depending on the number of MID servers within the environment and their connection speed. To validate distribution, check the /extlib/ directory of the MID server to ensure that the file size of the JAR matches the file size of the JAR that was uploaded.


Please wait 15 minutes for the JAR file to be downloaded to the MID Server before continuing. You can use this time to check your emails, grab a coffee, or have a quick chat with Karen from finance. Once complete, the JAR file will be located in the /<MidServer>/extlib/ folder. You can validate that the upload has completed by confirming that the file size of the JAR file in the extlib folder matches the file size in your instance.

Configuring the Agents to use the updated Agent JAR

Once the MID server has downloaded the new agent JAR file, you can configure your agents to use the new JAR.

  1. Navigate to Evanios Operations > Integrations > Integration Agents.
  2. Select an agent.
  3. In the Related Links section, click Stop Agent.
  4. In the Agent Version field, click the lookup using a list icon Lookup using a list icon (magnifier) to find the new agent version that you created.
  5. In the Related Links section, click Start Agent.

If the Agent Status does not change to Started, this could indicate that there is a problem with the JAR file. This issue can occur when the MID server has not finished downloading the JAR file or, rarely, when the JAR file has been corrupted on transfer. Confirm that the JAR file size in the /<MidServer>/extlib/ directory matches the file size in the MID Server JAR files record. Once the MID server has the full JAR file, try restarting the agent again.