CMS and Portal Integration

Need a Portal?

Choose the appropriate solution for each Portal

2

JSR-168

JSR-168Standardized Portlets

for any Portal

The Portlet Architecture:One to One Relationship of Portlet to

Data Source or Application.

Presentation Layer Standard

3

JSR-170

JSR-170Standardized Interface to Content (Data) Sources

Content (Data) Layer Standard

4

Classical „Portal+CMS“

Structure Integration

The HiFi- „Content Portal“

Many Apps... ...More Content

1 2 3

Portal & CMS: scenarios

5

Overlap!?

Status Quo: CMS – Portal ?

Portal CMSContent Managementa

Application/Portlet Mgmt c

Structure ManagmentbDevelopment Support d

User Managemente

Presentationf

Performanceg

CachinghPersonalization i

Traditional Venn-Diagram

6

CMS & Portal Scenario: #1

Suggested Portal Type for:✴ Portal consists 90+% of

Applications✴ Highest Level Personalization (not

just groups)✴ Creation of „Portal Pages“ is Portal

Administration Work

1Classical “Portal+CMS Play”

7


1Classical “Portal + CMS Play”

7


1Portal

Highly Personalized Application Driven

Classical “Portal + CMS Play”

7


1

ContentIndividual pieces of

Content are referenced as

Portlets

PortalHighly Personalized

Application Driven

Classical “Portal + CMS Play”

8

Out-of-the box portlets:

Inbox

Content

1

Portal Integration

9


2

* [Fictitious Example, actual implementation differs]


9



Application Driven

2



9



Application Driven

2

ContentPortal Structure is (partially) managed as Content in CMS



10



33The “Content Portal”

10



ContentContent Managed,

Access driven, cached JSR-168 aware Content


10



ContentContent Managed,

Access driven, cached JSR-168 aware Content

PortletsJSR-168 compliant

Portlets, placed and managed through

CMS


11

3


Suggested Portal Type for:

✴ Portal consists 80+% of Content

✴ Group Based Access Control, Low Personalization

✴ „Portal Pages“ are created and managed in CMS

✴ Portlets can be placed by Author

✴ Content makes up highest portion of Portal

✴ Application Portlets are treated like content Blocks

✴ OOTB Content Based Caching


12

33


The “Content Portal”

12

Any Portlet

33



13

3 „Portlet aware Content Management“✴ Communiqué features a JSR-168 compliant portlet

container.

✴ Allows authors to place and manage portlets just like content using all the benefits of a full-fledged CMS (Approval Workflows, Staging, Authorization Management)

✴ Access Controls & Personalizes actual Information (not just Presentation (Portlets))

✴ Supports the entire caching chain of a classical CMS

3



14

1

2

33

Who Staging PublishingWorkflow

Deploy &Replication

Versioning of Page

Structure

Portal Admin ? ? ? ?

Any CMS Authorwith sufficient rights CMS Staging

FacilitiesCommuniqué Workflows

Deployment & ReplicationFacilities

Repository VersioningFacilties





Process Comparison

Create a new Portal Page

15

1

2

33

Who Staging PublishingWorkflow

Deploy &Replication

Versioning of Page







Process Comparison

Place an Application Portlet on Portal Page

16





1 2 3


16





1 2 3


Choose the appropriate solution for each Portal!

CMS and Portal Integration

Documents

Transcript of CMS and Portal Integration