midwest documentum user group harley-davidson documentum wcm 10/10/2006
TRANSCRIPT
Midwest Documentum Midwest Documentum User GroupUser Group
Harley-DavidsonHarley-Davidson
Documentum WCMDocumentum WCM
10/10/200610/10/2006
Overview of Harley-Davidson• 10,000+ employees worldwide• Corporate HQ in Milwaukee, Wis.• More than 1,300 H-D dealerships in 60 countries
worldwide• Over 1 Million members of Harley Owners Group
Content Management at Harley
• 3 years ago Harley had no content management
• Content was managed by a 3rd party and H-D wanted to gain control
• Wanted public site and intranet on same enterprise platform
• Implementing e-Room for collaboration
History of Documentum
• Documentum 5.2.5 installed for H-D.com and Employee Portal – “Ride” with Documentum Partner – Braun Consulting (2004)
• E-Room installed for content collaboration (2004)• Upgraded to 5.3 SP1 with TSG (2006)• Dealer Portal Added to Platform with TSG/IBM
(2007)• Upgraded to 5.3 SP5 with TSG (2007)
WCM Applications• H-D.com
– For Access by public– Site use to promote/sell products– Leverage from WCM
• Ride – Employee Portal– For Access by employees– Site used for corporate communications– Same WCM architecture / platform as H-D.com– Bea Weblogic Portal
• Dealer Portal– For Access by external dealers– Site used to distribute information to dealerships– Leverage from WCM and Portal Software– IBM Websphere Portal
Web Publisher Overview
Basic Web Publisher
• Authors select a template• Complete temple with:
– Text – Images– Dates– Other relevant content existing in repository
• Content is saved in XML and can be rendered using XSL into:– HTML – JSP– XML– Other
Harley Content H-D.com• Authors select page layout• Authors select images and content components• Content components are authored separately
What are typical issues?
• While separate components provides huge benefits…– Change one image or text and it is changed
throughout the entire site….
• Navigation between pages and components can be difficult as the site and number of component grows
• Creating additional objects/pages for localization can be complex
Harley Approach – In Context Editing
Staging / WIPSite
ProductionSite
* Edit Page
Web Publisher Page
List of all components
on Page
Edit Selected Page in Web
Publisher
Edit selected page from list of components
* Custom to Harley
Object Map Tool (In Context Editing)
Localization – Typical Web Publisher
1. Create Localized Page (1 to n languages)2. Create Localized content (1 to n times, 1 to n
languages)3. Update the page to point to new components
Harley Alternative
1. Tool to allow authors to automatically generate localized pages and content for multiple components and languages
2. Allow editors to use In Context Editing to update
Localization Tool
Other Unique WCM components for Harley
• Web Services
• Dealer Portal Architecture
• Navigation Manager
• OpenMigrate
Custom Web Services• Authentication Service
– Authenticate • Content Service
– Get Content – Create Content – Update Content – Checkout Content – Cancel Checkout Content – Checkin Content – Delete Content
• Query Service – Run a Query
• Policy Service – Attach Policy
H-D System H-D System H-D System
Web Services Layer
Advantages to a Custom Web Services Approach
• Custom Logic needed for Harley– For certain business rules
• Integration with Services Group (no Documentum Knowledge)
• Reduction of upgrade efforts– No client Application changes based on
upgrade of Documentum
Dealer Portal Content Management Portal Diagram
Portal-Personalization-Dealer Authentication-Dynamic Content Display
Content Management-Content Entry-Version-Security-Checkin/Checkout-Approval
Content Authors (WCM)Other Harley CMS Systems
Portal determines which content appears in which page based on business rules!!!
IBM Portal
• Chose IBM portal to deliver content to users• Reason?
– More robust portal engine (programming infrastructure)– More robust set of features– Use of out-of-the-box content portlets– Politics
• Eliminated IBM portal as an option for content creation and management– User interface was lacking– Metadata controls lacking i.e. no drop downs– Limitation on date fields– Workflow limitations– Chose Documentum Web Publisher
Dealer Portal Data Flow
TSG createdRSS producer
iWCM
Web Publisher
Content Authors (WCM)Other Harley CMS Systems
TSG createdWeb Services
Web PublisherEphox editor
Navigation Manager
• Most Web Publisher created sites use attributes of the content to derive the navigational structure
• Navigation Manager publishes page hierarchy in XML
OpenMigrate
• Used for “New Models” and content localization • Customized OpenMigrate to allow “Batch Zip” importing• Attributes entered in spreadsheet, but can be updated from
application• Successfully migrated a batch of 37,000 documents
Lessons Learned• Content delivery side – The out-of-the-box functionality of IBM’s portal
did not completely satisfy the business needs.• Set standards early and live by them. RSS feed standards changed.
Same goes for requirements!• As far as upgrades go, you can never do enough testing in the
development environment• Navigation Manager
– Business is happy with functionality, makes building a site easier– IT is concerned about extending the product to meet future needs
• “Black Box” – limited ability to extend and customize Navigation Manager– Does not support globalization out of box– The product does not “play well” with content not managed by Navigation
Manager. • To remedy the issue we needed to install a separate instance of Web Publisher
– Unsupported without contract