Webcast Wcm

1. Lotus Web Content Management Edson Oliveira ([email protected])

2. Agenda

O que h de novo?

Construindo um site com o WCM

O que fazer e o quem no fazer

3. O que h de novo?

4. What we shipped in 6.1 - Introduction

6.1 is the first major release of WCM since 6.0 in 2006

Many incremental (yet very significant) improvements since 6.0

Focus on improving product quality, stability and scalability

No major data migration required to go from 6.0 to 6.1, and improvements made to the 5.1 to 6.1 migration (or to 6.1.0.1)

Performance has been improved significantly with focus both authoring and rendering (in certain tests rendering performance has improved by 50%)

5. What we shipped with 6.1

Simplified & Enhanced Authoring

Security Inheritance

Improved inline eclipse help

Simplified user selection

Additional templating options

Enhanced Function

Custom workflow action support

Library management APIs

Syndication management APIs

Performance improvements

Active content filter

Additional rendering tag options

6. What we shipped with 6.1 (cont.)

Expanded Integration

WebSphere 6.1 exploitation

WebSphere 7.0 support (6.1.0.1)

Simplified Architecture

Improved install integration

Scriptable maintenance tasks (ConfigEngine tasks)

Improved JSP deployment handling for custom extensions

6.1.0.1

Workflow of Components, Categories, Taxonomies in WCM API

Presentation template added to API

Regular cumulative fixpack delivery for simplified maintenance

7. Enhanced Professional Editing Capability for WCM IBM is enhancing its Lotus WCM Rich Text Editor capabilities by embedding Ephoxs EditLive Editor Product Capability available of customers using LWCM 6.1 and above. Ready to be shipped by end of Q1 09 Customers can download a trial version from Ephox now at http://www.ephox.com/ibm

8. 6.1 Additional Authoring Template options

New options to simplify the content form allowing Authoring Template creators to hide more buttons, toolbars and fields from content creators.

Field labels can now be replaced.

Existing templates from 6.0 will continue to work exactly as they did

9. 6.1 Rendering Tags

History Component Dates

field=creation|creator|lastmodifier Renders the creation date, creator or the last modifier of the targeted item

ID, Security, Profile and Workflow Components

ifempty=(some text) Will render the value of ifempty tag attribute if the selected field does not render anything

ID, Profile and Text, Short Text Component/Elements

htmlencode=true | false Will encode all text being rendered

The format tag attribute was added in 6.0 to add a few simple options to control how certain components rendered. More options have been added in 6.1

FILENAME, SIZE, WIDTH, HEIGHT (and more) for Image Component

10. 6.1 Syndication API

The main purpose of the new API is to allow for dynamic control of syndication.

The main functions:

Enable, disable syndicators and subscribers

Start full and partial updates

Dynamically check syndication updates to see if its running or not

View syndicator or subscriber details (Name, libraries being syndicated)

Query for the last syndication run's detail(Items updated/saved/modified/removed)

What does this mean?

Applications could be written to manage syndication. Syndication could be performed at the same time each day or at special events (a specific document entering a custom workflow stageetc).

Easier to determine when syndication is running or completed.

Errors encountered can be caught faster by monitoring the status

11. 6.1 Additional APIs

Some new methods have been added to Content to allow for approvers to be changed.

Approvers can now be added and remove

Approver access can be checked

The library service exposes APIs to manage WCM libraries

Create, save, copy, export, import

Method on the WebContentLibraryService to export a list of information about all web content artifacts in a Library.

Additions to Workspace

New set of find by methods added to the API to make it easier to find items by their workflow state (also in 6.0.1.4)

For improved rendering support can retrieve items by reference (also in 6.0.1.4)

12. 6.1 Custom Workflow Actions

Allow for customer code to be invoked as part of the WCM workflow process.

Can simply register CustomWorkflowActionFactory via the Eclipse Plug-in framework

Custom workflow actions are created in the UI

The action is linked with the customer code

13. New: WCM Portal Pages Tightly integrate WCM with Portal

14. Goals

Get to a common model between portal and WCM

Pages vs. Site Areas

Both are models of a web site hierarchy

Both need to model

Structure parent/child

Design layout, style

Properties metadata, content elements

Both drive static navigation

So lets just have one

Portlets vs. Content

Both are things you show on pages

But they are fundamentally different

Portlets are dynamic, stateful, event driven, etc.

Content is static, stateless, context driven, etc.

Keep these separate

Make it easy for web site administrators to create WCM pages and maintain the mapping to WCM content

15. Common Information Architecture

Portal and WCM can use the same site architecture

Converged site and page layout management and tools

JSR 286 Portlets

Portal will understand where WCM content lives & WCM will understand what portal pages the content exists on

Map/associate site areas/content items to Portal pages

Seamless navigation

Linking

Search

Context-awareness

Friendly URLs - WCM context path appended to friendly portal page URLs

Use seedlists for registering WCM content elements with Search engine. This contains all content elements that are mapped to topology nodes

End result will be significantly lower deployment times and easier integration

16. Site Convergence with WebSphere Portal Page Layout

Site administrators can define portal pages that are marked as WCM templates pages and thus can be re-used when creating a new WCM page

WCM template pages are stored under a specific root node

Root node can be created anywhere in the portal site

Menu Portlet Related info portlet Details Portlet Header Footer Menu Portlet Related info portlet Details Portlet Header Footer Menu Portlet Related info portlet Details Portlet Header Footer Content Template page Page instances Content, Media, etc.

17. Site Convergence with WebSphere Portal Site Topology

Integration of Portal Site management with WCM site management

Instead of defining Portal pages and then mirroring those as WCM site areas, WCM will just leverage the Portal page hierarchy as the WCM site area hierarchy.

Render WCM managed pages along side standard Portal pages

Manages entire page, not just inside of a portlet (leveraging Portal to display the navigation or including rendering the navigation elements)

WCM library Content 1 3.1 3 A virtual portal Page Page Content Node Content Node Content Node 3.2

18. Site Management Convergence JSR286 WCM Rendering Portlets

New Page Type (WCM page), Content structure drives Portal display page

In context Preview. In context display of searched content. Support for public pages (no session required!) Creating WCM Pages Define the Portal Layout Connect to sets of content from WCM WCM library Content 1 3.1 3 A virtual portal Page Page Content Node Content Node Content Node 3.2

19. WCM template pages samples

Template with one WCM rendering portlet

Template with two WCM rendering portlets

20. WCM Pages

Create new WCM page

21. WCM Pages

Set WCM page properties

22. WCM Pages

WCM navigation portlet select content 3 link

23. WCM Pages

Switched to page Site area 1 with content 3 selected

24. WCM Pages

WCM navigation portlet select content 6 link

25. WCM Pages

Switched to page Site area 2 with content 6 selected

26. New: JSR 286-based WCM rendering portlets Newly enhanced WCM rendering portlets available via the Portlet Catalog

27. Overview

Available as catalog shipment

Running on top of WebSphere Portal 6.1.0.1

Requires some additional Fixes to leverage all functions

http://www-01.ibm.com/software/brandcatalog/portal/portal/details?catalog.label=1WP1001S6

New features compared to the current WCM rendering portlet

Dynamic page context support in portlet

Portlet UI enhancements

New and simplified config UI, based on OneUI design

Lightbox menu selection UI style

New error messages in-context

Performance improvements

Session-less rendering

Portlet fragment caching

Bookmarkable content selection

Uses public render parameter for context selection

Can also be set by custom portlets

Localization of portlet title via resource bundle

SA log file entries

Better Web 2.0 CSA theme support

28. Portlet UI Enhancements

29. Portlet UI Enhancements

30. Performance improvements

Portlet does no longer require a session for rendering

Everything stored in the URL as private or public render parameter

Completely bookmarkable

Leverage the portal fragment cache for WCM content

You can set the cache policy per portlet either global via the config mode or per portlet instance via the edit_defautls mode

Settings:

Scope

Per user or shared across all users

Expiration

Never, time in seconds, or always

Future

Allow attaching cache settings on content items

31. New: WCM Search enhancements Seedlist 1.0 and In-context Links

32. WCM Search enhancements

Available with WebSphere Portal 6.1.0.1

Turned off per default

How to enable it:

WP ConfigService > Custom properties

wcm.config.seedlist.version=1.0

wcm.config.seedlist.servletpath=/seedlist

Support of seedlist format 1.0

Open, ATOM-based format

Provides access control information in the seedlist so that the crawler can filter it based on the user issuing the search

Support of custom meta-data in the seedlist

