Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

OpenCms Days 2015 OpenCms at erarta

Erarta is the largest private museum of contemporary art in Russia. Its permanent collection contains over 4500 works by more than 350 artists from all over the country. The museum is located in Saint Petersburg and has galleries in London and Hong Kong.

An OpenCms-based website for Erarta was launched in 2012 starting with version 8.0. This has grown to a portal with thousands of articles, images, videos, an online shop and a number of integration modules connected to ERP system, delivery services, payment gateways and more. Key factors to the success where the transparent and intuitive user interface, the flexible access control model as well as the easy integration of external applications.

This session will show how OpenCms was introduced at Erarta and how the application has been evolved over the years, including updates from 8.0 to 8.5 and soon to 9.5.

Ähnliche Bücher

Kostenlos mit einer 30-tägigen Testversion von Scribd

Alle anzeigen

Ähnliche Hörbücher

Kostenlos mit einer 30-tägigen Testversion von Scribd

Alle anzeigen
  • Als Erste(r) kommentieren

  • Gehören Sie zu den Ersten, denen das gefällt!

OpenCms Days 2015 OpenCms at erarta

  1. 1. >1 OpenCms at Erarta.com Alexey Asyaev ITDT Ltd. Russia The story of one project
  2. 2. > 2 ITDT Ltd.  Alexey Asyaev, CEO, ITDT Ltd.  Small team – (10+ team members)  Located in Kirov, Russia  Java development - (90%)  Stack 1: Tomcat + OpenCms - (50%)  Stack 2: LifeRay, Gate-in, IBM WebSphere (Portals), SOA, ESB and other integration technologies - (50%)  With OpenCms since 2006 ...and we love it!
  3. 3. > 3 Agenda: A story of one project  Some facts about the project  Starting point: what we have had  Requirements: what was specific  Problems and approaches  Key success factors  Few words about project management  Project evolution and migrations  Future development
  4. 4. > 4 What is Erarta today  ERARTA is the biggest global project in Russian contemporary art  Museum / Galleries / Shop  Projects / Exibitions / Concerts / Events etc. www.erarta.com
  5. 5. > 5 Erarta.com – web page Some clicks to get an impression... It was an actual state, what was in the beginning?
  6. 6. > 6 Erarta: what did we have at start Web Page 1 Web Page 2 Web Shop Web Applications Back Office Applications & Data ERP Ticketing system Misc... DB_1 DB_2 DB_n UnSecure / UnConvenient / Legacy and out-of-the date Lots of ideas, wishes, bug reports, not completed development etc.. Integration ?
  7. 7. > 7 Erarta: We have an idea! Wait: what's about content, our legacy content...? Just one step...
  8. 8. > 8 Erarta: Aims and Tasks  Reliable platform & stable application  Frequent changes of requirements  Design: look&feel  Business logic/functionality  Legacy content migration  Performance and ability of its increasing  Many integration tasks  Customer involvement in the planning and implementation
  9. 9. > 9 Erarta: Content migration Document_Type 1<xml?> VFS Document_Type 2 Document_Type n RDBMS RDBMS <xml?> <xml?> *.xls *.html Migration Utilities Legacy content Problem: How to get content migrated in time. New web page
  10. 10. > 10 Erarta: Content migration - challenge VFS Old content Time... Existent web pages New web page New content
  11. 11. > 11 Erarta: Requirements - content  Many different types of content (Documents)  Many forms of visualization of the same Documents  Data integrity and replication  Parent-child relations  Some data come from external data sources  Heterogeneous data model  Multi-lingual content  Integration with external applications
  12. 12. > 12 Erarta: Visualization - Exibitions
  13. 13. > 13 Erarta: Visualization - News
  14. 14. > 14 Erarta: Requirements - content  Many different types of content (Documents)  Many forms of visualization of the same Documents  Data integrity and replication  Parent-child relations  Some data come from external data sources  Heterogeneous data model  Multi-lingual content  Integration with external applications
  15. 15. > 15 Erarta: Data integrity and replication Document (Child) RDBMS Entity Document (Child) ERPDocument (Parent) RDBMS Document (Child) Entity VFS External Services Ext. ref. Replication (XML) Integration
  16. 16. > 16 Erarta: Aims and Tasks  Reliable platform  Frequent changes of requirements  Design: look&feel  Business logic/functionality  Legacy content migration  Performance and ability of its increasing  Many integration tasks  Customer involvement in the planning and implementation
  17. 17. > 17 Performance: how to measure and improve  Is it «fast enough» or «relatively slow»?  Measurement (Important: regular)  Tools – JMeter  Test plan (initial and further development)  Automation / Documenting Release 1 Release 2 Release 3 0 5 10 15 20 25 30 35 Test plan Functionality Jenkins
  18. 18. > 18 Performance: how to measure and improve  Measurement is done  We use proper tools  Regular / Automatic  Documenting  OpenCms tools  Think about content (image resizing)  Static Export  Flex cache  Built-in indexers (Lucene/SOLR) Develop Measure Tune What can we do if it's not enough?
  19. 19. > 19 Erarta: Aims and Tasks  Reliable platform & stable application  Frequent changes of requirements  Design: look&feel  Business logic/functionality  Legacy content migration  Performance and ability of its increasing  Many integration tasks  Customer involvement in the planning and implementation
  20. 20. > 20 Erarta: Requiremetns - collaboration  Collaboration  Iteration planning  Working on requirements  Issue tracking with Jira  Clarification of the requirements  Task estimations — budget/costs  Qualification and QA-cycle  Version delivery  Support (tickets)
  21. 21. > 21 Erarta: Aims and Tasks  Reliable platform & stable application  Frequent changes of requirements  Design: look&feel  Business logic/functionality  Legacy content migration  Performance and ability of its increasing  Many integration tasks  Customer involvement in the planning and implementation
  22. 22. > 22 Project life-cycle management  Quality  Unit testing (JUnit)  Functional testing (Selenium)  Source quality management (SonarQube)  Performance  Load & performance testing (JMeter)  Continuous integration  Jenkins  Issue tracking and more (Jira)
  23. 23. > 23 Project life-cycle management Jenkins Dev. Env. Hosting Environment Live Staging Testing QA Data replication Application deployment Continuous integration Issue tracking, release planning, support etc.
  24. 24. > 24 Erarta.com – web page - shop Some clicks to get an impression... JUnit – where it make sense in our case.
  25. 25. > 25 Project life-cycle management  Minimizing support efforts/costs  Minimizing deployment faults and system downtimes  Simplifying taking new crew members aboard Web Pages black box
  26. 26. > 26 Erarta: Aims and Tasks  Reliable platform & stable application  Frequent changes of requirements  Design: look&feel  Business logic/functionality  Legacy content migration  Performance and ability of its increasing  Many integration tasks  Customer involvement in the planning and implementation
  27. 27. > 27 Erarta: Integration  System MUST be OPEN  External Applications  ERP  On-line payments  Delivery services (transport)  Ticketing systems  Social media (registration/login)  ...
  28. 28. > 28 Migration: PRO and CONTRA  Why to migrate?  Performance  Bug fixes  Look&Feel...?  New features...?  How often it make sense to do?  Every version?  Every second...?  Never?  The best case: Customer understands the benefits from moving to a new version
  29. 29. > 29 Migration: from 8.0.4 to 8.5.2  New Form-based editor  Improved look&feel  Improved performance  In-place editor (ADE)  Improved site-map editor  SEO-friendly features  Aliaces, redirects etc.  Sitemap.xml, robots.xml generation
  30. 30. > 30 Migration: from 8.0.4 to 8.5.2 ToDo List (what we have done):  Testing of compatibility  with core API  standard update-wizard  Analysis and planning of “upgrade”  Application re-design (based on testing results)  Content migration (built-it XSLT-based functionality)  What was the most time/efforts consuming?  Data/Сontent?
  31. 31. > 31 Migration: why to move to 9.5.2  Flexible design (grid-based responsive layout) - (nice)  Extended in-line editor — ADE improvements  Do more with ADE (less Workspace manipulations)  Fast preview (many devices) — (convenient)  Improved galleries management (ADE)  Built-in spellchecker  Some other small and nice features...
  32. 32. > 32 Erarta: Future development  Mobile version (in progress)  Integration with social media (extended)  Integration with trading platforms (e-markets)  Increasing performance (clustering)  Integration with different ticketing systems  ... We are sure we will move to OpenCms 10.x.x and beyond
  33. 33. Thank you very much! Questions??? # Alexey Asyaev ITDT Ltd. Russia alexey.asyaev@itdt.ru www.itdt.ru

×