Configuring MarvelClient on Nomad clients

MarvelClient does not require any manual configuration if there is a MarvelClient Config database at one of the default Domino paths, as is true in the majority of environments. However, in an environment where the MarvelClient Config DB is in a unique or custom location, administrators must use one of the following options to manually configure MarvelClient:

Mobile Device Management

MarvelClient can be configured by most MDM (Mobile Device Management) providers using the HCL Nomad App Config definition. The following settings are configurable by MDM:
  • Basic Configuration Settings
    • marvelClientConfigDB - Domino server name and path of MarvelClient Config DB. Specify the fully qualified server name or use %notes_homeserver% to specify the user's home mail server. For example, %notes_homeserver%!!panagenda\pmc_config.nsf
    • enableMarvelClient – MarvelClient is enabled by default. Set this variable to FALSE to disable MarvelClient on HCL Nomad for devices.
  • Advanced Configuration Settings
    • marvelClientConfigDBNotResolvable - Default MarvelClient Database to use if %notes_homeserver% is specified in marvelClientConfigDB field and can not be resolved. For example, myserver!!panagenda\pmc_config.nsf
    • marvelClientConfigDBUnavailable - MarvelClient Config Database to use if unable to connect to the database specified by marvelClientConfigDB or marvleClientConfigDBNotResolvable. For example, myAlternateServer!!panagenda\pmc_config.nsf

For more information on MDM, see Managing HCL Nomad via an MDM provider.

Desktop Policy

MarvelClient can be configured by setting notes.ini parameters via Desktop Policy Custom settings. Create a Desktop Policy with the following notes.ini defined in the Custom Settings:
  • Basic Configuration Settings
    • NOM_MC_DB – This value will be used as the location of MarvelClient Config Database; it can be fully qualified or use %notes_homeserver% to specify the user's home mail server. For example, %notes_homeserver%!!panagenda\pmc_config.nsf
    • NOM_MC_DISABLE – When set to 1, MarvelClient will be disabled and not allowed to manage HCL Nomad on all new installations.
  • Advanced Configuration Settings
    • NOM_MC_DB_NotResolvable – This value will be used as the location of the MarvelClient Database if %notes_homeserver% is specified in marvelClientConfigDB field and can not be resolved. For example, myserver!!panagenda\pmc_config.nsf
    • NOM_MC_DB_Unavailable – This value will be used as the location of the MarvelClient Config Database to use if the server is unable to connect to the database specified by marvelClientConfigDB or marvleClientConfigDBNotResolvable. For example, myAlternateServer!!panagenda\pmc_config.nsf
Note: If you want Notes and Nomad clients to use the same custom setting, use the generic setting name without the NOM prefix. For example, use MC_DB rather than NOM_MC_DB. Use settings with the NOM prefix only if you want them to apply to Nomad and not to Notes.