1. Liferay Portal
and
Red Hat SOA Platform
working together
Henri Sora; Director, Technology & Services
Jouko Pirinen; Senior Software Developer
24.4.2012

2. Two extranets
Project one Project two
- One integrated - One large extranet
dashboard to use a ERP - Offer calculation
and multiple CRM - Project information
systems together
- Construction
- A business critical tool
material acquisition
for day to day
operations of the client - Interfaces two
organizations external applications
- Two-way SMS and e-
mail applications

3. Business Problems & Project Scope
Project one Project two
- Ambientia replaced an - Ambientia replaced
older system that did manual work but the
not perform well (no actual project was
knowhow, no green field
maintenance, aged development
architecture) - The client wanted to
-The client 1) boost sales and to 2)
organisations needed to guide product selection
integrate 1) order and of its sales force
2) problem tickets

4. Technology
Liferay Portal
• Three-tier application using
Liferay as infrastructure
JBoss SOA Platform
• Integration interfaces
• Asynchronous queues
Red Hat Enterprise Linux
• MySQL
• Linux platform in overall
Vmware VSphere
• Virtual Infrastructure

5. Application Architecture
Liferay & portlets
- Full MVC architecture of the actual application
- Model: Service Builder
- View: JSP & Alloy UI
- Controller: Spring controller
- Liferay’s organization features
Red Hat SOA Platform
- Integration to external systems
- Client specific API’s for certain integrations
- Handles synchronous and asynchronous queues

6. Project 1, Architecture

7. Service Architecture 1
https://super.ambientia.fi/display/FNE/Palvelun+arkk

8. Service Architecture 1
https://super.ambientia.fi/display/FNE/Palvelun+arkk
 Actual application logic

9. Service Architecture 1
https://super.ambientia.fi/display/FNE/Palvelun+arkk
 Asynchronous off-loading
 Synchronous Call

10. Service Architecture 1
https://super.ambientia.fi/display/FNE/Palvelun+arkk
t
al e
os
be t th
m
ld bu
ou P
in l c A
yt co SO
an oto as
pr W
g


11. Project 2, Architecture

12. Service two
Uses similar
architecture as
previous
project also
- queues
- SOAP
- SMTP
- IMAP
Integration
targets
- SMS
- E-mail
- ERP
- CRM

13. JBoss SOA Platform tools used
- JBoss Developer Studio
- Content Based Routing
- JBoss messaging
- JMS
- Asynchronous and Synchronous model
- Smooks Transformations
- JBoss Web Service API
- Some custom made actions

14. Liferay & Spring tools used
Liferay Spring
- Liferay 6.0 - Spring Portlet MVC
- Portlets - Injections
- JSP & Alloy UI & Velocity - Controllers
- Service builder - Multipart (file upload)
- Domain + service layer support
- Liferay permission - Handler mappings
checking utilities - Parameter Handler
(users, roles, inheritance) Mapping
- Organization methods - Dependency Injections

15. The Combination

16. Benefits of the combination
• Loose coupling with the app and the ESB lead
to larger development team, and therefore,
faster development
• No loss of information while having downtime
• Client specific interfaces that are unified at
ESB
• New interfaces and protocols are almost
trivial
• Asynchronous queues and handle peaks

17. Problems during the projects
Project Management
- Change management
- UI models compared to IKIWISI
- Interfacing systems that were not ready at the
time…
Technology
- UI – not the technologies itself
- JavaScript and browser compatibility
- Complex queries with Service Builder  smaller
chucks combined to end results

18. Conclusion
- Both clients are still active.
- Both systems can be quite easily maintained
and changed because of the architecture
- The systems can handle variant load without
performance problems
- JBoss SOA Platform and Liferay prevented us to
write infrastructure code
- We are positive about the tools and eager to
work with them in the future also.

19. Questions?
Twitter: @henrisora

20. Thanks
Twitter: @henrisora