Developing custom XPages for customers makes it necessary that these XPages behave in the same way on our development servers as they do on the customers IBM Lotus Domino environment. But sometimes this just doesn’t work…..
Naturally, first thing you do in order to check for discrepancies is to take a look at the server version and the upgrade pack or extension library version. Don’t forget to check the language and regional settings. This has some effect on automatically generated messages and formats. But, if everything matches you start to wonder. Perhaps the java.policy of the Domino Server needs to be edited? But you wouldn’t forget about that, wouldn't you? So, where else to look?
Finally, you remember the
xsp.properties file on a Domino Server. By standard this file isn’t created. But if it exists it might have great impact on your XPages. You have an additional local
xsp.properties file inside your NSF but this only overwrites the settings you have configured. Otherwise the settings of the servers xsp.properties file are used. There is a xsp.properties.sample file in your data directory in the properties folder which explains most settings.
Hint: Where to find the xsp properties file inside your NSF with the package explorer:
If you change the settings in the xsp.properties file on your server there might be some effects you never wished for... such as:
xsp.client.script.dojo.version is set to 1.3.1 and your XPages are coded for version 1.5.
xsp.partial.update.timeout is set in the servers properties file to 1 and you wonder why you have timeouts?
xsp.session.transient is set to true and you lose objects.
xsp.redirect is set to true and your requestScope does not work completly..
We even had problems with different
xsp.theme defined. But this is still a mystery.
…. and many more.
After digging our way through all these problems, we finally have a standardized xsp.properties file. By the way, please don’t try INOTESDISABLEXPAGECMD=1 in your notes.ini
We recommend to take a look in the IBM press book "XPages Portable Command Guide" (ISBN: 0-13-294305-0). It describes many xsp properties and some notes.ini parameters and is very helpfull to get a basic information level for administrations to configure a xpages enabled web/domino server. Also it gives some hints on how to monitor xpages enabled web servers and to scale their memory.
How might a xsp properties file inside a NSF look