Installation Guide for Driven Server

If you haven’t already, download the Driven Server installation package (Driven Server including Tomcat web server and Elastic Search server):

Next, unzip the download into your installation directory (referred later as ${dir})

The "Teams" feature for Driven lets you collaborate your application-development activities with other members. To use the team feature and have the Driven server to send notifications to new members, we first have to configure the SMTP properties which are stored in ${dir}/conf/driven.properties.

Start the server: Driven server includes Apache Tomcat with the Driven .war file packaged as the default context. The server will startup on port 8080. Driven applications data is written to ${dir}/driven and logs are written to ${dir}/logs.

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

After starting the server, inspect ./logs/server.log to ensure that there were no errors in starting the server. When the server starts, if there is no data, it initiates storage and creates a default admin user. The username/password is logged in the $DIR/logs/server.log.

$ tail -f logs/server.log

NOTE: The server UI listens on 8080. The CLI listens on 9200. Clustering is negotiated on port 9300
So in order for Driven server to be accessible from another machine, make sure that port 8080 is open
on the machine where Driven server is installed.

From the browser, go to the Driven login, which is the URL you registered with property driven.http.url in the file driven.properties. Ensure that you can login with the following credentials: username: admin, password: admin. Upon successful authentication, you will be asked to change your password.

You should have received a license when registering. After starting the server go to http://<hostname>:8080. You will be presented with a form to enter the text of the license.

Once you log in, click on the user icon in the top right corner of the landing page, and select Team list. Note the key associated with the team name default. You will need it later.

Stop the server:

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

Remove the installation directory: rm -rf ${dir}