Re: Upgrading Application Layer from 7.10 to 7.11 (328 Views)
Reply
Valued Contributor
Beth Tuttle
Posts: 203
Registered: ‎04-23-2009
Message 1 of 4 (328 Views)

Upgrading Application Layer from 7.10 to 7.11

My RTE, web ,and clients are all 7.11.228.

 

My App layer is still 7.10.

 

I have read through http://support.openview.hp.com/selfsolve/document/KM753871/binary/SM7.11_ApplicationPatchMgr.pdf.

 

Is that all there is?  Is it that easy.  Pretty much apply the patch, review the Merge Report, reconcile all of the NEW7.11 and move the changes forward to production.

 

7.10 is our first stab at SM (we've been live since 11/2009). 

 

How long, with minimal customizations, should this upgrade take?

 

Thanks,

Beth aka FlygURL

Honored Contributor
Vadim Gorda
Posts: 5,773
Registered: ‎11-10-2008
Message 2 of 4 (328 Views)

Re: Upgrading Application Layer from 7.10 to 7.11

Hello Beth,

Personally I have not done that migration because we have a deep customization in our project (SM 7.01) so it is not possible to do the migration at the moment, but my colleagues have done that migration with the HP guides and then say that it was successful. I can not tell you if they had a deep customized system, but as I know it was finished without an errors.

Honored Contributor
Jas1
Posts: 410
Registered: ‎04-05-2010
Message 3 of 4 (328 Views)

Re: Upgrading Application Layer from 7.10 to 7.11

Using the demo db, the review report was generated in 20 minutes or less. I suggest you get generate a review report off a copy of your production db, to get a better feel of how much change is required. Sometimes, trying to find the reason for a customisation and whether it is still valid for current business may end up consuming more time than expected.

Advisor
ZiggyPopp
Posts: 19
Registered: ‎04-08-2010
Message 4 of 4 (326 Views)

Re: Upgrading Application Layer from 7.10 to 7.11

We have a fairly significant tailoring in our system and it took me about 2.5 days to do the whole thing and generate the custom patch.
One thing to keep in mind though, is that HP released this without fully testing the mechanism. It is possible to create the custom patch for migration up to test and prod on one time with out errors. If you get everything right the first time, this is not an issue, but if you find issues that need to be resolved and attempt generating a new custom patch, it will fail. I worked with support for about a week on a work around, but could not get a tested/proven work around in time to move forward. Had to pull the patch from our current release.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.