XI 3.1 SP3, what do you need?

[Former Member]

Hi all,

For the upcoming XI 3.1 SP3, I'm trying to understand what type of information (beyond the usual guides) would be helpful to streamline your upgrade project?

Our objective is to use your feedback and publish helpful content on the BOpedia wiki : [http://wiki.sdn.sap.com/wiki/display/BOBJ/BOpediaonSCN|http://wiki.sdn.sap.com/wiki/display/BOBJ/BOpediaonSCN]

Thanks

JC

[Former Member]

Thanks for all answers.

Just to set expectations, it will not include all FixPacks. The current information I have (unconfirmed until the final cut) is that it will include up to FP 2.5

The reason for this is simple, at one point there needs to be a cutover so the code can be built, stabilized, go to the qualification tests and the release process. There is a tradeoff between how far in the process you keep inserting code and the quality of the release.

We're obviously constantly in research for the best balance here.

Thanks

JC

[Former Member]

JC:

It would be good to know information on distributed deployments;

such as how to handle upgrades on machines that are distributed/firewalled off..and HA machines..etc..

More information needed on Unix deployment, I always find the guides are weak when it comes to unix information.

Also: There needs to a way to communicate clearly; the upgrade scenarios.

The table of that information was good in the past.

Example: IF you are on SP1...then do this

if you are on SP2 then do this

if you are on SP1 with any FP do this..etc...

As many installation scenario that can be covered in a TABLE should be presented...that way you get customer types.

ALSO; Information about deployments with SAP customers (BW or ECC)..duh..that is obvious, the SP3 materials should have tons on that, but it's lacking.

Personally I think there should be a separate SAP IK SP3 upgrade GUIDE!!! why not.....BOBJ and SAP are one right...why not provide MORE info for your customers that are hybrid (SAP + BOBJ)...

Thanks,

Dwayne Thomas

[Former Member]

For me please just make the SP3 available ASAP, make sure it install fast and contains all fixed issues from previous fixpacks.

Don't worry the users will take care of the testing )

[Former Member]

My suggestion is to be very careful. Based on the track record of SP2 that takes 4-7 hours to install per server (and silence install did not speed up much). Make sure you have a test environment to test it out thoroughly.

The general rule of thumb: unless your current environment is having problem AND the upgrade is addressing your problem, DO NOT upgrade just for the sake of upgrade. Wait a little bit for any defect to get resolved. It does not pay to be on the "bleeding edge".

Hope this helps.

Edited by: Simon To on Mar 12, 2010 6:26 AM

[denis_konovalov]

Hello Simon,

All post Sp2 installers fro Fix PAcks and Service Packs have been re-design to improve install speed. SP3 install should take much less time compared to Sp2.

[Former Member]

Thank you Denis.

However, the long install time was just one of the problems with SP2. SP2 has a lot of bugs. FixPacks were released one after another. Some FixPack fixed a bug but introduced another bug.

With that being said, I am sure SP3 has some new features that might merits the upgrade. But don't rush into it. Customers should test it out thoroughly first as I have suggested. Take 6 months or so, and by then, most of the bugs should have been found and hopefully resolved.

[denis_konovalov]

I completely agree that a full testing process should be in place before any upgrade.