Blog Entry

My last couple of blog posts have focused on stubbing in GroupWise. What it is and if you need it.

Quick reminder: Stubbing is the ability to move a GroupWise message out of the GroupWise database and store it in a different Archive Database but have it appear in the endusers client as if it were still in the GroupWise database.

Stubbing for everyone

Stubbing is not a 'feature' of GroupWise but a capability used by 3rd parties to reduce the size of GroupWise databases and speed up access to the data that has been archived for compliance purposes.

This means most users won't ever see or hear about stubbing. But 3rd party Archiving vendors will be talking about it.

There are many ways to do stubbing, some more favorable than others due to limits of scalability, robustness, ubiquitous access from different clients, and full integration with GroupWise.

Novell has decided to look into putting the capability for stubbing into the next version of GroupWise. This project has been accomplished through the efforts of vendors and individual efforts. The Messaging Architects and GWAVA have both been involved with helping Novell bring this to market.

We know that Novell will get this right. When I'm asked if it will be available in GroupWise Bonsai, the answer is yes.

All of the vendor community is grateful to Novell for allowing this to happen. It wasn't that long ago that 3rd party assistance in the development of APIs and functionality for GroupWise was not possible. Now, companies like The Messaging Architects, GWAVA, Nexic, Advansys, Omni, Notify Technologies, and others are feeling the love from Novell to help make the GroupWise product and eco-system more successful.

Thanks Novell

Richard Bliss
Read my personal blog at http://gwbliss.blogspot.com