Rhythmyx 5

1
Rhythmyx 5

• Architectural Overview

2
Percussion Software

• Established software company
• Expertise building and managing content-centric
  applications
• Domino-based tools (Notrix, Powerflow, Lyrix)
• Standards-based (JAVA, XML, XSL, Web Services)
• Focus content reuse, transformation, workflow
  and integration
• Solid customer base
• 2500 customers worldwide
• Higher customer retention rate than industry
  average
• Ensuring customers success is a key company
  metric
• Financially strong Continuous growth
• 25 growth in CMS sales 1H03 vs. 1H02
• 70 growth in CMS sales in 2002
• Self-funded, privately-held, profitable since 1997

3
Sample Customer Successes
Public Sector
Technology
Public Sector
Education/Learning
Financial Services/ Insurance
e-Business
Pharmaceuticals/ Healthcare
Media/Entertainment
Utilities
Manufacturing/ Consumers
4
Where Should ECM Add Value?
CONTENT PRODUCTIVITY
LOBRequirements
Meaning
Assembly
ApplicationFrameworks(.NET, IBM, BEA,Oracle, )
Lifecycle Mgt.
Impact Analysis
Components
UNIFIED DEVELOPMENTPLATFORM
HETEROGENEOUS ENVIRONMENTS
Globalization
Portals(IBM, BEA, Oracle,SAP, )
Taxonomy
CodeContentSynch
ContentObjects
XML/DataExport
StaticExport
Caching
De-Coupled Delivery
SchemaMapping
Templates
SCM
Lib. Svcs.
ITRequirements
File Conversion
Content Integration
Index Retrieval
Storage
Archiving
CONTENT AVAILABILITY
5
Rhythmyx ArchitectureItem-Level Content
Management

• Transparent in Content Capture
• Content is segmented into Items with elements
  (Title, Abstract, Author)
• Each item may have multiple formats and purposes
  Text, Link, etc.
• Content items are assembled together to build
  full pages
• Use of items enables Rhythmyx to build up website
  following site structure

6
Engine-based Architecture

• Provides more functionality out of the box
• Engines produce graphical user interfaces for
  knowledge workers
• Improves ROI

7
Rhythmyx Engine Architecture Content Editors
The fields that comprise a content editor are
created and defined using the content editor
GUI. This GUI will automatically create the
underlying schema in the content repository and
the content capture screen.
8
Rhythmyx Engine Architecture Meta Management
Meta-data fields can be defined within the editor
and be either hard-coded or user-selected. Meta
can be associated through a parent-child
inheritance. Rhythmyx can also connect to
external databases to retrieve standard
enterprise Meta-data
9
Rhythmyx Architecture Workflow Engine

• State/Transition Model
• Supports
• Unlimited Schema
• Unlimited States
• Unlimited Transitions
• Transitions can be activated via User Interaction
  or Timed Event.
• Notifications are sent via email as content
  flows through system. SMTP Mail.

10
Rhythmyx Assembly EngineBuilding XSL Stylesheets

• Rhythmyx Templates
• XSL Stylesheets
• Can be loaded directly in OR
• Created in HTML and then converted
• Tags within Templates establish foundation for
  building XML DTD.

11
Rhythmyx Assembly EngineActive Assembly

• Active Assembly allows producers to quickly
  control layout changes without template redesigns
• Graphical, browser-based UI layer above
  templates
• Rearrange prominence of content based on business
  needs
• Introduce new content
• Remove content
• Choose content style from a palette of
  choices
• Flexibility is controlled to adhere to
  corporate
  standards and branding
• One template enables many layouts

12
Rhythmyx De-Coupled Publishing

• Rhythmyx Publishes Content to either File Systems
  or External Databases
• Licensing accommodates unlimited delivery
  destinations
• Publishing Mode Removes a Potential Point of
  Failure and Allows for Optimized Delivery
  Performance

13
Rhythmyx Dynamic Delivery

• Removes a potential point of failure in web
  infrastructure
• CMS has no impact on delivery optimization and
  performance

• Content destined for server-side applications is
  formatted (HTML, XML, CSV) and published into
  local repositories
• Existing Repositories can be leveraged

14
(No Transcript)
15
Using RhythmyxWith Scripting Languages
Command Content. Demand Ownership.
16
Using Rhythmyx With Scripting LanguagesWhy use
Scripting Languages?

• Scripting Languages Provide
• Ease of Maintenance
• Headers, footers and other elements can be
  included automatically in pages.
• Automated Components
• Automatic indexes, list of Whats New!
• Navigation
• Script based on file location, metadata, etc.
• Custom, Dynamic Web-based Applications
• The infamous Mortgage Calculator example,
  Personalization, Web-based applications, etc.
  Usually has a DB backend. Skys the limit!

17
Using Rhythmyx With Scripting LanguagesWhat
Content Management Adds

• With Rhythmyx, a lot of the traditional jobs of
  scripting can be streamlined
• Shared components, headers/footers, auto (and now
  manual) indexes and navigation
• Setup and maintenance is as easy or easier for
  developers
• Use, configure and modify pre-built components.
  Rhythmyx was designed to handle these things.
• More importantly, it is MUCH easier for end
  users!
• Maintain components without technical help
• Extra benefit of greatly reducing live Web and
  Application Server load
• BUT!....

18
Using Rhythmyx With Scripting LanguagesScripting
Languages STILL have a place!!

• Why is it a good idea to use scripting languages?
• Maintain investment in custom applications and
  infrastructure
• Keep custom code intact but add Rhythmyx
  functionality
• People like to use what they like to use!
• And with Rhythmyx you are free to choose any
  level of integration you need!
• So what are all the ways Rhythmyx can be used
  with Scripting Languages? Glad you asked!...

