Downloads

Config db ntf: 20110905074500
Analyze db ntf: 20110905074500
Windows Version: 2.5 :: MAC OS X Version: 2.0.29 :: Linux Version: 2.0.29
Eclipse Plugin:


Major Improvements: Significantly enhanced Cleanup feature, new Runtype [On First Server Access (FSAC)], Performance improvements (especially in combination with running e.g. backup to analyze database on first server access), Enhanced Runtime and new Smart File Downloader Monitoring, Namelookup timeout fix


General Notes

Supported IBM Lotus Notes releases: 5.x, 6.x, 7.x, 8.x, up to 8.5.2 FP3 (Administrators need at least IBM Lotus Notes 7.x on WIndows or Linux)
Supported client-side operating systems: Microsoft Windows NT4 (>=SP2), 2000, XP, 2003, 2008, Vista, 7, and Citrix/WTS, Apple Mac OS X Leopard, Linux
Supported server-side operating systems: any supported by IBM (operating system independent)
NOTE: Support is limited for platform and release combinations not supported by IBM
Linux & Mac OS X: Skinning, Realtime, Zip/Unzip and Attachment Blocking are not available on Linux or Mac OS X; also, MarvelClient on Mac OSX and Linux does not support the runtype "After Login - Before Sync" - any such actions must be set to run "After Login" (Agents and INI Management)
IMPORTANT NOTESThis release contains select important updates highlighted in red

This release allows for significant runtime improvents (=reduces the duration of after login) through the Namelookup fix and by using the new "on first server access feature" (see configuration database updates section).

The cleanup feature (action Advanced\JCL. Cleanup) has been enhanced significantly.

Configuration Database

CHANGESeveral of the forms have been changed to display horizontal lines between table rows to make it easier to identify which descriptor / label belongs to which cells/fields
CHANGEThe workspace page "Action if found" option "Nothing special" has been reworded to "Change properties as follows ..."
Also, when selecting the option "Delete page if empty" a line will be displayed stating "If the page is not empty, change properties as follows:"
NEW

The Cleanup action (Advanced\JCL. Cleanup) has been enhanced significantly - it now allows to automatically carry out any combination of below actions:
a.) delete or move replicas with cutoff date problems out of the data directory and optionally recreate them,
b.) delete or move old (=not used for a configurable number of days) databases (non-replicas) out of the data directory
c.) correct / cleanup links on the worspace/desktop pointing to local replicas that have been moved or deleted.

Special attention MUST be paid to the warning shown at the beginning of the cleanup action:


WARNING

Prior to deactivating simulation you must ensure that you have tested thoroughly and that you completely reviewed the simulation results.



Also, please note that the cleanup action will NOT do anything on clients with file- or directory links. log.xml will then contain a respective note.
(Example: <le><t>5753</t><l>1</l><c>WARNING</c><f>CO::DBManager_Impl::Execute</f><m>encountered a file- or dirlink; disabling cleanup action</m></le>)
This is planned to be fixed in the next release.

NEW

Added a new runtype "On first server access" to actions of type "backup", "run agent" and "run program"
- in essence this new runtype allows to run actions as soon as the first database is opened on a particular server after client startup, be it throught the UI (client itself) or the background replicator or the policy engine, for example.

This new runtype allows to significantly reduce client startup times by moving e.g. the backup to analyze database, hw/sw audit, collection of location and connection documents to the background after client startup!

The component can be configured as follows (via a "Notes.ini & variables" action)
As of MC 2.5.0, "on first server access" actions are enabled by default, so it is not necessary to specifically enable them - however, fsac_thread_servers must be explicitly configured as of 2.5.0:
mc:fsac_thread_enabled=true (defaults to true, so does not need to be set to enable first server access)
mc:fsac_thread_servers=server on which the config database resides (defaults to NO server at all = MUST be set to a servername, or <ini:mailserver> for the users mailserver, for example)



