IBM Domino lessons learned from using the new FP8 feature of having the view index outside the NSF database (NDX)
At a customer today I wanted to implemented the new IBM Domino feature of having the view index outside the NSF.
First I upgraded to FP8 IF3, then I updated notes.ini from the configuration document with the new setting NIFNSFEnable=1 and restarted the server.
I then wanted to start carefully with one database only ...with something like "load compact -c -nifnsf on databasename.nsf".
Unfortunately I misspelled the database path and hit enter. To my surprise the Domino server did not just report back in the console that the database could not be found, ...instead is started compacting on ALL DATABASES!
Not quit what I expected or wanted .... but I let it continue
Lesson learned...software does not always act as expected ...act accordingly..get you spelling in order!
I kept an eye on the compacting and I noticed that one big database (GB) just barely got touched only creating a small NDX file and the compacting moved on.
I am a little unsure what to expect now. My guess that it created some kind of "stub", because the database most likely was in use it could not compact it.
So I hope that when DBMT starts compacting it will finish the job....but I am not sure, may need to run the ""load compact -c -nifnsf " again.
Lesson learned ... it is always "fun" when software stops in the middle of doing something ...what is going to happen next?
OK this one i primarily my fault,... I got the great idea ..why not open the NDX file in the Domino Designer and have a look around?
Lesson learned... don't do that... your server will come to a grinding halt...
You are probably not meant poke around in a NDX database ;-)
I am sure there is plenty more to be learned...
Making "X-Forwarded-For" log feature IBM Domino FP8 actually work
In March I wrote about the new log feature in IBM Domino in connection with using a Reverse Proxy.
The issue is that you will always get the IP address of the Reverse Proxy in you HTTP log files and not the actual IP of the user.
This is what the HTTP header "X-Forwarded-For" is used for, however pre FP8 is was not supported on IBM Domino server.
In FP8 it is supported...but not documented.
Thanks to Vitor Pereira who (commented on my blog entry) created a PMR, we now have an answer how to get it working.
Add HTTP_LOG_ACCESS_XFORWARDED_FOR=1 to the servers notes.ini file, restart server and it works!
However if you using domlog.nsf for log data (which is fine for low traffic) you need to change the design to see the X-forwarded-for IP.
You would presume the item would be named something like "XForwardedFor", but no .. it is "ForwardedFor" ..or rather because it is misspelled it is "ForwaredFor" ;-)
New logging feature in IBM Domino FP8 when using Reverse Proxy - X-Forwarded-For
When using a Reverse Proxy (like Nginx) is in front of a IBM Domino web server you have the issue that the IP address of the client accessing the Domino web server is not forwarded to the log files on the Domino server.
What you get is the IP address of the Reverse Proxy instead...which is not very helpful.
This is normally fixed by the Reverse Proxy server adding a HTTP header field called "X-Forwarded-For" (XFF) which the web server then can log.
Unfortunately the IBM Domino web server will no log the "X-Forwarded-For" field..until FP8 it seems.
A long overdue request from 2010 apparently has been fulfilled in FP8.
My question is just ...how to enable? .. a notes.ini setting ?
(I presume the "X-Forward" is actually supposed to be X-Forwarded-For (?)
IBM Domino: Moving the view indexes outside the NSF database
As a new feature in IBM Domino Feature Pack 8 (FP8) for IBM Domino 9.0.1 is that you can move the view indexes outside the NSF.
View indexes and Full Text Indexes are data derived from the "core" data, the documents in the database.
This means they can always be rebuilt, if you have the data in the documents.
Benefits from moving view index outside NSF:
1) A smaller database file size, to avoid reaching the 64GB limitation.
2) Faster database backup and restore.
3) Better performance by allowing concurrent access to database and views.
1) Very important when having large databases with many documents. View indexes can easily take up many GB.
Use the Administrator "Manage Views" to see the view sizes in the databases
2) I use DomBackup (Openntf) which is very fast and does not care about indexes,
3) Updating view locks views so this is a very nice and important enhancement
How to enable
To enable moving view indexes outside NSF is very simple and need just a few steps.
1) You must run Feature Pack 8 (FP8)
2) Set parameter NIFNSFEnable=1 in Notes.ini and restart server.
3) Make sure you have transactional logging enabled on server and ODS is minimum 51
4) To enable the feature for a database you need to compact it with the parameters: "load compact -c -nifnsf on databasename.nsf"
It will the create an index file with the extension .ndx
This from a database I have enabled the feature for.
I have had no issues so far.
What about ACL, Readers? I asked IBM this in a Q&A and they told me that the view data was encrypted
There are other features like moving the index to another folder etc.
Have a look here https://www.ibm.com/support/knowledgecenter/en/SSKTMJ_9.0.1/admin/admn_moving_views_out_of_databases.html
Watch out ...Intel Atom C processors will completetly die due to a flaw in processor
If you have a NAS, a router (like Cisco), a firewall or a less capable PC with a Intel Atom C processor you might be heading for trouble.
Due to a "clock flaw" in the Intel Atom C2000 processors they are "likely to fail at an accelerated rate after 18 months of operation" theregister.co.uk states
Fail as in "completely die" and not boot again ...ever
The specific SKUs are:
C2308, C2338, C2350, C2358, C2508, C2518, C2530, C2538, C2550, C2558, C2718, C2730, C2738, C2750, and C2758 (stepping B0)
Intel is silent.
Have a look here
Shrinking the 0.44 MB large IBM Domino favicon.ico to something useful
Normally favicons are very tiny graphic files, just a few KB in size.
But to my surprise I saw that the IBM Domino favicon was a whopping 449,4 KB in size . and took over 0.7 seconds to load
The reason is that an ICO file can contain many images inside and thus be a multi-purpose graphics file.
Which can be great at times.... but sending a half megabyte favicon is probably not what you want
If you want to keep the IBM Domino favicon but only a 16x16 version, you can just download the normal IBM Domino favicon from the server, open it in GIMP, delete all the layers except for a 16x16 image and save it again.
Upload it to the Domino server again to "Domino/html/favicon.ico".
If on Linux remember to change ownership.
After this change the file was 1.1 KB and loaded in an instant