MarvelClient consists of the following major major components:

Two databases on HCL Domino Servers

    • A Config(uration) database which contains instructions for clients
    • An Analyze database storing detailed information about clients and their respective configuration

      MarvelClient does not require any server tasks.

      Typically, both of the above databases are replicated across all mail servers, which are assumed to be the servers end-users can reach most efficiently. The databases scale along easily, even in large environments with several 100,000 users.

One local MarvelClient binary/file on HCL Notes Clients*

No local file is required for HCL Nomad clients since panagenda MarvelClient is fully integrated into the Nomad app (starting with version 1.0.4).

    • mc.dll or pmc.dll on Microsoft Windows, Citrix and Windows Terminal Server
    • libmarvelclient.dylib or libpmc.dylib on Intel Mac OS X 64 bit
    • mc.dylib on Intel Mac OS X 32 bit
    • on Linux

* once installed, the local MarvelClient file automatically creates and updates a couple of additional local files in the so called MarvelClient Working Directory.

Additional component for MarvelClient Eclipse

MarvelClient Eclipse also includes a plugin which allows the binary to natively talk to Eclipse et vice versa.
Installing and updating the plugin is taken care of automatically by the local MarvelClient file.

Additional component for MarvelClient Upgrade

MarvelClient Upgrade comes with an additional executable file which can be easily deployed to end users by MarvelClient itself.
For further details, please refer to the separate documentation of MarvelClient Upgrade.

For an overview of how the client component communicates with the databases, see how MarvelClient communicates with the server-side databases.

Getting started in just a few minutes will guide you through initial installation and first steps.