When I login and want to acccess my homepage I get an error message.

Solution: Remove a cookie named “WASReqURL”

Bookmark:

IBM released interim fix 1 for Lotus Domino 8.5.1 fixpack 2 a few days ago. This fix solves some problems with DAOS enabled databases. It’s recommended that you install this interim fix if you are running DAOS enabled databases on this version of Domino.

The fix and installation instructions can be found at IBM Fix Central.

Bookmark:

There is a known bug in the 8.0 mail template, that incorrectly shows friday January 1st, 2010 as the first week of 2010. Officially January 4th, 2010 starts the first week of 2010 and the week from December 28th to January 1st is the 53th week of 2009.

Not everyone seems to be affected by this bug, but if you are, all week numbers in Notes are one week ahead. It’s easy to check: just go to January 1st on your calendar in Notes. It should say “week 53 – 0 weeks left in year” at the botom. If it doesn’t, you are probably affected.

IBM supplies the following workaround: in the Notes client, go to File -> Preferences. In there, go to Calendar and To Do -> Regional Settings and look for the “Week Numbers” section. Set this to “Always use the ISO standard” and the week numbers should be fine. You can also do this via a notes.ini setting:

FooterWeekNo=2

It’s not a showstopper bug, but it can be irritating.

Bookmark:

A few days ago, I had to move the data directory of a Domino server to another partition on that server. So I shut down Domino and moved the data directory to the new partition. After this, I changed the “Directory”  parameter in notes.ini, so that it pointed to this new location.
I thought that was it so I started up the Domino service again, only to be confronted with a non-working Domino server. The following error showed up on the console:
An error occurred during license use management initialization

After this, the Domino service just stopped. A technote from IBM explained that this problem was caused by two files: Domino8.lic and nodelock. I checked the data directory and those files were present. The technote suggested to reinstall the Domino server, but I wanted to avoid that.
I started looking around in the Windows registry and discovered that there are two references to the data directory in there. Of course, these were still pointing to the old location. After changing these registry keys to the new location, I could start the server again without any problems.

The keys can be found in:
HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Domino\
and
HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Domino\1

The name of the key is:
DataPath

Just edit the values and fill in the new path of the Domino directory.

PS: If, for some reason, you don’t want to change the registry, you can also recreate the data directory at it’s old location. Then copy the two files (Domino8.lic and nodelock) to that directory and you will be able to start the server. All other data can stay at the new location. But I prefer to just change the registry.

Bookmark:

In my first blog I’d like to explain a little about building a plug-in for Eclipse and how to integrate it into a Lotus Notes Client.

The first thing we’ll do is set up your Eclipse environment. I used the RCP edition of Eclipse Ganymede (3.4). I’m sure it’ll also work in other versions but I have not tested those. I’ve only tested on the Lotus Notes Client 8.5.1.

We need to add the Notes JVM for Eclipse to use. The target platform also has to be configured as well as the launch configuration.

When you’re done you should have a working Eclipse environment in which you can develop and test Lotus Notes Client plug-ins. This means you can press the run button and Eclipse will start a Notes Client and run the plug-in in that client. Make sure no Lotus Notes Client instances are open before you run your plug-in project or you’ll get an authorization error.

The next step is to create a plug-in. Create a new Eclipse Plug-in Project and base it on the view template. Make sure to add the ‘com.ibm.notes.java.api‘ dependency to your project. And don’t forget to include the Notes.jar library if you want to be able work with Notes databases in your project.

Eclipse plug-ins work based on extension points. We can extend the menu, toolbars, help, preferences … We now created a plug-in based on the view template. Eclipse can show these views almost anywhere. But for us to show it in the Notes sidebar we have to create another extension based on the com.ibm.rcp.ui.shelfViews. We can then link our view to this one and it will be shown in the sidebar.

With our plug-in up and running, we’ll need a way to make it distributable. And we have to be able to install it into any Lotus Notes Client.

Make a new Feature Project and add our plug-in to it. Afterwards make a new Update Site Project and add our feature to it. Don’t forget to build the plug-ins or you’ll have an empty site.

In your Notes Client, install a new application, add a folder and browse to your site (the folder containing site.xml). You’ll get all the features in this site with each feature displayinh its plug-ins.

Eclipse (and thus the Lotus Notes Client) works with features. Each feature contains one or more plug-ins. You need an update site to make your feature available. A feature is the actual plug-in, integrated into Eclipse.

You should now have a simple view – plug-in that you can install into any Notes 8.5.1 client.

This concludes my first post. Have fun extending

Bookmark: