Human resource planning
Task Resource Dev Stage Prod Notes Plan website Project manager
Business analystPend Pend Pend
Create a project plan Project manager Pend Pend Pend
Create analysis document Project manager
Business analyst
Tech architectPend Pend Pend
Oversee site prototype and design documents. Project manager Pend Pend Pend
Oversee deployment of hardware and software Project manager Pend Pend Pend
Plan for ongoing monitoring and maintenance Project manager Pend Pend Pend
Design server architecture Tech architect Pend Pend Pend
Design server topology Tech architect Pend Pend Pend
Design WCM topology Tech architect Pend Pend Pend
Review DB considerations Database architect Pend Pend Pend
Design DB server architecture Database architect Pend Pend Pend
Review User registries Database architect Pend Pend Pend
Determine syndication strategies Tech architect Pend Pend Pend
Determine a security architecture Security architect Pend Pend Pend
Users, Groups and Roles Security architect Pend Pend Pend
Users and groups Security architect Pend Pend Pend
Control access Security architect Pend Pend Pend
Design content acquisition architecture Tech architect Pend Pend Pend
Review IBM Web Content Manager API Tech architect Pend Pend Pend
Review IBM Web Content Integrator Tech architect Pend Pend Pend
Review WebDAV Tech architect Pend Pend Pend
Design delivery architecture Tech architect Pend Pend Pend
Design web content delivery architecture Tech architect Pend Pend Pend
Design ongoing maintenance strategies Tech architect Pend Pend Pend
Determine portal pages to be created Information architect Pend Pend Pend
Determine site areas to be created Information architect Pend Pend Pend
What authoring templates are required Information architect Pend Pend Pend
What presentation templates are required Information architect Pend Pend Pend
What template maps are required Information architect Pend Pend Pend
Profiling strategies Information architect Pend Pend Pend
Create design architecture Website designer Pend Pend Pend
Design a prototype website using HTML Website designer Pend Pend Pend
Design customizations Website designer Pend Pend Pend
Create presentation templates Website designer Pend Pend Pend
What components are required Website designer Pend Pend Pend
Elements required for authoring template Website designer Pend Pend Pend
Elements required to be stored in site areas Website designer Pend Pend Pend
personalization strategies Website designer Pend Pend Pend
Design library architecture: Authoring system architect Pend Pend Pend
Web content libraries Authoring system architect Pend Pend Pend
Work with authoring templates Authoring system architect Pend Pend Pend
Template maps Authoring system architect Pend Pend Pend
Work with folders Authoring system architect Pend Pend Pend
Workflow and change management Authoring system architect Pend Pend Pend
Manage versions of items Authoring system architect Pend Pend Pend
Item management Authoring system architect Pend Pend Pend
WCM: The deployment team
The database administrator
A database administrator is responsible for deploying the database servers and data repositories based on the technical architecture developed by the database architect.The database administrator is responsible for installing all databases used by the website and related systems. The databases the administrator sets up are based on the technical architecture developed by the technical and database architects. The database administrator will need to become familiar with the user documentation of the data and user repositories used by the web content system.
The WebSphere Portal administrator
A WebSphere Portal administrator is responsible for the overall deployment and management of the servers in a WebSphere Portal deployment based on the architecture developed by the technical architect.
Install and configuring WebSphere Portal:
The WebSphere Portal administrator is responsible for installing and configuring all the instances of WebSphere Portal used in the overall system.
Migration:
The WebSphere Portal administrator is responsible for migrating data and configuration settings from older versions of WebSphere Portal.
The web content administrator
web content administrator is responsible for configuring the web content servers within a WebSphere Portal system.
Web content authoring environments
In a web content authoring environment, a web content administrator performs the following tasks:
Create new pages
An administrator might need to create new pages to display additional authoring portlets used by different users, or for displaying web content viewer portlets to preview sites within.
Configure an authoring portlet
Each authoring portlet in an authoring environment needs to be configured to ensure that it has been configured correctly for the users using each authoring portlet.
Configure a web content viewer portlet
Each web content viewer portlet in an authoring environment needs to be configured to display the content being previewed.
Create web content libraries
The web content administrator creates has a set of web content libraries based on the recommendations of the web content architect.
Clone a web content repository
Before enabling syndication, a web content administrator, with a database administrator, clones a web content repository from the authoring environment to other environments.
Manage syndication
Syndication relationships are normally created on subscriber servers. As you typically syndicate only out from an authoring environment to other environments, we would not normally create a syndication relationship from an authoring environment, but a web content administrator might need to manage syndication settings and configurations from time to time.
Create and manage feed configurations and jobs
Sometimes web content is stored and maintained in external systems. Use Web Content Integrator to consume content from external systems using feeds.
Tune an authoring environment configuration settings
Authoring environment configuration settings can be tuned for specific features.
Web content delivery environments
In a web content delivery environment, a web content administrator performs the following tasks:
Create new pages
An administrator might need to create new pages when displaying content using web content viewer portlets.
Configure a web content viewer portlet
Each web content viewer portlet in a delivery environment needs to be configured to display the correct content.
Manage syndication
A web content administrator creates syndication relationships to the delivery environment from the web content staging and authoring environments.
Tune a delivery environment configuration settings
Delivery environment configuration settings can be tuned for specific features.
In a UAT environment:
A user acceptance testing environment is set up like authoring and delivery environments depending on the type of UAT being performed. The tasks required to set up the UAT environment are the same as those for the authoring and delivery environments.
The security administrator
A security administrator is responsible for securing the overall system including access control strategies and firewalls.
Implementing the security plan outlined in the security architecture document:
The security administrator is responsible for deploying the security features and processes outlined in the security architecture document developed by the security architect.
See:
Manage the user registry:
The security administrator maintains the security registry by running various update delete tasks.
Manage users and groups:
The security administrator maintains the users and groups stored in the user registry.
Manage access control
The security administrator manages access controls to pages, portlets, modules, and other applications.
Additional security tasks
There are various other tasks carried out by the security administrator depending on what environment is being used.
The development team
Overview
Based on the design documents developed by the technical design team, the development team is responsible for creating custom applications using the product API.
The portlet developer
The portlet developer is responsible for developing new portlets.The portlet developer is primarily responsible for creating custom portlets used to aggregate content and function from external applications. The portlets they develop are based on the portlets identified in the design document.
Theme developer
A theme developer is responsible for creating new themes based on the designs developed by the information architect and the graphic designer.Theme developer is primarily responsible for creating custom themes based on the Web site designs outlined in the design architecture and the HTML used in the website prototype. Themes are has a set of JSPs, images, and style sheets packaged together in a common directory structure. They can either be packaged directly in the wps.war or inside a separate WAR file of their own, or with other themes, skins, and resources.
The web content developer
A web content developer is responsible for extending Web Content Manager using the Web Content Manager API, developing JSP components and creating web content plug-ins.
We can use the Web Content Manager API to extend the functions of Web Content Manager.
Custom authoring interfaces
Custom authoring interfaces are used by content authors as an alternative to using the authoring portlet.
We can create custom plug-ins to add custom features to your site such as custom workflow actions and text providers for multi-locale sites.
Related: Design architecture
The website creation team
Overview
Based on the design documents developed by the technical design team, the website creation team is responsible for creating the website and related systems.
The website creator
A website creator is responsible for building a website by creating presentation templates, authoring templates, site areas, components and categories. The web site creator is also responsible for creating content management items such as folders and workflows. The items created by a website creator are based on the designs created by the information architect and graphic designer.
Create web content management items
Before creating a website, the web content creator begins by creating any required content management items:
Folders are used to store item-types within logical groupings.
Workflows are required to manage the approval processes of items.
Projects are used to manage the approval process of a collection of items.
Create a website
To create a website the following Web Content Manager items will need to be created:
Site areas Site areas are used to define the site framework of a site. Content items that form part of the site framework will be stored within the site framework. Authoring templates Authoring templates are required for the different types of pages in a website. Content items created by content authors will be based in the authoring templates created by the website creator. Presentation templates Presentation templates determine the layout of the pages in a website and are linked to authoring templates by the template maps defined in site areas. Elements and components Elements are added to authoring templates and site areas to store different types of content. Components are used to create single elements that can be reused across a website. Categories Categories are used to profile items that have been configured to allow content profiling.
The web content author
A web content author is responsible for creating web content for the sites developed and managed using Web Content Manager.Content authors create content either by accessing an authoring portlet, or using a custom content authoring interface.
Presentation templates determine the layout of the pages in a website and are linked to authoring templates by the template maps defined in site areas.
Work with elements and components
Elements are added to authoring templates and site areas to store different types of content. Components are used to create single elements that can be reused across a website.
The web content manager
A web content manager is responsible for performing ongoing site maintenance activities.
Moving, linking and copying items:
From time to time a web content manager will need to redesign the structure of a website by moving or copying items.
From time to time a web content manager will need to reapply or change the authoring template used by content items and site areas.
From time to time a web content manager will need to restore an item to a previously saved version.
Edit user profiles:
Profiling information specific to a web content system can be added to a user profile to allow us to personalize content for a specific set of users.
Manage access controls
From time to time a web content manager will need to reapply or change the access controls of has a set of items.
The content acquisition team
Overview
Based on the content identified in the analysis document, the content acquisition team is responsible for importing content from legacy systems into the new website. The team consists of a mixture of administrators and developers. Team members need to be experts in both legacy products and WebSphere PortalThe Web Content Manager API:
We can use the Web Content Manager API to import content into Web Content Manager.
Web content feeds
Use Web Content Integrator to consume content from external systems using feeds.
Use WebDAV for web content:
With for WebSphere Portal, we can use standard operating system tools to create, modify, and delete web content rather than the standard authoring portlet.
Related: Content acquisition architecture
The maintenance team
Overview
Based on the maintenance architecture developed by the technical design team, the maintenance team is responsible for the ongoing monitoring and maintenance of the overall system.
The database administrator
After all databases have been setup, the database administrator is then responsible for the ongoing monitoring and maintenance of all databases in the system.
The WebSphere Portal administrator
The WebSphere Portal administrator is responsible for ongoing maintenance of the WebSphere Portal servers in the system.
The web content administrator
Manage syndication:
Syndication relationships are normally created on subscriber servers. As you typically syndicate only out from an authoring environment to other environments, we would not normally create a syndication relationship from an authoring environment, but a web content administrator might need to manage syndication settings and configurations from time to time.
Manage feed configurations and jobs:
Sometimes web content is stored and maintained in external systems. Use Web Content Integrator to consume content from external systems using feeds.
Maintain an authoring system:
From time to time a web content administrator needs to perform some maintenance tasks.
The security administrator
Manage the user registry:
The security administrator maintains the security registry by running various update delete tasks.
Manage the users and groups:
The security administrator maintains the users and groups stored in the user registry.
Manage access control:
The security administrator manages access controls to pages, portlets, modules, and other applications.
Additional security tasks:
There are various other tasks carried out by the security administrator depending on the environment being used.
The performance engineer
The performance engineer is responsible for ensuring that all the hardware and software in the system are tuned for maximum performance and reliability.
Previous topic: Define the projectNext topic: Create an analysis document
Related: