Web Content Management System
The University seeking proposals from experienced and qualified vendors for a Web Content Management System for the University.
Technical Specifications
1. Operating System and Database
All University websites run on Red Hat Enterprise Linux 5, Apache 2, PHP 5, and MySQL 5. .
a. Describe other operating system services (and version releases) and utilities required by your solution.
b. Specify the notification protocols supported by the system.
c. If the CMS requires a database, list standard database connection types that the CMS supports (example JDBC).
2. Web/Application Server
The CMS web/application server MUST be certified and supported on Apache HTTPD, PHP 5. Specify which releases the system supports.
3. Load Balancing
The CMS SHOULD support load balancing to provide scalable, highly available services. Specify supported methods for load balancing.
4. Virtualization
The CMS web/application server SHOULD support virtualization.
5. Software Installation and Maintenance
a. The system MUST be installed and updated by University personnel on University -owned hardware located in University data centers.
b. Describe the installation and update procedures, including:
i. Whether root privileges are required
ii. The process for notifying customers of new
releases/updates
iii. The version/release support strategy, including:
1. Major and minor version release frequencies.
2. How system bug fix patches are made available
(individually or as a service pack).
3. The strategy for rolling out future releases.
4. The strategy for determining functionality in future
releases.
c. Specify the recommended and minimum memory, number of
CPUs, and disk space for the proposed server hardware. List the
requirements for virtual and non-virtual environments.
d. Describe your system’s capability to support local modifications to
updates.
i. Do you provide APIs?
e. Provide a summary of known outstanding bugs associated with the
current software version.
f. Specify whether, and how, we can install a test instance of the
CMS on University servers during the pre-award period.
