Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (16)
En vedette
Similaire à Preparing for first class 12
Similaire à Preparing for first class 12 (20)
Dernier
Dernier (20)
Preparing for first class 12
- 1. Preparing for FirstClass 12 May 21, 2013 Gary Falcon gfalcon@aptiris.com
- 2. Agenda FirstClass 12: Vision & Timeline Technical Considerations FirstClass 12 Overview Summary
- 10. FirstClass 12.0 Components FirstClass Server Internet Services FirstClass Client (desktop) FirstClass Web Services
- 11. FirstClass 12.0 Features FirstClass Web Services module New HTML5 client (desktop & tablet) Plugin support FirstClass API Integration of client and community functions HTML document editor On-the-fly spell-check
- 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
- 14. Server Applications FC Server FC Internet Svcs FC Web Services FirstClass Client, iOS Client TCP 510 UDP 810 SMTP, IMAP, POP, LDAP, … TCP 25, 143, 110, 389… HTTP TCP 80, 443 HTTP TCP 80, 443 TCP 80, 443 TCP 80, 443
- 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. Server Capacity Minimum Recs +1 CPU +2 GB RAM More for high concurrency VM recommended
- 17. Other Preparation DNS / Subdomains New name for FCWS (webmail, mail, login, fcweb, etc.) SSL Wildcard certificate recommended
- 19. Summary
- 20. Who should adopt? Replacement for old web logins New students New staff Users not dependent on custom forms or RAD applications
- 21. Who should not adopt? FirstClass Administrators Power-Users Users requiring use of custom forms & RAD apps
Notes de l'éditeur
- 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