Use cases: search key words

How to enable it:

WP ConfigService > Custom properties

wcm.config.seedlist.metakeys=

Add custom meta-data field to WCM content

Add a new Text Component with a name that you've specified in the ConfigService


In-context links

URLs in the seedlist are now PoC URIs pointing the the WCM content item

Links itself do not contain the page information

Allows to add/remove pages without making the seedlist stale

When such an URI is clicked the PoC resolver will try to find the WCM Portal Page responsible for rendering this content item and dispatch to that page

If no such page is found the default is the current behavior of rendering the content item via a standalone servlet


In-context links

35. Outlook What are we focusing on? A quick look at what we are focusing on for the next release....

36. Outlook What are we focusing on?

Change Management & Preview in Context (Projects)

Projects will allow users to control delivery of changes to their websites and allows them to preview those changes in context prior to publishing them.

Projects can be delivered as a group of changes during syndication

Portal Site Convergence

Removes the boundaries between Portal and WCM site management. True WCM & Portal integration with the result that WCM content will know where it belongs within Portal. WCM search results, previewing, bookmarks will take you to the right page in Portal (contextual links)

JSR-286 Rendering Portlet

Allows for anonymous rendering of content without user sessions

Per-portlet caching control

UI Redesign

Dramatically reduce the number of clicks necessary to perform common scenarios

Focus on simplifying navigation around the UI and making it easier to find and work with items

WebDAV

37. Change Management & Preview in Context (Projects)

Batching of multiple changes into a Project to preview all changes prior to publishing within the context of their live site, and when ready to control delivery of all the changes

Users create projects and associate items with the Project

Users can reference other draft items that are within the same project.

Projects use item state to control when it becomes available to render or reference within the library (outside of the project). This does not require workflow

38. Change Management & Preview in Context (cont.)

A project support a number of changes (Creation, edit, moves and deletes). With preview in context of all changes made within the project

39. Some ideas how to leverage WebDAV

Allow authoring of WCM content via WebDAV

Reading of content (sub-)trees or single items

List content hierarchy

Cover meta-data via additionally generated files in the WebDAV structure

Create WCM meta-data xsd(s)

Easy creation of components in a drag&drop like manner

Add a component by adding a corresponding file (image for image component, etc.)

Update of all downloadable data

E.g. Download an image, modify it and store it back (same for richt text, etc.)

Meta-data files are stored back as meta-data of the corresponding objects as described in the XML

Create / Update presentation templates

E.g. by using an external tool like Dreamweaver for creating the presentation template

These are not product announcements and the design may change !!!

40. Using WebDAV with WCM Drag and drop images into WCM using the Microsoft Windows Exporer

41. Using WebDAV with WCM Creating presentation templates using external tools, e.g. Adobe Dream-weaver

42. Useful WCM Links

WCM (and Portal) Wiki

http://www-10.lotus.com/ldd/portalwiki.nsf

WCM developerWorks Forum

http://www.ibm.com/developerworks/forums/forum.jspa?forumID=452&start=0

Catalog shipment

http://www-01.ibm.com/software/brandcatalog/portal/portal/details?catalog.label=1WP1001S6

43. Sample from the wiki

Web 2.0 effects with WCM

http://www-10.lotus.com/ldd/portalwiki.nsf/dx/dynamic-fx-demo-how-to-create-web2.0-effects-in-wcm-sites

44. Construindo um site com o WCM

45. Consideraes e decises

Entender os objetivos do site

Entender qual ser o pblico

Considerar os objetivos e os fatores chaves

Encontrar um aplicao muito vistosa

Definindo cenrios para casos de uso

Planejando o site framework e as site areas

Metadata, keywords e categorias

Determinar os componentes do site

Usando workflow e syndication

46. Entender os objetivos do site Antes de iniciar a construo do site, importante voc entender quais so os objetivos e qual ser a audincia (pblico alvo), com isso ficar mais fcil para determinar quais componentes voc dever estar usando.

47. Entender qual ser o pblico Todo projeto tem como objetivo o ROI (Return on Investiment), e isso pode ser alcanado com a audincia. Qualquer falha nesse ponto significativa para o projeto. importante conhecer a demografia da audincia e por que eles teriam interesse em acessar o site. A tolerncia das pessoas com informaes em sites diferente da tolerncia com contedo impresso. Se voc no encontrar as necessidades da sua audincia da primeira vez, dificilmente ter uma segunda chance.

