1 / 12

Calypso Patch Management Policy

Calypso Patch Management Policy. Engineering Operations. Effective: Oct 22, 2013. Click to continue. Patch Management Process. Implementation Process. Maintenance. Click to continue. Patch Management Process. Contains o nly Clients HD calls Delivered as Cumulative Hotfix. SP1. SP2.

ranae
Download Presentation

Calypso Patch Management Policy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Calypso Patch Management Policy Engineering Operations Effective: Oct 22, 2013 Click to continue

  2. Patch Management Process Implementation Process Maintenance Click to continue

  3. Patch Management Process • Contains only Clients HD calls • Delivered as Cumulative Hotfix SP1 SP2 SP3 …HD’s …SERVICE PACK …HD’s …HD’s * Contains All Reported HD Calls & Select Enhancements * Delivered as periodically Service Packs August 2013 V14 …Release Trunk Branch All Enhancements & HD calls Click to continue

  4. Patch Management in V14 • The patch management​ process in V14 has two stages. • STAGE 1 - Service Packs • STAGE 2 - Client Patch Click to continue

  5. ​​STAGE 1 - Service Packs • Client receives changes to address HD calls raised by all clients and selected enhancements. • Cumulative Hotfixes are not delivered for individual HD calls. • Changes will be delivered in the next service pack by downloading a new installer. • Engineering Operations will meet with each Professional Services Project Manger when they initiate their project to discuss and agree based on their project plan how long they can take service pack updates. • At an agreed time we will branch them off a service pack to a client patch where they will only get their own changes, STAGE 2. Click to continue

  6. ​​STAGE 1 - Service Packs (Continued) • We require a client to move to their own client patch before the start of UAT to minimize changes and reduce project risk. • Drivers for making the decision on when to move to a clientpatch: A. Requirement for an enhancement that Calypso will not deliver in a service pack and R&D will require you to branch off the current service pack to get the enhancement. B. Project timelines, the shorter the project the sooner you will branch off of a service pack. C. There are rare times when Calypso will ask clients to upgrade a service pack for practical reasons, such as rolling out a mandatory Market Change. This will always be discussed with clients to coordinate.​ • Requests to branch should be routed through your project manager who will coordinate with Engineering Operations. • As all inflight HD calls must be reviewed and adjusted, moving to a client patch can take up to a week to work out depending on the number and status of in-progress calls. Click to continue

  7. STAGE 2 - Client Patch • In this STAGE a client receives​ changes only to address HD calls they report • The code fixes are delivered as cumulative hotfixes (chf files) each time an HD is resolved • All HD’s reported in this phase are included in the Next Service Pack for the benefit of other clients Click to continue

  8. Summary - Client Patch • “Service Packs” • Include changes requested by all clients and select enhancements. • Clients do not receive hotfixes, HD calls are delivered in the “Next Service Pack”. • Service Packs are delivered as a new installer and client then re-applies local configuration changes. • “Client Patch” • Created after client and Calypso agree on target version for the project. • All in-progress requests must be coordinated before a client can branch. • Only contains changes requested by the client making the request. • Changes are delivered as a Cumulative Hotfix. Click to continue

  9. Using Cumulative Hotfixes Click to continue

  10. Standard Process for Applying a Cumulative Hotfix 1. Ensure you have the current ‘Calypso Update Pack’(‘cup’) that is available on the download page installed **This is required to ensure you have the current patch.bat script before executing a hotfix 2. Apply the Cumulative Hotfix File(‘chf’) using the patch script 3. Run all of the sql files under bin/dbscripts/<db version>/sql that are named CAL-XXXX.sql. (Do not manually run other scripts.) 4.Run ExecuteSql to ensure all DB changes are applied and version is set correctly 4. Run deployLocal.batto install the updated wars 5. Test the installation Click to continue

  11. FAQ • How to tell what version you are running • The version, SP# and revision can be found in • Navigators About box • Logfiles • Do I have to take a new Installer when a service pack is released? • Yes – you must also work with product support to determine if any changes are missing due to timing of the release and any recent HD requests you may have made. • Does it matter what order I apply a cup or chf? • You must be on the min version of the “cup” recommended by Calypso before applying a “chf”, this ensures the most current version of the patch tool is used to install the “chf”. • When applying a CHF it must be a higher revision # Click to continue

  12. This policy applies to V14 only and the policy on V13 and older versions is unchanged.

More Related