You use the vso.xml file to map the objects, classes, methods, and attributes of the plugged-in technology to Orchestrator inventory objects, scripting types, scripting classes, scripting methods, and attributes. The vso.xml file also defines the configuration and start-up behavior of the plug-in.

The vso.xml file performs the following principal roles.

Start-Up and Configuration Behavior

Defines the manner in which the plug-in starts and locates any configuration implementations that the plug-in defines. Loads the plug-in adapter.

Inventory Objects

Defines the types of objects that the plug-in accesses in the plugged-in technology. The finder methods of the plug-in factory implementation locate instances of these objects and display them in the Orchestrator inventory.

Scripting Types

Adds scripting types to the Orchestrator JavaScript API to represent the different types of object in the inventory. You can use these scripting types as input parameters in workflows.

Scripting Classes

Adds classes to the Orchestrator JavaScript API that you can use in scripted elements in workflows, actions, policies, and so on.

Scripting Methods

Adds methods to the Orchestrator JavaScript API that you can use in scripted elements in workflows, actions, policies, and so on.

Scripting Attributes

Adds the attributes of the objects in the plugged-in technology to the Orchestrator JavaScript API that you can use in scripted elements in workflows, actions, policies, and so on.