SUM Solution Manager 7.2 SP12 Upgrade query

[avijish]

Hi Experts,

I am planning to Upgrade my Solution Manger from SPS08 to latest SPS12 on Windows/MSSQL 2012 but have below queries.

1. The stack XML generation process suggests adding the JAVA stack with different SID to Maintenance Planner(MP) manually and creating 1 stack file for both ABAP and JAVA after defining dependencies(as per upgrade guide). I have both these systems available on MP, do I still need to register JAVA stack manually or I can directly define the dependency of JAVA stack into ABAP stack and continue to generate the Stack XML for SUM tool

2. As above process will generate one single Stack XML and I understand I have to run the SUM tool twice, once for ABAP using ABAP sidadm login and once for JAVA using JAVA sidadm login which means running two upgrades. Should I use the step 1 Stack XML for both? Or should I create two separate XML for the ABAP and JAVA systems individually and use for the respective SUM upgrade.

3. Also is there a sequence eg ABAP SUM upgrade process first then JAVA SUM upgrade process

4. Which SUM guide to refer SUM for ABAP, SUM for JAVA or SUM for dual stack?

Anyone who has gone through this upgrade any inputs will be highly helpful. Thanks in advance

Regards

Vijish

[timkarl89 · Accepted solution]

Hello Vihish,

1. I am not sure what you mean with the "stack XML generation process". You are asking for a SPS-Update. So both systems (ABAP and Java) should already be registered to a LMDB and a update into the SAP Backbone should be in place. This process ensures the system data in the maintenance planner application. So you need to generate a separate XML for AS ABAP and AS Java since with 7.2 we are speaking about a splitted dualstack.

2. Yes - two separate SUM runs with two separate stack.XMLs (please be aware of: with SPS9 the SolMan-Java-stack uses the Netweaver 7.5 stack; ABAP stays on NW7.4 because of the dependency to the CRM software components.

3. I always start with ABAP:

• ABAP takes a way longer since the software component packages are implemented in a sequence (AS Java uses just the latest on). So from a planning perspective I start with ABAP first
• Java uses the UME of ABAP, so you can't operate Java without ABAP. The other way around works: so while SUM is updating Java, you could continue with some post-update activities on AS ABAP (e.g. SPAU - which could be time consuming)

4. For ABAP you should use the ABAP guide; for Java you should use the Java Guide 🙂

Kind regards

Tim

[avijish · Accepted solution]

Hi timkarl89

Thanks for your kind response which answers all of my queries. Yes as both ABAP and JAVA systems with different SIDs are registered on MP I can create two separate XMLs and continue with the upgrade. Thanks again!

Regards,

Vijish AN