4.0

Query parsing is performed by the plug-in that contains the objects you are looking for. The query language
used by the find operation is defined by the plug-in. Consequently, the syntax of the query parameter differs
according to the implementation of the plug-in. Most of the officially supported Orchestrator plug-ins do not
store any objects in the inventory, so they do not expose anything that can be searched for. Table 8-1 provides
the syntax and behavior for the query parameter for the officially supported Orchestrator plug-ins.
This table describes the find operationquery parameter syntax for each of the supported Orchestrator plug-
ins.
Table 8-1. Query Syntax of the Orchestrator Plug-Ins
Orchestrator Plug-In Query Parameter Syntax Query Behavior
Database (for example Lifecycle
Manager)
String Searches for object names in SQL
database tables. that Orchestrator sets
the search String in an SQL WHERE
keyword search. It searches the primary
keys, then the object IDs in the database.
Enumeration Not applicable The enumeration plug-in stores nothing
in the inventory. You can find
enumerations on each data type that
contains enumeration types.
Jakarta common set Not applicable The Jakarta plug-in stores nothing in the
inventory.
JDBC Not applicable The JDBC plug-in stores nothing in the
inventory.
Library Not applicable The library plug-in stores nothing in the
inventory.
Mail Not applicable The mail plug-in stores nothing in the
inventory.
SSH If you have configured Orchestrator to
use SSH connections, you can make
queries SSH commands.
The SSH plug-in stores nothing in the
inventory.
VMware Infrastructure 3.5 String or null Ignores the query string and returns all
objects of the specified type.
vCenter Server 4.0 String or null Ignores the query string and returns all
objects of the specified type.
XML Not applicable The XML plug-in stores nothing in the
inventory.
When you develop plug-ins, you can define a query language to use find to search for named objects through
the custom plug-in. This definition is not mandatory. The syntax of the query parameter is entirely dependent
on the query language that the plug-in implements. To avoid defining a query language, make find return all
objects, as in the case of the VMware Infrastructure plug-ins.
The size of the array of objects that the QueryResult returns depends on the definition of the plug-in through
which you make the query. For the queries you make through the standard Orchestrator plug-ins, the array
contains an unlimited number of FinderResult objects. Developers of third-party plug-ins, however, can set a
limit on the number of results the query returns. In these cases, if the value of totalCount exceeds the number
of objects in the array of FinderResult objects, the array does not include all the objects found in the queried
inventory. The totalCount property does report the total number of FinderResult objects found. The
totalCount property can be negative, which signifies that the plug-in cannot determine how many
corresponding objects are in the plug-in.
vCenter Orchestrator Developer's Guide
270 VMware, Inc.