Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
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.
Image RemovedImage AddedField 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.
Info 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.
Info 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.
Info 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.
Info This field appears only when you select the Memory checkbox. Click Save.
Info For default values for these fields, refer to the section Deployment Configuration on the page Microservice Settings - Runtime.
Anchor | ||||
---|---|---|---|---|
|
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.
Warning | ||
---|---|---|
| ||
Before you activate a deployment, you need to subscribe the deployment to a queue which is in active state. |
It may take a while for the deployment to go into the active state.
Anchor | ||||
---|---|---|---|---|
|
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.
Anchor Deactivate Deactivate Click Subscribe Queue.
On the Subscribe Queue window, select the Queue you want the deployment to subscribe to, and click Save.
Info |
---|
|
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.
Info |
---|
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.
- Select the deployment that you want to delete.
- Click the icon under Actions column.
Click Delete.
Related topic
Panel | ||||
---|---|---|---|---|
| ||||
What is new |