mc:fsac_thread_enabled=true (defaults to true as of 2.5.0)
and
mc:fsac_thread_servers=name_of_server upon which, as soon as accessed, any "on first server access" actions are supposed to be executed.
(accessed means a database is being opened not just "file-database-open-servername-enter" - the server defaults to "no server specified --> even if enabled, nothing will happen).

NOTE that the on first server access thread will wait 1 minute to actually execute any "on first server access actions" after a database on the specified server has been opened, as to not reduce bandwidth of immediate replication or in case a user is opening a database directly from the server.

- requires DLL update to at least 2.0.33

Updated
Documentation for Configuring the
Smart File Downloader		SFD can be configured via the following two mc-variables - default values as of MC 2.5.0 are mc:dlm_disabled=0 and mc:dlm_initialdelay=5
mc:dlm_disabled=0
(mc:dlm_disabled=1 would disable smart file downloads)
mc:dlm_initialdelay=number of minutesthe Smart File Download component shall wait before it runs after client startup
(by default, the initial delay is set to 5 minutes - for testing purposes you may wish to set it to 0 or 1 minute)


- requires DLL update to at least 2.0.33
NEWA new option has been added to DLL update actions, which allows to prevent DLL downgrades
NEWDLL update actions now also support conditions (also for previous DLL versions)
NEWAdded new action examples for the new "On first server access runtype" feature (see DLL changes)
NEWAdded two new action examples to manage names.nsf and bookmark.nsf on the replicator page for IBM roaming users (not needed for MC roaming users)
ENHANCEMENTThe view "All Actions\by RT, Prio, Title" has been updated to display all currently available runtimes (before login, after login, on first server access (NEW - see DLL changes), ...) properly
CHANGEThe desktop icon action has been changed to prompt upon save if the icon bitmap data could not be resolved for automatic deployment of a desktop icon (and replicator page entries) with the corresponding desktop icon picture.
CHANGEChanged the existing "upload into analyze database" examples to run "on first server access" (see DLL changes)

Analyze Database

FIX/CHANGEA field $NoPurge="" has been added to all configuration (cleanup and export ID file) and XSLT documents, plus language setting documents to prevent documents being deleted if using "remove documents older than xx days" in replication options of an Analyze database replica.
NOTE that you must manually resave the cleanup and export id file document once for the field to populate in the respective documents.
NEWA new view OS / HW\by Resources has been added to the analyze database allowing to easily identify users with too few disk space / memory and similar:
NEW

Added a new view "Smart File Downloads\by Progress" to monitor download progress of smart file download actions:


Smart File Download (SFD) actions require marvelclient_upgrade to be licensed in the license document.
For further licensing details regarding Smart File Download, see Release Notes 2011-04-24.
Configuration details are as follows:
SFD actions need to be created in the configuration database and configured via the following two mc-variables:
mc:dlm_disabled=0
(by default, the smart file download is disabled, even if it is covered by the license - this is because SFD runs in a seperate thread after client startup)
mc:dlm_initialdelay=number of minutesthe Smart File Download component shall wait before it runs after client startup
(by default, the initial delay is set to 5 minutes - for testing purposes you may wish to set it to 0 or 1 minute)

- requires DLL update to at least 2.0.33

ENHANCEMENTThe view "Lotus Notes\Runtime Analysis" has been enhanced to display the duration of all (known via uploaded config.xml) available runtypes, plus total synchronisation time. In addition, the new DLL release 2.0.33 will also upload details of the time between runtypes (e.g. the time between Before login - Init and Before Login) - this does now allow for monitoring of almost complete client startup times (there is a remaining duration IBM itself needs after the end of After login, which MC does not log, but the existing runtimes should now allow to easily spot problem candidates / regions / offices / ...)

The following image shows an example startup time analysis:

- requires DLL update to at least 2.0.32
CHANGEThe XSLT documents have been changed (see above $NoPurge field); above all the config.xsl attachment/content-wise to allow for monitoring Smart File Download Progress.

.DLL Updates (Windows)

FIX (2.5.0)Fixed a problem where realtime relocation could result in a client crash in Notes 8.5.2
FIX (2.5.0)Fixed a problem where relocation did not work in cases were MarvelClient considered a database to be still opened even though it was not.
FIX (2.0.32)Fixed a bug in desktop icon action: on unstacked desktops "move must have" did not work properly. it did the same thing as "move all".
NEW (2.5.0)The name for multifile zip archives can now be customized in the MarvelZip Configuration action (defaults to "Archive.zip")
NEW (2.5.0)Added two references <notes:journal_fs_path> and <notes:names_fs_path>. This allows to reference the fully resolved filepath of journal.nsf and names.nsf - if "names.nsf" is a file link, then <notes:names_path> only returns "names.nsf" (and hence backup would only backup the filelink but not the actual addressbook pointed to by the filelink).
Customers are advised to keep using <notes:names_path> (all examples and default configurations in the configuration database have remained unchanged) unless they require a solution to use MC roaming for the local addressbook which is being linked to via a file link - in such a case, customers are advised to contact their supporting panagenda partner or panagenda support.
NEW (2.5.0)Added two new references <notes:journal_fs_directory> and <notes:names_fs_directory> which supply the directory for journal and names.nsf in case they are linked into notes via a file link.
NEW (2.5.0)Two new references <notes:journal_path> and <notes:journal_replicaid> have been added to detect an existing journal.
The corresponding values are resolved in the following order:
1. If <ini:RoamingJournal> exists, the result values will be resolved from RoamingJournal in notes.ini
2. If 1. was not fulfilled and notebook.nsf exists, the values will be resolved from notebook.nsf
3. If 1. + 2. were not fulfilled and journal.nsf exists, the values will be resolved from journal.nsf
If 1. + 2. + 3. are not fulfilled, both values are empty.
NEW (2.5.0)A new config option has been added for roaming between single user clients: Setting <mc:fs_roaming_delete_redundant_idfiles> to "true", "yes" or "1" will enable the following roaming behaviour:
if a file based roaming action runs, which contains an archive named ids.zip, which again contains at least one id file, then all other id files - except for those in the to be roamed ids.zip - will be deleted in the target Notes data directory.
Please make sure that you set this variable priort to the execution of the actual roaming action (=an ini & Variables action running permanently [before login - init] and with a lower priortiy number than the roaming action)
NEW (2.5.0)Improved performance for "ClearCachedStacks" (search any log.xml for an example)
NEW (2.0.25)A new option has been added to DLL update actions, which allows to prevent DLL downgrades
FIX (2.0.28)In previous releases, lookup up location details (%LOOKUP_*) did not obey mc:db_dbopentimeout

In general, customers are advised to set
mc:db_dbopentimeout=10000
and
mc:db_checktimedout=true
to make sure that clients to do need (the OS default of) 90 seconds to time out when trying to open e.g. the configuration database.
Customers are also advised to NOT set db_dbopentimeout below 8000 (ms) as a clusterfailover may well take 7 seconds depending on your environment.

The above mc:db_* settings together with the FIX in 2.0.28 ensure that end users do not encounter client startup delays of several minutes that would otherwise occur in problematic connectivity situations with a timeout of 90 seconds as per attempted database connection(!).

(REMINDER from release notes for DLL 1.6.19:
New option to specify a serverside database access timeout using
mc:db_dbopentimeout=[number of milliseconds], e.g. mc:db_dbopentimeout=8000 will cancel opening a database if this takes more than 8 seconds
(default = no timeout)
In addition, mc:db_checktimedout allows to specify whether a previously timed out database access should be attempted again;
mc:db_checktimedout is a boolean and thus accepts the value "yes", "1", "true" (or "no", "0", "false" = default = retry every database again)
e.g. mc:db_checktimedout=true will not try to open a previously timed out database again during a specific run (e.g. after login) -
NOTE: the list of timedout databases is cleared immediately after login and at the beginning of a client shutdown as it usually makes sense
to retry a database during shutdown that timed out after login.
NOTE: mc:db_checktimedout operates based on a specific database "URL" (= servername together with entire database path), NOT on a per server basis.)
NEW / ENHANCEMENT (2.0.31)(Not just backup) actions can now be further restricted with the following conditions:
mc:last_fs_roaming_no_instance_found=1
and
mc:last_fs_roaming_target_empty=1

Together with mc:last_fs_roaming_failed introduced in 2.0.17, this allows to create conditions for the following cases:
mc:last_fs_roaming_failed: Equals "1" if MarvelClient could not connect to the root drive of the roaming source (=if the network drive was not available)
mc:last_fs_roaming_no_instance_found: Equals "1" if MarvelClient could not find any newer instance/backup to roam onto the client being started (=no roaming took place).
mc:last_fs_roaming_target_empty: Equals "1" if MarvelClient could open the drive and directory of the roaming source, but the directory was empty.
NEW (2.0.32)Added logging of various durations during client startup (e.g. time between before login - Init and before login, where we are "waiting for IBM");
even though this does not include the time it needs to start the client from after "after login" until the UI (user interface) shows up, it allows to easily pinpoint virtually any performance problems affecting client startups
NEW (2.0.33)Added logging for smart file download actions to config.xml
NEW (2.0.33)Added a new feature to run actions "On first server access"

.dylib Updates (Mac OS X)

FIX (2.0.29)On previous Mac releases, the ip-addresses saved in config.xml where not correct - this is now fixed.
FIX (2.0.29)Location and connection actions now support all %LOOKUP_* placeholders
FIX (2.0.29)User mailfile details are now properly saved to config.xml (missing in previous Mac releases)

.so Updates (Linux)

FIX (2.0.29)Location and connection actions now support all %LOOKUP_* placeholders
FIX (2.0.29)User mailfile details are now properly saved to config.xml (missing in previous Linux releases)

Contact Support

Visit panagenda MarvelClient on our website!