IRM integration with BlackBerry

Question

Hi,
Will IRM integration with BlackBerry be available in future releases of IRM? In that case, I would appreciate if you could tell me when you have planned to make this support available.
Thank you.

Answer 1

The IRM integration with Beehive was developed by and is maintained by the Beehive team, you may be able to get more help on the Beehive forums (http://forums.oracle.com/forums/category.jspa?categoryID=180). In the meantime I'll try to answer your query to the best of my knowledge.
The ClassificationId can be can be any text that you wish to use to identify the beehive classification e.g. Beehive Classification ID.
The ClassificationLabelName should be used to identify the Beehive classification to the user, it will be displayed in the IRM user interfaces in places such as the information bar.
The ClassificationSystemID and KeySetUUID values should each be set to their own UUID. You can generate one on linux using uuidgen.
The DesktopSyncURI and the DesktopURI values should be set to the IRM classification url e.g. https://irm.example.com:16101/irm_desktop.
The IrmDesktopServiceEndPoint should be set to the IRM server url followed by /irm_sealing/desktop_services e.g. https://irm.example.com:16101/irm_sealing/desktop_services.
The IrmSealingServiceEndPoint should be set to the IRM server url followed by /irm_sealing/sealing_services e.g. https://irm.example.com:16101/irm_sealing/sealing_services.
The IrmUserName should be a valid user that can log into IRM and Beehive
The IrmUserPassword should be the password for the above account
The other values can be left blank.
The ClassificationServices error from IRM is likely to be related to the xml file in the classification plug-in jar file. The most frequent causes of those have been where XML editors have reformatted the example configuration changing things like
<uuid>2de4af00-3b14-11de-8a39-0800200c9a66</uuid>
to
<uuid>
2de4af00-3b14-11de-8a39-0800200c9a66
</uuid>
The fussy XML parser then refuses to parse the UUID properly because of the surrounding whitespace. This is most likely to be a problem with fields that take UUIDs, so probably just worth checking those first.
Hope this helps,
James