cancel
Showing results for 
Search instead for 
Did you mean: 

upgrade SP09 to SP14 SLD and CMS configuration lost

Former Member
0 Kudos

Hi all,

I have upgraded the Java Infrastructure successfully, but I had to reconfigure the SLD (object server etc.) as well as the CMS track information in order to get the Infrastructure working again. Luckyly I only had a test track with test components set up otherwise I assume I would have lost my work.

Is this supposed to happen? I can't imagine that this is the way an upgrade for a development infrastructure should work. Somehow the configuration data should be stored and reimported after the upgrade.

Maybe I missed something during the upgrade regarding the preserving of the configuration data.

Has anyone made the same/a better experience during the JDI upgrade?

Any input is greatly appreciated.

BR Helga

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

Check whether version of all components in JDI and WAS is same.

Version Mismatch may lead to such situations.

NEx

htammen
Active Contributor
0 Kudos

Hi Helga,

I did several updates of NWDI yet and never had such a problem.

My updates

Java & ABAP Stack: SP07 --> SP09

Java Stack: SP09 --> SP11

Java Stack: SP09 --> SP12

Regards

Helmut

Former Member
0 Kudos

We went from SP9 to 12 to 13 to 14 and had no such problems. I don't recall any specific action we had to take to preserve configuration.