19
Using Rhythmyx With Scripting LanguagesModes of
Working with ANY Scripting Language

• 1. Embedded Script in Rhythmyx Templates
• Use existing functionality as-is in pages,
  Rhythmyx simply passes-through the script in the
  template.
• Rhythmyx can publish .anything (.asp, .php, .cfm,
  .jsp, etc.)
• Script continues to be rendered on the live
  website.
• Developers manage site much as before, but users
  can now create, edit and publish content.
• Can use HTML mockup or Just In Time publishing
  for preview

Published File With Script
Rendered Page
Rhythmyx Server
Application Server
20
Using Rhythmyx With Scripting LanguagesModes of
Working with ANY Scripting Language

• 2. Managed Code Snippets
• Theres that Mortgage Calculator Example again!
• Created by Developers, used by contributors
• Allow users to manually or automatically drop
  functional components into page (i.e. through
  Active Assembly).
• Similar to above example in that script remains
  the same, and is rendered on by the delivery
  infrastructure
• Also, HTML representation or JIT Publishing can
  be used for preview.

Published File With Script Assembled by Users
Rendered Page
Rhythmyx Server
Application Server
21
Using Rhythmyx With Scripting LanguagesModes of
Working With ANY Scripting Language

• 3. Publishing for Consumption
• Inside-out approach to CMS deployment
• Typically one of two methods (or both)
• Database Publishing Any format into ANY schema
• File System Publishing Snippets of formatted
  HTML
• Allows existing custom code to be leveraged AS-IS
  with NO modification AND
• Existing code can be rewritten to take advantage
  of formatting and rendering power of Rhythmyx.

Snippets
Rendered Page
Page with Script
Rhythmyx Server
File/Database Servers
Structured/Raw Data
22
Using Rhythmyx With Scripting LanguagesJust what
exactly is Just In Time Publishing?

• Glad you asked!
• Just In Time (JIT) Publishing allows users to see
  EXACTLY how content will appear on the live site.
• When a user previews a page
• User presses Preview
• Rhythmyx publishes the content to an internal
  stage/dev/test server
• The users browser is redirected to the published
  content
• The user sees their content with all dynamic
  elements rendered correctly
• Eliminates having to set up separate Preview
  template
• If it previews correctly, it will render
  correctly
• Easy to set up, and seamless to the end user

1. User presses Preview button.
2. File Published to Dev Server
Rhythmyx Server
Dev/Test Server
4. User sees their content and rendered dynamic
elements.
3. Browser redirected to rendered page
23
Managing MultipleChannels
Managing Multiple Channels
Command Content. Demand Ownership.
24
Building and Managing Multiple Sites

• Building the first site

• Content Capture
• Accepting Content from either End User of Data
  Feed
• Associating Meta-Data with Content
• Storing Content in the System Repository (SQL
  Database)

25
Building and Managing Multiple Sites

• Building the first site

• Content Assembly
• Retrieving Approved Content from the System
  Repository
• Assembling the item(s) into the proper structure
  and format
• Applying the look and feel as defined by the XSL
  stylesheet

26
Building and Managing Multiple Sites

• Building the first site

• Content Publishing
• Moving Approved and Properly Formatted Content
  into the web environment.

27
Building and Managing Multiple Sites

• Building a new site with the same look, feel, and
  structure.

• Content Capture
• A defining meta-data field needs to be set - Biz
  Group HR

28
Building and Managing Multiple Sites

• Building a new site with the same look, feel, and
  structure.

• Content Assembly
• The collection of queries that retrieve content
  from the System repository (called Editions)
  would be organized by Site (Biz Unit or other
  logical entity) ex. You would have the HR Edition
  that would pull the content for the site.

29
Building and Managing Multiple Sites

• Building a new site with the same look, feel, and
  structure.

• Content Publishing
• The physical location of the web content would
  be defined in the publishing area. Each site
  would have its own defined tree structure.

30
Building and Managing Multiple Sites

• Building a new site with the new look, and feel

• Content Publishing
• Because of the complete separation of content
  from presentation, building new sites and site
  structures, is handled by the XSL template and
  publishing schema.

31
Product Road Map2004 and beyond

• Desktop integration
• Expanded integration with Office 2003 and other
  desktop clients
• Use Web Services to support advanced authoring
  functionality
• Tighter integration with standard collaboration
  platforms
• Content integration
• Document Management improvements
• Continue to increase simplicity of usable site
  migration
• Developer capabilities
• Web Services continue to evolve
• Workbench enhancements
• Content delivery
• Publisher enhancements
• Ease of use and ease of implementation
• Vertical market solutions

32
Web Services Developer Kit

• Allows developers to integrate all Rhythmyx
  functionality into any application
• Content Contribution, Rhythmyx Inbox, Search,
  Active Assembly, etc.
• Allow workflow actions
• Available for portals, Lotus Notes, Outlook and
  other enterprise applications
• Published WSDLs

33
Rhythmyx Architecture - Security

• CMS Clients
• Access via HTTPS (SSL)
• With or without SOAP depending on client
• Application Server
• User authentication and session management
• Manages interface to directory services
• Secures any publisher activities
• Rhythmyx Server
• Process content based on session permissions
• Interacts with Repository via dedicated DBMS
  accounts
• Repository
• Manages both internally stored content and
  virtualized external content

AppServer
HTTP(S)SOAP
JDBC
34
Rhythmyx De-Coupled DeliveryLowest Cost of
Scaling
Manage Content
Rhythmyx
Typical CMS
Runaway CMS Licensing
De-Coupled Delivery
35
Rhythmyx De-Coupled DeliveryLowest Cost of
Scaling
Typical CMS
CMS Tier
Delivery Tier
Rhythmyx
CMS Tier
Delivery Tier