7.4

Table Of Contents
Table 15. Workflow Subscription and Event Broker Terminology (Continued)
Term Description
Message Transports information about the event between the various
services and components. For example, from the producer to
the event broker service, or from the event broker service to the
subscribers.
Event Broker Service The service that dispatches messages that are published by a
producer to the subscribed consumers.
Payload The event data.
Subscription Indicates that a subscriber is interested in being notified about
an event by subscribing to an event topic and defining the
criteria that triggers the notification.
Subscriber Consumes the events published to the event broker service
based on the subscription definition. The subscriber might also
be referred to as the consumer.
Provider Registers event topics in the event broker service.
Producer Publishes events to the event broker service.
System Administrator A user with privileges to create, read, update, and delete tenant
workflow subscriptions and system workflow subscriptions using
the API or vRealize Automation plug-in. vRealize Automation
does not include a user interface for the system administrator.
Tenant Administrator The user with privileges to create, read, update, and delete
tenant workflow subscriptions for their tenant.
Workflow Subscription Specifies the event topic and conditions that trigger a
vRealize Orchestrator workflow.
System Workflow Subscription A specialized workflow subscription that reacts to system events
and to events in all the tenants.
Tenant Workflow Subscription A specialized workflow subscription that specifies which
conditions trigger a vRealize Orchestrator workflow for events in
the same tenant.
Blockable and Replyable Event Topics
Event topics might support blockable and replyable events. The behavior of a workflow subscription
depends on whether the topic supports these event types and how you configure the workflow
subscription.
Non-Blockable Event Topics
Non-blockable event topics only allow you to create non-blocking subscriptions. Non-blocking
subscriptions are triggered asynchronously and you can not rely on the order that the subscriptions are
triggered or that the vRealize Orchestrator workflows run. Non-blocking subscriptions only return a
response if the topic is replyable.
Life Cycle Extensibility
VMware, Inc. 15