Where it says HCL, MarvelClient also runs on IBM Notes and Lotus Notes
The local MarvelClient file (for MarvelClient Essentials: pmc.dll on Windows and libpmc.dylib on Mac, for a licensed MarvelClient: mc.dll on Windows and libmarvelclient.dylib on Mac) is deployed into either the IBM HCL Notes program or data directory and activated on clients with one additional entry in notes.ini (EXTMGR_ADDINS=, see below).
For architectural reasons, on Citrix it is highly recommended to deploy the local MarvelClient file into the Notes program directory.
The MarvelClient file auto-adapts to the respective end-user’s Notes release, install type and language – from Notes 6 to including 1012, for Basic and Standard (=Eclipse) Notes clients, ICAA CAA (HCL/IBM Client Application Access), local and network-drive based, single-, multi-user-, roaming- and non-roaming-installations – meaning that one single file covers all possible IBM Notes client types and configurations.
Integration with IBM HCL Notes
MarvelClient is entirely based on the security architecture of IBM HCL Notes and Domino.
The integration with IBM HCL Notes is based on the so called extension manager service, a specific form of integration into the IBM HCL Notes/Domino platform (for further details see: http://tinyurl.com/ax98ylc).
Extension managers are widely used for a great many different topics in the IBM HCL Notes/Domino world, such as (on both Domino servers, as well as Notes clients):
In principle an extension manager is a (.dll/.so/.dylib) file written in C (++), which makes use of an integration mechanism into Notes/Domino provided by IBM/ HCL.
Upon starting the Notes client, each extension manager add-in is loaded, which again registers itself for a variety of subsequent events in IBM HCL Notes (such for when attachments are being opened or saved, or the successful login of an end-user, depending on type of addin) as to be called again by IBM HCL Notes upon each such subsequent event.
panagenda MarvelClient integrates itself into IBM HCL Notes at several such events – depending on licensed and used feature set. For a detailed description also see About Runtypes.