Driven Administrator Guide: Starting and Stopping the Driven Server

version 2.2.6

Driven Administrator Guide: Starting and Stopping the 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

Starting and Stopping the Driven Server

Starting the Driven Server

The Tomcat distribution from Driven contains the Driven Server WAR file and starts up on port 8080 by default.

Driven application data is written to ${INSTALL_DIR}/driven by default, and logs are written to ${INSTALL_DIR}/logs.

Launching and Testing the Driven Server

Step 1: Start the Driven Server

Run the startup.sh script in the Driven installation directory:

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

Step 2: Inspect the log file for startup errors

After starting the Driven Server, inspect the ${INSTALL_DIR}/logs/server.log file to ensure that there are no startup errors. When the server starts and there is no data, it initiates storage and creates a default admin user account. Both the user name and the password for the default account is admin.

Note	The Driven Server UI listens on port 8080.

Step 3: Enter Driven license information

After the Driven Server starts up, open http://${HOST_NAME}:8080 to enter your license key if required. You should have received a license key when registering.

Step 4: Change your login credentials

Open http://${HOST_NAME}:8080 in a web browser. Log in with the default user account credentials (admin for both user name and password). When prompted to set a password, be sure to change it from admin.

Step 5: Test the Driven landing page

Once you have logged in, click the user icon at the top right corner of the landing page and select My Teams on the menu. You should see the team named Default. You can record the API key now to skip the task of retrieving the key when you are installing and configuring the Driven Plugin.

Stopping the Driven Server

Run the shutdown.sh script in the Driven installation directory:

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