Preparing for first class 12


Published on

Webinar presentation about the upcoming FirstClass 12 release by OpenText

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • HTML-5 – must be web-based experienceNo client; what users expect – UI will be familiar to any current user of web appsEases administrationEases development; developers can draw on more resources
  • Modular means 2 things:Organizations may not want all components (i.e. no mail)Need to be able to plug in external components
  • Great mobile experience is requiredHTML-5 Provides parity across devicesReduces development overhead… Which means more features, better quality
  • Scalability remains critical to the success of FirstClassThis is why FCWS is being delivered on ApacheFor very large sites, multiple FCWS instances may be clusteredOpenText is also looking to FC12 to drive product growth in the marketplace
  • Bridge gap between client & communities
  • As of yesterday, OpenText indicated that release is on-schedule for a May releaseThis will be FirstClass 12.0; additional features will be coming in service packs and 12.1
  • New Server is required to support FCWSNew IS and Desktop Client will focus on performance improvements & bug fixes; functionally similar to 11FCWS is the significant, new component
  • Service Packs for the highest-priority items (those that could not be completed in time for the FC12 release) will be released as soon as possible, likely this summer.12.1 will likely ship late Fall, 2013
  • If adding FCWS to a server running other FC components, should have capacity to allocate minimum of 1 CPU and 2GB RAM.Field data will need to be gathered to refine this recommendationMore will certainly be required for large sitesUse of Virtualization allows easy increases to CPU and memory; likely a good choice for FCWS
  • Preparing for first class 12

    1. 1. Preparing forFirstClass 12May 21, 2013Gary
    2. 2. Agenda FirstClass 12: Vision & Timeline Technical Considerations FirstClass 12 Overview Summary
    3. 3. Vision & Timeline
    4. 4. FirstClass 12: Vision
    5. 5. FirstClass 12: Vision
    6. 6. FirstClass 12: Vision
    7. 7. FirstClass 12: Vision
    8. 8. FirstClass 12: Vision
    9. 9. FirstClass 12.0 Release
    10. 10. FirstClass 12.0 Components FirstClass Server Internet Services FirstClass Client (desktop) FirstClass Web Services
    11. 11. FirstClass 12.0 Features FirstClass Web Services module New HTML5 client (desktop & tablet) Plugin support FirstClass API Integration of client and communityfunctions HTML document editor On-the-fly spell-check
    12. 12. FC12 SP1 / FC 12.1 FCWS-based WebDAV FCWS-based CalDAV Document co-authoring & versioning Enhanced document sharing Extended oAuth support Platform-specific mobile apps Forms engine / new Designer
    13. 13. Technical Considerations
    14. 14. Server ApplicationsFC ServerFC Internet SvcsFC Web ServicesFirstClass Client,iOS ClientTCP 510UDP 810SMTP, IMAP,POP, LDAP, …TCP 25, 143,110, 389…HTTP TCP 80, 443HTTP TCP 80, 443TCP 80, 443TCP 80, 443
    15. 15. IS Web Uses FirstClass Logins Rapid Web Designer Personal web publishing Home Page Construction Kit Custom IS templates Publishing FirstClass containers Android / Blackberry apps FirstClass Communities
    16. 16. Server CapacityMinimum Recs +1 CPU +2 GB RAM More for highconcurrency VM recommended
    17. 17. Other PreparationDNS / Subdomains New name for FCWS(webmail, mail, login, fcweb, etc.)SSL Wildcard certificate recommended
    18. 18. FirstClass 12 Overview
    19. 19. Summary
    20. 20. Who should adopt? Replacement for old web logins New students New staff Users not dependent on custom formsor RAD applications
    21. 21. Who should not adopt? FirstClass Administrators Power-Users Users requiring use of custom forms &RAD apps
    22. 22. Questions?Gary Falcongfalcon@aptiris.com404.377.9915 x44