Skip to main content link. Accesskey S
  • Anonymous
  • Log on
  • Help
  • IBM logo
  • WebSphere Portal Family wiki
  • All Wikis
  • Home
  • Community Articles
  • Product Documentation
  • Learning Center


Search

Advanced Search

Categories

Tag Cloud

  • 6.0
  • 6.1
  • 6.1.0.1
  • 6.1.5
  • 7.0
  • 7.0.0.2
  • 8.0
  • actions
  • administrator
  • authoring
  • Banking template
  • best practices
  • blogs
  • builder
  • building a site
  • caching
  • catalog
  • Clickstream Engine
  • clusters
  • ConfigEngine tasks
  • content
  • customizing
  • databases
  • demo
  • deployment
  • deployment scenario
  • developer
  • developing
  • device class
  • elements
  • examples
  • Express
  • feature set
  • fix pack 2
  • Government to Business template
  • info center
  • information center
  • installation
  • installing
  • LDAP
  • Learning
  • libraries
  • LikeMinds Recommendation Engines
  • logging
  • mentors
  • message catalog
  • messages
  • migration
  • mobile
  • mobile devices
  • mobile experience
  • mobile experience 8.0
  • mobile theme
  • mobile webkit
  • MPA
  • multiplatform
  • pages
  • performance
  • personalization
  • planning
  • portal
  • Portal 6.1
  • Portal 8 theme
  • portlets
  • product doc
  • product documentation
  • projects
  • properties
  • Redbooks
  • Redbooks Wiki
  • remember me cookie
  • resources
  • REST
  • Retail Vendor template
  • rules
  • samples
  • search
  • security
  • sifters
  • sites
  • solutions catalog
  • syndication
  • test infrastructure
  • theme
  • theme optimization
  • topologies
  • troubleshooting
  • tutorials on personalization
  • video
  • wcm
  • web content
  • webkit
  • WebSphere Portal
  • WebSphere Portlet Factory
  • wikis
  • workflows
  • worksheet
  • XML configuration interface
  • z/os
  • zos
InformationInformation
You are currently viewing machine translated content. IBM translation might be available. Click IBM Translated Product Documentation to see what is available.X


Home > IBM Redbooks: Building a Sample Website Using IBM Web Content Manager 7.0 > 2.2 Architectural frameworks for content
Rate this article 1 starRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

2.2 Architectural frameworks for content 

expanded Abstract
collapsed Abstract
This section describes various architectural frameworks for content in WCM including portal, traditional, internal facing, and external facing frameworks.
ShowTable of Contents
HideTable of Contents
  • 1 Portal
  • 2 Traditional
  • 3 Internal facing
  • 4 External facing
The architectural frameworks for content in WCM consist of portal, traditional, internal facing, and external facing.

This section describes the various architectural frameworks for content in WCM.

Portal


Portal provides the basic framework services for content aggregation, role-based access, personalization, and security.

The underlying J2EE platform provides low-level middleware services such as enabling security through a user registry and session management. These underlying services coupled with the basic portal framework services can provide content life cycle management in terms of content authoring and content delivery. Different roles, such as author, reviewer, and approver, can move content from authoring to delivery.

The content management and delivery framework embedded in portal can be used in tandem with other features, such as personalization and content aggregation, which provides an effective presentation layer in the architecture. The portal framework allows the delivery of pages and sites that combine content from the CMS and other kinds of portal content from back-end systems.

Traditional


In the traditional architectural framework, content is prepared in pure HTML format by using different HTML editors, and the content is hosted on a web server for presentation.

The URLs are exchanged with the reviewers and approvers for verification and validation over e-mail. The hosting platform does not provide content management. The dynamic applications came into existence with CGI scripts but had many limitations. The evolution of the J2EE platform brought new ways to display content on web sites: Static web content can be coupled with the dynamic content that is generated through servlets and JavaServer Pages (JSPs). However, the traditional framework still lacks in content management functionality.

Internal facing


Internal facing sites are sites designed for and used by the employees of an organization.

Internal sites typically provide access to content and applications that employee access on a frequent basis. Often, key applications or content are delivered that attract employees to visit the sites. Such entities include news, alerts, and role-specific content. Intranet users can benefit greatly if the sites provide applications that are useful for day-to-day activities, such as sales management, defect tracking, customer relationship management, or technical support.

The integration of Web Content Manager and Portal allows content to be interspersed amongst other portal artifacts (pages, portlets, gadgets and widgets)

External facing


External facing sites are sites designed for and used for by general public or partners of an organization.

On external facing sites, the content should be clear, relevant and up-to-date and be easily and quickly accessed by users. Users' opinion of a website may directly influence the image of the associated organizations in the public eye.

The site should be engaging and easy to use. Users want a site where the content they are looking for is easily found through navigation or search. The site should be fast and responsive, making use of caching techniques at various levels to enhance the response times for a variety of scenarios. A user may want to register with the site using a unique ID, content can then be personalized according to the profile of each user. The design of such a framework should consider how the content is managed, searched, cached, and personalized for users, with the goal of attracting and keeping the attention of the users.

expanded Article information
collapsed Article information
Category:
IBM Redbooks: Building a Sample Website Using IBM Web Content Manager 7.0
Tags:
Redbooks

This Version: Version 2 December 13, 2011 2:58:56 PM by Amanda J Bauman  IBMer

expanded Attachments (0)
collapsed Attachments (0)

 


expanded Versions (2)
collapsed Versions (2)
Version Comparison     
Version Date Changed by               Summary of changes
This version (2) Dec 13, 2011 2:58:56 PM Amanda J Bauman  
1 Dec 13, 2011 1:33:30 PM Amanda J Bauman  
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedSubscribe to RSSHelpAbout
  • All Lotus and WebSphere Portal wikis
  • IBM developerWorks
  • IBM Software support
  • IBM Social Business User Experience Blog
  • IBMSocialBizUX on Twitter
  • IBMSocialBizUX on Facebook
  • Lotus product forums
  • IBM Social Business UX blog
  • IBM Collaboration Solutions
  • Recently added feedRecently added
  • Recently edited feedRecently edited
  • Recently added comments feedRecently Added Comments
  • Wiki Help
  • Forgot user name/password
  • Wiki design feedback
  • Content feedback
  • About the wiki
  • About IBM
  • Privacy
  • Contact IBM
  • IBM Terms of use
  • Wiki terms of use