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 graphs have 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 a Production environment, then all the deployable graphs following that deployment would need to be in Version One. 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 graph's version deployed in the particular environment is the currently active version, as selected from the Versions tab. 

If the listener graph is using the Xponent Graph API, then the endpoint 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.

Deploying the Graph

While deploying a graph, if any connections are missing from the version you are trying to deploy, a pop-up will prompt you to fill in those details before proceeding with the deployment. 

Additionally, the application will create blank connection for you. All versions of a project will utilize the current connection details. Remember, Deployment will not proceed until the credentials are filled.

Redeploy the Graph 

If the graphs had already been deployed before the Single Source of Truth launch into production which is not available in the Engine but not in the Hub’s database. 

This status allows the user to stop the graph, which removes the graph from the Engine database.

Also, it allows the user to redeploy the graph, which adds the same record to the Hub's and Engine's database. A graph that is in the Redeploy Recommended state will remain in the same state until the user stops the graph.

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. Xponent recommends 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 Xponent will automatically scale based on 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 the listener count in a version and then publish the 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.

Deployment Alerts

After deployment, any state change in the graph triggers an email notification to contacts listed in the Contacts tab of the Project Admin screen. However, these notifications are sent only after a delay of 5 minutes and under the following conditions:

• Transition from "Running" to "Critical".
• Transition from "Critical" to "Running".

In case of a failed deployment, the system attempts to restart it twice. If the deployment remains unsuccessful, it stays in the "Critical" status until it has been running smoothly for at least 5 minutes. The current deployment status of the graph is also visible on the organization-level dashboard.

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