After you have created a dedicated queue for prioritized execution of Transactions, Templates, or Process Flows, you need to create a corresponding runtime deployment that can subscribe to and process the messages of that Queue.
To create a runtime deployment, follow the instructions given below.
On the Account menu, click Maintenance.
In the left panel, select Deployments.
On the Deployments manage page, click Create Deployment.
In the Add Deployment window, enter the details in the following fields. Screenshot to be changed.
Field
Description
Name
A name for the deployment.
Description
A description for the deployment.
Minimum Pod
The minimum number of pods you want to start with.
Maximum Pod
The maximum number of pods you want to have in the deployment.
CPU Request
The minimum CPU cores you want to allocate to a pod in the deployment.
CPU Limit
The maximum CPU cores a pod in the deployment can use.
Memory Request
The minimum memory you want to allocate to a pod in the deployment.
Memory Limit
The maximum memory a pod in the deployment can use.
Concurrency
The maximum number of RabbitMQ messages that a pod can process at a time.
JVM Parameters
The JVM parameters you want to specify for a pod.
Message Count
The option to enable autoscaling based on the number of messages in Ready state in the queue.
This field is enabled only if you configure and deploy the application to use KEDA for autoscaling.
Message Count Threshold
The threshold value of the messages (in Ready state in the queue) at which you want the system to scale up/down a pod.
This field appears only when you select the Message Count checkbox.
CPU
The option to enable autoscaling based on the CPU utilization.
CPU Threshold
The threshold value (in percentage of CPU Request defined for the pods) at which you want the system to scale up/down a pod.
This field appears only when you select the CPU checkbox.
Memory
The option to enable autoscaling based on the memory utilization.
Memory Threshold
The threshold value (in percentage of Memory Request defined for the pods) at which you want the system to scale up/down a pod.
This field appears only when you select the Memory checkbox.
Click Save.
For default values for these fields, refer to the section Deployment Configuration on thepage Microservice Settings - Runtime.
Activating a deployment
A deployment that you have created can process the messages of a queue only when the deployment is active. You can activate a deployment by turning it ON on the Deployments manage page.
Prerequisite
Before you activate a deployment, you need to 15262394the deployment to a queue which is in active state.
It may take a while for the deployment to go into the active state.
Subscribing a deployment to a queue
To subscribe the deployment to an active queue, follow the steps given below.
Select the deployment that you want to view.
Click the icon under Actions column.
Click Subscribe Queue.
On the Subscribe Queue window, select the Queue you want the deployment to subscribe to, and click Save.
A deployment can subscribe to only one active queue at a time.
You can unsubscribe a deployment only when it is not in active state. To deactivate a deployment, go to the deployment on the Deployments manage page, and then use the OFF/ON toggle switch to turn it OFF. Deactivating the deployment terminates the associated runtime service and gives you the option for unsubscribing the deployment (More > Unsubscribe Queue).
Viewing a deployment
You can view an existing deployment by following the steps given below.
Select the deployment that you want to view.
Click the icon under Actions column.
Click View.
You'll be able to view all the details of the deployment.
You can also edit () or delete () a Deployment from the View window.
Editing a deployment
You can edit an existing deployment by following the steps given below.
Select the deployment that you want to edit.
Click the icon under Actions column.
Click Edit.
Edit the required fields.
Click Save.
Deleting a deployment
You can delete an existing deployment by following the steps given below.