View Source

CIT STANDARD OPERATING PROCEDURE

SOP to Validate CommonSpot After Upgrading

Procedure Number:
SOP 2010-000

Related Processes and Procedures:
DRP 20yy-000 Disaster Recovery Procedure Template
(Remove the above reference and include any Disaster Recovery, Standard Operating or other procedures related to the procedure documented herein).

Revision History

Date	Author	Version	Description
		0.0	New Document
		0.9	Final Draft
		1.0	Approved Document

BACKGROUND AND PURPOSE

(Provide any applicable background information and purpose of this document. For example, what are we trying to accomplish?)This document will provide detail instructions on how to validate an upgrade to the CommonSpot hosting service has been done successfully.

SERVICES

(Specifically what services are covered within this procedure? What other services do these services depend on?)

Services included within the scope of this document are indicated below: The Service Owner, Service Manager and services the included services depend on are also listed. (This is a required section for this document.)

Included Service	Service Owner	Service Manager	Service Dependencies
CommonSpot	Donna Taber	Nathan Reimer	Oracle, ColdFusion, Solaris Cluster, SAN, Network

SCOPE

(What is in scope and what is not in scope for this procedure?)

In-Scope: Instructions on how to validate an upgrade has been successfully completed.

Not-in-scope: Instructions on how to use CommonSpot.

CARD (Contingencies, Assumptions, Requirements, Dependencies)

(Indicate contingencies, assumptions, requirements and dependencies not indicated elsewhere which are required for execution of this procedure.)

Any relevant Contingencies, Assumptions, Requirements or Dependencies should be included.

Contingencies describe "what if" scenarios and how to accommodate them.
Assumptions are things which are presumed to be valid or true. Many assumptions will have a risk related to them.
Requirements are items which are necessary in order to successfully execute this procedure.
Dependencies are related items which depend on this procedure. Alternatively, the converse may also be relevant.

(If this section is not required, indicate "Not Applicable" rather than removing this section from the document).

TASK DESCRIPTION

Provide a description of the individual tasks which constitute the SOP. Flow chart diagrams may be included for clarity.)

Task Number	Task Description	Responsible Party
1.	After upgrade has completed, load URLs and check for errors: CMS Test - Read/Only: http://test-hosting.cit.cornell.edu Author: http://authortest-hosting.cit.cornell.edu CMS Production - Read/Only: http://hosting.cit.cornell.edu Author: http://author-hosting.cit.cornell.edu
2.	Login into Authoring CMS Test - http://authortest-hosting.cit.cornell.edu/login.cfm CMS Production - http://author-hosting.cit.cornell.edu/login.cfm Username: admin-cit Password: citadmin
3.	Make a change on Test page: CMS Test - http://authortest-hosting.cit.cornell.edu/test.cfm CMS Production - http://author-hosting.cit.cornell.edu/test.cfm
3.1.	How to make a change: Click Page View, then Author mode Click the Formatted Text Block element icon, then Text Make a text change, then click Finish Click the yellow icon, then click Submit Click Ok Changes have been published and should now be live on Read/only too
4.	Validate change on Read/only CMS Test - http://test-hosting.cit.cornell.edu/test.cfm CMS Production - http://hosting.cit.cornell.edu/test.cfm

PEOPLE

(Indicate functional units, titles of individuals who are both responsible and accountable for this SOP. If applicable, indicate skill sets required to execute the SOP in the event that the assigned individuals are not in a capacity to do so.)

Roles and responsibilities should be included in this section. Accountable individual or functional group for this standard operating procedure should be indicated. In the event that individuals or functional units specified cannot perform their function as described in this procedure, what skill sets would be required to perform the standard operating procedure?

APPENDICES and ATTACHMENTS follow the approval block.

Approvals

Name	Function	Comments	Signature	Date
	Director
	Service Owner
	Service Manager

Appendix A: First Appendix

Include any material for Appendix A as referenced in the main document.

(If this Appendix is not required, remove this appendix from the document).

Appendix B: Second Appendix

Include any material for Appendix B as referenced in the main document.

Add additional appendices, as required.

(If this Appendix is not required, remove this appendix from the document).

(Add any attachments that may have been too large to include in the main text portion of this document. Label as Attachment 1, Attachment 2, etc.)