Table of Contents

Driven Administrator Guide

version 1.2

Starting the Driven Server

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

Driven application data is written to ${DIR}/driven by default, and logs are written to ${DIR}/logs (${DIR} = Driven installation path).

Launching and Testing the Driven Server

Step 1: Start the Driven Server

Run the script in the Driven installation directory:

$ cd ${DIR}
$ bin/

Step 2: Inspect the log file for startup errors

After starting the Driven Server, inspect the ${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.

The Driven Server UI listens on port 8080.

Step 3: Enter Driven license information

After the Driven Server starts up, open http://_hostname_: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://_hostname_: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.

Step 6 (Optional): Record the API key

If you want to enable team-sharing of information in Driven, record the API key that appears on the My Teams page. You can use the download icon (copy-download-icon) by the API key to copy it to your clipboard. You will enter the key when you configure the Driven Plugin.


Congratulations! Your Driven Server installation is now configured and ready to go. But before Driven can render data about Cascading applications in the graphical user interface, the Driven Plugin for the must be set up. (If you used the beta version of the Driven Plugin, ensure that you use the licensed version for the self-hosted deployment.) See Installing and Configuring the Driven Plugin.

If the plugin is already installed and configured, then proceed to Installing the Driven CLI Client.