bea portal and cms

BEA Portal and CMS

Washington DC BEA User Group

December 8, 2005

© Copyright 2002 Anexinet Corp. We Listen. We Deliver. You Succeed.TM

Agenda

Portals

CMS

BEA’s Portal & CMS

JSR-170

Best Practices


Portal DefinedThe W3C defines a web portal as "a web site that provides information content on a common topic, for example a specific city or domain of interest. A web portal allows individuals that are interested in the topic to receive news, find and talk to one another, build a community, and find links to other web resources of common interest."


Portals Business JustificationImprove collaboration with Business Partners

Reliable Information Delivery

Improved Employee Information retrieval

Single point of access for related services

More effective management of business workflows

Assist in compliance with SOX, HIPAA, and other regulations

Aggregated views of the company


Portal Services Presentation Services Presentation Navigation Personalization Taxonomy

Application Services Search Identity and/or profile

services Content Management Collaboration Reporting and Intelligence

services Rules Management

Data Services Distributed Transaction Transformations Data Access Data Integration Event Messaging


Content Management DefinedA CMS is...a set of business rules and editorial processes employed by people surrounding web content, designed to align online publishing efforts with organizational objectives. -Tony Byrne, CMS Watch

Content management or CM is a set of processes and technologies that support the evolutionary life cycle of digital information. This digital information is often referred to as content or, to be precise, digital content.

-Wikipedia The digital content life cycle consists of six primary phases:

create, update, publish, translate, archive and retire.


Content Management JustificationIncrease Revenue

Content Accountability

Enforce Brand

Portray company assets in multiple ways

Reduce costs

Consistent company voice


Content Management ServicesLibrary services Checkin/checkout Content reuse

Workflow services Manage business rules of content production

Audit content, i.e. reporting

Deployment services Manage content output rules

Transformation services

Classification services


BEA CMS System


BEA CMS Repository

Repo’s are Hierarchy based, just like a file system.

File based Repo Every node relates to a file

on the file system Metadata stored in db

Database Repo Default Watch Performance related

issues

Content types Templates Forms

Library services Checkin/checkout Versioning Content Lifecycle

Moderator type workflow

Workspace

Repo Types Features


BEA Virtual Content Repository (VCR)Content Bridge pattern

Unifying Content Access


BEA CMS DeliveryCM tag library

Campaigns

Content Selectors


Applications of the CMSContent Administration Content Views Content Type Repository

Portal Visitor Views content through portlets

Content Creator Actually gets delegated rights to the Portal Admin


Recap BEA CMS System


BEA Portal Application


BEA Portal – Unified Portal Framework

Enterprise Portal Architecture

Flexible deployment architecture

Federated Portals

Unified security model

BEA WebLogic single sign-on

Industrial strength foundation

Enterprise Integration

Web integration

Unified user profile

Content integration


Portal Lifecycle ManagementDevelopment

Framework

Visual programming environment

Portal user interface controls

Java Page flows

Loosely-coupled portal applications

Intelligent Administration

Portal assembly tools

Delegated administration

Role-based entitlements

Adaptable Delivery

Multi-level presentation hierarchy

Portlet definitions

Inter-portlet communication

Mobile services


Portal Business ServicesEasily add content, manage

Provide dynamic access to content from multiple repositories

Search helps visitors find the information they need

Build multiple channels of communities that improve productivity

Rule-based personalization

Event and behavior tracking, and a framework to achieve business goals with visitor’s interactions.

Integrated commerce functionality and increase the value of your portal.


Recap Bea Portal


JSR-170JSR 170: Content Repository for JavaTM technology API

Spec Lead is David Nuescheler of Day Software, Inc. A Swiss company

The API should be a standard, implementation independent, way to access content bi-directionally on a granular level within a content repository. A Content Repository is a high-level information management system that is a superset of traditional data repositories. A content repository implements "content services" such as: author based versioning, full textual searching, fine grained access control, content categorization and content event monitoring. It is these "content services" that differentiate a Content Repository from a Data Repository.Many of today's (web)applications are interacting with a content repository in various ways.


BEA CMS and JSR 170The VCR can be both a consumer of the a 170 repo as well as provide a 170 implementation on top of the VCR


CMS and Portal Best Practices – Top Ten

Know who use content

Know who creates content

Know who approves content

Know why the content is used

Know the content composition

1) Get to know your Content



Who is the content consumer

What brand are you promoting

What appeals to the consumers

When/Where/Why/How does the consumers use content

2) Get to know your Content Consumers



What systems contains what information

What is the schema of the content

Privileges to access the information

3) Know you connecting Systems



Not everything has to be in the CMS

CMS has several layers of cache

Portlets have cache

JSP Cache

4) Design for Performance



Know your portlets

Know your pages

Know your content

Determine how your content will appear on the web site

Metadata is glue

Enriched content is useful

Enriched content is reusable

4) Metadata

bea portal and cms

Documents

information content

web content

web portal

cms watchcontent management

set of business rules

web site

web resources of common

file systemmetadata