A Notes preloader can be configured to run at OS startup. The preloader allows for faster Notes client startup by preloading some required Notes libraries when the OS is started.
The preloader opens and closes certain databases to load Notes libraries into memory and then shuts itself down. When enabled, users experience a faster Notes startup.
Enabling the preloader makes registry changes during Notes installation. On a locked down system, registry changes would require elevated privileges; the Notes installer already needs to run with those privileges.
The preloader is most effective with Windows XP.
How do I enable the preloader for a Notes install or upgrade?
The preloader option is off by default. You can enable the preloader option during Notes client install or upgrade using the Launch parts of Notes when the operating system starts to enable faster Notes startup option in the user interface. The option appears on the same install screen on which Notes can be enabled as the default mail, calendar, and contacts programs.
You can also enable the preloader option as follows:
-- Start the installation using /v"PRELOADNOTES=1" argument on the SETUP command line:
SETUP /v"PRELOADNOTES=1"
-- Add the following argument to the CmdLine setting:
CmdLine= /v"PRELOADNOTES=1"
-- Enable the preloader option using an MSI transform
Create a transform using the InstallShield Tuner for Lotus Notes and enable the "Preloader" option under Features > Notes Client.
Can I enable the preloader after I've run the Notes 8.5.2 installer?
Yes, you can enable preloading after Notes install by making the following changes to the Windows Registry:
For registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run, specify the key name as "IBM Lotus Notes Preloader" and use the full path to the Notes preloader executable in the Notes install directory, for example:
C:\Progam Files\IBM\Lotus\Notes\NNTSPRELD.EXE
What exactly does the preloader do?
When the preloader runs, it preloads a portion of the Notes APIs and subsystem, a portion of the Java JVM, and some NSF databases that are used immediately at the time of the Notes client startup.
After the preloader has brought portions of the files into the OS file system in memory cache, the preloader executable exits; leaving no permanent EXEs or DLLs loaded in memory.
The preloader runs with respect to the Notes installation where the Notes preloader executable is located. In terms of client data, it uses the standard Notes client mechanisms to locate the current NOTES.INI for the user.
In Notes 8.5.2, the preloader does the following:
Calls NotesInit which causes low level Notes DLLs and files to be loaded
Reads several client databases including DESKTOP8.NDK, CACHE.NDK, BOOKMARK.NSF, and NAMES.NSF
Loads a number of Java JVM DLLs
If you make AntiVirus/AV exceptions at the EXE level (for example. NOTES2.EXE, NLNOTES.EXE or NTASKLDR.EXE), then you should consider adding NNTSPRELD.EXE to that same exception list.
However, if exceptions are made at the directory or file level, the preloader acts on the same set of files as the Notes client when it starts.
If you make exceptions for specific EXEs to run, then the NNTSPRELD.EXE should be included in those exceptions.
The NNTSPRELD.EXE runs with user privileges, in the same manner as the NLNOTES.EXE process.
Are admin rights required to both install and run the preloader?
No. Admin rights are required only for the install.
Does the preloader commit files to disk?
No, the preloader does not commit any files to disk. The portions of files read into memory will remain in the Windows in-memory file system cache. The preloader does not persist any of its data directly.
MSDN article: File Caching (Windows)
What's the recommended way to validate results?
Compare Notes cold startup times with and without the preloader with OS restarts in between. You should notice cold startup improvements after preloading has occurred compared to starting Notes after an OS restart without the preloader running.
NOTE: If your cold starts have variations due to daily tasks (i.e., software updates or anti-virus updates), be careful not to factor those variations into your timings. It would be best to perform a couple of timings to ensure that you have consistency in your numbers.
Is there a visual way to see the preloader activity?
The recommended way to verify preloader acitivity is through a comparison of cold startup times with and without it running. But for a visual look at the I/O that occurs during the preloading, you can use a tool like sysinternals by Microsoft.
Tuesday, September 14, 2010
Domino 8.5.2 - Detecting corrupted databases
Automatic Corrupt Database Collection
When the Domino server detects that a database has corruption, it will automatically store the corrupted database as a separate file in a separate directory. The detection and collection of corrupted database is done at database open. To enable and control the automatic collection of corrupt databases, set the following Domino configuration variables:
DATABASE_CAPTURE_ENABLED enables the automatic collection of a corrupted database as detected by the sever when the database is opened. Set to 1 to enable.
Note: Upon startup, the Domino server will enable the function and reset the value of the variable in the notes.ini file so that the corrupt database collection is not started on subsequent server restarts without user intervention.
DATABASE_CAPTURE_LIMIT is the maximum number of corrupt databases that will be collected by the server. If not set, the default value is 10. If set to 0, there will be no limit on the number of corrupt databases collected.
DATABASE_CAPTURE_SIZE_LIMIT is the limit, in megabytes (MB), of the total size of all collected databases. If not set, the default value is 100. If set to 0, there will be no limit on the total size of corrupt databases collected.
DATABASE_CAPTURE_DIRECTORY is the directory that will contain the collected databases. It is specified relative to the "data" directory. If not set, the default value is "IBM_TECHNICAL_SUPPORT\ACDC" which will place the corrupted database files into the "data\IBM_TECHNICAL_SUPPORT\ACDC" directory.
Collected databases have the same name as the source database file with a ".cor" extension.
The automatic facility will collect any database detected to have corruption within the configuration parameters currently active.
Corrupted Database Collection Tool
The dbcapture tool is provided as a standalone tool to collect a specific database manually at the discretion of the administrator or user. The tool respects the number and size limits when collecting a database. The tool ignores the DATABASE_CAPTURE_ENABLED configuration variable.
To collect a database manually, enter the following command at the server console:
load dbcapture abc\red.nsf
where "red.nsf" is the name of the database file to be captured in the "abc" directory relative to the data directory. The dbcapture tool can also be run from an Operating System command prompt by entering the following command:
dbcapture abc\red.nsf
Databases will not be collected, automatically or with the dbcapture tool, in the following cases:
• The DATABASE_CAPTURE_LIMIT has been reached
• Collecting the database would exceed the total size for collected databases as set in DATABASE_CAPTURE_SIZE_LIMIT
• The database has already been collected
• The database is being processed by the compact or fixup tasks.
When the Domino server detects that a database has corruption, it will automatically store the corrupted database as a separate file in a separate directory. The detection and collection of corrupted database is done at database open. To enable and control the automatic collection of corrupt databases, set the following Domino configuration variables:
DATABASE_CAPTURE_ENABLED enables the automatic collection of a corrupted database as detected by the sever when the database is opened. Set to 1 to enable.
Note: Upon startup, the Domino server will enable the function and reset the value of the variable in the notes.ini file so that the corrupt database collection is not started on subsequent server restarts without user intervention.
DATABASE_CAPTURE_LIMIT is the maximum number of corrupt databases that will be collected by the server. If not set, the default value is 10. If set to 0, there will be no limit on the number of corrupt databases collected.
DATABASE_CAPTURE_SIZE_LIMIT is the limit, in megabytes (MB), of the total size of all collected databases. If not set, the default value is 100. If set to 0, there will be no limit on the total size of corrupt databases collected.
DATABASE_CAPTURE_DIRECTORY is the directory that will contain the collected databases. It is specified relative to the "data" directory. If not set, the default value is "IBM_TECHNICAL_SUPPORT\ACDC" which will place the corrupted database files into the "data\IBM_TECHNICAL_SUPPORT\ACDC" directory.
Collected databases have the same name as the source database file with a ".cor" extension.
The automatic facility will collect any database detected to have corruption within the configuration parameters currently active.
Corrupted Database Collection Tool
The dbcapture tool is provided as a standalone tool to collect a specific database manually at the discretion of the administrator or user. The tool respects the number and size limits when collecting a database. The tool ignores the DATABASE_CAPTURE_ENABLED configuration variable.
To collect a database manually, enter the following command at the server console:
load dbcapture abc\red.nsf
where "red.nsf" is the name of the database file to be captured in the "abc" directory relative to the data directory. The dbcapture tool can also be run from an Operating System command prompt by entering the following command:
dbcapture abc\red.nsf
Databases will not be collected, automatically or with the dbcapture tool, in the following cases:
• The DATABASE_CAPTURE_LIMIT has been reached
• Collecting the database would exceed the total size for collected databases as set in DATABASE_CAPTURE_SIZE_LIMIT
• The database has already been collected
• The database is being processed by the compact or fixup tasks.
Monday, July 5, 2010
How to determine the version of a Sametime server
To determine which version of the Sametime server is installed, open a web browser, and in the Address field (or by pressing Ctrl+O), enter the following:
http:///Sametime/buildinfo.txt
(where is the Fully Qualified Domain Name of the Sametime server)
To determine the server version, compare the contents of the buildinfo.txt file to the appropriate table below (based on your server platform),
Normal 0 false false false EN-US X-NONE X-NONE
http://
(where
To determine the server version, compare the contents of the buildinfo.txt file to the appropriate table below (based on your server platform),
Windows, AIX, Linux, and Solaris
(see next table for i5/OS information)
| Release | Type | Version= | Build date |
| 8.0.2 | Standard | Windows, AIX, Linux, Solaris: SAMETIME8.0.2_20081209.1843_WIN32AIXSOLLIN_WESTFORD | Tue Dec 9 20:53:06 EST 2008 |
| Entry | Windows, AIX, Linux, Solaris: SAMETIME8.0.2_20081209.1843_WIN32AIXSOLLIN_WESTFORD | Tue Dec 9 20:53:06 EST 2008 | |
| Limited Use | Windows, AIX, Linux, Solaris: SAMETIME8.0.2_20081209.1843_WIN32AIXSOLLIN_WESTFORD | Tue Dec 9 20:53:06 EST 2008 | |
| Connect Server (Resell) | Windows, AIX, Linux, Solaris: SAMETIME8.0.2_20081209.1843_WIN32AIXSOLLIN_WESTFORD | Tue Dec 9 20:53:06 EST 2008 | |
| 8.0.1 | Standard | Windows, AIX, Linux, Solaris: SAMETIME8.0.1_20080415.2101_WIN32AIXSOLLIN_LEXINGTON | Tue Apr 15 23:00:16 EDT 2008 |
| Entry | Windows, AIX, Linux, Solaris: SAMETIME8.0.1_20080415.2101_WIN32AIXSOLLIN_LEXINGTON | Tue Apr 15 23:00:16 EDT 2008 | |
| Connect Server (Resell) | Windows, AIX, Linux, Solaris: SAMETIME8.0.1_20080415.2101_WIN32AIXSOLLIN_LEXINGTON | Tue Apr 15 23:00:16 EDT 2008 | |
| 8.0 | Standard | Windows, AIX, Linux, Solaris: SAMETIME8.0_20071119.1501_WIN32AIXSOLLIN_LEXINGTON | Mon Nov 19 17:30:34 EST 2007 |
| Entry | Windows, AIX, Linux, Solaris: SAMETIME8.0_20071119.1501_WIN32AIXSOLLIN_LEXINGTON | Mon Nov 19 17:30:34 EST 2007 | |
| Limited Use | Windows, AIX, Linux, Solaris: SAMETIME8.0_20071119.1501_WIN32AIXSOLLIN_LEXINGTON | Mon Nov 19 17:30:34 EST 2007 | |
| Connect Server (Resell) | Windows, AIX, Linux, Solaris: SAMETIME8.0_20071119.1501_WIN32AIXSOLLIN_LEXINGTON | Mon Nov 19 17:30:34 EST 2007 | |
| Trial | Windows, AIX, Linux, Solaris: SAMETIME8.0_20071119.1501_WIN32AIXSOLLIN_LEXINGTON | Mon Nov 19 17:30:34 EST 2007 | |
| 7.5.1 CF2 | Limited Use | Windows, AIX, Linux, Solaris: SAMETIME7.5.1CF2_20080625.1701_WIN32AIXSOLLIN_LEXINGTON | Same as 7.5.1 |
| Standard server | Windows, AIX, Linux, Solaris: SAMETIME7.5.1CF2_20080625.1701_WIN32AIXSOLLIN_LEXINGTON | Same as 7.5.1 | |
| 7.5.1 CF1 | Limited Use | Windows, AIX, Linux, Solaris: SAMETIME7.5.1CF1_20070717.0801_WIN32AIXSOLLIN_LEXINGTON | Same as 7.5.1 |
| Standard server | Windows, AIX, Linux, Solaris: Sametime7.5.1CF1_20070717.0801_WIN32AIXSOLLIN_LEXINGTON | Same as 7.5.1 | |
| 7.5.1 | Limited Use | Windows, AIX, Linux, Solaris: SAMETIME7.5.1IMLU_20070627.1101_WIN32AIXSOLLIN_LEXINGTON | Wed Jun 27 13:52:16 EDT 2007 |
| Standard server | Windows, AIX, Linux, Solaris: SAMETIME7.5.1_20070416.1601_WIN32AIXSOLLIN_LEXINGTON | Wed Apr 18 11:23:55 EDT 2007 | |
| 7.5 CF1 | Standard server | To check whether Sametime 7.5 CF1 is installed on a Sametime server, check for the existence of buildinfoST75CF1.txt in the domino/html/sametime subdirectory of the Sametime server data directory. | Thu Aug 10 02:19:28 EDT 2006 |
| 7.5 | Standard server | Windows, AIX, Solaris: SAMETIME7.5_20060810.0001_WIN32AIXSOL_LEXINGTON | Thu Aug 10 02:19:28 EDT 2006 |
| 7.0 | Limited Use | Windows, AIX, Solaris: SAMETIME7.0_55.5_WIN32AIXSOL_LEXINGTON | Wed Sep 14 09:43:21 EDT 2005 |
| Standard server | Windows, AIX, Solaris: SAMETIME7.0_55.4_WIN32AIXSOL_LEXINGTON | Fri Aug 19 13:20:51 EDT 2005 | |
| 6.5.1 FP1b | Standard server | Windows, AIX, Solaris: ST6.5.1FP1_17.5_WIN32AIXSOL_LEXINGTON | Wed Jul 13 14:44:34 EDT 2005 |
| 6.5.1 FP1a | Standard server | Windows, AIX, Solaris: ST6.5.1FP1_17.3_WIN32AIXSOL_LEXINGTON | Fri Jul 1 01:22:35 EDT 2005 |
| 6.5.1 FP1 | Standard server | Windows: ST6.5.1FP1_16.2_WIN32AIXSOL_LEXINGTON | Thu May 12 10:43:11 EDT 2005 |
| AIX, Solaris: ST6.5.1FP1_16.2_WIN32AIXSOL_LEXINGTON | Tue May 10 21:02:46 EDT 2005 | ||
| 6.5.1 EMS | EMS | Windows: ST6.5.1_43.1_WIN32_LEXINGTON | Thu Sep 2 12:49:08 EDT 2004 |
| 6.5.1 | Standard server | Windows: ST6.5.1_16.3_WIN32_LEXINGTON | Sun Mar 21 17:37:56 EST 2004 |
Thursday, June 24, 2010
ID Vault in Domino 8.5.1
Remember to grant ID Vault Administrator, Auditor role otherwise you will receive error when extracting IDs. The role can be granted by managing ACL on the ID vault from the Files tab.
Subscribe to:
Posts (Atom)