SSP Recommended System Requirements

SSP is typically deployed with independent web server and database installations. While it is technically possible to run both the web server and DB on the same server, it is not recommended for security and performance reasons.

Web/Application Server

This server may be a virtual or dedicated server. With the increase in virtualization capabilities and the flexibility it provides, the recommended configuration is a virtual server with access to 4+ cores and a minimum of 4GB of memory and 10GB of hard disk space dedicated to SSP. 8GB of total memory of this server for the OS and SSP is recommended. See the Load Balancing documentation for additional details on options for distributing the load across many physical, virtual or logical front end web servers.

Database Server

SSP typically utilizes existing database server infrastructure, and the existing memory and disk allocations normally suffice. A minimum of 8GB of RAM and 20GB is required. See specific server performance details in the MsSQL and Postgres documentation.

SSP Security

SSP makes extensive use of a multi- tiered security model for the application. The first tier represents the objects that make up the SSP system and users. This first level of security loosely corresponds to roles in the system (Administrator, Advisor, Student). An example of this security would be whether an individual has the capability to send an Early Alert in SSP. The second tier of security represents individual data records and what users can manage the data. For example, a Journal Entry may be marked as a disability record when created, in which case only those users with disability access applied to their user account will be able to view the data.

The SSP installation and configuration process will provide pre - configured permissions for the install. Users may be assigned these permissions by way of organizational units in Active Directory (or other services) or manual assignment of users to permissions. Supported authentication sources include LDAP /AD , local database, CAS or Shibboleth .

SSP Technical Lead

An institution should explore having a technical resource that is familiar with SSP setup, configuration, and administration of the system. This individual will act as local support at the institution beyond the traditional help desk service that an institution typically offers. This individual will be able to answer basic technical questions about SSP and perform administration of the system through its administrative screens. The most important purpose of this role is to determine what can be addressed by internal staff and what requires the assistance of a vendor. It will be the responsibility of the technical lead to interface with the vendor to resolve issues and understand the necessary fix. The technical lead will report back to the institution concerning SSP issues, timeline for completion of bugs, and other technical items the institution may wish to be aware of.

The technical lead should have 1 - 2 years experience in technical support or programming. She/He should be well versed in technology, be able to troubleshoot campus systems and provide clear communication to the vendor. The technical lead will understand the SSP data loading process and how to debug the process in the event a bug occurs.