Using a Heavyweight Portal with FatWire Content Server Andrei Gologan London, June 10 th 2010
With group sales of EUR 17.92 billion in 2009 and 34,676 employees, the OMV Aktiengesellschaft is one of the biggest listed industrial companies in Austria and the leading energy group in the European growth belt.
in EUR mn EBIT Clean EBIT Income from ordinary activities Net income after minorities Net cash provided by operating activities Balance sheet total Stockholders`equity Number of employees 2) Group Sales 1) 1,374 9,363 41,282 21,376 3,214 2008 2,340 2,309 25,543 3,405 1) excluding petroleum excise tax 2) Petrom Employees 2009: 28,894 1,410 1,182 17,917 1,418 2009 572 34,676 1,847 10,035 21,415
Key companies and key subsidiaries of OMV Aktiengesellschaft OMV Aktiengesellschaft OMV Refining & Marketing GmbH (100%) Petrom SA (51%) OMV Exploration & Production GmbH (100%) OMV Gas & Power GmbH (100%) OMV Solutions GmbH (100%) Petrol Ofisi (41.58%) OMV Deutschland (10%) Borealis ( total 36 % )
Business segments of the OMV Group Exploration & Production Gas & Power Refining & Marketing incl. Petrochemicals
Refining & Marketing incl. Petrochemicals OMV market leader in Central Europe AT 1: including 577 Petrom filling stations 2: OMV holds 41,58% of Petrol Ofisi stakes as of 03/2010 Burghausen Schwechat BAYERNOIL 2.333 1 96 28 59 61 105 444 396 221 93 174 545 1 ~3.100 2 Arpechim Petrobrazi 111 1
Exploration & Production Worldwide activities
OMV Gas & Power Relevant Market
~ 410.000 pageviews/month
~ 260.000 pageviews/month
Main Intranet Sites
~ 940.000 pageviews/month
~ 1500 registered users
~ 750.000 pageviews/month
~ 8500 registered users
Online Platform Overview
OMV Online Platform is designed to deliver all OMV and Petrom corporate, country and intranet sites:
16 corporate an country sites
3.506.633 page views per month
1.050.000 sessions per month
5 production servers
1 editorial system
The main components of this solution are WebSphere Portal 6.1 and FatWire Content Server 7.5
There also thirty party components that have not been included in the scope of this presentation like: Eyepin Newsletter, IBM Lotus Forms, Webmethods, etc.
Online Platform Responsabilities
OMV.com Page Structure
Cache Related Components static theme elements (images, .js, .css) CMS BlobServer (images, downloads) CMS ContentServer (html fragments) theme (html)
Online Platform Search
Online Platform Administration
IBM WebSphere Portal
Pages and rights are defined
FatWire Content Server
Content is created and edited
Stages of the online platform Test Production Publish Deploy Promote Deploy Development Promote Integration Publish Deploy Publish Deploy Editorial CMS Portal Portal End Users Web Office Contributors Onlne Manager Portal Admins Portal Admins Portal Operation Contributors Developers Portal Operation Contributors Development Machines Development Machines Local Test-environment Developers Delivery CMS Portal Editorial CMS Portal Delivery CMS Portal Editorial CMS Portal Delivery CMS Portal
Allows online preview of complete page
Content can be allocated from content servers
First Architectural Approach (1 of 3)
First Integration Approach consisted to have both FatWire and WebSphere Portal running in the same Java Virtual Machine.
The integration have been implemented via FatWire jsp tags (Taglibs) used into Content Portlets.
It was quite fast to develop
This approach leaded to an instable platform under load.
Both products were fighting for resources
It was impossible to allocate errors to a specific product
First Architectural Approach (2 of 3)
First Architectural Approach (3 of 3)
Current Architectural Approach (1 of 3)
Current architecture consists in running WebSphere Portal and FatWire in separated JVM’s.
The major change in this architecture is that content is retrieved via http calls (clipping technique) and placed in the portlet view mode.
This architecture allowed us to increase Fatwire results cache and to balance Fatwire requests within the same Portal requests.
It allows to be more flexible and scalable approach
(all software versions were updated to the newest version and will be kept updated)
Current Architectural Approach (2 of 3)
Current Architectural Approach (3 of 3)
Technical Architecture Change measures have been successfully rolled-out, building a solid foundation for future functional enhancements
All systems were upgraded to newest versions
All existing application were migrated to new systems
The Stability improved with the first steps of the project, ensuring an overall targeted availability of minimum 99%
01.01.2010 – There is a significant performance gain due to the Architecture Change (see slides on the right)