View Source

For most of the available Namespaces and Variables you can use a config.xml file as a starting point (you can find this file in the MarvelClient Working Directory) – typically it is sufficient to look at the config.xml of one or two machines to get a hang of which Namespaces and Variable names can be used. There are usually only differences between major MarvelClient (2/3/4), Notes releases (7/8 for example) and platforms (Windows/Mac/Linux).

Above screenshot shows using a Reference to generically configure the target directory field of a backup action to point to each user’s “<notes:client_directory>” (not a good idea, by the way ;-)).
Looking at a sample MarvelClient config.xml shows that this would be resolved to “C:\Lotus\Notes\Client” on the client from which the config.xml was opened:

MarvelClient provides over 150 different IBM Notes Client and operating system details in the notes: and os: namespaces, all of which can be referenced. This allows for flexible rule sets to be compiled without any programming.
The following table lists the most important Namespaces:

Namespaces for MarvelClient References
notes	IBM Notes client details; <notes> … </notes> in config.xml
ini	References a notes.ini entry; available variable names and values depend on the respective target user's notes.ini
os	Operating system details; <os> ... </os> in config.xml
env	References an operating system environment variable; available variables names and values depend on the respective target user's operating system environment. (on Windows, think launching cmd.exe and entering the "set" command)
filesystem	Performs a real-time query for disk, directory or file properties (e.g. size, number of files, and similar)
user	This Namespace is meant for your own variables, allowing you to freely write your own variables into this namespace: Example: using a "*.ini & Variables" Action to set "user:replica_type" to "stub".
Action_alias	Allows to reference results and variables of MarvelClient Actions; for example “<alias:replica_type>” allows to reference a Desktop Icon & Replica Action in order to query for whether a local replica exists for a given application.
mc	MarvelClient "System variables"; <mc> … </mc> in config.xml
mz	"System variables" for MarvelClient Zip/Unzip and Attachment blocking (formerly called MarvelZip); <mz> … </mz> in config.xml

When looking at a config.xml file, you will notice that more namespaces exist; they are usually not all too useful for creating Actions and Conditions, though.

The available Variable names from within the Namespaces mc, mz, os and notes can be derived from a representative config.xml (in each client’s Working Directory or in the Analyze database if so collected).

Note that the config.xml file is recreated upon every client start – after closing an IBM Notes Client, any therein stored variables are NOT read back ever.

NOTE that namespaces and variables are NOT write-protected. You must not change important system variables (e.g. notes:client_directory, mc:working_directory or similar).