ATTACHMENT_16__SOFTWARE_RELEASE_TO_PRODUCTION_PROCESS.pdf

Page 1 of 6 8/03/12

Completing and Submitting a Software Release to Production

TCO-SYS-002-Software Release-INST

Purpose: Complete and Submit a Software Release Instruction Form for Processing

NOTE: Processes TCO-COMM-001-Software Notification Process, TCO-COMM- 002-Transmittal, and TCO-COMM-003-Information Bulletin should be followed.

A separate Software Release Information Form must be submitted for each platform and/or move type.

Any information and/or documents created in the completion of this process should be filed in the proper folder(s) for audit purposes In support of the new deployment plan process for our release sheets, CMSG still requires an email alerting them to the fact your software will be released to production. Please send this email 24 hours before your release/deployment so they can plan their work accordingly. Be sure to include the deployment plan link on your email.

Web Software Release Information ->

For an INITIAL Web release to production:

If it has a Siteminder/eAuth interface, the request MUST be submitted to IPUSO two weeks before the application is scheduled to be up in production. The OCIO team only meets on Monday and Wednesday and the request must be approved by them before it will be implemented.

The RFA for the database and the web configuration must be submitted to IPUSO one week before the application is scheduled to be up in production. The software released for initial configuration does NOT have to be the final software. This allows IPUSO to complete any security paperwork required to secure user ID’s and passwords. Notify CMSG staff two working days before the one week timeframe to complete the detailed instructions that accompany each move.

If a preliminary version of software is released for configuration purposes, the web will not be brought up until the final software has been installed.

When a date is known or firmed up as testing proceeds, provide the date to CMSG staff.

This will allow the production staff (IPUSO, DBMO, and eAuth Team) as well as CMSG to manage their workload.

For UPDATES to existing webs:

If there are no eAuth or database changes needed, notify CMSG staff two working days before it is required in production to put the move together and complete the detailed instructions that accompany each move. Even if you do not have the final software together, this will allow preliminary software to be gathered and instructions to be completed and waiting until final software is available.

Page 2 of 6 8/03/12

For DATABASE changes:

The DBA’s require 24-hour notification before any after-hours (after 3PM) work will be done in either TCO or production.

For Software Rollbacks:

Follow the steps below. A new System Release Checklist and Software Release sheet is required for restoring previous versions of software in production. The previous version of the KC287 needs to be referenced in the System Release Checklist and Software Release sheet you are requesting to be restored to production level.

Release Procedures:

1) Lead Tester will prepare the Web Software Release Information Form when the current tested and certified software is ready for release to production. The form is found on the TCO SharePoint site:

https://fsa.sc.egov.usda.gov/mgr/itsd/otc/TCO/Shared%20Documents/Forms/AllItems.aspx

2) The following describe the information for each Block of the release form:

Application Name: Enter the application name of the software ready for release

Date: Enter the current date

Type of Move: Select the box pertaining to the type of move o Web o DB o eAUTH o EAS o MQ o Batch o Other (FSA-13A’s, etc)

Loading Timeframe:

o Date to be loaded – Enter the date the move is to be loaded in production.

o Time to be loaded – Enter the time or time frame the move is to be loaded in production.

Database Moves (including DTS): Complete on a DM move to production o Database Name – Enter the database name o Database Type – Enter the database type o DBA notified – Enter “Y” or “N” if DBA has been notified 24 hours in advance o SSIS instructions – Attach SSIS installation and/or scheduling instructions.

o List ALL KC-287’s: Enter into the boxes all build KC-287 control numbers for this release. Start with the most recent control number. If a control number is obsolete enter “obsolete” along side the number in the box. Enter into the boxes all FSA-13A’s that are required for production access.

o Other: Provide any other information believed necessary to facilitate preparation of the release.

o If this is Shared Library, Shared Service or configuration change (i.e., JNDI change) that impacts other applications – make sure the following steps are included.

