VDS Logging

The astute observer will notice that the most recent releases of SAP’s NetWeaver Virtual Directory Server are missing the logging control buttons. There is a  very good reason for this seemingly missing functionality.  Much like NetWeaver Identity Management, VDS is also merging into the NetWeaver, specifically NetWeaver’s logging framework.  This means that there is not a need to have VDS offer internal logging.

However, VDS also offers the ability to run in a “Standalone mode” which allows for VDS to run independently of NetWeaver.  If you plan on running in this mode you’ll need to take advantage of the following configuration tweak in order to access the logs:

Update the file standalonelog.prop that can be found in the Configurations folder.  If you do not have this file, information can be found in the SAP NetWeaver Idenity Management Operations Guide. This document can be found on SDN. The file is a basic text file that includes setting the log level and desired location of the log file.

Once this file is configured it needs to be placed in the Work Area folder (typically underneath the Configurations folder.  Note that creating this file will not bring the buttons back, it will only create the logs in the paths specified in standalonelog.prop.

From what I understand the internal log viewer will be back in the next Service Pack for VDS.  It will be good to have it back.


Perception of Risk is Influenced by Ease of Pronunciation

I missed this study earlier  (HT: Bruce Schneier).  The result is exactly what one  would expect.   There has always been a general distrust of the alien, fear of the unknown.  The impact on IT is that when they bring new items up for review they can expect higher scrutiny for anything containing hard to pronounce names.  Experience teaches us that most innovations fail so when we encounter something unfamiliar we consider it more risky.   Difficulty in pronouncing its name  amplifies this effect.   In fact this is why we have proof of concepts, pilots and test markets for innovations.   When faced with three choices to make under time pressure we will tend to choose the one that is most familiar because cognitively we map what is familiar to safe.  Difficulty in pronouncing a name, can also slow the time it takes process the choice.   Look how long it took Linux to gain acceptance in the executive suite despite the cost differential and ease of pronunciation.  The experience of using it in the data center is now sufficiently broad that except in the most conservative companies, it is no longer considered risky.  Imagine how much longer it would have taken if the name was something like Lydrarjickavar.