A plug-in must conform to a standard file structure and must include certain specific folders and files. You deliver a plug-in as a standard Java archive (JAR) or ZIP file, that you must rename with the .dar extension.

The contents of the DAR archive must use the following folder structure and naming conventions.

Table 1. Structure of the DAR Archive




Contains the vso.xml file that defines the mapping of the objects in the plugged-in technology to Orchestrator objects.

The VSO-INF folder and the vso.xml file are mandatory.


Contains the JAR files that contain the binaries of the plugged-in technology. Also contains JAR files that contain the implementations of the adapter, factory, notification handlers, and other interfaces in the plug-in.

The lib folder and JAR files are mandatory.


Contains resource files that the plug-in requires. The resources folder can include the following types of element:

  • Image files, to represent the objects of the plug-in in the Orchestrator Inventory tab.

  • Scripts, to define initialization behavior when the plug-in starts.

  • Orchestrator packages, that can contain custom workflows, actions, and other resources that interact with the objects that you access by using the plug-in.

You can organize resources in subfolders. For example, resources\images\, resources\scripts\, or resources\packages\.

The resources folder is optional.

You use the Orchestrator Control Center to import a DAR file to the Orchestrator server.