Content Management System

snortfearServers

Dec 4, 2013 (3 years and 4 months ago)

428 views
























Township District 214

Content Management System

System
Manual

Revision 1.
3

DRAFT

June
24
,

2010



District 214; Content Management System, System Manual
DRAFT


Page
2

of
15



Contents


1.

System Interfaces

................................
................................
................................
................................
..................

5

2.

Infrastructure Manifest

................................
................................
................................
................................
...........

8

3.

System Backup

................................
................................
................................
................................
...................

10

4.

System Disaster Recovery

................................
................................
................................
................................
..

12

5.

Development Platform

................................
................................
................................
................................
.........

13

6.

Database Platform

................................
................................
................................
................................
...............

14

7.

Appli
cation Code Updates

................................
................................
................................
................................
...

15








District 214; Content Management System, System Manual
DRAFT


Page
3

of
15



Background


The CMS system is a custom developed solution based on the Microsoft .NET platform. The system is
used to manage web site content via a browser. It stores web pages and assets (JPGs, DOC, PDF, XLS,
etc.) in a Microsoft SQL Server 2005 database. The system
requires two production servers and one
development server. The first production server is a Microsoft Windows 2003 IIS Ver. 6.x web server, the
second is a Microsoft SQL Server 2005 Standard database server. The development server contains both
web and da
tabase servers. There is also an integration server which is not currently required for
production use.


T
h
e CMS solution is the product of a software development engagement between the district and
American Eagle Inc. In this engagement, it was specified

that the District will own the underlying
Microsoft Visual basic .NET source code for the CMS solution. The source can be modified for use within
the district as needed but not sold to other customers.


The CMS solution is deployed at the district on a VM
Ware platform. The four servers run the Microsoft
Windows 2003 Server 32 bit Standard Edition OS. See the Infrastructure Manifest, production chart for
details.


The CMS uses predefined webpage templates to allow users to create and publish web content fo
r the
district and school sites. The district site uses the following main navigation:


All the school sites use the following navigation:


The scope of the CMS solution at the district covers the following web sites:

1

www.d214.org

District 214

2

bghs.d214.org

Buffalo Grove High
School

3

eghs.d214.org

Elk Grove High
School

4

jhhs.d214.org

John Hersey High
School

5

rmhs.d214.org

Rolling Meadows
High School

6

phs.d214.org

Prospect High
School

7

whs.d214.org

Wheeling High
School

8

vs.d214.org

Vanguard School

9

nc.d214.org

Newcomer School

10

fvas.d214.org

Forest View
Alternative School




District 214; Content Management System, System Manual
DRAFT


Page
4

of
15



Each school site shares a common set of templates and a web based console to manage web content:


Each site provides CMS user access at the following websites / URL(s):

1

www.d214.org/admin

District 214

2

bghs.d214.org/admin

Buffalo Grove
High School

3

eghs.d214.org/admin

Elk Grove High
School

4

jhhs.d214.org/admin

John Hersey High
School

5

rmhs.d214.org/admin

Rolling Meadows
High School

6

phs.d214.org/admin

Prospect High
School

7

whs.d214.org/admin

Wheeling High
School

8

vs.d214.org/admin

Vanguard School

9

nc.d214.org/admin

Newcomer School

10

fvas.d214.org/admin

Forest View
Alternative School


District 214; Content Management System, System Manual
DRAFT


Page
5

of
15



1.

System Interfaces


The CMS has the following system interfaces:

1.

CMS user authentication

a.

Description:
Access to the CMS is
bas
ed on AD authentication
. A CMS user must be in
the “
District CMS Users

, AD

group
. The interface imports all users in this AD group
every morning at 7:00 a.m. via a Scheduled Task called “
Integration_WS.exe
activedirectory
” on the production database server named:
fv
-
cms1
. NOTE: users no
longer in the “
District CMS Users
” AD grou
p previously in the CMS will be marked

D
eleted
”.

b.

NOTE: User
permissions within the CMS are managed via administrator groups.
Administrator groups are granted feature and content permissions and user are assigned
to these admin groups. Users are also
assigned to a CMS manager.

2.

Staff information

(aka staff directory)

a.

Description:
Staff data is searchable on all D214 websites. Staff data is grouped by
building. Staff data is extracted daily from the APECS accounting system based on job
code. NOTE; Not al
l job codes are extracted
, the following table defines the extract
definition:

b.



c.

Staff data is exported from A
PECS

nightly
via CSV file
and imported via
a
SQL job to an
intermediate table
-
db, then imported into the CMS
. The following graphic dep
i
cts the
p
rocess:


District 214; Content Management System, System Manual
DRAFT


Page
6

of
15



d.


3.

Course information

a.

Description: TBD

4.

Application database

a.

Description:
The CMS
, written on the Microsoft
V
isual
B
asic
.NET
platform is a web based
application

