Vertigo and GroupWise Events



Last Monday we've released Vertigo

Apart from a couple of bug fixes, we've added a couple of new features there too.

There's a new GMS webtab for managing your GroupWise Mobile Server from within Vertigo. We've also removed the 'Color' column for categories, because all categories now have the same color, like how they are shown in the GroupWise Win32 client.

The most exciting new feature is the one dealing with GroupWise Events. Any third party application can register for 'Events' for selected mailboxes:

"GroupWiseRegistered Web Services Events is an extension of GroupWise Web Services that provides access to events or actions that occur on a GroupWise user's mailbox. Using events, developers can be notified in real time when a specific event occurs on a mailbox. In other words, GroupWise Web Services Events is a Web Service (similar to SOAP) that allows you to programmatically configure and retrieve specific GroupWise Web events that have occurred on a user's mailbox."

For example, if you want to track when an item is deleted in a GroupWise user's mailbox, you create an Event Configuration that tracks deleted items. During the configuration, you can provide an IP address and a port on which to be notified when the specific event occurs. After you're notified, it's up to the application to process the event records (stored in the user's database) accordingly and then to remove that event record.

A good example of third party applications which use events are the BlackBerry Enterprise Server for GroupWise and the GroupWise Mobile Server.

A typical GroupWise Administrator, though, has no tools (apart from an undocumented 'deleventsbykey=' switch in GwCheck to remove Events) by default to check:

    • Whether an event has been set up for a particular mailbox


    • What the name of that event is


    • Whether that event is enabled or disabled


    • What the persistence value is of that event, to know how long those event records should be stored on the POA


    • To which IP address port the event notification will be sent


  • Whether event records are still queued for a particular mailbox

He also has no tools by default to:

    • Delete an event


    • Modify an event (IP address, IP port, http, enabled status)


  • Remove event records

It all depends on what the 3rd party vendor provides there. Now, in the SOAP documentation one can read:

"Event records can potentially require lots of disk space. Therefore, event records need to be periodically removed from user's databases. By default, event records persist in a user's database for seven days. The persistence value has a range of 0-20 days."

Normally the third party solution should care of all this. But in case something goes wrong with that application or just for the purpose of monitoring events, we've added a new feature to Vertigo in order to be able to at least see what's happening under the hood and then to manage it, if needed. Have a look at these screen caps:

In this example you see that an event 'SC_RIM_BES_P1' has been setup for my mailbox. if you double click on this event, you can see for which Event Categories and Event Names this event has registered itself for. When a certain event takes place, an event record is created to track the change in the user's database. Event types fall into six categories: address book, address book items, folder, items, login, and proxy access.

So in this case all Item events are checked, most of the Folder events and all Address Book events. This is what the BlackBerry Server Enterprise server uses to send a new item to my BlackBerry device, to add a new folder to the device when created in my mailbox etc.

Regarding the GroupWise Mobile Server, sometimes it is nice to determine how things were setup, from the GMS documentation I copied this part:

4.1 Synchronization Problems With Two NIC Cards

If you have two NIC cards installed on the machine running GroupWise Mobile Server, there could be an issue if you are not synchronizing your devices. When a user provisions an account with a mobile device, the secondary NIC is added to the GroupWise Event Configuration. This address is used to slap (to send a notice that an event has triggered) the GroupWise Mobile Server machine when a change has occurred on a users account. Because the wrong address is used, and no slaps reach GroupWise Mobile Server. In addition, a synchronizing does not work if pull is used.

So, if we go back to the 'Event Details' screen you notice that the IP address port can be changed and written back to the event record. We will add a similar feature to the 'Multi User Mode' in a next version of Vertigo, so you can do a mass update if needed.

From the main screen, you can also click 'Event Records' and then see which Events are still in the queue to be processed by the third party application. In this example you can see that my BlackBerry Enterprise Server still has to process two new items which have been added to 'a' folder, probably my Inbox, and two items which have been moved to a specific folder. Also an Address Book modification is still waiting there to be processed.


How To-Best Practice
Comment List