Cisco Cisco Process Orchestrator 3.1 User Guide
13-5
Cisco Process Orchestrator 3.1 User Guide
Appendix 13 Using Adapters
Advance Message Queuing Protocol (AMQP) Adapter
Automating Cisco AMQP Tasks
Declaring an AMQP Exchange
Use the Declare Exchange activity to create or check an AMQP broker exchange.
Step 1
In the Process Editor Toolbox, choose AMQP > Declare AMQP Exchange, then drag and drop the
activity onto the Workflow pane.
activity onto the Workflow pane.
Step 2
Click the General tab and enter the required information.
Note
Exchange names must be unique within a virtual host.
Step 3
Click the Declare Exchange tab and specify the information that describes the exchange, including:
•
Type— type of exchange you want to declare (see
•
Durable—Durable exchanges last until they are deleted. Temporary exchanges last until the server
shuts-down. Not all scenarios and use cases require durable exchanges.
shuts-down. Not all scenarios and use cases require durable exchanges.
•
Auto delete—Auto-deleted exchanges last until they are no longer used.
•
Arguments—Enter the name and value pair arguments for the queue
Step 4
Enter the information in the remaining tabs as necessary, then click Save to complete the activity
definition.
definition.
Declaring an AMQP Queue
Use the Declare Queue activity to create or check a queue on the AMQP broker. This activity will create
a queue if the queue does not already exist.
a queue if the queue does not already exist.
When you declare a new queue, you can specify various properties that control the durability of the
queue and its contents and the level of sharing for the queue.
queue and its contents and the level of sharing for the queue.
Step 1
In the Process Editor Toolbox, choose AMQP > Declare AMQP Queue, then drag and drop the activity
onto the Workflow pane.
onto the Workflow pane.
Step 2
Click the General tab and enter the required information.
Note
Message queue names must be unique within a virtual host.
Step 3
Click the Declare Queue tab and specify the information that describes the queue, including:
•
Durable—Whether the queue is durable or transient. Durable queues survive broker restart whereas
transient queues do not (they must be redeclared when the broker comes back online). Not all
scenarios and use cases require durable queues.
transient queues do not (they must be redeclared when the broker comes back online). Not all
scenarios and use cases require durable queues.
•
Auto delete—Delete the queue when it is empty.
•
Exclusive—The queue belongs to the current connection only, and is deleted when the connection
closes.
closes.