A quick tipp for using the ONTF Dependency Documenter from Andrew Magerman.
If you have a lot of libraries in your database, the resulting image might be too large to fit into the page and the result seems to be truncated.

I have talked too Andrew already, and it seems that there is some kind of limitation on the image size for a page design element.

You can work around this issue by resizing the image in the image properties.

We also discussed some options and I am sure that Andrew will provide an updated version of the plugin soon.

While working with the cAPI, I ran into a nasty problem with signing design elemnts in an application on the server with a different ID than the server ID.
This seems only to be a problem with XPages related design elements.
When you try to open an XPage from that database in the browser, you will get a 403 Error message.
When I sign the same database from the client with the same ID using Ytria SignEZ, everything works as expected.

Other elements are not affected. So forms, views, agents and script libraries are signed correctly. Well, don’t get me wrong, even XPages are signed correctly, but they just do not work any longer after signing.

So, how do I sign a database in the background on the server with a different ID?

Here is, what I do. The ID is stored as an attachment in a configuration document. The file is detached at runtime to a temporary directory outside the Domino installation path. The code opens the file and returns a handle to the ID

So far, so good. As I said before, the code runs without any issues and the verification also does not report any errors.

At ConnectED, I went to the “Meet the Developers Lab” and asked for advice. The problem seems not to be in my code, but the Devs had a vague idea, what might be the problem.
I did some tests today and here is what I found out.

When you sign a design element using the client, The last entry in the $UpdatedBy field is the name of the signer.
When you do the same on the server, then the server’s name is the last name in the list.
Hence it is different from the name that is stored in the $Signature field, the error occurs.
This also explains, why I can open XPages that have been signed using my code and the server ID instead of the signer ID. In this case, names in $UpdatedBy and $Signature are identical.

As far as I can see, there is no workaround for that. So the only way to get this solved is to open a PMR with IBM …

Uploading files to an ESXi datastore ist terrible slow using the build-in upload mechanism. However if you add FTP to your ESXi server, and use an ftp client to upload/download files, the upload/download will be much faster.

ProFTPD runs good in ESXi 5.x and offers high transfer rate over normal transfers.

My vSphere Client starts with a german User Interface. Obviously, the language depends on the OS language. In my cas, it’s German …

To be able to provide screenshots with english labels and error messages in a way, that I can find results on Google more easily. I was looking for a way to switch the language of my vSphere Client to English.

There is no setting in the UI itself, but here is a little trick, how it can be done without pushing language files around like in the pre WW1 days.

Simply add one of the following parameters to the start parameter of the vSphere Client desktop icon

TriggerHappy 2.0 for Domino on Linux has been released on OpenNTF. It is still BETA and not intended to be used in production.
For now, I only provide the 32Bit version, because despite the 64Bit Version compiles and links, it freezes my server on startup.

The 32Bit version starts without issues, but invokes NSD on server quit and restart. Will look into that, but with Connect 2014 just around the corner, I do not have much spare time to do so.

If anyone is willing to offer help and could review the sourcecode ( Ben? Nathan?, Daniel? ) … Much appreciated.

Starting with IBM Domino 9.0, DBMT has been introduced. You can use the DataBase MainTenance tool for performing multiple daily/weekly administrative tasks on user’s mail database files. The DBMT tool relieves the administrator of the need to run the Updall task.
When DBMT is executed, it uses the copy-style compact (compact -c ) to compact databases. Compact -c has the disadvantage of fragmenting files and this can have an impact on the performance of your server.

But DBMT behaves a bit different here. DBMT preallocs the .TMP file to the used space size of the .NSF.

I did a test on my server. Here is the result.

Unfortunately, the “old” compact task itself does not yet have the preallocation feature included. I hope, that we will see this feature in a future release …

If you are already familiar with DBMT, you might be aware of this; if you are new to DBMT, you can save some time reading this article

DBMT is a new feature in Domino 9.0 that allows you to configure the regular maintenance options that you are familiar with to run automatically on schedule to keep your databases running smoothly. There are a lot of options that are described in the Administration Help Database

But, the Administration Help is wrong in one particular case:

“Specify any additional system databases using the notes.ini variable DBMT_FILTER. Separate entries in the list either by a space ( ), a comma (,) or a semi-colon (;). The names are case-insensitive and are relative to the data directory.”

The correct name for the variable is DBMT_COMPACT_FILTER

Even after upgrading to 9.0.1, you will find this incorrect entry in the help.

Starting with version 9.0.1 of IBM Notes / Domino,a new managed bean called the deviceBean is introduced within the XPages run-time to provide an easy to use and easy to program way of identifying a popular range of mobile and tablet devices directly within ServerSide JavaScript or Expression Language (EL) computed expressions.

This new ODS prevents data corruption that can occur only under very rare certain circumstance for medium and strong encrypted databases. A temporary solution has already been built into 8.5.3 and 9.0.

Starting with 9.0.1, the issue has been fixed permanently.

Once a Notes Client or Domino Server has been upgraded to 9.0.1, set CREATE_R9_DATABASES=1 in notes.in and the next copy style compact of the database will upgrade the database to ODS52 and the encrypted databases will no longer be exposed to this very rare corruption.

Thank you Bruce for all you have done for the (Lotus) Notes community and for giving OpenNTF to us in 2001.

I remember that day back in 2007 in Dublin, when I first met you in person at ILUG. We have met a few times on other events since then, and I hope to (perhaps) see you as a speaker at the EntwicklerCamp conference in 2014.

A couple of days ago, I received a mail asking me to join Alistair Rennie (General Manager, IBM Collaboration Solutions ) at the sixth annual IBM Leadership Alliance conference, October 23rd – 25th, at the Fairmont Copley Plaza, Boston, Massachusetts.

The conference has it’s focus on IBM’s newest collaboration capabilities and solutions. IBM will share the latest on strategy and technical direction, from Application Development and Social Integration, to Mobility and Messaging & Collaboration. Content shared during this meeting will include IBM confidential information that will be governed by the terms of the confidentiality agreement between IBM and each attendee. So do not expect any post about what will be presented at this invitation only event.

Hotel and flight is already booked. Public transportation seems to be fairly easy in Boston. And the hotel and venue is close to Boston Logan International Airport