Is OpenCms a right tool to implement a restricted area of a web page? We say - "Yes", for sure, because we successfully use it in a wide range of our projects. "Restricted area of a web page" is a rather broad concept. It may have different requirements for an e-commerce solution, a management panel of an on-line service or an external web-based CRM-module connected to back-office services. But there are several common challenges for which solutions are available. In this session common problems and solutions for topics like user management and registration, customer communications, integration with external and legacy systems, access rights management and more will be explained. One example shown will be the CallbackMaster project. It is a smart click-to-call widget based on OpenCms which automatically determines the level of engagement of your website visitors and measures the amount of time potential clients spend on your website. At the right moment it offers the visitor an option for a free call back from a company representative.

1. >1
Restricted web page areas
with OpenCms
OpenCms Days 2015
Alexey Chirkov
ITDT Ltd.
Russia

2. > 2
Agenda
Restricted web page areas with OpenCms
 Definitions and Requirements
 Typical Use Cases
 Problems and Approaches
 Examples and Demo
 Future development and dreams...

3. > 3
Definitions
 What is «Restricted Web Page Area» (RWPA)?
 What forms of RWPA do we have?
 B2B, B2C, G2C etc.
 How we do get an access to RWPA? What resources
can we access?
 Web browser
 Cooperative access

4. > 4
Definitions and Requirements
Web Page
Restricted
Web Page Area
Simple mode
Extended mode
Internet/
Intranet
Business Applications and Services
?

5. > 5
RWPA implementation
problems
 How to get robust but flexible security system?
 Which technologies used?
 How to store and process different resources types?
 Is it possible to use common interface for end-users
and managers?
 How to provide integration services?

6. > 6
Restricted Web Page Requirements
End-user interface
Simple mode
Extended mode
Management
Interface
Admin Interface
User Interface Content/Data
Documents
Images
Reports etc
Access
Control
Infrastructure: Web server, Application server, Load balancing, HA etc...
DB_1
DB_2
DB_n
Secured / Convenient / Flexible
Internet/
Intranet
Integration
+

7. > 7
How to cook it?
Secured, Convenient, Flexible...
… but how to cook it?
Magic cauldron

8. > 8
Restricted Web Page Development
(Tasks)
 User interface design and development (CRUD)
 Data model design
 Domain model (documents, objects)
 Data store (database)
 Services
 Access control
 Search (Indexing)
 Admin (Config) etc.

9. > 9
Choice technologies problem
ExtLib
Bootsrap
ASP.NET
User Interface Business Logic Data source
Bootstrap + Spring MVC + PostgreSQL.
...
Spring MVC
Zend Framework
.Net
...
MSSQL
PostgreSQL
MongoDB
...
ASP.NET + .Net framework + MSSQL
... ... ...

10. > 10
Specified technology stack
Bootstrap + Spring MVC + MySQL via Spring Framework JDBCBootstrap + Spring MVC + MySQL via Spring Framework JDBC
JSF + Spring + PostgreSQL via JPA
Does OpenCms suit requirements?

11. > 11
Does OpenCms suits
requirements?
Does OpenCms suits requirements?
 Reliable access restriction to protected resources
 Remote access using Web-interface
 Unified and convenient user interface
 Store and control different content type
 Platform reliability

12. > 12
Implementation open issues
The main implementation issues:
 How to implement end-user self-registration?
 Quick and convenient
 Robot protected.
 How to present resources in typical way?
 Is user interface enough user friendly?
 What about integration components?

13. > 13
Simple mode / Extended mode
Registration/Login
DocCenter
End-user InterfaceVFS
Database
Internet/
Intranet
Documents
Workspace
Management Interface
Restricted Web Page Area (OpenCms)
Access
Control
Integration Module 1
Integration Module 2
Integration Module n
Integration
+

14. > 14
Extended mode+
(High Availability and Scaling)
 Additional performance and high availability — not a
problem.
Node NodeNode
Node NodeNode

15. > 15
The theory is good...
 but what about practice?

16. > 16
Sample: CallbackMaster —
click-to-call widget
Include widget code
Access web page

17. > 17
Sample: CallbackMaster —
click-to-call widget
 Click-to-Call widget project:
 End-user registration and Profile management
 Widget configuration interface
 Call and payment reporting
 Integration:
 IP-PBX
 SMS
 Payment gateways and more

18. > 18
Sample: CallbackMaster —
Architecture
Registration/Login
(OAMP*)
Newsletter (OAMP*)
End-user Interface
PostgreSQL
Internet /
Intranet
Workspace
Click-to-call Widget Project
Access
Control
IP-PBX
Payment Gateway
SMS Gateway
Integration
+
UI: ADE+
Webform (OAMP*)
Click-to-call widget

19. > 19
CallbackMaster — Live Demo
 Click-to-call
 User interface sample

20. > 20
Sample: CallbackMaster —
Core and Modules
 OpenCms 8.5.2
 End-user UI (ADE+)
 User registration module (based on OAMP)
 Newsletter module (based on OAMP)
 Integration:
 IP-PBX
 Payment gateways: eWay,Robokassa
 SMS gateway: websms.ru

21. > 21
Sample: Results and Conclusions
 Convenient UI
 Robust framework
 Smooth intergration with third-party APPS
 Save Time & Cost
UI DataModel Integration
0
20
40
60
80
100
120
JSF+Spring+PostgreSQL
OpenCms+Spring

22. > 22
CallbackMaster: future development
Future application development tasks:
 Additinal language version
 Provide service to customers in other countries
 Multi-language content is native for OpenCms
 Migration to Opencms 9.5.2
 Make user interface more convenient
 This platform version provide such functionality

23. > 23
Anything to improve? Yes!
It would be great to have:
 Visual XML Schema-editor
 Compose and deploy Documents on fly
 Simple list and detail formatter auto-generation
 Non-blocking publication
 Indexing
 Immediate indexing
 Visual Solr configuration editor

24. Questions ???
Alexey Chirkov
ITDT Ltd.
Russia
alexey.chirkov@itdt.ru
www.itdt.ru
OpenCms Days 2015