Cisco Cisco Process Orchestrator 3.0 Guida Utente

AMQP is the emerging standard for messaging and events in the cloud. For example:

vCloud Director can publish vCloud Messages, also known as “blocking tasks,” “notifications,” or 
“call-outs,” related to different provisioning. An orchestrator can not only receive these events, but 
can also respond to them to delay execution. 

AMQP is supported with vCloud Orchestrator. 

OpenStack selected AMQP as the messaging technology for OpenStack.

AMQP is integrated with more than 70 developer platforms, providing a nice framework for 
event-oriented integrations.

AMQP enables event-driven capabilities of Enterprise Service Bus-style designs. It enables queuing, so 
automation can fetch messages when there is capacity. You can use asynchronous methods servicing 
requests as capacity allows when possible, and reserve real-time, synchronous methods only when 
absolutely needed. AMQP’s open platform is a natural choice for event and message design patterns

Process Orchestrator can trigger processes in response to messages placed on AMQP queues/exchanges. 
Processes can also read messages from queues/exchanges one at a time if they want to respond to 
messages one at a time rather than in parallel, to operate more as a queue. Processes can submit messages 
to queues/exchanges.

JMS is another possible integration enabled through AMQP. AMQP has providers to place JMS 
messages on queues/exchanges.

The following diagram shows the major functional elements of the Process Orchestrator system. These 
elements are discussed in the sections that follow.