Blog Entry

richardbliss's picture
blog
Reads:

7695

Score:
0
0
 
Comments:

5

Stubbing in GroupWise 8. Tread carefully

Author Info

28 October 2008 - 9:19am
Submitted by: richardbliss

(View Disclaimer)

Stubbing will be introduced in the new GroupWise 8 product. Developed in conjunction with a Novell GroupWise partner, there are a lot of questions about what stubbing really is and should a GroupWise admin deploy it. Here is an attempt to explain.

Stubbing takes a GroupWise message, moves it out of the GroupWise message store and places it in a 3rd party repository, usually an email archiving system.

Then, a tag/flag/stub is left in GroupWise that appears in the GroupWise client. When a user clicks on the message in their client, the stub redirects the client to pull the message from the archive system, rather than from the GroupWise message store.

Stubbing became popular with Microsoft Exchange because message stores within the Exchange system became to large, introducing instability. Stubbing was seen as a means of reducing the message store but keeping the enduser experience the same.

Now Microosoft has begun to recommend against stubbing. The promise of more stable systems has become offset by a new set of problems. Here is the link for Microsoft recommending against stubbing.

http://technet.microsoft.com/en-us/library/cc671168(EXCHG.80).aspx

Be very careful when deploying a stubbing solution. Stubbing is not for everyone and can have some unexpected side-affects that can impact your GroupWise system.

1. Stubbing is only available in the GroupWise Windows client.
This means that a stubbed message will appear in the Windows client and the message body will be able to be retrieved, but users of the Mac or Linux client will not be able to access the message in GroupWise.

BlackBerry users and those using GroupWise mobile server will not be able to access the message.

WebAccess users will not be able to access the message.

2. Irreversible - If you stub a message or a large number of messages, those messages are removed from the GroupWise message store and placed in a 3rd party repository. If the decision is made to no longer use stubbing, those messages cannot be put back.

Kudos to Novell to keep GroupWise current with Exchange, but a warning to GroupWise administrators. Be very careful about using stubbing.

Richard Bliss
More comments can be read at http://gwbliss.blogspot.com

Here are some things to co


Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.




User Comments

Anonymous's picture

Bummer

Submitted by Anonymous on 28 October 2008 - 10:51am.

I was really hoping that the stubbing feature would work through WebAccess in addition to the Windows Client. That would have finally given us a path to get a way from using GroupWise Client Archives and allow access for our users to their archived email when they weren't logged into our intranet. Oh well.

richardbliss's picture

Web access but not WebAccess

Submitted by richardbliss on 28 October 2008 - 4:12pm.

If you deployed an Archiving solution with Stubbing, even though you wouldn't be able to see your stubbed email through the WebAccess Gateway, you would probably still be able to access your archive through the web since the stubbed messages will be placed in an archive system that is accessible from the web.

This means you will have web access to your email but not using WebAccess Gateway to get them.

Anonymous's picture

Thats is just fabulous!

Submitted by Anonymous on 29 October 2008 - 6:33pm.

Now I can tell clients that if they want to use this they have to get familiar with two and more then likely very different web interfaces when on the road.

Are you kidding me?!

Anonymous's picture

Already tried that

Submitted by Anonymous on 30 October 2008 - 9:26am.

My org already tried that (GW Webaccess plus the web "Archive" link within Webaccess, which just goes to a separate web interface) with a 3rd-party solution and user feedback has been very negative. We quickly learned just how many people use and depend on Webaccess (more than we ever thought).

FlyingGuy's picture

What is the point....

Submitted by FlyingGuy on 28 October 2008 - 11:07pm.

Messages not available for:

- Linux Client
- Mac Client
- Web Client

This is totally and completely useless. I dont have a single client that does not use the web interface. I don't have a single client that does not have at least one non-windoze machine.

Why on earth did Novell waste precious programmer time and money to implement this? Arguably they did it with "a partner", but I doubt the "partner" did it through OLE which is the current client side programming interface.

More waste of time and resources when there are so MANY other things that need to be accomplished. The GW database engine has been rpoven over and over again to handle HUGE mail DB's the sizes of which would cripple Exchange.

I have a client that has an ARCHIVE that is over 30 gigs! It would be very nice to be able to access the archive from the web interface. How about spending some programmer resource on that. The POA knows how to access an archive, it just needs to be able to see the thing, which means, yeah you guessed it, the archive needs to be stored on a server.

© 2013 Novell