IBM Workplace Web Content Management

IBM Workplace Web Content Management Rapidly Manage Intranet, Extranet, Internet and Portal Assets Mark A. Barrett Worldwide Technology Advocate Workplace, Portal & Collaboration

What is Web Content Management? Control and management of all content and presentation look and feel placement of assets publishing Determine review, approval processes and lifecycle Control deployment of new content across web infrastructure

Evolution of Web Content Management 3

Workplace Content Management Scenario

Sample Workplace Web Content Management Site Layout 4 tables Site navigator Page Content Menu of Links

Challenges of Web Content Some challenges that Web Content Management addresses: 1. Keeping your site current 2. Content Chaos 3. Bringing visitors back

Common Challenges of Web Content 5 Challenge #1 Keeping your site current Challenge #2 Content Chaos Challenge #3 Bringing visitors back Why is it a challenge? Only a small group of technical people can change the web site It doesn't demand attention Cross-functional effort Time consuming Costs of Outdated Pages Why is it a challenge? Where did that come from? Who owns it? How old is it? Is it still current? Are we still selling that product? Why are 1999 events still listed? Cost of Chaos Why is it a Challenge? Low attention span Lots of competition Easy to leave one click and they re gone Costs of Losing Customers Lost customer confidence Tarnished image Benefits of WCM: Users can create their own content Content is published rapidly Lower traffic Lost opportunities Legal Exposure The hassle of keeping the site current results in neglect Site usage declines Benefits of WCM: Content is owned Content has a life-cycle Content has structure Content re-creation Employee frustration If they run into problems,19% of customers will never come back It costs Benefits 6x more to of sell WCM: to a new customer than to an existing one You can increase profits 85% by Content is accurate increasing customer retention 5%... Content is targeted & relevant Content can be easily found!

Out of the box Web Content Management - Functionality Provides Authoring, Assembly, Staging, Maintenance, and Delivery of all content to web sites Template-based content creation Easy for end users to author, review, and publish content Eliminates webmaster bottleneck Separation of content, structure and design Sitemap Taxonomies Security Reuse of content. Site structure automatically becomes navigation component Categorize documents and reuse in multiple places Personalize delivery Users only see and do what they have permission to do Reusable Components Lifecycle Point and Click components allow rapid development Workflows, ownership and dates bring control to your data API for extensibility Easy data access by other applications Flexible Extension of product Portal integration Out of the box portlets enable rapid Portal development

Creating content 2 Content creation is templatebased, so authors are guided through the creation process. Content is created in a WYSIWYG rich-text editor - or imported removing the need for technical skills

Workflow approval 1 Content workflows ensure the right people approve content before it is published, and only the right people see it after it is published

Managing content 1 Various views are used to manage content, assets and sites

Customized delivery 2 The same assets and content can also be reused in internet, intranet and extranet sites Different people see different content, depending on their preference, roles etc

IBM Workplace Web Content Management variations Website IBM Workplace Websphere Portal Server WWCM portlets Website WWCM Domino Edition Domino App Server WWCM Java Edition WebSphere App Server Lotus Domino NSF Repository DB2/ CM/ Filesystem/JDBC/Oracle

IBM Workplace Web Content Management variations Website IBM Workplace Websphere Portal Server WWCM portlets Website WWCM Domino Edition WWCM Java Edition Domino App Server WebSphere App Server Lotus Domino NSF Repository DB2/ CM/ Filesystem/JDBC/Oracle Existing Domino Infrastructure

Web Content Management timeline Future IBM Workplace Web Content Management 2.5 Component of WebSphere Portal 5.1 IBM Workplace Web Content Management 2.0

Web Content Management timeline Versioning External API JSP support Reuse of external DB2 CM resources Performance improvements Additional languages Portlet SSL Support Win 2003 support IBM Workplace Web Content Management 2.0 Component of WebSphere Portal 5.1 Future IBM Workplace Web Content Management 2.5

Web Content Management timeline Portlet-based UI enhancements Enterprise user directory (WMM) support Enhanced Rich Text Editor Portal Search Managed reuse of Portal documents WebSphere Personalization Portal Install IBM Workplace Web Content Management 2.0 Component of WebSphere Portal 5.1 IBM Workplace Web Content Management 2.5 Future

Web Content Management timeline Repository convergence common model Federated search Clustering Tasks & workflow Authoring & RTE Stylesheets Templating Linking Multi-lingual site management JSP Rendering IBM Workplace Web Content Management 2.0 Component of WebSphere Portal 5.1 Future IBM Workplace Web Content Management 2.5

! " #! "

+*, #$% #$% &! "!! () ) *& '

+*, - - - - '. /01 &! "!! ( *' 2/ /2& '

8-34 -34-534 -534 '. / &! "6 ' 0) 6 "! ' 2!!!! (! ' ( "*0) ' 7