o Dependent applications need to be listed on the Release Sheet for CMSG

- you should have all applications listed on the 287(s). If you do not have them on a 287 – contact your developer to verify that no applications are impacted.

https://fsa.sc.egov.usda.gov/mgr/itsd/otc/TCO/Shared%20Documents/Forms/AllItems.aspx

Page 3 of 6 8/03/12 o Verify that these applications get carried forward onto the RFA.

o List these dependencies on the SharePoint calendar move request (there is a block just for this). Be sure to discuss with IPUSO on the weekly CERT-2-PROD meeting (every Tuesday at 2:00).

o CMSG – please work with the tester if you notice any missing dependencies on production moves – you are the group that will be contacted by IPUSO if something is missing.

o If files are outputted, list additional information o Include the following verbiage if this release sheet is for FSA-13A’s: “Please create a RFA to release all (project name) FSA-13A’s for (project name) processing that will be needed in production.”

o Request production staff to update the Release Event on the TCO Home SharePoint site Department Calendar on completion.

TCO Home page: https://fsa.sc.egov.usda.gov/mgr/itsd/otc/TCO/default.aspx

Complete Event items for the specific release:

o RFA# o Known Dependencies o RFA/Deployment Status o Prod. Processing Comments o RFA Completion Date o Complete System Release Checklist. See https://fsa.sc.egov.usda.gov/mgr/itsd/otc/TCO/Shared%20Documents/Forms%20a nd%20Templates/System%20Release%20Checklist.docx for template.

NOTE: CERT web applications are restarted every morning so any configuration changes are picked up daily – Production does not perform these daily restarts. Any configuration changes or Shared Libraries/Services require a manual restart for dependent applications.

List pages modified: List any pages that must be modified for production (for database access, production groups, etc.).

List pages removed: List any KC-287’s that show pages to be removed.

List notification: List who should be notified by production staff when completed (e-mail or phone?).

Tester Name: Name of tester completing request.

3) E-mail the completed Web Software Release Information Form to the CMSG mailbox

(ug-mokansasc2-cmsg). The subject line should include the application name at the beginning and followed with the software release number. The contents should contain information for the release. In support of the new deployment plan process for our release sheets, CMSG still requires an email alerting them to the fact your software will be released to production. Please send this email 24 hours before your release/deployment so they can plan their work accordingly. Be sure to include the deployment plan link on your email.

4) CMSG review and process the Web Software Release Information

Review the Web Software Release Information form for discrepancies and return to

Lead Tester if any are found

Locate the software and/or data and secure o S:\TCO-Shared\Test_Area is where the files are kept o S:\TCO-Shared\Test_To_PROD is where CMSG copies the files for IPUSO to retrieve

Request check of the file size from the Lead Tester https://fsa.sc.egov.usda.gov/mgr/itsd/otc/TCO/default.aspx https://fsa.sc.egov.usda.gov/mgr/itsd/otc/TCO/Shared%20Documents/Forms%20and%20Templates/System%20Release%20Checklist.docx https://fsa.sc.egov.usda.gov/mgr/itsd/otc/TCO/Shared%20Documents/Forms%20and%20Templates/System%20Release%20Checklist.docx

Page 4 of 6 8/03/12

Create the RFA (Request for Action) and submit to IPUSO for implementation. If it is a DB then the IPUSO will pass RFA to DBMO.

Notify Lead Tester of completion and RFA numbers o Reply to all in original email

File any documents in the appropriate place for auditing

Software Release Information -> (for County/State Release – Sys36/AS400)

Release Procedures:

1) Lead Tester will prepare the Software Release Information form for a county or state release that is ready for production. The form is found on the TCO SharePoint site:

https://fsa.sc.egov.usda.gov/mgr/itsd/otc/TCO/Shared%20Documents/Forms/AllItems.aspx

2) The following describe the information for each Block of the release form:

Release No.: Enter the release number (none if Beta or Transmission)

