BBM Enterprise registration and archiving process

  • 7022055
  • 10-Oct-2017
  • 30-Oct-2017


Retain 4.1+
BBM Enterprise
Windows and Linux


How do I troubleshoot archiving for BBM protected?


This article is written assuming that you have already followed all of the steps in the Retain manual for RetainBAAS for BBMP. The logging referenced in this article is found in the RetainServer log dated for the specific day you are troubleshooting. Retain log location

After you have added entitlements in the BAAS admin page, Blackberry sends the registration information to the Retain server and the Blackberry device, this is known as the intersect notification.

If you can see that the device has been added to the Blackberry Device Management page, then BAAS has successfully connected to the Retain server.

This is logged as:
[ajp-bio-48009-exec-1] [TRACE] AsyncAuthenticationProvider: User [offline/admin] logging in using application cd9abe4d-aad7-48bf-8cc2-dda51d6d9935
[ajp-bio-48009-exec-1] [TRACE] IntersectNotificationController: handleIntersectNotification called with notification = IntersectNotification [cause=ServiceChange, devicePin=[PIN12345], status=active,
oneTimePassword=[xyzxyzxyzxyzxyzxyzxyzxyzxyzxyzxyzxyzxyzxyzxyzxyzxyzxyzxyzxyzxyzxyzxyzx], tenantId=[abcdefghi-1234-5678-1234-xyzxyzxyzxyx], userEmail=[], displayName=null]
[ajp-bio-48009-exec-1] [TRACE] IntersectNotificationController: handleIntersectNotification exit

The BBM enteprise mobile app should also show that the device is now set to archive messages. This app will show this as a policy to archive.

When the Retain server and the BBM enterprise app both know about each other and they are supposed to archive, messages should start injecting into the Retain server.

This is logged as:
We will attempt to archive [5] message now.