Driven Administration Guide

version 1.1.1

Installing the Driven Server

Note

If you plan to keep your data perform the migration process from Driven 1.0 to Driven 1.1. If you do not want to keep your existing data, then perform the upgrade without the migration steps. Refer to the Driven Migration Cookbook for information on upgrade and migration of your data. It is highly recommended that you contact Concurrent Technical Support before performing the migration process.

This section explains how to get started with installing the Driven server. It is highly recommended that you set aside atleast one dedicated machine for the Driven server installation.

Download and Install the Driven Server

Step 1: Download the Driven server installation package

If you have not already, download the Driven Server installation package, which includes Apache Tomcat web server and Elasticsearch server.

$ wget -i http://files.concurrentinc.com/driven/1.1/driven-server/latest-tomcat.txt

Step 2: Unzip the Driven installation package

Download the installation package into your installation directory, which will later be referred as ${DIR}.

$ unzip driven-tomcat-<version>.zip
$ cd driven-tomcat-<version>

Configuring the Driven Server

The Driven server configuration file is ${DIR}/conf/driven.properties.

Step 1: Choose a data location

By default, data is written to ${DIR}/driven. Otherwise, choose an appropriate location.

driven.storage.data.path=_DATA_LOCATION_

Step 2: Configure the SMTP properties to enable the Team feature in Driven

The Teams feature of Driven lets you collaborate with other members. To use this feature along with having the Driven server send notifications to new members, you need to configure the SMTP properties.

driven.smtp.enabled=true
driven.smtp.host=
driven.smtp.port=
driven.smtp.tls=
driven.smtp.username=
driven.smtp.password=
driven.smtp.from=

Configure Driven with its external URL in order for emails to contain the correct links.

driven.http.url=http://<hostname>:<port>

Start the Driven Server

The Driven Server includes Apache Tomcat with the Driven .war file packaged as the default context. The Driven server starts up on port 8080.

Driven applications data is written to ${DIR}/driven and logs are written to ${DIR}/logs.

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

Step 1: Inspect the log file for startup errors

After starting the Driven Server, inspect ${DIR}/logs/server.log 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. The username/password is logged in ${DIR}/logs/server.log.

INFO EntityManager | initialized admin account:admin/*****. Please login and change the admin password.

Note	The Driven server UI listens on port 8080. The Driven Scope listens on port 9200. Clustering is negotiated on port 9300. In order for the Driven Server to be accessible from another machine, make sure that port 8080 is open on the machine where Driven server is installed.

Step 2: Enter License information

You should have received a license when registering. After starting the server go to http://<hostname>:8080. There you will be presented with a form to enter license information needed to complete the Driven server installation.

Step 3: Authenticate your login credentials

From a web browser, go to the Driven login:

http://<hostname>:8080

Make sure that you can login with the following credentials: username: admin , password: admin. The password must be changed on the first login.

Step 4: Test the Driven Landing Page

Once you have logged in, click the user icon at the top right corner of the landing page. Select the Team list. Note the key associated with the team name default. You will need this key at a later time.

Congratulations! Your Driven server installation is now configured and ready to go.

Stopping the Driven Server

To stop the Driven server, perform the following:

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

Uninstalling the Driven Server

To uninstall the Driven server, perform the following steps:

Step 1: Stop the server

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

Step 2: Remove the installation directory

$ rm -rf ${DIR}

Installing Driven Plugin

Before you can start visualizing your Cascading applications, don’t forget to install the Driven Plugin