on 12-23-2012 10:43 PM
Trying to upgrade Portal from NW 7.0 to NW 7.3.
SUM Versions used: 1.0
SP: 6 Patch Levels: I tried both 0 and 1First_error_source.png
Dec 23, 2012 4:06:41 PM [Info]: com.sap.sdt.j2ee.tools.appl.ApplPackFile
Loader.loadUsageMapping(ApplPackFileLoader.java:365) [Thread[main,5,main]]: Mapp
ing file /usr/sap/EPA/SUM/java/config/UsageMapping.xml not found, will return em
pty map.
Solution Manager Configuration: See attachment for LVSM output:
Solution Manager configuration for the LVSM output:
When I tried to add SAP ERP 6.0, it produced an inconsistency and also LVSM showed warning; however 3 products as shown above displays no error.
I've tried several options with no luck. I also tried to download stack.xml more than once with different configurations ending up with the same error message.
Does anyone know possible reason for this situation?
Thank you,
Bala
Update: I reviewed ABAPProductUsages.xml (located in SUM/java/config directory) and found ASS instead of AS. I deleted one S, repeated the pahse, continued before running into 'sap.com/BI' cannot be found error. Currently investigating why. Will update.
I reviewed more documents on definition of Products, Product instances, Product Systems, Software compnonent versions, Hub versus Sidecar etc. Based on review, I changed the Landscape pattern from Hub to Sidecar because the portal is used by
SRM system but not ECC. I ran LVSM, and it returned Green. The configuration seems correct but when I try to run MOPZ, it seems running forever while calculating "Target Constellation". Here is the screenshot:When I set the landscape pattern to Hub or blank, it triggers the error message I menioned in my original post. I believe Sidecar seems like correct setting for how we use Portal but not able to create stack file. Any thoughts?
The documents listed below were useful to get a good understanding on terms products, product instances etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Kush,
Yes, this blog provided all details on portal upgrade. I reviewed my Portal system, configured it as sidecar to SRM system-details in the blog, generated stack.xml, and then performed the upgrade. The upgrade took about 15 hours for portal.
And I published this blog titled "Tips on Portal Upgrade".
Good luck.
Bala
User | Count |
---|---|
78 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.