Deployment

Once a graph has been tested visually it is ready to be deployed in a lights-out or headless fashion.

Before deploying a graph, ensure that the graphhave the latest desired changes in the version that is selected to be deployed. This is important as each environment can only have one version deployed. An example would be if you decided to deploy Version One in Production environment, then all the deployable graphs following that deployment would need to be in Version One. 

Graphs can be deployed via the Admin screen for the project or via the Customer Journey Execution tab. Current deployments are found under the Deployments section of the project administration screen. 


The deployments tab will show all graphs in each Environment. In order to deploy a graph, the graph must have a valid listener node. A deployable graph is any valid graph that has a listener node. 

If a graph does not have a listener it will not be shown in the list. If the environment does not have valid connections then the Invalid Connections message will be shown when the  (deploy button) is clicked. The version of the graph that is deployed in the particular environment is the currently active version as selected from the Versions tab. 

If the listener graph is using the Kitewheel Graph API then the end point will be different for the chosen environment. This allows deployment to a higher production environment while development continues in the development environment.   

Starting and Stopping a Graph 

  •  The deploy button is used to start the graph. Graphs will continue to execute until the Halt button is pressed. 
     
  •  When the graph is running in the selected version and the Halt button is also shown. 


Multiple Listeners

By default, each graph will have the Listener status set to 1. You can set the listener count to multiple if you wish to speed up the processing for a Queue listener. It is important to make sure that the increase in listeners will be balanced with data processing needs. Kitewheel recommend that a max of 2 on the queue listener should be suitable in most circumstances. You do not need to set listener count for any other types of listener graphs as Kitewheel will automatically scale based off of the data processing volumes. It is also not advisable to increase the Listener count for Twitter and Database Listeners in case of any conflicting data override.

When you increase listener count in a version and then publish said version, the listener count will then be increased in that new version. The platform will remember the number of listeners you had set with that version.

Changing the number of listeners is an admin functionality. If you wish to change your permission, please contact a Kitewheel Support team. 

Deployment Alerts

Once the graph is deployed any execution problems will be emailed to contacts that have been added in the Contacts tab of the Project Admin screen. 


The email will come from no-reply@kitewheel.com and will have this format: 


From: Kitewheel <no-reply@kitewheel.com>

Subject: Kitewheel 2016 Deployment Event Alert

Date: January 18, 2017 at 1:10:50 AM EST

To: <Contact>

This is an automated email from Kitewheel.

There was a Deployment State Change, from: Running to Critical, for the graph detailed below.

<ERROR MESSAGE>

Deployment Details:

Graph Name: <Graph Name>

Version: <Version or Current>

Project: <Project Name>

Environment: <Environment Name>

Organization: <Organization Name>