Deployment Optimization During XSS Portal Upgrade

I’m in the sandbox phase of a portal upgrade project, upgrading from NetWeaver 7.01 to NetWeaver 7.5, with Usage Type EP-CORE for what is basically just a Self-Services portal (the backend is ERP 6.04). As this portal has been around for a while, EP-CORE didn’t exist when it was first installed (we’ve already upgraded once before, from 7.00 to 7.01), only the full EP usage type, so there are a bunch of extra software components installed that we don’t use and don’t need: Visual Composer, KMC, etc.

My hope was that the Deployment Optimization Option (https://blogs.sap.com/2013/07/24/doo-upgrade-and-optimize-your-sap-portal-system/) would be available to allow us to strip away all the extra junk and end up with a leaner, meaner, more efficient XSS portal. However, when I attempt to setup the upgrade stack in Maintenance Planner, the tool preselects what looks like every software component under the sun and will not allow me to deselect any. Components that I believe are only applicable to BI Java, VC, and KMC — in other words usage types EP and BI Java — are in the stack, and I can’t get rid of them. Far from stripping out unneeded components, the tool is adding even more.

I’ve tried running a CISI (Correction of Installed Software Information) process, and it appeared to work, but that obviously didn’t impact this much. I realize Boris’s old blog only talks about upgrades to NW 7.3 or 7.4, but it’s from 2013 and 7.5 wasn’t an option yet then. It also talks about this being part of Maintenance Optimizer, not Maintenance Planner, but MP is the successor to MOpz, and MOpz isn’t an option for upgrades to 7.5 anyway.

So, what’s the deal? In 7.5 are we forced to install all of the full EP software components, regardless of actual usage? Or is there some further correction, perhaps in LMDB, or perhaps in a repeated CISI process, that will influence this? Or am I misunderstanding something somewhere?

Per Maintenance Planner (after CISI), the current software product stack is:

  • EHP4 for SAP ERP 6.0 / NW7.01
  • — Portal Content
  • — Portal Content Common
  • — Portal Content Self Services
  • — SAP XSS (Self Services)
  • SAP ERP 6.0
  • — SAP XSS (Self Services)
  • — SAP NW – EP Core
  • — SAP NW – Applic. Server Java

The target software product stack is:

  • EHP4 for SAP ERP 6.0 / NW7.01
  • — SAP XSS (Self Services) NW7.3
  • — Portal Content Common NW7.3
  • — Portal Content NW7.3
  • — Portal Content Self Serv NW7.3
  • SAP ERP 6.0
  • — SAP NW – Applic. Server Java
  • — SAP NW – EP Core
  • — SAP XSS (Self Services)
  • SAP NetWeaver 7.5
  • — Application Server Java
  • — EP Core – Application Portal
  • — Enterprise Portal*

* Note on that last one, Enterprise Portal, it’s marked as “to be installed.” This seems to be the source of the problem, but I cannot find a way to deselect it. Otherwise, this appears to be correct to me. Is there perhaps a dependency from one of the Portal Content components that’s driving this?

Any insight or guidance will be much appreciated.

Thanks!
Matt

I'm in the sandbox phase of a portal upgrade project, upgrading from NetWeaver 7.01 to NetWeaver 7.5, with Usage Type EP-CORE for what is basically just a Self-Services portal (the backend is ERP 6.04). As this portal has been around for a while, EP-CORE didn't exist when it was first installed (we've already upgraded once before, from 7.00 to 7.01), only the full EP usage type, so there are a bunch of extra software components installed that we don't use and don't need: Visual Composer, KMC, etc.My hope was that the Deployment Optimization Option (https://blogs.sap.com/2013/07/24/doo-upgrade-and-optimize-your-sap-portal-system/) would be available to allow…

Deployment Optimization During XSS Portal Upgrade

Very Helpfull

User Rating: Be the first one !
Train Asked on May 25, 2017 in SAP PORTAL.
Add Comment
1 Answer(s)

    Hi Matt,

    Not sure whether Deployment optimization is fully available to select/deselect components and also the compatibility with releases.

    Keeping time constraint in mind, better option would be going with a regular upgrade (for all components) irrespective of usage. It would be quicker and simpler.

    Regards,

    Harish Karra

    Add Comment

    Your Answer

    By posting your answer, you agree to the privacy policy and terms of service.