how to handle customized java packages during upgrade EHP2.NW7.0 to EHP1.NW7.3

[Former Member]

Hi,

We are upgrading our portal system from EHP2.NW7.0 to EHP1.NW03 using the SUM tool.

In the step, 'review The target release components list' we have options about what to do with each software component. Most of the components are in status deploy. Some of our custom built components have only the option to 'Reject' or 'scan inbox'. Scan inbox repeats the checks and we donot want to reject the components. We would like to keep those components in our upgraded system.

Any advice on how to proceed.

Regards,

Mazdul

[Former Member]

Yes, it was solved.

If your system is part of NWDI system, you have to follow the steps mentioned in the SUM guide. This is very important. Page 32 of Update Guide - Update of SAP Systems Using Software Update Manager 1.0 SP07

If your system is not part of NWDI, or if you have missed the steps when you started, you can try the work around that we did.

In our case, the system was not part of NWDI but the softwares were developed in exactly similar systems and imported.

Workaround we did:

We exported the required .SCA files from the NWDI system we used to build it. Placed them in the upgrade directory where we had placed other SCA files. And then did a rescan. The SUM tool was able to identify the packages and the target package level remained the same in the system.

But most probably the old packages will not work as the complitation was done using old java packages. So you have to ask your developers to build the packages again, after the upgrade and import them. 

Hope it solves the issue.

Please note that the best way to do is to follow the procedure in the SUM guide.

Regards,

Mazdul

[former_member193086]

Thanks for the detailed response. I will follow your recommendations.

[former_member193086]

Hi - Did you resolve this? I'm facing the exact same issue.