12
Integrating with Zarafa Steve Hardy, Zarafa

Integrating with Zarafa

  • Upload
    zarafa

  • View
    1.381

  • Download
    0

Embed Size (px)

DESCRIPTION

Presentation of Steve Hardy about integrations with Zarafa at Zarafa SummerCamp 2011

Citation preview

Page 1: Integrating with Zarafa

Integrating with Zarafa

Steve Hardy, Zarafa

Page 2: Integrating with Zarafa

Integrating with Zarafa: API’s

• MAPI– Main interface– Allows full control of all

messaging functions– Has realtime

notifications– Bindings for c++,

python, php– Also secondary

functions like statistics, or synchronization

Page 3: Integrating with Zarafa

Integrating with Zarafa: API’s

• Z-Merge– Synchronization

framework– Server-to-server– Uses incremental sync

to do bi-directional sync– One-to-many

relationships possible for data

– Only Current implementation is SugarCRM

Z-Merge

Zarafa

Application

Page 4: Integrating with Zarafa

Z-Push 2.0: more integration possible

• Management will be done by WebServices– Allows policy

management from your application

– Allows remote wipe from your application

Page 5: Integrating with Zarafa

Z-Push 2.0: more integration possible

• Management will be done by WebServices– Allows policy

management from your application

– Allows remote wipe from your application

Presentation Z-Push

11:30, Track 1 (Sebastian Kummer)

Page 6: Integrating with Zarafa

• Overall MAPI coverage• Notifications (Allows realtime notifications into Python)• Added ICS interfaces• Zarafa-Archiver interfaces• Server statistics

• We have started to ship core components created in python– zarafa-msr is python– Parts of zarafa-archiver are in python

Additions to Python API

Page 7: Integrating with Zarafa

Integrating with Zarafa: Plugin frameworks

• Zarafa WebAccess– Plugins already

available:• S/Mime e-mail

encryption• Alfresco• Z-Push device

management

Page 8: Integrating with Zarafa

• Various ways of adding functionality• Packaging mechanism will be comparable to Zarafa WebAccess• Two parts

– Server / backend (PHP)– Client / frontend (Javascript)

• Most extensions will mainly use client-side (javascript) extensions• Server-side (PHP) extensions will remain fairly much the same as in

Zarafa WebAccess

Zarafa WebApp extensions

Page 9: Integrating with Zarafa

• Various ways of adding functionality• Packaging mechanism will be comparable to Zarafa WebAccess• Two parts

– Server / backend (PHP)– Client / frontend (Javascript)

• Most extensions will mainly use client-side (javascript) extensions• Server-side (PHP) extensions will remain fairly much the same as in

Zarafa WebAccess

Zarafa WebApp extensions

WebApp development

13:30 Track 1: Creating Addons with Zarafa WebApp

Page 10: Integrating with Zarafa

• Insertion points– Inject your code into various points in the existing WebApp– Allows modification of behaviour

• Bidding– Each extension (even the standard parts of WebApp) can ‘bid’ to deliver

functionality– Example:

• Normal e-mail dialog has bid of ‘1’• Extension overrides standard email dialog by bidding ’10’• Another extension bids ‘100’ • Result: Dialog may be openend by the highest bidding extension

• Widgets– Simple separate widgets that can show in sidebar or home screen

WebApp extension patterns

Page 11: Integrating with Zarafa

Sencha-based web application

• Delivers easy-to-create UI

• Various sencha apps already available

• Plug your widget directly into WebApp

Page 12: Integrating with Zarafa

• Talks this afternoon from various communities– Fedora– Ubuntu– SuSE– Debian

• Starts at 15:00, track 2

Integration of Zarafa in distributions