Hi There,
I have recently performed a Support Pack stack upgrade on a standalone java system and would like to share my learning and errors faced(and resolutions too :wink: ).
Just to brief about the system details:
System : SAP Enterprise Portal (NW 7.0 Ehp1)
Current level : SPS 10
Target level : SPS16
Tools used for upgrade : SUM 1.0 SP12 (for SPS upgrade) , MOPZ( for stack file generation)
From my experience working on this activity below are steps(say checklist) I could come up with to perform the SPS upgrade with SUM tool on Java system.
Please feel free comment on these steps if I am missing anything.
Sounds like we are good to start the activity :cool:
Lessons "Earned":
That looks so easy, isn't it? Well, a good planning always helps to complete the activity with less hurdles. Below are the lessons I learned from this activity and I am interested to share:
The deployment of the portal has failed.
For more information, see the following log file <Location till SUM directory>\sdt\log\SUM\COLLECT-PORTAL-IMPORT-RESULTS_01.LOG
refer to SAP note 1130469.
Resolution was available from previous discussion on SCN post: Reference NW BI-JAVA 7.01 SP6 deployment failed with error main_rules.ept
4. Finally the upgrade was completed and the system was released to business for testing and users were facing run-time exceptions while logging to the portal. We checked the default trace from NWA with filter on 'userid' and found the below exception.
[EXCEPTION]
java.lang.NoClassDefFoundError: com/sap/portal/pcm/iviewserver/NewIVSObjectDescriptor
------------------------- Loader Info -------------------------
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@cc032d6]
Parent loader name: [sap.com/com.sap.portal.ivs.systemlandscapeservice]
References:
not registered!
Resources:
\usr\sap\SID\JC<nr>\j2ee\cluster\server1\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.ivs.systemlandscapeservice\private\lib\com.sap.portal.ivs.systemlandscapeservice_core.jar
---------------------------------------------------------------
The error occurred while trying to load "com.sap.portal.pcm.system.SystemDescriptor".
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:303)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.sapportals.portal.prt.core.broker.PortalServiceItem.__createServiceInstance(PortalServiceItem.java:730)
at com.sapportals.portal.prt.core.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:543)
at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:185)
at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:153)
at com.sapportals.portal.appintegrator.accessor.system.AbstractSystemAcessor.resolveAlias(AbstractSystemAcessor.java:186)
at com.sapportals.portal.appintegrator.accessor.system.SystemAccessorFactory.getSystemAccessor(SystemAccessorFactory.java:56)
at com.sapportals.portal.appintegrator.layer.AbstractIntegrationLayer.getLocalOrRemote(AbstractIntegrationLayer.java:539)
at com.sapportals.portal.appintegrator.layer.TopLayerSwitch.mustRedirectToProducer(TopLayerSwitch.java:101)
at com.sapportals.portal.appintegrator.layer.TopLayerSwitch.getNextLayer(TopLayerSwitch.java:72)
at com.sapportals.portal.appintegrator.LayerProcessor.getNextLayer(LayerProcessor.java:273)
at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:169)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:249)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:249)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:557)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1064)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Now, that feels scary :shock: to understand Java Language. To summarize, this exception means the java could not see its SLD running, that was what I understood and apparently it is true. SLD on Java portal was not running post SPS upgrade with the below error:
Server misconfiguration. Please set profile parameter BufferInstances to false when running a multi-node cluster.
Now that's more like the language I speak :lol: . Straight forward answer for the issue, set the parameter 'bufferinstances' to 'false' when you have more than one node.
refer to section 2 on Post Installation Guide SLD of SAP NW 2004s (http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/652b1f46-0a01-0010-25ae-e7cb07b55...)
SLD->administration->Profile->Section:ObjectManager->Set 'BufferInstance' to 'false'
Now start SLD and restart Java engine on the portal.
... and like every story this is a happy ending.
Thanks for reading this blog, I hope this would have been useful to you.
Feel free to comment your views on the this post and any suggestions/learning from your experience.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
10 | |
9 | |
5 | |
4 | |
4 | |
4 | |
4 | |
3 | |
3 | |
3 |