48. Considerar os objetivos e os fatores chaves

Para seu produto de Web content managemet ser um sucesso, considere e defina os fatores chaves de sucesso que determinaro se o Web site est de acordo com os objetivos.

Adicionalmente, voc tambm deve entender como voc pode mensurar os fatores chaves de sucesso.

Existem vrias maneiras de mensurar os fatores chaves, somente a freqncia ao seu site no o suficiente. Abaixo esto alguns exemplos:

Entender os objetivos de negcio e dos usurios;

Navegao intuitiva;

Prover flexibilidade de design; etc.

49. Encontrar um aplicao muito vistosa Uma maneira se assegurar o uso do Web site, identificar pelo menos uma aplicao muito vistosa ou caracterstica que todos provavelmente iro usar freqentemente e deixar ela disponvel somente no Web site.

50. Definindo cenrios para casos de uso Ns estvamos definindo at agora qual era a expectativa da audincia para o Web site. O prximo passo definir como os usurios iro atingir a informao. Uma primeira abordagem definir um nmero de casos de uso chaves, que representam a maneira com voc espera como os usurios iro interagir com o Web Site. Esses casos de uso devero ser criados tanto para os usurio que iro acessar o site somente para pegar informaes com usurios que estaro usando a ferramenta de web content management para incluir novos contedos.

51. Qual produto vou usar?

Depois de entender esses objetivos ai que comeamos a pensar nos produtos.

Usarei somente o Web Content Management?

Usarei o Portal com o Web Content Management?

Hoje em dia a maioria dos sites querem ter aplicaes como enquetes, localizao de lojas, consultas a documentos, etc. Devido a esse cenrio muito provvel que a combinao Portal + Web Content Management seja a melhor opo.

52. Planejando o site framework e as site areas

Aqui estamos falando do mapa do site, que dever ser construdo de uma maneira que facilite a navegao dos usurios pelo Web site.

Aqui a anlise consiste em duas partes:

Uma abordagem top-down para investigar o contedo que ser mostrado no site, mais as necessidades da audincia que acessam o site. Esta abordagem ajuda a formular o escopo do site e suporta nosso entendimento de como a totalidade do site ser estruturada.

Uma avaliao botton-up, que inicia do mais bsico nvel do site, o contedo da pgina. Este processo determina qual metadata, categoria e keyworks devero se includos no perfil dos documentos.

Desse trabalho, temos como resultado:

Site framework

Hierarquia das categorias

Hierarquia dos tipos de documentos

