The document discusses Novell's mobile collaboration products and roadmaps. It summarizes Novell GroupWise Mobility updates through 2013 which focus on quality, new device support, and scalability. It outlines plans for the "Eenou" release in early 2013 to include task management and ActiveSync protocol updates. "Black Forest" later in 2013 will improve GroupWise integration and scalability. It also summarizes Novell Messenger features and roadmaps including multiple device connections, and looks at supporting technologies like Novell's Push Notification Service.

1. Mobile Collaboration
Data Synchronizer and Messenger Futures
Nadeem Ahmad Nazeer Kai Reichert
Distinguished Engineer Senior Product Manager Collaboration
kreichert@novell.com
nnazeer@novell.com
Dirk Giles
GroupWise & DataSynchronizer Engineering
dpgiles@novell.com

2. Introductions

3. Agenda
• Mobile world
• Novell GroupWise ®
– Mobility Service
– WebAccess
– Administration
• Novell Messenger
– Device Applications
– Multiple Connections
• Mobility Support Technologies
– Novell Push Notification Service (NPNS)
3 © Novell, Inc. All rights reserved.

4. Mobility
4 © Novell, Inc. All rights reserved.

5. Novell GroupWise and Mobility
®

6. Mobility and Data Synchronizer…
moving forward
2012 2013 Future
Mobility 1.2.x Updates Eenou (Mobility): Next:
• Quality • Scalability • Shared Items
• New Devices & OS support • ActiveSync Protocol Update • Appliance Deployment
• Device Limits • Tasks • Scalability
• Scalability • New Device Support • Filtering
• Usability • Monitoring • Failover
• Diagnostics • ActiveSync Protocol
• Device Quarantine Update
• Quality • Quality
Black Forest (Mobility):
• Scalability
Data Synchronizer
• GroupWise Integration
• Quality
Fox (DataSync):
• Partner Specific
Development
* Features under consideration
6 © Novell, Inc. All rights reserved.

7. Data Synchronizer Today and
Tomorrow
Today: Tomorrow:
Data Synchronizer serves Application integration will
as the vehicle for both continue to be delivered
mobility services and through the Data
application integration Synchronizer product line
Mobility services will be
split off to facilitate a more
streamlined and scalable
architecture
7 © Novell, Inc. All rights reserved.

8. The Road to Eenou
Mobility Updates 1.2.x
Update 4 Update 5
• SLES 11 SP2 support • New device and OS support
• ZenWorks Mobile • Monitoring and health preview
Management support
• Quality and performance
• Customer-reported issues enhancements
Additional Changes:
• Improved data retention policy
• Performance improvements
• Logging optimization
8 © Novell, Inc. All rights reserved.

9. Eenou Milestone – 1st Half 2013
ActiveSync Protocol 12.1
MDM compatibility / device compatibility / device deployment
– Email, calendar, contacts, tasks
PIM Message Bus
Double devices, performance and load
– Directly send and receive events, Single-purpose
database / no sync engine
Improved address book & contact management
Monitoring and Diagnostics
Task support
9 © Novell, Inc. All rights reserved.

10. Integrations and Improvements
(“Black Forest”) – 2nd Half 2013
• Align with GroupWise Windermere
• Scalability
• Mobility service management interface (REST)
• GroupWise interaction interface
– GroupWise web admin integration
– GroupWise client and WebAccess integration
• Update ActiveSync protocol
• Preview shared items support
10 © Novell, Inc. All rights reserved.

11. Data Synchronizer
Business Benefits and Futures
Enterprise data Delivers major
available everywhere application integrations
Data Synchronizer development is based on customer and
partner requirements for specific connectors.
Current Connectors
– Novell Vibe – Microsoft Dynamics, Opentext
– SharePoint, Salesforce.com, SugarCRM – SAP CRM, etc. (under
development by partners)
– Easy Archive, d.velop
11 © Novell, Inc. All rights reserved.

12. Monitor Demo

13. Mobility with GroupWise ®
• WebAccess Templates
– Supports iOS 6
– Updates for Android support
• Web-based Administration
– RESTful API
– Use browser to administer
– Can run on an iPad!
13 © Novell, Inc. All rights reserved.

14. Novell Messenger

15. Current Messenger Architecture
Directory
Mobile
User Authentication &
FIREWALL
Settings
Internet
Messaging Agent
Home
Archive Agent
Storage
Remote Office
15 © Novell, Inc. All rights reserved.

16. Novell Messenger…
moving forward
2012 2013 Future
Messenger Dillon: Eaglewood: Next:
• iPhone app • Web client • Shared History
• Android app • AD Integration* • File Transfer
• Multiple Connections • Web Administration* • Simple desktop share
• Quality and performance • Quality and performance • Integrations
– XMPP
– MS Lync
• Quality and performance
* Features under consideration
16 © Novell, Inc. All rights reserved.

17. Novell Messenger
Dillon features
• Mobile Apps
– iOS
– Android
• Multiple device connections (multiple client support)
17 © Novell, Inc. All rights reserved.

18. Mobile Messenger Demo

19. Novell Messenger
Discovered Issues
• iOS Devices and Backgrounding
• Push Notifications
19 © Novell, Inc. All rights reserved.

20. Supporting Technologies

21. Push Notification Service?
21 © Novell, Inc. All rights reserved.

22. Why we need it?
• Single mobile app for all customers
• Simple message payload
• Abstraction over different push providers
• Ease of deployment (service and app)
• Single certificate for all push notifications services
• Sending messages to multiple platforms
22 © Novell, Inc. All rights reserved.

23. Architecture - Design
23 © Novell, Inc. All rights reserved.

24. Sign a Secure Certificate
Two options:
1. Create a new private key
2. Import an existing key
24 © Novell, Inc. All rights reserved.

25. Certificate Portal
All Fields are pre-populated
25 © Novell, Inc. All rights reserved.

26. Implementation Considerations
• Data privacy / Security
– Data passes through Novell and Apple services before getting to device
– Allow the customer to decide what type of data is in a notification
• Performance
– Batch requests to NPNS
• Notifications are messages to the user that there is
something new
– APNS will only store and forward one notification (last one received)
– APNS payload is restricted to 256 bytes
– Take away: the server should store the new data and send a notification
with a summary (based on privacy settings).
– The application should retrieve the data from the server when it comes
back into the foreground
26 © Novell, Inc. All rights reserved.

27. Messenger NPNS Configuration
27 © Novell, Inc. All rights reserved.

28. Demo

29. Questions?

31. This document could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein. These changes may be
incorporated in new editions of this document. Novell, Inc. may make improvements
in or changes to the software described in this document at any time.
Copyright © 2011 Novell, Inc. All rights reserved.
All Novell marks referenced in this presentation are trademarks or registered trademarks of
Novell, Inc. in the United States. All third-party trademarks are the property of their respective
owners.