Overview#

There are a number of global and local DirXML Variables that are automatically defined:

NameScopeTypeDescription
dirxml.auto.localserverdndriverstringLDAP format DN of the current server (IDM 4+)
dirxml.auto.driverdndriverstringSlash format DN of the current driver
dirxml.auto.driverguiddriverstringGUID of the current driver
dirxml.auto.treenamedriverstringTree name of the local eDirectory instance
fromNDSpolicybooleantrue if the source datastore is eDirectory false if the source datastore is the connected application
destQueryProcessorpolicyjava objectInstance of XdsQueryProcessor used to query the destination datastore
srcQueryProcessorpolicyjava objectInstance of XdsQueryProcessor used to query the destination datastore
destCommandProcessorpolicyjava objectInstance of XdsCommandProcessor used to query the destination datastore
srcCommandProcessorpolicyjava objectInstance of XdsCommandProcessor used to query the destination datastore
dnConverterpolicyjava objectInstance of DNConverter
current-nodepolicynode-setThe loop variable for each iteration of <do-for-each>
current-valuepolicynode-setThe loop variable for each iteration of <do-reformat-op-attr>
current-oppolicynode-setThe current operation. Setting this variable using <do-set-local-variable> causes the first operation specified by <arg-node-set> to become the current operation for the remainder of the current policy execution or until it is set to another value. The new current operation must be an element sibling of the original current operation and must have been added by the current policy.

More Information#

There might be more information for this subject on one of the following:

Add new attachment

Only authorized users are allowed to upload new attachments.
« This page (revision-5) was last changed on 31-Jul-2014 13:09 by jim