Users Guide

API for ASM vRO Integration

The ASM vRO Integration includes a package with useful elements such as the actions, workflows, and

inventory. The ASM vRO Integration is operated through the ASM plugin API. The API includes the SDK

module, types, objects, and their methods. The types are used for representing the API objects into the

inventory or finder view. The API objects contain attributes and methods that are useful for automating

procedures which require ASM operations. For more information, see the chapter-Workflows and

Actions. You can also see the description of the types, objects, attributes, and methods from the API

Explorer.

API Types

The API types provide mapping of the API objects to the finder objects. In scripting, API types are also

used to define the type of required input, output, and attribute.

ASM — ASM PLUG IN:

• Scripting object: FinderResult

• An abstract type, FinderResult, is a top-level vRO type that is used to define an object as an inventory.

This type is used for the root level inventory object of the ASM vRO Integration.

ASM — Appliance:

• Scripting object: ASMAppliance

• This type is mapped to ASMAppliance, which is responsible for storing ASM appliance configurations

and making REST API calls. The FinderResult object of this type is a child object of the

ASM:ASM_PLUGIN type object. It also contains the child objects of the ASM:ServiceFolder type and

the ASM:TemplateFolder type. See ASMAppliance for detail.

ASM — Service:

• Scripting object: Service

• This type is mapped to Service class. This object is a child object of the ASM:ServiceFolder type object

in the finder. It also contains child objects of the ASM:ServiceComponent type. See Service for detail.

ASM — ServiceComponent:

• Scripting object: ServiceComponent

• This type is mapped to ServiceComponent. The object of this type has the ASM:Service type object as

the parent in finder. See ServiceComponent for detail.

ASM — ServiceFolder:

• Scripting object: ServiceFolder