Skip to Content

Solution Manager 7.2 SP04 Upgrade using Maintenance Planner tracks

Greetings Experts,

We have successfully upgraded our Solution Manager system to 7.2 SP03 and are now ready to upgrade to SP04.

I understand the strategy behind Maintenance Planner tracks and have a question.

As both ABAP and JAVA instances comprise the Solution Manager system, should we include them both in the Solution Manager track or are we now required to plan AND execute their upgrades separately?

Thanks for your input.

Mike Dumas

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Feb 27, 2017 at 03:56 PM

    Hello Mike,

    I had this upgrade recently done on our test system and I did them both separately and it did work as expected.

    Thanks

    Yogesh

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 28, 2017 at 07:22 AM

    Hi Michael,

    Yes it was the case of dual stack in solman 7.1 where you have one SID as well.

    As now you have 2 different systems in Solution Manager 7.2 ABAP and JAVA with 2 different SIDs you need to generate 2 stack.xml files

    one for abap and one for java and then continue to upgrade them one by one.

    hope this resolves

    Thanks

    Prakhar

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 27, 2017 at 05:37 PM

    Thanks Yogesh.

    I was expecting to perform two upgrade processes on Solution Manager instead of just one. That implies we will also have two separate Solution Manager (ABAP/JAVA) Tracks in Maintenance Planner.

    Add comment
    10|10000 characters needed characters exceeded