Driven Administrator Guide: Upgrading Driven Server

version 2.2.6

Driven Administrator Guide: Upgrading Driven Server

1. Prerequisite: 1.1. Upgrading

1.2. Check your team’s demands and expectations

1.3. Check your hardware and software
2. Planning a Driven Deployment: 2.1. Understanding the Deployment Architecture

2.2. External Dependencies

2.3. Selecting a Deployment Topology
3. Installing and Configuring the Driven Server: 3.1. Downloading the Driven Server

3.2. Installing the Driven Server

3.3. Configuring the Driven Server
4. Starting and Stopping the Driven Server: 4.1. Starting the Driven Server

4.2. Stopping the Driven Server
5. Uninstalling the Driven Server: 5.1. Stopping the Server

5.2. Removing All Files and Data
6. Using the Driven Admin Features: 6.1. Manage Users

6.2. Managing A Single User

6.3. Manage Teams

6.4. Manage System
7. The Driven Command Line Client: 7.1. Installing the Driven CLI Client

7.2. Backing Up and Restoring Driven Repositories

7.3. Backing Up Your Driven Data

7.4. Extracting Data with the scope Command

7.5. Examples of Command Usage

7.6. Common Command-Line Options

7.7. How-To Tips
8. Integrating with Third-Party Monitoring Applications: 8.1. Using Java Management Extensions (JMX) with Driven

8.2. Using Nagios Plugins with Driven
9. Upgrading Driven Server: 9.1. Before WAR Replacement

9.2. Upgrade the Driven Server
10. Troubleshooting Driven: 10.1. The Driven Server installation generates a Java incompatibility error

10.2. Can not install a valid license

10.3. Transmission of application metrics data to Driven stops but app status remains in RUNNING state

Upgrading Driven Server

Most Driven upgrades can be accomplished with a WAR replacement.

However, if you are upgrading from versions 1.0.x or 1.1.x and wish to keep your existing data, you will need to perform a reindex to migrate your data to the current schema. Documentation on this procedure can be found in older documentation, but please consider contacting technical support for guidance. - Driven 1.1 > 1.2

Before WAR Replacement

Back up the data of your Driven deployment. See Backing Up and Restoring Driven Repositories. for more information.
For sites running a stand-alone Elasticsearch cluster: Check the version of your external Elasticsearch cluster. If not already running Elasticsearch 1.5.2, please upgrade your cluster to Elasticsearch version 1.5.2. Also, if required, upgrade Elasticsearch plugins to be compatible with version 1.5.2.

Upgrade the Driven Server

To upgrade the Driven Server, you need to replace the WAR file contents of your existing deployment with the contents of the 2.2 WAR file while the webserver is stopped.

After you have upgraded the server node(s), install version 2.2 of the Driven CLI Client.

Perform the following steps on each of your Driven server webserver nodes.

Step 1: Download the Driven Server WAR file

Download the WAR archive from http://files.concurrentinc.com/driven/2.2/driven-server/{drivenServerWar }
Alternatively, on UNIX, Linux, and Mac, run the following command:

$ wget -i http://files.concurrentinc.com/driven/2.2/driven-server/latest-war.txt

Step 2: Stop the webserver. Run the shutdown.sh script in the Driven installation directory:

$ cd ${INSTALL_DIR}
$ bin/shutdown.sh

Step 3: Remove the contents of the ${INSTALL_DIR}/webapps/ directory by running the following command:

$ rm -rf ${INSTALL_DIR}/webapps/*

Step 4: Copy the new WAR file to the ROOT context of the webserver webapps directory:

$ cp ${UPGRADE_WAR} ${INSTALL_DIR}/webapps/ROOT.war

Step 5: Ensure that the system user that will run Tomcat has execute and write permissions on the copied WAR file.

Step 6: Start the webserver. Run the startup.sh script in the Driven installation directory:

$ cd ${INSTALL_DIR}
$ bin/startup.sh

Step 7: Follow the steps in Driven CLI Client.