5.5.1

The objects searched for can also be identified by ID or by relation using the findForId and findRelation
operations, as the following example shows.
public FinderResult findForId(String type, String id, String username, String password);
public FinderResult[] findRelation(String parentType, String parentId, String relation, String
username, String password);
NOTE FinderResult is not an Orchestrator scriptable object.
The following table shows the properties of the FinderResult object.
Type Value Description
String
type
Type of object found.
String
id
ID of the discovered object.
Array of properties
properties
A list of the discovered object's
properties.
The format of the properties values
is defined by each plug-in in its
vso.xml file, under the FinderResult
description.
String
dunesUri
A string representation of the object.
If a FinderResult object is accessed
through a plug-in, it is identified by a
dunesUri string, rather than by
another type of string or ID. The
format of the dunesUri is as follows.
dunes://service.dunes.ch/Custom
SDKObject?id='<object_ID>'
&dunesName='<plug-
in_name>:<object_type>'
ModuleInfo Object
ModuleInfo stores the name, version, description, and display name attributes for each plug-in. A Web
service application can use these attributes to modify its behavior based on the presence or absence of
certain plug-ins or plug-in versions.
The getAllPlugins operation returns arrays of ModuleInfo objects to list all the plug-ins a user can access, as
the following example shows.
public ModuleInfo[] getAllPlugins(username, password);
The following table shows the properties of the ModuleInfo object.
Type Value Description
String
moduleName
Name of the plug-in, used as a prefix
in object names.
String
moduleVersion
Plug-in version.
String
moduleDescription
Description of the plug-in.
String
moduleDisplayName
Plug-in name shown in the
Orchestrator inventory.
Developing a Web Services Client for VMware vCenter Orchestrator
70 VMware, Inc.