ASH Service Level Agreement (DRAFT)

This service level agreement provides the information and guidelines set forth and agreed upon between Middleware and ASH clients for the installation and support of the ASH environment.

Middleware Primary Contact
________________________________________
Middleware Secondary Contact
________________________________________
ASH Client Primary Contact
________________________________________
ASH Client Secondary Contact
________________________________________

Service Provided

  • JBoss container with support for J2EE 1.4 applications
  • Web application for managing deployed applications
    • Applications can be deployed, redeployed, or undeployed
  • Web application for managing logging
    • JBoss's log4j.xml file can be edited directly
    • Any custom log files created under the /apps/logs directory can be viewed with the web application
    • If greater log control is needed then logs can be written to NAS space
  • Load balancing configuration
  • 1 Gigabyte of RAM
  • 6 Gigabytes of disk space
  • ~ 1 Gigahertz of processor
  • Data backup
  • NAS VPN connectivity (future)
  • Banner VPN connectivity (future)

Client Requirements

  • Applications must run entirely inside the JVM

Outages

In all cases, primary and secondary contacts will be notified by e-mail concerning outages.
If you would like to paged as well, include your pager number in your contact information.

Planned

The maintenance window for ASH software and hardware is Sunday's from 6am to 12pm.
ASH clients will be notified (2) weeks in advance of any planned outage.
Planned outage dates and times are negotiable.

Unplanned

ASH clients will be notified as soon as possible when any unexpected failures occur.

Problem Priorities

Urgency Description Time to Address
Critical Unplanned outage.
Critical component failure.
System is unstable or crashed.
Immediately using on-call personnel.
Serious Degraded system performance.
System stability affected.
Bug/Security fix.
Same day using on-call personnel.
Normal Duplicate component failure. Immediately during business hours.
Low Scheduled bug fix.
Scheduled software enhancement.
Maintenance window.
 
middleware/ash/sla.txt · Last modified: 2009/10/07 17:17 (external edit)
 
Except where otherwise noted, content on this wiki is licensed under the following license:CC Attribution-Noncommercial-Share Alike 3.0 Unported
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki