Deployment Guide
• This type is mapped to ServiceFolder. The type and class both provide nothing much other than the
inventory structure and hierarchy. The object of this type has the ASM:Appliance type object as its
parent while having child objects of the ASM:Service type objects. See ServiceFolder for detail.
ASM — Template:
• Scripting object: Template
• This type is mapped to Template. In finder view, the objects of this type is structured under the
ASM:TemplateFolder type object. See Template for additional information.
ASM — TemplateFolder:
• Scripting object: TemplateFolder
• This type is mapped to TemplateFolder. The type and class both provide nothing much other than the
inventory structure and hierarchy. The inventory object of this type has the ASM:Appliance type object
as its parent while its child objects are of the ASM:Template type. See TemplateFolder for detail.
API Objects
There are eight API objects that are included in the ASM SDK module. This section covers each object and
the associated attributes and methods.
ASMAppliance
This object establishes HTTPS connection to the ASM REST webservice in order to make the requests.
This is the most crucial object for the Integration.
Attributes:
• id (java.util.UUID): Identifier issued by the vRO Integration, which is used to track the ASM Appliance
for internal operations
• name (String): User-given name of the ASM appliance
• serverUrl (String): URL of the ASM Appliance
• sslTrustAllCerts (boolean): Indicates if the SSL trust is enabled or disabled.
Methods:
• addDuplicateServer: This method clones server(s) from the configuration of an existing server
component. It duplicates servers which have the same relations to other resources (For example:
Duplicated servers will be added to the cluster where original server belongs to). Server pool must be
able to allocate physical server resources for the chosen configuration.
– deployment – Target Service where new server component(s) are added.
– targetServer – ServiceComponent of server type that provides the configuration for the duplicate
server(s).
– newServerName – Name of the new server(s); if more than one instance of servers are requested,
sequence number is appended to the name.
– numInstances – Specifies the number of server instance(s) that will be added to the Service.
• addDuplicateStorage: This method clones storage(s) from the configuration of an existing storage
component. Duplicated storages have the same relations to other resources (For example: Duplicated
12