on 10-12-2009 6:44 PM
When we patched MDM 5.5, we would un-install the old software via Control Panel, then install the new patched executables, restart and reload the repositories. With 7.1 this appears to have changed, as it's using SAPINST for installation.
When we apply a SP, do we need to uninstall the old version, using SAPINST, then re-install using the Install Master disc from the SP stack? Or do you just overlay the original install somehow?
I'm having trouble finding any recommendations from SAP on how to go about patching MDM, especially the newer releases.
Thanks,
Rich
You're suggesting I just "try" the upgrade, or you've actually used this methodology successfully in a Windows MDM 7.1 environment?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yep, once 7.1 is installed, you just download the new install master patchset, and use that to run sapinst and patch the various components... overlaying what's already there. It even stops & starts the services. Very nice!
Thanks guys!
Rich
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rich,
I will recommend to uninstall and then fresh installation of all the components...
There is a huge difference in the installation process of 5.5 and 7.1.
7.1 installation using SAPINST is more controlled and proffesional way...
While installing using SAPINST, it creates lots of configurations and setting, users and their permissions...
If you keep old components and trying to install in with SAPINST... then some settings may get mixed up...
So, best is to go for fresh installation using SAPINST.
Regards,
- Shailesh.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As MDM 7.1 is on Netweaver Stack, It should not be required to uninstall MDM old SP stack before upgrading.
You can take backup of everything and try to upgrade the current SP of MDM without uninstalling anything in DEV environment and only when things are working fine proceed with QA and PROD.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.