We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byDraven Biswell
Modified over 4 years ago
Calypso Patch Management Policy Engineering OperationsEffective: Oct 22, 2013 Click to continue
© 2013 Calypso Confidential Patch Management Process Stage 1: Service PacksStage 2: Client Patch 2 Click to continue
© 2013 Calypso Confidential Patch Management Process Stage 1: Service PacksStage 2: Client Patch August 2013 V14 …SERVICE PACK …HD’s …Release Trunk Branch SP1SP2 …HD’s Contains only Clients HD calls Delivered as Cumulative Hotfix All Enhancements & HD calls SP3 …HD’s * Contains All Reported HD Calls & Select Enhancements * Delivered as periodically Service Packs 3 Click to continue
© 2013 Calypso Confidential Patch Management in V14 The patch management process in V14 has two stages. STAGE 1 - Service Packs STAGE 2 - Client Patch 4 Click to continue
© 2013 Calypso Confidential 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. 5 Click to continue
© 2013 Calypso Confidential 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. 6 Click to continue
© 2013 Calypso Confidential 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 7 Click to continue
© 2013 Calypso Confidential 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. 8 Click to continue
© 2013 Calypso Confidential Using Cumulative Hotfixes 9 Click to continue
© 2013 Calypso Confidential 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/ /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.bat to install the updated wars 5. Test the installation 10 Click to continue
© 2013 Calypso Confidential 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 # 11 Click to continue
This policy applies to V14 only and the policy on V13 and older versions is unchanged. 12
©2005 Genworth Financial, Inc. All rights reserved. Company Confidential Winflex LTCI Illustration Software February, 2006 ©2006 Genworth Financial, Inc.
Upgrading to Banner 6 University of Scranton John Tabor.
Making the System Operational
Cummins® INSITE™ Update Manager Training
Software change management
Windows XP Embedded Windows Embedded for Point of Service Support Lifecycle Nic Sagez Product Manager Mobile and Embedded Product Group.
COMOS Mobile Solutions 1.0 Simplified global collaboration
What’s New in Fireware XTM v11.9.1
Imports…and the Errors they Bring to the Table Michele Borucki CoursEval Implementation & Success Specialist.
1 Resolving Host Selector Issues. 2 Table of Contents Page 3 - 6: User unable to connect to an account. Page 7: Host Selector crashing. Page 8 - 9: Saving.
Lesson 6 Software and Hardware Interaction
MTS Delivery Development © 2009 IBM Corporation EMEA GLOBAL Total Microcode Support (GTMS)
© 2013 Calypso Confidential Introduction to Calypso Product Support 1 © 2010 Calypso Confidential.
SAP AG CSU Chico Working with IMG Copyright 1996, 1997, James R. Mensching, Gail Corbitt Contents of this file are for the exclusive use of the.
1 of 3 This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. © 2007 Microsoft Corporation.
Week 12 - Lesson 19: Configuring and Managing Updates
Software Configuration Management
1 Chapter Overview Installing New Hardware Installing Updates Managing Client Access Licenses Troubleshooting Boot Problems.
How To Keep Up With Security Patches Eric Schultze Security Strategies Microsoft.
© 2018 SlidePlayer.com Inc. All rights reserved.