One Site, Two Servers: A Cascade Server CMS Solution, by David Dent

Post on 15-May-2015

1.030 views 3 download

Tags:

description

Sites requiring an intranet and a public version present a special challenge to Cascade Server developers. In this presentation, David Dent from the United States Naval Academy will show how his team approached the problem.

Transcript of One Site, Two Servers: A Cascade Server CMS Solution, by David Dent

BY C. DAVID DENT @MRDAVE2176

ONE SITE – TWO SERVERS

UNITED STATES NAVAL ACADEMY

WHY TWO SERVERS?

Policy• Navy policy only allows us one public-facing web

server and domain.Security• Some Intranet pages contain “security sensitive”

information. (i.e. midshipman brigade movements)

Accessibility• Our intranet server is the gateway to many

applications only viewable “on the Yard”

• Homepage• Contact information• Links to files• Photos of work• Course descriptions• Faculty bios with

pictures• Midshipman Project

Briefs

• Homepage• Contact information• Links to files• Photos of work• Course descriptions• Faculty bios

WHY TWO SERVERS?

INTRANET PUBLIC

• Homepage• Contact information• Links to files• Photos of work• Course descriptions• Faculty bios with

pictures• Midshipman Project

Briefs (last updated 2008)

• Homepage• Contact information• Links to files• Photos of work• Course descriptions

from last year• Faculty bios• An “old site” folder

WHY TWO SERVERS?

INTRANET SITE PUBLIC SITE

CASCADE SERVER

Reusable Content

Expiring Content

Consistent Design

Multiple Destinations

Strong Role – Group – User security model

Non-Techie Friendly

Common Area Site Area

USNA CMS SERVER

templatemetadata set

data definition

configuration set

configuration set

content type

content type

custom content type

base page

base page

base page

Common Site Area

USNA CMS SERVER

content type

custom content type

base page

Intranet

transport

transport

base page

base page

Public

content typeIntranet

Public

CONTENT TYPE

My content types (which are shared in a common area) can’t publish to a site-specific destination

So everything gets published everywhere.

Pages that are security sensitive were getting sent to the public server.

EDUCATE ON PUBLISHING

Initial Solution.Have the users uncheck the destinations and configurations when publishing sensitive pages.

EDUCATE ON PUBLISHING

Roadblock.How do you handle folders full of files or mixed intranet and public pages?

LOCAL DOCUMENT TYPES

Common Area Site Area

templatemetadata set

data definition

configuration set

configuration set

content type

content type

custom content type

base page

base page

base page

Second Solution

CURRENT SOLUTION

Common Public Site Area

content type custom content type

base page

Intranet

transport transport

base page

base page

Public

content type

IntranetPublic

Intranet Site Area

custom content type

base page

Shared Content

CLONE PAGE

Intranet SiteThis Page is the

same as the public page

Just a reminder for the user

This is the original page

IS_USNA()

Is_USNA() is a PHP subroutine that is included but isn’t integrated (yet) into the Format/Data Definition of our “Standard Template”

PHP code does require #START-CODE and #END-CODE wrappers.

This is considered an “advanced” feature for our users.

FINAL RESULTS

PUBLIC SITE INTRANET SITE

IDEAL SOLUTION

THANK YOU

C. David Dent

ddent@usna.edu

@MrDave2176

http://www.usna.edu