Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Zimbra Overview


Published on

Zimbra Overview, Zimbra Perspectiva

Published in: Technology

Zimbra Overview

  1. 1. Zimbra Overview<br />
  2. 2. Discussion Topics<br /><ul><li>Problem Statement
  3. 3. Product Overview
  4. 4. Demo
  5. 5. Architecture</li></li></ul><li>Low User Productivity Means Missed Opportunity<br />Decades-old technologies not built for today’s work<br /><ul><li>Hundreds of emails per day
  6. 6. Thousands of emails in inbox
  7. 7. Complicated multi-party meetings</li></ul>Common activities are awkward or poorly integrated<br /><ul><li>Can’t find people
  8. 8. Can’t link tasks to email and meetings
  9. 9. Can’t coordinate resources around documents</li></ul>Small email quotas kill productivity <br /><ul><li>Self-archiving
  10. 10. Not backed up in the cloud
  11. 11. Not portable from device to device</li></li></ul><li>Lack of Openness Results in Reduced Business Agility<br />Windows centricity limits platform choices<br /><ul><li>Limits on devices; users want any device, anywhere, anytime access such as iPad, smart phones
  12. 12. Unix and Mac users unsupported
  13. 13. Lack of consistent experience across Mac, Linux, Windows and online/offline</li></ul>Proprietary systems difficult to unlock <br /><ul><li>Few integrations to data and applications, such as travel, purchase orders, business analytics, HRMS and ERP</li></li></ul><li>SaaS Benefits are Not Available to Private Clouds<br />Client-side is very costly to manage<br /><ul><li>IT helpdesk filled with .pst issues
  14. 14. Plug ins are hard to roll out across 1000's of users</li></ul>First-gen email servers require armies of administrators<br /><ul><li>Hard to install
  15. 15. Hard to update
  16. 16. Hard to scale
  17. 17. Hard to keep running</li></ul>Non-portable applications create management headaches<br /><ul><li>Tied to on-premise deployments – impossible to move to the cloud or vice versa</li></li></ul><li>High Expectations for IT Administrators<br />Application Management<br /><ul><li>Simplified management – self service
  18. 18. Auto update
  19. 19. Fast deployment
  20. 20. Security and compliance
  21. 21. Security policy control
  22. 22. Device wipe
  23. 23. Service level</li></ul>End-user Requirements for Applications<br /><ul><li>Any device
  24. 24. Any application
  25. 25. Anywhere, anytime access
  26. 26. Access to rich content</li></ul>IT Admin<br />Datacenter Flexibility<br /><ul><li>Cost efficient, TCO Comparison
  27. 27. Deployment flexibility – on premise, hosted and hybrid
  28. 28. Storage and HA interoperability with cross application technologies</li></li></ul><li>End User: SaaS is Driving Change<br />
  29. 29. The Zimbra Advantage: Bringing SaaS to the Private and Public Cloud<br />Enhances user productivityby streamlining the interaction between people, applications & data<br />Productivity<br />Customer Momentum <br /><ul><li>Over 150,000 Organizations
  30. 30. 60M Commercial Mailboxes
  31. 31. 110 Countries</li></ul>Open Source Community<br /><ul><li>1M+ Server Downloads
  32. 32. 3M+ Client Downloads
  33. 33. 39K+ community members</li></ul>Provides an openand extensible collaboration platform that promotes universal access to applications & data<br />Openness<br />Simplifies platform management, reduces administration costs and embraces portability across Private & Provider Clouds <br />Manageability<br />
  34. 34. University of Pennsylvania Video: A Comparison of Admin Costs<br />Penn administration resources and costs charged back to departments<br /><br />
  35. 35. Zimbra Customers in 110 Countries<br />South Africa<br />Realty Services<br />Chile<br />Large Business<br />Command and Simulation Solutions<br />SMB & SME<br />Government<br />Education<br />Simon Fraser<br />Service Providers<br />Australia<br />
  36. 36. Product Overview and Demo<br />
  37. 37. VMware Solutions for IT as a Service<br />Secure, Manageable, Open<br />VMware EnabledPublic Clouds<br />IndependentPublic Clouds<br />Secure Private Cloud<br />VMware End-User Computing<br />View<br />Thin App<br />Zimbra<br />SaaS Applications<br />Other SaaS Providers<br />Application Access<br />VMware Cloud Application Platform<br />Google App Engine<br />VMforce<br />Spring<br />vFabric<br />Hyperic<br />Other cloud infrastructure providers<br />OherPaaS Partners<br />Application Portability<br />VMware Cloud Infrastructure and Management<br />vCloud Datacenter<br />vCenter<br />vShield<br />vCloud Director<br />vCloud Express<br />Application Mobility<br />VMware vSphere: Foundation for Cloud Computing<br />
  38. 38. Zimbra Web Client<br />Product Overview<br />iPhone<br />Android<br />Windows<br />Zimbra Server<br />ActiveSync, Mobile Browser<br />Zimbra Desktop<br />BlackBerry<br />SOAP<br />BES, Mobile Browser<br />Standards Clients<br />Apple Desktop<br />MS Outlook<br />Exchange<br />Server<br />Active Directory<br /> LDAP, WebDAV <br />POP, IMAP, CardDAV, CalDAV<br />MAPI<br />
  39. 39. Demo<br />
  40. 40. Zimbra Email <br /><ul><li>Web application surpasses traditional email client capabilities</li></ul>Conversations and Tagging<br />Fast, search-based inbox<br />More efficient management of larger inboxes, quotas<br />Cross-platform<br />Offline access with Zimbra Desktop<br /><ul><li>Mobile and Desktop sync</li></li></ul><li>Zimbra Enterprise Calendaring<br />Advanced web-based calendar<br /><ul><li>Manage multiple schedules
  41. 41. Peer free-busy lookup, resources and rooms
  42. 42. Easy sharing and full schedule delegation</li></ul>MS Outlook and Exchange interoperability<br />Mobile and Desktop sync<br />
  43. 43. Zimbra Briefcase, Collaboration and Sharing <br />Integrated file management and location-independent storage<br /><ul><li>Easily share files and jointly manage with peers
  44. 44. Check in/out all file types with version control </li></ul>More efficient, intuitive day-to-day collaboration<br /><ul><li>Share and delegate access to Inboxes, Contacts, Schedules, Folders
  45. 45. Publish publicly or to internal groups
  46. 46. Email workflow integration</li></li></ul><li>Extensible Framework and Workflows<br />Zimlets enable 3rd party web services and new applications to be integrated directly in Zimbra<br />Customers and partners may develop their own or use existing from the open source community<br />
  47. 47. Simple, Powerful Administration of IT as a Service<br />Proven open technologies, web-scalable architecture streamlines administration<br />On-demand user provisioning and policy management<br />Delegated role-based administration<br />Class-of-service and multi-tenancy<br />Quota and storage policy management<br />Automated service monitoring, failover and data backup<br />Critical infrastructure integration<br /><ul><li>LDAP, Active Directory
  48. 48. Archiving and Discovery
  49. 49. Anti-spam/virus</li></ul>On average, 33% less time is spent administering Zimbra than MS Exchange*<br />* Source: University of Pennsylvania case study Nov 09<br />
  50. 50. Customized Experiences<br />Change available features and quotas per user or groupwith class-of-service<br />Completely re-brand and re-theme the experience<br />
  51. 51. Architecture<br />
  52. 52. Zimbra Client Architecture<br />Mobile Clients<br />Desktop Clients<br />Browser Clients<br />ZimbraHTML Client<br />Microsoft Outlook<br />Zimbra Desktop<br />Apple; other Standard <br />Zimbra AJAX Client<br />BlackBerry<br />Apple<br />Zimbra OutlookConnector<br />IMAP, POP;Card & CalDAV<br />Zimlet AJAX Framework<br />Windows Mobile<br />Platform API Interfaces<br />BES<br />Zimlet WS Proxy<br />SOAP<br />RSS<br />POP<br />REST<br />LMTP<br />CalDAV<br />IMAP<br />Atom<br />ActiveSync<br />CardDAV<br />Zimbra MobileConnector for BES<br />Zimlet JSP Tags<br />Zimbra Collaboration Server<br />Postfix MTA<br />IncludingAnti-Spam and Virus<br />Jetty + JVM + OS<br />
  53. 53. Mailbox Server (MBS) Architecture<br />Zimbra Collaboration Server<br />(Jetty + JVM)<br />Directory<br />Message and File Store<br />Attachment Index & View<br />Meta Data<br />Free/BusyProviders<br />Search<br />DatabaseReliability<br />JDBC<br />3Rd PartyStorage System<br />StandardZimbraStorageSystem<br />MySQL<br />Lucene Index<br />Zimbra Journaling<br />Open LDAP<br />External LDAP<br />AutonomyKeyview<br />Microsoft Exchange<br />Active Directory<br />
  54. 54. Multi-Server Architecture<br />
  55. 55. Network Architecture<br />Standard Clients<br />(Thunderbird/Eudora)<br />Browser Clients<br />(Zimbra AJAX / HTML)<br />Load Balancer<br />Load Balancer<br />Message Labs<br />IMAP / POP Proxy<br />HTTP / SOAP Proxy<br />SMTP<br />LMTP<br />Postfix <br />MTA <br />Open LDAPDirectory<br />(Master + Replica Farm)<br />MBS Cluster<br />MBS Cluster<br />
  56. 56. Security<br />
  57. 57. Ports<br />
  58. 58. Network Security<br /><ul><li>SSL certificates</li></ul>Installation of SSL certificates recommended on load-balancers<br /><ul><li>HTTPS</li></ul>Webmail Client<br />Outlook Connector<br /><ul><li>IMAP and POP with SSL</li></ul>Configured on the Proxy system for secure access<br />
  59. 59. Domain level setup<br /><ul><li>Domain</li></ul>Each domain is its own entity.<br />Public Service Hostname can be setup for webmail, IMAP and POP access for each domain.<br /><ul><li>GAL (Global Address List)</li></ul>GAL lookups are restricted to the particular domain only.<br />External GAL integration can be setup on a per-domain basis. <br />GAL modes include Internal (Zimbra), External or Both<br />Each domain can point to a different external Directory<br />Galsync account.<br /><ul><li>Authentication</li></ul>Can be setup on a per-domain basis<br />Can connect to any directory service<br />Need Administrator level access on the external directory<br /><ul><li>Multi-Tenancy - BES</li></ul>Maintained with Domain restrictions.<br />
  60. 60. Sizing & Scaling<br />
  61. 61. Sizing Methodology<br /><ul><li>Sizing Questionnaire – gathering current environment data
  62. 62. Preliminary Recommendation</li></ul>Architecture recommendation<br />Server recommendation<br />Storage recommendation<br />Redundancy and High Availability<br />
  63. 63. Sizing Questionnaire<br />
  64. 64. Server and Storage Estimate<br />
  65. 65. Scaling ZCS<br />PROXY<br />StatelessRoutingTier:XML/HTTP,SSL/TLS,<br />POP, IMAP, …<br />MTA &AS/AVTier:SMTP, <br />AS/AV<br />Internet,Intranet<br />Internet(externalAS/AV)<br /><ul><li>Proxy Server</li></ul>Deployed in DMZ with internet facing IP address.<br />Handles all client connections – IMAP, POP, Mobile, Webmail, Offline clients<br />Proxy servers scale horizontally when there is change in traffic pattern. <br />Key reasons for adding a new server:<br />Increase in number of Active and Concurrent users.<br />Customers with large multi-gigabyte mailbox sizes.<br />MTA server<br />Deployed in DMZ with internet facing IP address<br />Can scale horizontally when increase in messaging traffic.<br />Responsible for Recipient validation and message delivery to message stores.<br />Key reasons for adding new server<br />Number of messages per user per day<br />Peak messaging traffic<br />Zimbra Confidential Information<br />
  66. 66. Scaling ZCS cont.<br />Mailbox Server<br />Stores all user mailbox data.<br />Deploy multiple mailbox servers and spread users across the servers.<br />Scales horizontally by allowing to add new mailbox server at any time.<br />Ability to store the mailbox data between fast and slow storage (HSM).<br />Key reasons to add a new mailbox server:<br />Number of users increases beyond the capacity<br />Rebalancing of users across multiple servers.<br />Mailbox/MetadataStore:<br />Index,<br />Folders,Tags,<br />Searches,<br />Zimlets,Etc.<br />Message/BlobStore:Network-AttachedStorage(HSM, Archiving,WORM, etc.)<br />Zimbra Confidential Information<br />
  67. 67. High Availability & Disaster Recovery<br />
  68. 68. <ul><li>“Single copy” failover (LAN/MAN)
  69. 69. Veritas, Red Hat Cluster Suite or VMware HA
  70. 70. Shared network storage (SAN, NAS, RAID)
  71. 71. Heartbeats & I/O barriers avoid “split-brain” </li></ul>Zimbra Collaboration Server<br />Zimbra Collaboration Server<br />…<br />Zimbra Storage<br />ZimbraStorage<br />HeartbeatProtocol<br />RHEL<br />RHEL<br />Shared Storage<br />ZCS Cluster Architecture<br />
  72. 72. Storage Level Snapshots<br />Storage level snapshots can be used take an image of the entire mailbox store.<br />In case of a disaster, you can use the snapshots and backups for faster recovery. <br />
  73. 73. SOAP APIs<br />
  74. 74. Zimbra SOAP APIs<br /> Zimbra provides a comprehensive set of SOAP APIs for user administration, provisioning, customisation and portal integration. SOAP APIs are available at:<br /> <br />SOAP API usage<br />SOAP ADMIN API - USE FOR PROVISIONING & ADMINISTRATION<br />SOAP CALENDAR API   <br /><br />
  75. 75. SOAP Admin API Sample Method<br />Creation of Accounts:<br /><CreateAccountRequest> <br /> <name>...</name><br /> <password>...</password>*<br /> <a n="attr-name">...</a><br /> </CreateAccountRequest> <br /><CreateAccountResponse> <br /><account name="{name}" id="{id}"> <br /><a n="...">...</a><br /></account> <br /></CreateAccountResponse> <br />Notes: <br />accounts without passwords can't be logged into <br />name must include domain (uid@name), and domain specified in name must exist <br />default value for zimbraAccountStatus is "active" <br />
  76. 76. Single Sign-on<br /><ul><li>Zimbra provides a pre-authentication mechanism to enable a trusted third party to forward authentication credentials to the Zimbra system. This enables the user not have to enter the login information twice.
  77. 77.  
  78. 78. Example Single Sign-on Flow:</li></ul>A portal application is accessed by the User<br />The application presents a “Mail” link.<br />Using our framework, an Authentication Token is created.<br />Secret keys are exchanged between the Portal application and Zimbra<br />Server computes Hash secret key and creates an authentication sequence<br />User is redirected to Zimbra mail app with this authentication token with secret HMAC key.<br />
  79. 79. Example SSO and API integration<br /><ul><li>A short movie showing an example integration done by Plymouth State University using Single Sign-on, Zimbra client and server SOAP APIs.</li></li></ul><li>Example SSO and API integration<br />
  80. 80. Branding & Integration<br />
  81. 81. Custom UI Skins<br />Skins, also known as themes, in the Zimbra Web Client (ZWC) are a combination of HTML, CSS and properties files that control the appearance of the ZWC application. The skinning system allows you to easily change the appearance of ZWC, for example, to use the logo and colors of your company or institution. You can create many different skins to provide your users with choices for the appearance of the application, or you can restrict users to a single skin to enforce brand identity.<br />
  82. 82. Customized Experiences<br />Change available features and quotas per user or groupwith class-of-service<br />Completely re-brand and re-theme the experience<br />
  83. 83. Flexible Branding Options<br /><ul><li>Zimbra-branded (default) skin by default, but Zimbra provides flexibility to change logo & font/background colors</li></li></ul><li>Skin Example 2<br />
  84. 84. Skin Example 3<br />
  85. 85. Integration: GAL & Auth<br /><ul><li>Simple admin console web wizard to configure global address lookups and authentication per domain</li></li></ul><li>Zimbra - Exchange Interoperability<br /><ul><li>Zimbra and Exchange users can share free-busy information
  86. 86. Works within the native UI of each product
  87. 87. Unified GAL (auto complete on compose, etc.)</li></ul>Active<br />Directory<br />Zimbra Server<br />Microsoft<br />Exchange<br />Zimbra<br />Outlook<br />
  88. 88. Migration<br />
  89. 89. Migration to Zimbra<br /><ul><li>Our tools can help with scenarios ranging from a small business up to a large service provider for full enterprise migration strategy.
  90. 90.  
  91. 91. For general migration scenarios:</li></ul>Consulting, best practices, sample scripts, and documentation provided<br />Supported migration formats include IMAP (email), CSV (contacts), iCal (calendar)<br />Imapsync – IMAP based tool used for migration of email<br />REST interface – import of calendar and contacts<br />Sun iPlanet calendar migration tool<br />Icalmig – Oracle calendar migration tool<br />For more information on migration visit the Zimbra migration wiki(<br />
  92. 92. Migration to Zimbra (cont.)<br /><ul><li>Our tools can help with scenarios ranging from a small business up to a large service provider for full enterprise migration strategy.
  93. 93.  
  94. 94. For Exchange / Domino / GroupWise migration scenarios:</li></ul>Zimbra has developed wizard applications that perform direct server-to-server migration at the individual or batch level for Microsoft Exchange, Lotus Domino and Novell GroupWise.<br />Outlook / Exchange a PST importer application is also available to allow end users and administrators to upload PST files to their ZCS mailbox.<br />
  95. 95. Migration Planning Overview<br /><ul><li>Customer Requirements</li></ul>Accessing Customer Environment<br />Workload and Traffic flow <br /><ul><li>Migration Strategy</li></ul>Quick Migration<br />Split-Domain migration<br /><ul><li>Test Migration</li></ul>Small, Medium and Large size mailboxes part of pilot pool<br />Determine the time for the migration<br /><ul><li>Go-Live Steps</li></ul>Communication Plan<br />Final Migration plan<br />
  96. 96. Split-Domain Migration<br />
  97. 97. Exchange Migration Information<br /><ul><li>General Migration guidelines:</li></ul>Primary bottleneck for migrating from Exchange can be Exchange I/O Subsystem.<br />Number of messages and size of the messages can impact the length of the migration<br />Have the users clean out Trash and Junk folders prior to migration. <br />NOTE: This is an optional step you can choose so that you are not migrating unnecessary data.<br /><ul><li>General Setup Guidelines:</li></ul>Use at least Windows 2003 Server to run the migration wizard with Outlook 2007 installed.<br />Migration Wizard must be joined to the customer’s domain and logged into that domain with Exchange Administrator privileges<br />Recommended for the migration server to be at the Customer’s site since MAPI calls are made to retrieve messages.<br />Ports 443, 7070 and 7071 are used for communication by the Wizard to talk to the Zimbra environment.<br />
  98. 98. Exchange Migration Execution<br /><ul><li>General Migration execution guidelines:
  99. 99.  </li></ul>Migration Wizard performs best with 3 simultaneous threads per instance.<br />You can run multiple instances of the migration wizard.<br />If an account migration fails, you can restart the migration by using the SAME original account login name.<br />
  100. 100. Reference Documentation<br />
  101. 101. Reference Documentation<br /><ul><li>Installation Documents</li></ul><br /><ul><li>Product Information</li></ul><br /><ul><li>Zimbra Technical Wiki</li></ul><br />
  102. 102. THANK YOU<br />