County: Enter the County or State of the release (dependent on Beta or Transmission)

Select: enter Beta or Transmission to a specific site if appropriate

Date: Enter the current date

Application Process: Enter the application name of the software ready for release.

Library: Enter the library to be loaded in.

o List ALL KC-287’s in the “KC-287 No.” boxes: Enter into the boxes all build KC-287 control numbers for this release. Start with the most recent control number. If a control number is obsolete enter “obsolete” along side the number in the box. Enter into the boxes all FSA-13A’s that are required for production access.

o First/Lastjob Information: Identify module, how and when it should be executed.

Specify whether the lastjob can be executed more than once after national installation. Attach the lastjob sheet

File Information: Provide instructions related to installation and/or deletion of files, etc., including KC-287 No.

Other:

o Any other information specific to the release o Include the following verbiage if this release sheet is for FSA-13A’s: “Please create a RFA to release all (project name) FSA-13A’s for (project name) processing that will be needed in production.”

o Request production staff to update the Release Event on the TCO Home SharePoint site Department Calendar on completion.

TCO Home page: https://fsa.sc.egov.usda.gov/mgr/itsd/otc/TCO/default.aspx

Complete Event items for the specific release:

o RFA# o Known Dependencies o RFA/Deployment Status o Prod. Processing Comments o RFA Completion Date o Complete System Release Checklist. See https://fsa.sc.egov.usda.gov/mgr/itsd/otc/TCO/Shared%20Documents/Forms %20and%20Templates/System%20Release%20Checklist%20V1.1.docx for template.

https://fsa.sc.egov.usda.gov/mgr/itsd/otc/TCO/Shared%20Documents/Forms/AllItems.aspx https://fsa.sc.egov.usda.gov/mgr/itsd/otc/TCO/default.aspx https://fsa.sc.egov.usda.gov/mgr/itsd/otc/TCO/Shared%20Documents/Forms%20and%20Templates/System%20Release%20Checklist%20V1.1.docx https://fsa.sc.egov.usda.gov/mgr/itsd/otc/TCO/Shared%20Documents/Forms%20and%20Templates/System%20Release%20Checklist%20V1.1.docx

Page 5 of 6 8/03/12

3) E-mail completed Software Release Information form to the CMSG Sys36/AS400 Support Team, Melvin Hawkins, Christine Jones , and Melissa Mayeaux. The subject line should include the county/state release number. The contents should contain information for the release.

4) The CMSG Sys36/AS400 Support Team will review and process the Software Release request.

Review the Software Release Information form for discrepancies and return to Lead

Tester if any are found

Locate the software and/or data and copy to the Release Library o Software is located in the S36/AS400 on the control system

Request the Test Lead to verify the Libraries

Create the RFA and submit to IPUSO for implementation.

File any documents in the appropriate place for auditing.

Completion of RFA Implementation

1) IPUSO will update the Release Event in the Department Calendar found on the FSA

SharePoint Home site at this location.

2) Lead Tester and interested parties will refer to the Department Calendar on the TCO

SharePoint site for production status

3) Instances when software goes directly to production, the BI Support Team or IPUSO will send email notification to the Non-TCO Tested Software (NTTS) team when complete.

NTTS team will ascertain if software needs to be installed in CERT for syncing and testing purposes.

Process Completed

Page 6 of 6 8/03/12

Version Control Summary

Date Version Comments Authors

08/11/2010 1.0 Document DRAFT Glenn Olvera

08/25/2010 1.0 Document for Review Glenn Olvera

05/23/2011 1.1 Updates for FSA-13A Paul Spencer

08/16/2011

1.2 Updates to include Shared Libraries

instructions

Steve Holliday

08/03/2012 1.3 Added verbiage to Notes section on Page 1 and Step 4 to ensure lead tester sends CMSG release email 24 hours prior to moving software to production. Added verbiage to Page 5 to include NTTS follow-up when an RFA is completed.

Steve Holliday