7.2
Table Of Contents
- Foundations and Concepts
- Contents
- Foundations and Concepts
- Updated Information
- Using Scenarios
- Using the Goal Navigator
- Introducing vRealize Automation
- Tenancy and User Roles
- Service Catalog
- Infrastructure as a Service
- XaaS Blueprints and Resource Actions
- Common Components
- Life Cycle Extensibility
- vRealize Automation Extensibility Options
- Leveraging Existing and Future Infrastructure
- Configuring Business-Relevant Services
- Extending vRealize Automation with Event-Based Workflows
- Integrating with Third-Party Management Systems
- Adding New IT Services and Creating New Actions
- Calling vRealize Automation Services from External Applications
- Distributed Execution
- Index
Calling vRealize Automation Services from External Applications
In some cases, organizations may want to interact with vRealize Automation programmatically rather than
via the vRealize Automation console.
For such scenarios, the vRealize Automation API provides a standardized, secured RESTful interface for
cloud access and interaction, controlled through business-aware policy for consumers such as users,
infrastructure, devices, and applications.
All blueprints, including the ones created via the XaaS, are automatically exposed through the
vRealize Automation API. For more details, see the vRealize Automation API Reference.
Distributed Execution
All core vRealize Automation workows are executed in a distributed execution environment.
The vRealize Automation runtime environment consists of one or more DEM Worker instances that can
execute any workow installed in the core engine. Additional Worker instances can be added as needed for
scalability, availability and distribution.
Skills can be used to associate DEMs and workows, restricting execution of a given workow to a
particular DEM or set of DEMs with matching skills. Any number and combination of skills can be
associated with a given workow or DEM. For example, workow execution can be restricted to a specic
datacenter, or to environments that support a specic API the workow requires. The vRealize Automation
Designer and the CloudUtil command-line tool provide facilities for mapping skills to DEMs and
workows.
For more information about distributed execution and working with skills, see Life Cycle Extensibility.
Foundations and Concepts
40 VMware, Inc.