Table of Contents
Configuration Management
Environment Builds
Emergency Builds
Emergency fixes follow a similar SDLC process as that employed for regular changes. The reporter of the productioin issue must validate the applied fix in a near-to-production environment before the change is deploymed to PRD. The greatest differences between the standard change process and an emergency fix lies in the the use of the environments, the flow of the change through those environments, amd the speed with which the entire change cycle is completed. An Emergency Change Order (eCO) must be submitted to the CAB <link to CAB> for the purpose of notifying the help desk and creating a record of the unplanned change.
...
- once the fix is introduced in downstream environments, the work in-process that is not yet present in PRD may negatively impact the fix applied and additional work may be required
- the bug fix may negatively impact the work in process causing re-work to those efforts
Emergency Build Process
Scheduled Build Process
Kuali Planned Release Schedule
Tools
Resources
How-To's
Data Refreshes
DBA SLA for Refreshes
- Standard schema refreshes scheduled through Control M = same day turnaround. These refreshes are designed to use the PRD export created overnight every night. Therefore no DBA action is required.
- Schema refreshes that require manual intervention from the DBA team = 24 hour turnaround following receipt of RIP.
...
Refreshes requiring retention of the attachments table (DR for example)
Log
| Date | Target Environment | (PRD) Source backup date | Requestor | Reason | Form |
|---|---|---|---|---|---|
| TRN | Pam K | Post month end refresh | July 8 2014 Refresh (all but SUP) KFS Environments Request.docx | ||
| SUP | Pam K | Post month end refresh | July 2 2014 Refresh KFS-SUP Environment Request.docx | ||
| YE | Pam K | Post month end refresh | July 8 2014 Refresh (all but SUP) KFS Environments Request.docx | ||
| UAT | Pam K | Post month end refresh | July 8 2014 Refresh (all but SUP) KFS Environments Request.docx | ||
| DEV | Pam K | Post month end refresh | July 8 2014 Refresh (all but SUP) KFS Environments Request.docx | ||
| DR | Pam K | Post month end refresh | July 8 2014 Refresh (all but SUP) KFS Environments Request.docx |
Requirements
| Environment | PII Script Execution | Encryption following PII scripts |
|---|---|---|
| DEV | Yes | Yes |
| TST | Yes | Yes |
| UAT | Yes | Yes |
| SUP | No* | No (data already encrypted from import) |
| TRN | Yes | Yes |
...
| Note |
|---|
Before a UAT refresh is performed, please ensure that no failed batch jobs have created orphaned processes on the UAT.BATCH server. These processes will be owned by KFSCTMUSER or "505" and can interfere with the refresh procedure. Please notify the CM or SA to check this if you are unsure whether there are orphaned batch processes present. |
Procedures
Kuali Refresh Copy Procedure.doc
Request Forms (samples)
...