
Noun Tokens
339
no
vd
ocx
(e
n)
13
Ma
y 20
09
Query
Queries the source or destination data store and returns the resulting instances.
Fields
Datastore
Specify the data store to query.
Scope
Select the scope of the query. The options are entry, subordinates, or subtree.
Max Result Count
Specify the maximum number of results returned from the query.
Class Name
Specify the class name in the query. If a class name is not specified, all classes are searched.
Supports variable expansion. For more information, see
Section 3.6, “Variable Selector,” on
page 35
.
Select Object
Specify the base of the query. It can be the DN or an association. If neither is selected, the query
starts at the root of the datastore.
Match Attributes
Select the attributes to search for.
IMPORTANT:
To improve performance when using the query noun, create an index for the
attributes that you are going to use when querying the Identity Vault. For more information
about indexes, see the
Novell eDirectory 8.8 Administration Guide (http://www.novell.com/
documentation/edir88/edir88/index.html?page=/documentation/edir88/edir88/data/
a5tuuu5.html)
.
Strings
Specify the set of attributes to return. If nothing is specified, no attributes are read. Use an
asterisk to read all attributes.
Remarks
The Query token returns a
node set
containing the instance elements found as a result of the query.
To effectively use the results of a Query token it must be used in a context that is expecting a
node
set
. For example, you could assign the result to a variable of type
node set
, or iterate through the
result using a
for each
loop.
Treating the
node set
as if it were a
string
seldom provides anything useful. Extracting useful
information from the
node set
or its constituent instance elements requires the use of an XPath
expression and knowledge of the structure of an instance element. For additional information, see
the following:
“
instance
” in the
Identity Manager 3.6 DTD Reference
.
Summary of Contents for Designer for Identity Manager 3.5
Page 4: ...4 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 20: ...20 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 44: ...44 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 76: ...76 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 92: ...92 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 108: ...108 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 144: ...144 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 174: ...174 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 188: ...188 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 223: ...Conditions 223 novdocx en 13 May 2009...
Page 231: ...Conditions 231 novdocx en 13 May 2009...
Page 232: ...232 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 237: ...Actions 237 novdocx en 13 May 2009...
Page 245: ...Actions 245 novdocx en 13 May 2009...
Page 247: ...Actions 247 novdocx en 13 May 2009...
Page 263: ...Actions 263 novdocx en 13 May 2009...
Page 271: ...Actions 271 novdocx en 13 May 2009...
Page 275: ...Actions 275 novdocx en 13 May 2009 Example...
Page 324: ...324 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 333: ...Noun Tokens 333 novdocx en 13 May 2009...
Page 357: ...Verb Tokens 357 novdocx en 13 May 2009...
Page 363: ...Verb Tokens 363 novdocx en 13 May 2009 Example...
Page 390: ...390 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 418: ...418 Policies in Designer 3 5 novdocx en 13 May 2009...
Page 474: ...474 Policies in Designer 3 5 novdocx en 13 May 2009...