run on the Microsoft IIS 6 web server. The application

access
es

a
Microsoft
SQL Server 20
05 set of databases via ADO.NET
.

b.

NOTE: the application data layer does not utilize SQL stored procedure
s
, rather it
executes inline SQL code. The database appears to generally be normalized to 3
rd

normal form.

c.

ERD TBD from the vendor.

5.

Legacy websites:

a.

Desc
ription:
Non CMS sites are displayed within the CMS via an iF
r
ame.

The goal is to
provide a seamless experience to the user where the external / legacy content is
wrapped in the CMS site header and footer.

b.


6.

Secure l
egacy websites
( aka
HTTPS
, SSL )


District 214; Content Management System, System Manual
DRAFT


Page
7

of
15



a.

Descr
iption:
Secure legacy sites are handled the same as non
-
secure legacy sites as
described in
2.5.a

with the addition of a CMS WYSIWYG module.

b.

Once the legacy site page has been created, a WYSIWYG module named

https_security


module must be added to the page.

c.

NOTE:
The
underlying
legacy site is also expected to have an SSL certificate applied

the
CMS SSL certificate is
in addition to the certificate applied within the CMS
.

7.

External websites

a.

Description;
The CMS allows links to

external sites within a CMS web page or via the
navigation menus.
The CMS
,

by default displays a pop
-
up for every external link clicked

on a CMS page or navigation item
.

b.


c.


There is a CMS managed exception site list

managed via the
Content Pages :

External
Links Exceptions

feature
.

Adding an exception requires at least email verification from
Venetia Miles.

8.

Outbound email alerts

a.

Description;
The CMS will alert CMS managers when content changes are applied.

b.

The CMS will provide email alert on reque
st for content updates to subscribed users.

Subscribed users will have the option to opt
-
out of the subscription.

c.

NOTE: The CMS must be configured to relay emails through an existing SMTP server.

9.

Inbound emails (aka Contact US

foot feature
)

a.

Description;
Th
e CMS provides a CMS managed
Contact Us

form for public use.

The
user will be presented a web page to enter the message to be delivered to the selected
recipient. The sender will not see the recipient’s email address.

10.

Inbound emails to staff

a.

Description:
T
he CMS provides a managed
Contact
S
taff

form for public use.




District 214; Content Management System, System Manual
DRAFT


Page
8

of
15



2.

Infrastructure

Manifest

Platform
VMWare ESX VM
VMWare ESX VM
VMWare ESX VM
Tier
Production
/ Staging
Production
/ Staging
Production
/ Staging
Role
Web Server
Database Server
Integration Server
IP address
10.31.253.111
10.31.253.112
10.31.253.113
Server name
fv-cms1
fv-cms2
fv-cms3
# Processors
1-XEON 2.53 Ghz
1-XEON 2.53 Ghz
1-XEON 2.53 Ghz
RAM
3.75 GB
3.75 GB
3.75 GB
# Partitions
1
1
1
Logical drives
C: 25 GB
C: 25 GB > 80GB
C: 25 GB
Operating System
Microsoft Windows Server
2003 Standard
R2
R1
Microsoft Windows Server
2003 Standard
R2
R1
Microsoft Windows Server
2003 Standard
R2
R1
Service Pak(s)
SP2
SP2
SP2
Patch #
Current release
Current release
Current release
Norton Anti-Virus
Norton Anti-Virus
Norton Anti-Virus
Microsoft .NET 2.0
framework
Microsoft .NET 2.0
framework
Microsoft .NET 2.0
framework
Microsoft IIS
Microsoft SQL Server
2005 Standard
Microsoft IIS
Microsoft SQL Server
2005 SP3
Microsoft SQL Server
2005 Express
Microsoft SQL Server
2005 SP3
VMWare Tools
VMWare Tools
VMWare Tools
Adobe Media Server 3.5
ISAPI_Rewrite Ver. 2
Custom Software
AmericanEagle CMS.NET
application
AmericanEagle CMS.NET
Stored Procs
AmericanEagle
Integration.NET
application
Login account
Type: local machine
Login: administrator
Pword: alt*2i2i&
Type: local machine
Login: administrator
Pword: alt*2i2i&
Type: local machine
Login: administrator
Pword: alt*2i2i&
SQL CMS Import
Type: local machine
Login: localsqlagent
Pword: alt*2i2i&
Package pword: CMS-
General
CMS Project: Production Infrastructure Manifest
COTS Software


District 214; Content Management System, System Manual
DRAFT


Page
9

of
15



