tag:blogger.com,1999:blog-2813822908483947681.post244906412701339695..comments2024-02-08T13:45:58.449+00:00Comments on Graham's PeopleSoft Blog: 5 things about PeopleSoft Update Manager Change PackagesGrahamhttp://www.blogger.com/profile/09150581893711693248noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-2813822908483947681.post-15950613576486558962018-02-12T10:55:17.616+00:002018-02-12T10:55:17.616+00:00@RK> Sorry for delay in getting back to you.
F...@RK> Sorry for delay in getting back to you.<br /><br />Firstly, you can continue your original practice of applying update to Demo first. The only reason oracle recommend applying it to demo after you've updated production is because it help achieve the desired state of Demo. That is "demo should contain only updates that have been applied to production". If you apply to demo first then that's still ok as long you back it out of demo if the update never makes it to production.<br /><br />The very first time you apply a Change Package (CP) it runs in initial pass mode. In this mode you get a chance to manage (i.e. compare and reapply customisations) customised objects and then at the end of the job it creates a NEW CP which contains your recustomised objects . It is this NEW CP that you then apply to UAT and Production. However, as this CP contains customised objects it's NOT the CP you then want to apply to Demo. So you need to go back to the original CP (ie the one that gets renamed during the initial pass). Hope that makes sense.<br /><br />Graham<br />Grahamhttps://www.blogger.com/profile/09150581893711693248noreply@blogger.comtag:blogger.com,1999:blog-2813822908483947681.post-35168612059807079302018-01-30T17:53:14.980+00:002018-01-30T17:53:14.980+00:00I know this is an older post, but can you clarify ...I know this is an older post, but can you clarify 5)in the above comment? Apply the orig change package to DEMO environment. Can you elaborate on that, do you move that CP as a Move to production or how is CA assistant configured to do so? Traditionally before PUM, I'd apply the update to DEMO first and then migrate it to my dev environments and if I understand this, we now do DEV first then DEMO and I just want to make sure how I apply the update to DEMO. Thanks<br />RKhttps://www.blogger.com/profile/15260313907391306931noreply@blogger.comtag:blogger.com,1999:blog-2813822908483947681.post-17320897561540618092017-05-17T16:55:00.200+01:002017-05-17T16:55:00.200+01:00@Bart22:
1. the 'initial' pass - it doesn...@Bart22:<br /><br />1. the 'initial' pass - it doesn't only create the zip file, it also actually moves the changes to the target database, correct?<br /><i>GS: Yes. That's correct. Your initial target is normally going to be Development (or somewhere that has your customisations and closely matches production). </i><br /><br />2. Is it wise to create a demo change package and apply to an existing demo database (we don't want to use the PUM Image as demo database), and create separate change package(s) for the other databases? What is best practice?<br /><i>GS: It is the aim to keep Demo in step with Production. Any update you apply to production you should also apply to demo and equally don't apply an update to demo that you will not also apply to Production. It's vital you have a demo system which reflects production (less customisations) in which you can recreate issues. So, best practice is to <br />1) load target (dev) into PUM Image, <br />2) create change package and <br />3) run IP against target (dev), <br />4) this IP process will create a new "updated" change package which then can be applied to UAT/QA, production but NOT demo. <br />5) You need to apply to demo the original Change Package used in the Dev IP (this CP is renamed at the end of IP so you don't lose it). </i><br /><br />Hope this is helpful.<br /> GrahamGrahamhttps://www.blogger.com/profile/09150581893711693248noreply@blogger.comtag:blogger.com,1999:blog-2813822908483947681.post-13369212428024261302017-05-16T11:01:24.805+01:002017-05-16T11:01:24.805+01:00Graham,
Thank you for the overview - I have two q...Graham,<br /><br />Thank you for the overview - I have two questions:<br /><br />1. the 'initial' pass - it doesn't only create the zip file, it also actually moves the changes to the target database, correct?<br />2. Is it wise to create a demo change package and apply to an existing demo database (we don't want to use the PUM Image as demo database), and create separate change package(s) for the other databases? What is best practice?<br /><br />Many thanks,<br />BartBart22https://www.blogger.com/profile/08224700879216784574noreply@blogger.com