Demonstration Template

Document Sample
Demonstration Template Powered By Docstoc
					CommonSpot Content Server        ™

Technical Overview


Presentation and Demonstration to Cornell University
June 10, 2004




                                                       Efficient Content Management
Agenda
Introduction
      Product History & Release Schedules
      Driving Factors
      CommonSpot Architecture/Framework
      Standards Support
      Deployment Timeframes
CommonSpot Architecture
    Overview
    Performance & Scalability
    Configuration Options
‘Under the hood’ demonstration
     Template Architecture
     ColdFusion integration/customization
     Content Objects, Metadata, Content Reuse
     And what ever else we have time to show…
Question & Answers
                                                 Efficient Content Management
Introduction
Product History & Release Schedule
     Version 1.0 released end of 1998
     Version 4.0 released April 2004 (7th major release)
     One major release and two point releases per year

Driving Design Factors
     Easy of Use for non-technical users
     80-20 rule, comprehensive out-of-the-Box framework with extensive
         integration/customization support
        Integration between un-structured and structured data




                                                                 Efficient Content Management
Deployment Timeframes
    Framework development in weeks not months, average framework
     development is 2-4 weeks

    Typical implementations are lead by one or two technical
     developers

    ColdFusion talent provides significant leg up in extensibility and
     customization, but not required

    PaperThin provides Fundamentals and Jump Start technical
     training, best practices and performance consulting, as well as non-
     technical contributor training, train-the-trainer and on-line training
     options.

    25+ implementation partners to help in implementation, if needed



                                                          Efficient Content Management
Architecture




               Efficient Content Management
CommonSpot Architecture
  100% browser based
  Require IE 5.x or greater for authoring
         4.1 (Fall 2004) will support full Mac WYSIWYG authoring
             on Mozilla
    Built on top of ColdFusion 5.x or MX 6.1 Application Server
    Future Support - Java, .NET/COM
    Integration of ASP,JSP, PERL, CGI code
    Content stored in relational database (SQL Server, Oracle,
     MS Access Database) and on the file system
    Cross Platform Support - Windows, Linux & Solaris OS,
     J2EE Application Servers (IBM WebSphere, BEA, Sun One)
    SSL
    XML, Web services, RSS


                                                  Efficient Content Management
CommonSpot Architecture
  Flexible template architecture with support for HTML/CFML
     base templates
    Rich metadata and taxonomy support
    XHTML ‘transitional’ compliant
    Full Cascading Style Sheet and CSS positioning support
    Native Support for NT/Active Directory authentication
    Custom authentication API (LDAP, third party database)
    Email notifications through standard SMTP services




                                                 Efficient Content Management
Integration and Customization
    HTML/CFML base-templates
    Custom rendering of content objects
    Custom script elements
    Native access to all application, session, & request variables
    Over 2 dozen event hooks/callbacks
        - Custom authentication
        - Approval Workflow
        - Custom Application.cfm
        - and many more…
    Low level APIs




                                                    Efficient Content Management
Performance & Scalability

Support for dynamic and pure static servers
     Intelligent, high performance caching
     Static content generation
     Auto-detection of dynamic content

Scalable Server Configurations
      Development Server
      Authoring Server
      Production Server

Multi-Server load balancing / fail-over
      Content replication
      Shared database clustering
      Shared file-system support

                                              Efficient Content Management
Configuration
                          Server A
                     (Authoring Server)


                           Site A
       File System         (public
                            site)



                            Site B
                          (intranet)
       Database




    Single Authoring server with multiple sites




                                                  Efficient Content Management
Configuration
                           Server A
                      (Authoring Server)


                            Site A
        File System         (public
                             site)



                             Site B
                           (intranet)
        Database




                             Static
                            Content
                             Site A
        File System




    A single Authoring server with multiple sites
            and static content generation

                                                    Efficient Content Management
Configuration
                                                        Server B
                          Server A                     (Read-Only
                     (Authoring Server)             Production Server)


                           Site A                          Replication
       File System         (public                          Target                  File System
                                                                         Database
                            site)                           Site A



                            Site B
                          (intranet)
       Database




                                       Possible Firewall




     Replication to a single production server



                                                                                          Efficient Content Management
Configuration
                                                        Server B
                          Server A                     (Read-Only
                     (Authoring Server)             Production Server)


                           Site A                          Replication
       File System         (public                          Target                     File System
                                                                         Database
                            site)                           Site A



                            Site B
                          (intranet)
       Database


                                                             Static
                                                            Content      File System
                                                             Site A



                                       Possible Firewall




     Replication to a single production server
          with static content generation



                                                                                             Efficient Content Management
Configuration
                                                        Server B
                          Server A                     (Read-Only
                     (Authoring Server)             Production Server)


                           Site A                          Replication
       File System         (public                          Target                     File System
                                                                         Database
                            site)                           Site A



                            Site B                      Server C
                          (intranet)                   (Read-Only
       Database                                     Production Server)


                                                           Replication
                                                            Target                     File System
                                                                         Database
                                                            Site A



                                       Possible Firewall



                                                             Static
                                                            Content      File System
                                                             Site A




    Replication to a multiple production servers
           with static content generation
                                                                                             Efficient Content Management
Configuration
                                              Server B
                          Server A           (Read-Only
                     (Authoring Server)   Production Server)


                                              Read-Only
                                               Slave           File System
         Master
        Authoring                              Server
                       Database
         Server


                                              Server C
                                             (Read-Only
                                          Production Server)

     File System
                                              Read-Only
                                                Slave          File System
                                               Server




                    Shared-database Cluster




                                                                             Efficient Content Management
Configuration
                                                       Server B
                         Server A                     (Read-Only
                    (Authoring Server)             Production Server)


                          Site A                          Replication
      File System         (public                          Target                  File System
                           site)                           Site A



                           Site B                      Server C
                         (intranet)                   (Read-Only
                                                                        Database
      Database                                     Production Server)


                                                          Replication
                                                           Target                  File System
                                                           Site A



                                      Possible Firewall




     Replication to a shared-database cluster



                                                                                         Efficient Content Management
Demonstration
Template Architecture
         Content Templates
         Navigation/Look & Feel Templates
         Base Templates (CFML)
Integration/Customization Points
           Render handlers
           Custom scripts
           Event hooks / APIs
Other Concepts
         Content Objects
         Metadata
         Content Reuse
         Static Content Generation
         And what ever else you want to see …

                                                 Efficient Content Management
Questions and Answers




                        Efficient Content Management
Contact Information


PaperThin, Inc.
(617) 471 4440

Todd Peters, President
tpeters@paperthin.com
(617) 471 4440 x 204

Mindy Daigle, Education Practice Manager
mdaigle@paperthin.com
(617) 471 4440 x201




                                           Efficient Content Management
Product Roadmap
4.1 (Fall 2004)
       Mac based WYSIWYG Editing
       Taxonomy classification
       Full transaction logging
       UI scalability enhancements
       Email Review
       And more…

5.0 (Winter 2004)
       CommonSpot for Java
       CommonSpot for .Net
       XML publication and consumption
       Web services publication and consumption
       XSLT render handlers
       RSS & Content syndication
       Facet-based navigation
       Inclusion of pre-built Flash components
       And more…




                                                   Efficient Content Management

				
DOCUMENT INFO
Description: Demonstration Template document sample