Platform
VMWare ESX VM
VMWare ESX VM
Tier
Development
Virtual Center Server
Role
Web, Database &
Integration Server
VM control
IP address
10.31.253.99
209.175.7.52:80 and 8080
10.31.252.100
Server name
fv-cmsdev
fv-vc-1
# Processors
1-XEON 2.53 Ghz
1-XEON 2.53 Ghz
RAM
3.75 GB
3.75 GB
# Partitions
1
1
Logical drives
C: 30 GB
C: 25 GB
Operating System
Microsoft Windows Server
2003 Standard
R2
R1
Microsoft Windows Server
2003 Standard
R2
R1
Service Pak(s)
SP2
SP2
Patch #
Current release
Current release
Norton Anti-Virus
Norton Anti-Virus
Microsoft .NET 2.0
framework
Microsoft IIS
Microsoft SQL Server
2005 Standard
Web access: https://fv-vc-
1.d214.org/ui/
Microsoft SQL Server
2005 SP3
VMWare Tools
Adobe Media Server 3.5
Visual Studio 2008
ISAPI_Rewrite Ver. 2
AmericanEagle CMS.NET
application
AmericanEagle
Integration.NET
application
Login account
Type: local machine
Login: administrator
Pword: alt*2i2i&
SQL CMS Import
Type: Domain
Login: cms_webservice
Pword: pass@word2
CMS Project: Development & Support Infrastructure Manifest
COTS Software
VMWare Infrastructure
Client available: https://fv-
vc-1.d214.org/
Custom Software



District 214; Content Management System, System Manual
DRAFT


Page
10

of
15



3.

System Backup


The CMS has two major components to backup. The CMS code base and the CMS database. The CMS
code base is manually backed up from the production fv
-
cms1 server to the Integration server fv
-
cms3.


The CMS code production server is fv
-
cms1. The following gra
phic describes where the code is located:



The production code is
manually
backed up to the Integration server. The following graphic describes
where the code is backed up to:


District 214; Content Management System, System Manual
DRAFT


Page
11

of
15





The CMS database is a SQL Server 2005 database which is backed up via
multiple SQL Agent jobs from
the production server fv
-
cms2 to the Integration server fv
-
cms3. The backup jobs are run daily at 4 a.m.
The following graphic lists the SQL Agent backup jobs

on fv
-
cms2
:




The CMS database backups are backed up a second time

via NetVault jobs from the fv
-
cms3 server.

The CMS production servers fv
-
cms1, fv
-
cms2, fv
-
cms3 are all VMWare virtual servers on a host ESX
platform. Production Snap
-
Shots of these production VM(s) are made on a periodic basis.


District 214; Content Management System, System Manual
DRAFT


Page
12

of
15



4.

System Disaster Recovery


There are multiple DR processes dependent on the disaster type and severity.

1.

Partial database data recovery: Restore the nightly backup, including logs from fv
-
cms3 to the
development environment, fv
-
cmsdev. Then extract pages / content as needed to cop
-
p
aste to
the production server.

2.

Total database data recovery: Restore the nightly backup, including logs from fv
-
cms3 to the
production database server, fv
-
cms2.

3.

Partial application code recovery: Restore code files as needed from the Integration server, fv
-
cms3.

4.

Total application server recovery: Restore a VMWare snapshot file.


NOTE: Additional processes and steps TBD





District 214; Content Management System, System Manual
DRAFT


Page
13

of
15



5.

Development Platform


The CMS is developed by American Eagle

for Township District 214. The development is on the Microsoft
2.0 .NET platform in Visual Basic. The application manages and displays web sites and pages based
stored in the SQL database. File assets are physically stored on the fv
-
cms1 IIS web server an
d pointers
to these physical assets are stored in the SQL Server database stored on fv
-
cms2.

Th application data

layer does not utilize stored procedures, it instead uses in
-
line SQ
L

code to access the SQL database.


The application code is expected to be
delivered to the district in its entirety. The district has rights to
modify this code base for its use. It is recommended that the code base be loaded into a Microsoft Visual
Source Safe library to ensure code integrity.





District 214; Content Management System, System Manual
DRAFT


Page
14

of
15



6.

Database
P
latform


The CMS
stores all data in a Microsoft SQL Server 2005 32 Bit, Standard Edition, SP2 database on the
fv
-
cms2 server. The fv
-
cms2 server runs the Microsoft Windows 2003 Server 32 Bit, Standard Edition,
SP2.



NOTE: The fv
-
cms2 and fv
-
cms1 server(s) run on a VMware
host environment.


The CMS solution has
the following databases:

1.

CMSInterface

2.

District214

Neither database utilizes views, stored procedures, triggers, etc.






District 214; Content Management System, System Manual
DRAFT


Page
15

of
15



7.

Application Code Updates


Application code is developed and tested on
the fv
-
cmsdev server. Thi
s server has the Microsoft Visual
Stud
i
o 2008 IDE installed along with Microsoft SQL Server 2005 Development

database
.
Code update
files are copied to the production server fv
-
cms1 (IIS web server) and fv
-
cms2 (SQL database server).
The update files are
manually copied over the production files AFTE
R

a
file
backup has been created.