Provider and tenant administrators can create extensibility subscriptions to access vRealize Orchestrator workflows. vRealize Orchestrator workflows are triggered based on events if there is a subscription for some event topics which corresponds to a particular lifecycle phase of the application.
The characteristics of an extensibility subscription differ depending on whether the subscription was created by a provider administrator or a tenant administrator.
- The Tenant administrator can create a subscription but cannot specify organization scope. That subscription will be activated on events triggered by tenant only.
- The Provider administrator can create a subscription and specify provider scope. The subscription will behave just like tenant subscription or non multi-tenant environment. It will be activated based on events coming from the Provider.
- The Provider can create a subscription and specify the tenant scope. The subscription is activated based on events coming from any Tenant. It is not activated by events coming from Provider.
Subscriptions trigger vRealize Orchestrator workflows based on specific events. They do not invoke extensibility actions. Currently only a single vRealize Orchestrator instance is supported for any particular provider organization. For more information about events, event topics, and subscriptions see Extensibility terminology.
Prerequisites
Configure tenants and virtual private zones as appropriate for your deployment.
Procedure
Results
- If organization scope is Provider, then providers will see events based on their actions in same provider organization.
- If organization scope is Tenant, tenants will see the events, but the provider cannot see them. Events always live in the organization of the publisher.
- Select in Cloud Assembly.
- In the Events page Search box, enter the deployment ID for which you wish to view events.
The page displays events that match the search criteria.