"Looking to learn more about the different projects involved that make up Eclipse? We are running a series of free webinars to help you better understand how you can use the different Eclipse projects. Take a look and sign-up today."
Free Eclipse webinars via Eclipse in the News.
As noted in my previous post I have added the IBM SIP community as an extra community to my Sametime 7.5. One of my coworkers tried to do the same thing and it appears that if your IBM id is your e-mail address you should not append @<country code>.ext.ibm to your IBM id when signing in. Nice to know.
How nice is this! Now that we are running Sametime 7.5 internally I have configured an additional Sametime community by following the guidelines from Chris Pipin. This means that I now have my uncle from IBM in Denmark in my Sametime client as well. Nice! Only caveat is that you cannot lookup the address of the contact using the “Lookup…” button as you would expect. You have to simply enter the address, check “External address” and click the “Add” button.
There was a caveat for him to add me as well. My IBM id is “lekkim” but he has to append “@dk.ibm.ext” to the IBM id in order for him to find me.
Does anyone know it this means that bloggers can IM each other using the IBM Sametime community? I’m up for the test so feel free to try and add me (lekkim@dk.ibm.ext) to your Sametime client.
Happy IM’ing!!
"Validation reports whether a document adheres to the rules specified by the schema. Different parsers and tools support different schema languages such as DTDs, the W3C XML Schema Language, RELAX NG, and Schematron. Java 5 adds a uniform validation Application Programming Interface (API) that can compare documents to schemas written in these and other languages. Learn about this XML validation API."
Well I took the plunge and upgraded our internal Sametime 3.1 server to Sametime 7.5 and it was almost a dissapointing experience. Not a single issue. Not one… It was super easy – click, click, click and the server was upgraded without any problems – all users retain their buddylists and some hasn’t even noticed the upgrade. Only a few users have had the new client installed but we will be rolling the client out soon as well.
Although it was a very pleasant experience I did notice two things:
Apart from that – Happy Sametime Friday!! 🙂
I have got to get those abstracts for Lotusphere 2007 submitted over the weekend. As mentioned yesterday by Rocky Oliver there’s still time – deadline is 15 September.
"No matter where you are IBM Lotus Sametime V7.5 can find you with its new location awareness feature. Learn about the server-side and client-side mechanisms for location awareness and get a peak at a plug-in that uses location data to bring you local attractions."
One of our customers are experiencing some problems with some databases not replicating correctly. It might be connected to a recent upgrade to Domino 7.0.1 from 6.5.4 but we’re not sure. The problems can some times be fixed by clearing the replication history and manually replicating but that’s not really a long term solution.
To further troubleshoot I enabled the console log (set config console_log_enabled=1) and summary replication logging (set config log_replication=5) in the notes.ini via the Domino console. At the next scheduled replication I observed the strange messages (in bold below):
06-09-2006 10:49:35 Pushing dbname.nsf to servername/Organization dbname.nsf 06-09-2006 10:49:35 0 Bytes Saved from Field Level Replication 06-09-2006 10:49:35 0 Bytes Saved from Field Level Replication 06-09-2006 10:49:35 0 Bytes Saved from Field Level Replication Unambiguous Note NO Place Holders Unambiguous Note NO Place Holders Unambiguous Note NO Place Holders Unambiguous Note NO Place Holders Unambiguous Note NO Place Holders 06-09-2006 10:49:36 0 Bytes Saved from Field Level Replication 06-09-2006 10:49:36 0 Bytes Saved from Field Level Replication 06-09-2006 10:49:36 0 Bytes Saved from Field Level Replication 06-09-2006 10:49:36 0 Bytes Saved from Field Level Replication
I have never seen these messages before and it seems like they only appear with the databases we are having problems with.
If anyone has any information about these messages that they would be willing to share I would be a happy camper. I guess it’s also one of those times to be grateful that one can call Lotus Support!
I have submitted a patch to Simon Brown (author of Pebble) to make it possible to handle additional filetypes using the core Pebble 2.0 framework. I have done it by modifying the net.sourceforge.pebble.domain.FileMetaData and moving the information about the possible filetypes to an enum (net.sourceforge.pebble.domain.TypeEnum). This enum may be subclassed in my application which is built upon Pebble to provide support for additional filetypes. I have used the enum from Jakarta Commons Lang because Java 5 enums doesn’t support subclassing.
The filetypes usable by the Pebble instance is configured using a factory (net.sourceforge.pebble.domain.TypeEnumFactory) which is instantiated and set in the net.sourceforge.pebble.Configuration object using the applicationContext-pebble.xml file. The actual bean set is configured from the included pebble_import_factories.xml file since I need to replace the factory easily from my build.xml. I also need to replace the FileDAOFactory so that bean definition has been moved to the xml-file as well.
The applicationContext-acegi-security.xml has been modified as well to import a bean instance from pebble_import_acegi.xml since I also need to be able to easily add something here from my build.
I have also added the possibility of specifying whether the individual filetypes may be managed and whether new directories may be added to the containing filetype directory by the user.
I have put the patch file itself on my blog for downloading. The patch should be applied to the Pebble 2.0-RC2 source tree.