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 the Production environment, then all the deployable graphs following that deployment would need to be in Version One.
...
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 recommend 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 off of 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 said version, the listener count will then be increased in that new version.
...
| Note |
|---|
Changing the number of listeners is an admin functionality. If you wish to change your permission, please contact a Xponent Support team. |
...
| Anchor | ||||
|---|---|---|---|---|
|
The node-level timeouts allow us to track how often an execution or a deployed graph times out. If a deployment continuously times out:
The listeners set the graph to a critical state
Record the information
Pause the listening to avoid overwhelming resources
For example: The deployments tab will show the below critical listener error.
...
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.
...