Futures Convergence features: common document model reuse of enterprise content & improved document editing and management Portal tasks & WebSphere workflow Portal security, access control and auditing RAD tooling (IDE) Portal federated search WebSphere Portal clustering model and administration Other enhancements include: multi-lingual multi-site management content authoring, submission and linking templating and extensibility site archival / pre-rendering JSP rendering

Repository convergence Currently a simple XML repository implemented in relational databases and the file system The schema makes it easy to extend and modify the content model and can be used for both structured and unstructured content This repository will become the basis for a converged data store used for storing web content, documents and personalization rules Access to the repository will be based on open standard API s and protocols including JSR 170 WebDAV

JSR 170 JSR 170 is a proposed API to standardize access to content - Content Repository API for Java (JCR) The major content vendors are participating in the development of the specification The specification enables the development of content based applications that can be deployed on top of a number of different underlying repositories Specifies an API and information model for Node types Links Versioning Search Transactions Locking

Repository convergence using standards WebSphere Portal Document Management WebSphere Portal Global Search Mail Discussions Document. Management Domino.doc WPCP Personalization ILWWCM webdav apps PCM API Domino (.nsf) JSR 170 JSR 170 Extensions webdav ILWWCM RDB JSR 170 implementation RDB RDB FS CM RDB CM Domino.DOC

JSR 170 Extensions JSR 170 is a necessary API for accessing content but is not intended to provide a complete specification of all the services required by a content application Extensions are required to assure interoperability Content Model A set of predefined JSR 170 node types and links Rich enough to support different content applications requirements Workflow A model and set of API s that provide the ability to create and manage workflow tasks Schema definition A set of API s that allow for dynamic content definition (new customer-defined structured content types) Client framework A mechanism for desktop clients to access remote JSR 170 implementations

Multi-lingual multi-site management 1 Content to be easily created in multiple languages with the relationships between content automatically created based on intelligent profiling of the language. Business users will be able to view appropriate languages available for different content and maintain the different renditions easily Allows content consumers to see appropriate content for their preferences or based on regional location etc e.g. if an English user creates a News Article, a Chinese Version (with English Content) is automatically created and Chinese translator is notified of their translation task

Workflow Currently proprietary workflow engine Single content item based (i.e. no ability to march a group of content through a workflow) Limited configurability This engine will be replaced Multiple content item support (i.e. the concept of a workspace) This same workflow engine to be used by WebSphere Portal and Lotus Workplace for controlling business processes Can be customized to reflect the customer s business processes Several workflow styles will be supported Document-centric workflows that allow single documents to follow a controlled simple approval and publish path Task-centric more advanced workflows where tasks initiate document creation e.g. multiple documents to follow an approval cycle Portlet-based user interface for business processes Task list portlet exposes work flow activities in one place Unified set of portlets transform complex applications into a simplified set of front end activities hiding the processes going on behind the scenes Access to workflow services will be available through API

Workflow portlets and tools 1 Integration with Process Choreographer for visual workflow of business processes

Business processes 1 Set of activities carried out in a sequence Services can be choreographed to implement a business process i.e. each step or activity in a business process is implemented by a service The business process itself becomes a service Service choreography is described by the Business Process Execution Language (BPEL) Complex Business processes can be modeled more easily

Federated search 1 Common Portal search service to index/search content Federated result set - content from other sources Tie in with security and taxonomy will ensure better control of search results Search for authors Search across all content documents, web content etc, but can be restricted to specific parts of the repository and/or content types.

Customer Examples

Workplace Web Content Management Brings Value: Examples 2 HSBC Mexico- Mexico s largest bank Accurate, timely information for their customers Empowered 80 business users to create their own content Reduced Core Tech Staff from 8 to 2 Reduced publishing time from 10 days to 20 minutes Stuttgart Tramworks Mass-transit for the city of Stuttgart, Germany Reuse of existing IT infrastrucuture. Common Corporate Identity achieved for 1700 employees city-wide Paper based communication reduced by over 80%

Workplace Web Content Management Brings Value: Examples 2 Minter Ellison- Australian Law Firm Needed an accurate web and intranet presence Content publishing reduced from days to minutes Savings of up to one person-year! Subject matter experts control their content Knowledge management dramatically improved Alcan Inc USA Metals Production Needed to Launch new Corporate Image after merger Website Content creators independent of IT Dept Timely information for customers and shareholders

Rapidly Manage Intranet, Extranet, Internet and Portal Assets Give LOB users control over THEIR Web content Eliminate the Webmaster bottleneck. Bring Structure to your sites Eliminate Content Chaos with Taxonomy, Ownership and Lifecycle Rapid site development through reusable out of the box components Lower TOC= faster ROI Open Standards-based and integrated with IBM technology: Domino and Java/WebSphere editions Portal Server Now the WCM tool for Portal DB/2 Content Manager completes IBM s ECM offering Future JCR support WWCM allows the right information to get to the right people at the right time, so portals & websites are efficient and effective.

Thank You! Mark Barrett mark_barrett@us.ibm.com