Driven Administrator Guide: Starting and Stopping the Driven Server

version 2.2.6

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