Overview#

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

Name	Scope	Type	Description
dirxml.auto.localserverdn	driver	string	LDAP format DN of the current server (IDM 4+)
dirxml.auto.driverdn	driver	string	Slash format DN of the current driver
dirxml.auto.driverguid	driver	string	GUID of the current driver
dirxml.auto.treename	driver	string	Tree name of the local eDirectory instance
fromNDS	policy	boolean	true if the source datastore is eDirectory false if the source datastore is the connected application
destQueryProcessor	policy	java object	Instance of XdsQueryProcessor used to query the destination datastore
srcQueryProcessor	policy	java object	Instance of XdsQueryProcessor used to query the destination datastore
destCommandProcessor	policy	java object	Instance of XdsCommandProcessor used to query the destination datastore
srcCommandProcessor	policy	java object	Instance of XdsCommandProcessor used to query the destination datastore
dnConverter	policy	java object	Instance of DNConverter
current-node	policy	node-set	The loop variable for each iteration of <do-for-each>
current-value	policy	node-set	The loop variable for each iteration of <do-reformat-op-attr>
current-op	policy	node-set	The 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:

• Detect Status message and Send Email
• Driver Scope