Maintenance Planner Stack. XML - Please leave comments
I notice that many might be a expert in planning your xml stacks while those working in operations or handking SAP day to day operation might not even tasted in creating xml stacks ever in their lifes.
I hope those you come by this this particular blogs can share in the comments atleast of some topics related to creation of xml stacks, purpose for, why the intention and etc.
Generally the evolution of Stacks.xml started with making installation and upgrade media available through secure network instead previously it was distributed via disc, CD and other media ( that was the way back then).
The last time around we used to receive CD's from SAP for the collection of product that we were using. After which we safeguard those CD's in a tight locker for security and safety purposes.
As time passes by when internet became more violantly available, SAP came up with loading these installation CD's through website, for me it was interesting, eventough ordering CD was easy by just raising a ticket but getting it online was even better.
Then i knew the comes SAP download Manager where you can park all you downloads and if you get ever intererupted due to network failure, the activity resumes back after and the downloads are intact with the use of SAP download manager.
Its was then SAP start introducing or maybe introduced much earlier, just that i might have realized about Solution manager t-code MOPZ ( Maintenance optimer ) this is used to download your stacks.
To cut it short now through SAP LaunchPad -> SAP has Maintenance planner . Now this is where it get more simpler for integrator, installers, implementers, compared to previously it requires tremendous effort navigatin through MOPZ.
For those whom are experts, maybe share our ideas, how you use this day to day basis, thanks.
No comments:
Post a Comment