53. Metadata, keywords e categorias Quando criado um contedo, crucial que voc defina uma informao descritiva para esse contedo, que podem ser categorizadas e procuradas. Informao descritiva chamada de metadata, como foi definido pelo W3C (http://www.w3.org/Metadata/). Metadata a mquina compreensvel da informao para a web. Metadata requerida como uma parte da web que contem informao sobre a informao .

54. Determinar os componentes do site

55. Usando workflow e syndication A utilizao de uma ferramenta de web content management nos d a flexibilidade de criao de contedo em diferentes localidades e com diferentes nveis de segurana. O Lotus Web Content Management prov esses dois recursos, atravs dos processos de syndication e workflow.

60. O que fazer e o que no fazer

61. Antes de Comear Consulte os recursos disponveis (Help, Wiki, Artigos, etc.); Verifique se j foram definidos os Objetivos, Operao, Pblico Alvo, Site Framework, Taxonomia, etc; Verifique se existem fixes recomendados; Habilite a segurana do portal; Crie uma nomenclatura padro para componentes do site; Crie grupos; Crie as bibliotecas para o site e configure a segurana; Habilite o workflow para os componentes necessrios; No utilize o usurio WPSADMIN para criao do site; No habilite workflow para Workflow, estgios e aes;

62. Launch Page

Uma boa opo para facilitar a utilizao do WCM por usurios em conhecimento de informtica customizar a pgina inicial do Portlet de Autoria, veja exemplo abaixo:

63. Templates HOME Criao de um template de autoria e de um template de apresentao para trabalhar com componentes do WCM. Isso d flexibilidade na mudana do contedo de uma pgina, sem precisar alterar configuraes de portlets.

64. Template de Autoria Na apresentao do template de autoria para o usurio final, procure validar qual o modelo de apresentao que ele prefere. Valide de todos os botes so necessrios na barra de ferramentas.

65. Template de Autoria Procure direcionar o contedo ser criado pelo template para um site area, se no for possvel, deixa poucas opes para seleo.

66. Template de Autoria Deixe um help para ajudar o autor a preencher o template de autoria.

67. Template de Autoria Planeje a estratgia de versionamento para cada tipo de contedo, lembre-se que existem documentos que no necessitam de versionamento.

68. Template de Autoria Em configuraes do contedo padro, o campo NOME especial, pois o WCM utiliza ele como chave para os contedos. Esse campo no aceita caracteres especiais, ento no uma boa alternativa deixar ele disponvel para um usurio preencher. Mude as opes conforme figura abaixo.

69. Template de Autoria Todos os campos do WCM tem caractersticas especiais, utilize-as para dar maior conforto na hora do preenchimento e para evitar erros tambm.

70. Template de Autoria

Sesses que no tenham informaes relevantes na hora do preenchimento devem ficar escondidas, quanto mais simples voc deixar o formulrio para o usurio final, mas rpido e com mais qualidade ele vai produzir o contedo

A IBM fechou um acorde de OEM para utilizar o editor de texto EPHOX. No pense duas vezes, use!!!

Procure sempre utilizar o mesmo nome de campo ou os mesmos campos para identificar itens, isso reduz a necessidade de criao de templates de apresentao. O nmero de templates de apresentao no igual ao nmero de templates de autoria.

O nmero de campos em um template ficou muito grande? Porque no usar um JSP para fazer a entrada de dados. Veja esse documento http://www-10.lotus.com/ldd/portalwiki.nsf/dx/large-numbers-of-Elements-on-Authoring-templates

72. Componentes

Use componentes de HTML para criao de Layout;

Use Inline editing para habilitar a edio/criao de contedos diretamente na pgina do site;

Nos MENUS e NAVEGADORES coloque mensagens quando no so encontrados resultados para apresentao;

Identifique de forma clara cada componente com nomes ou tags (ex: MENU-NotciasGerais, NAV-MapaDoSite, etc);

Evite selecionar muitos critrios de pesquisa dentro dos MENUS;

Desabilite a organizao dos MENUS pela descrio do contedo, somente se necessrio;

73. Site Framework

Utilize elementos dentro dos Site Areas para customizao;

Selecione o contedo padro para cada Site Area;

Relacione os Templates de Autoria e Apresentao para casa Site Area;

No crie nomes com mais de 50 caracteres;

No utilize o nome de Site Areas para contedos, isso pode confundir quando um usurio procurar pelo contedo.

74. Segurana Exemplo de grupos para configurar a segurana do WCM: WCM Admins: Tem acesso tudo Site Admins: Tem acesso tudo com exceo elementos de workflow Site Designers: Acesso ao contedo, templates de apresentao, templates de autoria e componentes Content Authors: Acesso ao contedo e componentes Content Approvers: Acesso ao contedo

75. Syndication

Antes de iniciar uma tarefa de syndication configure a segurana da biblioteca;

Configure Subscriber.only para servidores que no iro sindicar suas bibliotecas;

Envie somente Live Items para os servidores de apresentao;

Procure utilizar o HostName na configurao do Syndication;

Evite editar itens em multiplos ambientes;

No crie a configurao de syndication de uma biblioteca para um servidor que j tenha uma biblioteca com o mesmo nome;

No habilite o Syndicator nos servidores de produo;

Se precisar fazer um Syndication two-away, selecione todos os itens em ambos os servidores.

76. Portlet de Visualizao

77. Geral

No utilize Remote Rendering Portlet para acessar contedo local;

No use o Cloudscape para ambientes de produo;

No modifique arquivos java ou JSP do produto;

No use a funo de personalizao como segurana;

No use APIs Internas, somente APIs pblicas so suportadas;

No habilite traces e deixe eles por muito tempo.

78. Referncias

WCM Wiki no Developerworks;

Help do Websphere Portal;

Best Practices for using IBM Workplace Web Content Management V6.0 (Artigo no Developerworks);

79. Obrigado Edson Oliveira [email_address] http://edsonlo.blogspot.com

Webcast Wcm

Technology

Transcript of Webcast Wcm