Migrate EP 5 SP6 to NW04s

We want to upgrade to the last version of SAP Portal, but in all the
documents we´ve read the upgrade is referred to EP 6 SP14 o higher
(NW04) but it´s not named the version NW04s.
Is it possible to upgrade from EP 5 SP6 to NW04s???. The tool to do the
upgrade, is it available for NW04s???
And other question, whitch is the version of portal in NW04s?.
Thanks and regards.
Raúl Martinez.

Hi,
You need to do a migration to NW04 then an upgrade to NW04S.
I am doing this right now from an EP6 SP2 portal.
I think the best way is to migrate to NW04 SP16 first, then upgrade to NW04S SP07.
For this you need two computers. One with the source portal (EP5 or EP6) and another with a NW04 SP16 clean, on same version database. You migrate the KM part, then the PCD part.
You can find all docs for migration at :
https://service.sap.com/nw-epmig
Then choose the EP5 scenario.
You can find the migration tools at :
https://service.sap.com/swdc , support packages and patches, sap netweaver (x2), sap netweaver 04, entry by component, ep migration, EP 5.0 MIGRATION TO NW04
Then you upgrade the NW04 SP16 system to NW04S SP07.
You can find documentation at :
https://service.sap.com/instguides , Sap Netweaver, Release 2004S, upgrade.
Take a look to the upgrade master guide and upgrade documentation.
Good luck.
Brad

Similar Messages

EP6 Migration to NW04 - J2EE requirements

Hi Guru's
We are in the process of migrating our Portal from EP6 sp2 to NW04 and the tool we are using to migrate is "EP60MIGTOOL_8".
It seems as if this tool requires J2EE version 6.40 on the source system.
Is this correct and do we have to upgrade our J2ee engine to 6.40 on the source system ??
Regards,
Morgan Moodley

Hi Morgan,
when you migrate from EP6 SP2 to NW04, you need two systems.
The source system, with EP6 SP2, at least PL30
The target system, with EP6 NW04, at least SP16 (maybe 17 now).
You execute the migration tools on the EP6 NW04 system, that copy KM/PCD data via the network .
Brad

Incorrect display of portal pages after migration to EP7

Hello,
after the migration from EP 6 to EP 7 some of the portal pages do not diplay correctly (for example user administration -> identity management, content administration -> webdynpro, system administration -> system configuration -> UME configuration). They show up as plain text, no theme is applied to these pages and navigation on these pages is not possible.
Has anyone else experienced this problem? I have searched in the SAP OSS and here on the SDN, but didn't find anything. The SAP support hasn't been able to help me so far.
Any help would be much appreciated.
Best regards,
Nicole

Hi Nicole,
we had the same problem with our migration from EP6 SP2 to NW04 and upgrade to NW04s.
The solution is to import the EP6 theme to the EP7 portal.
After that, everything should display ok.
to transport themes, go in portal to :
System Adm \ Portal Display \ Theme archive
Just export your themes from the EP6 portal.
Then in the 2004s portal, go to :
System Adm \ Portal Display \ Theme archive
Then import the EP6 Themes.
I hope this will help.
Brad

Role Assignment Migration Issue

Hi All,
We migrated from EP6.0 to NW04 and encountered an issue with role assignment. We currently have two LDAPs (1 for external customers and 1 for internal customers), when we did the migration, what we noticed is that for the external users, all their roles were not attached and for internal users, some of the roles were not attached. Has anyone encountered this issue?
Thanks

Hi Reyna,
I did some research on this. I was unable to find anyone who migrated from a portal with two ldaps configured. I was aware of some issues if people changed ldaps or migrated the uses from one ldap to another. Or if they didn't use the migration tools. Since you used the tools and used the same ldap, I'm not sure what is going on.
If you haven't already, I suggest you open a message with SAP. Let us know here if you make any progress. If I find out more, I'll post here too.
Thanks,
John

Role migrate issue

When I migrate some Roles from portal nw04 to nw04s, the roles have issue.
The issue is when I assign these role into some user, the role doesn't work.
My solution is I go to Content Administrator>xxx role>Change ID then the role is working for user.
I don't know why I need to do this process when I migrate role.
Anybody know why?

It's possible I'm not being very clear as I think you have misunderstood it. The Hyper-V hosts are fine and their access to the iSCSI CSV is functional. The problem is the VMs throw up this error when I add a Shared VHDx that is stored on the
Hyper-V Hosts CSV.
Hyper-V Host cluster 'HVCLLAB1' with an iSCSI CSV e.g. C:\ClusterStorage\Volume1. This is all fine.
Two virtual file servers in a cluster 'FSCL1'
The quorum and storage disks for the virtual file server cluster are Shared VHDx that are stored in the 'HVCLLAB1' CSV. They are added to the virtual file servers through Failover Cluster Manager running on one of the Hyper-V Hosts.
I hope that makes sense.
I think I got it.
You are nesting the VHDX files _within_ the cluster guests?
If that is the case then the cluster would not be online until after the guests finish their own boot and initialization processes.
Chicken and the egg.
Essential cluster resources like the witness disk should be direct attached to an iSCSI LUN not nested within the guest workloads.
Guest clusters are possible but the focus would be on the workloads they would be running internal to themselves.
I hope I have things correct this time around. Essentially, putting your cluster witness disk within the guest workloads is not a good practice.
Philip Elder Microsoft Cluster MVP Blog: http://blog.mpecsinc.ca

Error in KM Component Monitor

Hi,
After migrating from EP5 SP6 to EP6 SP14, we see the below error in the following navigation.
KM Admin -> KM Component Monitor -> Repository Managers the pcdrepository light is red.
Startup Error: Failed to init sub-manager: Exception loading and instanciating sub-manager: com.sapportals.wcm.repository.manager.generic.search.SimplePropertySearchManager (java.lang.NoSuchMethodException: com.sapportals.wcm.repository.manager.generic.search.SimplePropertySearchManager.<init>(com.sap.netweaver.bc.rf.mi.IManager))
Any ideas on this would be greatly appreciated.
Regards,
Rick Taylor

Hi Rick,
this is a known issue in SPS14. Please edit the PCD Repository Manager configuration. You'll have to change the Parameter "Property Search Manager" to "Not set" and restart the J2EE Engine.
Hope this helps,
Robert

Cutomer theme is not working properly

HI,
we have upgraded our portal version from EP6.0 sp 9 to EO 7.0 SP9. after upgrade customer theme is not displaying properly. like tabs ,font size are displaying with improper format. can any one tell me what needs to be done. But SAP standard themes r displaying corrrectly.

Hi,
we had the same problem last summer.
We migrated from EP6 SP2 to NW04. Theme was ok.
Then upgraded from NW04 to 7.0. Theme was corrupted, web dynpros were not usable.
You just need to export the EP6 theme, then import it in EP 7.0. No need to delete the old ep7 one.
You may have to restart the j2ee.
Brad

Help Immediately - java.util.zip.ZipException

We are migrating EP6 SP2 P5 to NW04 on Unix HP-UX 11.11.
We immediately launched the KMC migration and it comes up and the hour glasses endlessly.
We are migration the customers Production system and need some ideas of what might be wrong ASAP.
Thanks - Here are the lines of the log files:
1123871674779#INFO.- Reports button clicked at MainMigrationFrame
1123871674781#INFO.- SAP System Name is
1123871674781#INFO.- using tool version 6.90.20050627170305.0000/2693
1123871674781#INFO.- using system installation at /usr/sap
1123871674785#INFO.- Processing migration info
1123871674820#INFO.- java.util.zip.ZipException: oversubscribed dynamic bit lengths tree

folks if you get this error, it means your input file was not copied in binary mode. Our mistake.

Custom portal service not running ni NW 04

Hello!
We are about to migrate from EP6 SP2 to NW04 and I'm currently testing the results of the first test run.
One special problem I encountered is one of my custom portal services no longer running. It did without flaws back in EP6, so something seems to have changed.
My Service interface:
[code]
package com.rag.ekportal.bginfocenter.kmservice;
@author Juergen Wahlmann
public interface IBGFetcher extends IService {
[/code]
And the implementation:
[code]
package com.rag.ekportal.bginfocenter.kmservice;
public class BGFetcher implements IBGFetcher, Runnable {
[/code]
portalapp.xml
[code]
<?xml version="1.0" encoding="UTF-8"?>
     <application>
          <application-config>
          </application-config>
          <components>
               <component name="BGViewer">
                    <component-config>
                         <property name="ClassName" value="com.rag.ekportal.bginfocenter.bgview.control.BGViewer">
                         </property>
                         <property name="SecurityZone" value="sbi-ruhr.de/ekportal/medium_safety/com.rag.ekportal/components/bgviewer">
                         </property>
                         <property name="ResourceBundleName" value="bginfocenter">
                         </property>
                         <property name="ServicesReference" value="usermanagement,knowledgemanagement,com.rag.ekportal.bginfocenter.kmservice.BGFetcher,com.sap.portal.ivs.connectorservice,landscape">
                         </property>
                    </component-config>
                    <component-profile>
                         <property name="tagLib" value="/SERVICE/htmlb/taglib/htmlb.tld">
                              <property name="personalization" value="none">
                              </property>
                         </property>
                         <property name="templatesfolderName" value="Vorlagen">
                         </property>
                         <property name="guidelinesfolderName" value="Richtlinien">
                         </property>
                         <property name="bgContactsfolderName" value="BG-Ansprechpartner">
                         </property>
                         <property name="ksb2folderName" value="KSB 2">
                         </property>
                         <property name="bgControllingfolderName" value="BG-Controlling">
                         </property>
                         <property name="rvURL" value="/irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fcom.fo.admin!2fcom.admin.fo.iview!2fcom.admin.iview.fo.ri!2fcom.admin.iview.ri.fo.rag!2fcom.admin.iview.ri.rag.iv.begis_0_0?numberBG=">
                         </property>
                         <property name="KmServiceUser" value="KM Service User">
                         </property>
                         <property name="systemAlias" value="BeGIS_RV_DB">
                         <property name="personalization" value="admin"/>
                         <property name="plainDescription" value="JDBC System object for DB access"/>
                    </property>
                    <property name="table" value="janus_contract_bg_v">
                         <property name="personalization" value="admin"/>
                         <property name="plainDescription" value="Database View for reading contracts"/>
                    </property>
                    <property name="table1" value="user_roles_v">
                         <property name="personalization" value="admin"/>
                         <property name="plainDescription" value="Database Table for checking user role in RV DB"/>
                    </property>
                    </component-profile>
               </component>
          </components>
          <services>
               <service name="BGFetcher">
                    <service-config>
                         <property name="className" value="com.rag.ekportal.bginfocenter.kmservice.BGFetcher">
                         </property>
                         <property name="startup" value="true">
                         </property>
                         <property name="SecurityZone" value="sbi-ruhr.de/ekportal/medium_safety/com.rag.ekportal/services/bgfetcher">
                         </property>
                    </service-config>
                    <service-profile>
                         <property name="interval" value="300000">
                         </property>
                         <property name="enable" value="false">
                              <property name="type" value="boolean">
                              </property>
                         </property>
                         <property name="numberofruns" value="1">
                         </property>
                         <property name="repository" value="/rag_bgm_test/Beschaffungsgruppen">
                         </property>
                         <property name="KmServiceUser" value="KM Service User">
                         </property>
                         <property name="dbServer" value="xxx">
                         </property>
                         <property name="dbUser" value="xxx">
                         </property>
                         <property name="dbPassword" value="xxx">
                         </property>
                         <property name="dbName" value="xxx">
                         </property>
                         <property name="workfolderName" value="Arbeitsordner">
                         </property>
                         <property name="teamfolderName" value="Teamordner">
                         </property>
                         <property name="contactfolderName" value="Ansprechpartner">
                         </property>
                         <property name="publicfolderName" value="u00D6ffentlicher Ordner">
                         </property>
                         <property name="deletedfolderName" value="/rag_bgm_test/Gelu00F6scht/">
                         </property>
                    </service-profile>
               </service>
          </services>
     </application>
[/code]
The service didn't work after the migration, so I tried to deploy it again. This is the result:
[code]
Date : 01/12/2006
Time : 13:31:37:880
Message : [PortalServiceItem.startServices] service initialisation failed:com.rag.ekportal.bginfocenter.kmservice|BGFetcher
[EXCEPTION]
java.lang.NoClassDefFoundError: com/sapportals/wcm/repository/ResourceException
     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:727)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:613)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1042)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1563)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1518)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.restartQueuedApplication(PortalAppBroker.java:1866)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.updateApplications(PortalAppBroker.java:1702)
     at com.sapportals.portal.prt.deployment.DeploymentManager.updateApplications(DeploymentManager.java:1754)
     at com.sap.ip.portal.admin.portalanywhere.QueryHandler.handleTopic(QueryHandler.java:152)
     at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.executeActionHandleTopic(NotificationSAPJ2EE630.java:1141)
     at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.notifyActionSubscribers(NotificationSAPJ2EE630.java:1089)
     at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.receiveWait(NotificationSAPJ2EE630.java:386)
     at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.broadcastAndWait(NotificationSAPJ2EE630.java:553)
     at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.broadcastAndWait(NotificationServiceDispatcher.java:192)
     at com.sap.ip.portal.admin.portalanywhere.EventForwarder.sendQueryAndGetResults(EventForwarder.java:122)
     at com.sap.ip.portal.admin.portalanywhere.EventForwarder.sendQueryToAllServers(EventForwarder.java:144)
     at com.sap.ip.portal.admin.portalanywhere.EventForwarder.forwardEventToAllServers(EventForwarder.java:135)
     at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.forwardUpdateToAllServers(ArchiveUploader.java:253)
     at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doContent(ArchiveUploader.java:235)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     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:95)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
Severity : Error
Category : /System/Server
Location : com.sap.portal.prt.runtime.broker
Application : sap.com/irj
Thread : SAPEngine_Application_Thread[impl:3]_15
Datasource : 2390950:E:\usr\sap\PMT\JC00\j2ee\cluster\server0\log\defaultTrace.trc
Message ID : 000C29A5B62A00400000001300000A4000040A2887A939D9
Source Name : com.sap.portal.prt.runtime.broker
Argument Objs : java.lang.NoClassDefFoundError: com/sapportals/wcm/repository/ResourceException
     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:727)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:613)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1042)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1563)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1518)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.restartQueuedApplication(PortalAppBroker.java:1866)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.updateApplications(PortalAppBroker.java:1702)
     at com.sapportals.portal.prt.deployment.DeploymentManager.updateApplications(DeploymentManager.java:1754)
     at com.sap.ip.portal.admin.portalanywhere.QueryHandler.handleTopic(QueryHandler.java:152)
     at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.executeActionHandleTopic(NotificationSAPJ2EE630.java:1141)
     at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.notifyActionSubscribers(NotificationSAPJ2EE630.java:1089)
     at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.receiveWait(NotificationSAPJ2EE630.java:386)
     at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.broadcastAndWait(NotificationSAPJ2EE630.java:553)
     at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.broadcastAndWait(NotificationServiceDispatcher.java:192)
     at com.sap.ip.portal.admin.portalanywhere.EventForwarder.sendQueryAndGetResults(EventForwarder.java:122)
     at com.sap.ip.portal.admin.portalanywhere.EventForwarder.sendQueryToAllServers(EventForwarder.java:144)
     at com.sap.ip.portal.admin.portalanywhere.EventForwarder.forwardEventToAllServers(EventForwarder.java:135)
     at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.forwardUpdateToAllServers(ArchiveUploader.java:253)
     at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doContent(ArchiveUploader.java:235)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     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:95)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
Arguments : java.lang.NoClassDefFoundError: com/sapportals/wcm/repository/ResourceException
     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:727)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.createServiceInstance(PortalServiceItem.java:613)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1042)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1563)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1518)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.restartQueuedApplication(PortalAppBroker.java:1866)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.updateApplications(PortalAppBroker.java:1702)
     at com.sapportals.portal.prt.deployment.DeploymentManager.updateApplications(DeploymentManager.java:1754)
     at com.sap.ip.portal.admin.portalanywhere.QueryHandler.handleTopic(QueryHandler.java:152)
     at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.executeActionHandleTopic(NotificationSAPJ2EE630.java:1141)
     at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.notifyActionSubscribers(NotificationSAPJ2EE630.java:1089)
     at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.receiveWait(NotificationSAPJ2EE630.java:386)
     at com.sapportals.portal.prt.service.notification.impl.NotificationSAPJ2EE630.broadcastAndWait(NotificationSAPJ2EE630.java:553)
     at com.sapportals.portal.prt.service.notification.NotificationServiceDispatcher.broadcastAndWait(NotificationServiceDispatcher.java:192)
     at com.sap.ip.portal.admin.portalanywhere.EventForwarder.sendQueryAndGetResults(EventForwarder.java:122)
     at com.sap.ip.portal.admin.portalanywhere.EventForwarder.sendQueryToAllServers(EventForwarder.java:144)
     at com.sap.ip.portal.admin.portalanywhere.EventForwarder.forwardEventToAllServers(EventForwarder.java:135)
     at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.forwardUpdateToAllServers(ArchiveUploader.java:253)
     at com.sap.ip.portal.admin.portalanywhere.ArchiveUploader.doContent(ArchiveUploader.java:235)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     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:95)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
Dsr Component :
Dsr Transaction : 5f940fe0836711da887d000c29a5b62a
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives : /System/Server
Resource Bundlename :
Session : 2391
Source : com.sap.portal.prt.runtime.broker
ThreadObject : SAPEngine_Application_Thread[impl:3]_15
Transaction :
User : xxx
[/code]
Looks like something is wrong in the service definition (portalapp.xml) but I have no clue. Class names are spelled right, settings the same as in EP6 SP2, yet the portal engine is not able to find the implementation class of the service.
Any ideas?
Cheers,
Juergen

Hi Detlev!
The ServiceReference definition previously was located in the application config under SP2, but didn't work either.
Now I found the solution. A sharing reference of all non-custom services in the application config and an additional sharing reference to my custom service in the portal application's config like this:
          <application-config>
               <property name="SharingReference" value="usermanagement,knowledgemanagement,com.sap.portal.ivs.connectorservice,landscape">
               </property>
          </application-config>
          <components>
               <component name="BGViewer">
                    <component-config>
                         <property name="ClassName" value="com.rag.ekportal.bginfocenter.bgview.control.BGViewer">
                         </property>
                         <property name="SecurityZone" value="sbi-ruhr.de/ekportal/medium_safety/com.rag.ekportal/components/bgviewer">
                         </property>
                         <property name="ResourceBundleName" value="bginfocenter">
                         </property>
                         <property name="SharingReference" value="com.rag.ekportal.bginfocenter.KMService.BGFetcher">
                         </property>
                    </component-config>
Case closed, thx for you hint. I awarded points.
Cheers,
Jürgen
Message was edited by: Juergen Wahlmann, solution included

Htmbl table navigation problem

We have migrated portal 6.20 to NW04. We have a iVIew where we are displaying material list in htmlb table. But table navigation is not working for the table. Caching mechanizam for 6.2 and NW04 is diffrent so I made changes in portalapp.xml file.
removed the lines referring to the portal version from the portalapp.xml:
<application-config>
    <property name="ClassLoadingPolicy" value="5.0"/>
    <property name="DeploymentPolicy" value="5.0"/>
    <property name="AuthenticationPolicy" value="5.0"/>
</application-config>
Also, a line was added in the Portalapp.xml:
    <property name="ALLOW_BROWSER" value="No"/>
Also set the Allow Client-Side Caching = no and Cache Level = none
even in table navigation is,
     public void onNavigateMaterials(Event event) {
                         if (SESSIONEXPIRED)
                              return;
                         request = (IPortalComponentRequest) this.getRequest();
                         mySession = request.getComponentSession();
                         profile = request.getComponentContext().getProfile();
                         res = request.getResourceBundle();
                         Bean_R3_Materials materials =
                              (Bean_R3_Materials) mySession.getValue("R3_Materials");
                         TableNavigationEvent tne = (TableNavigationEvent) event;
                         int newRow;
                         newRow = tne.getFirstVisibleRowAfter();
                         materials.setVisibleFirstRow(newRow);
                         jspOutput = Constants.TAB_MATERIALS;
and bean is as
public Bean_R3_Materials() {
          this.visibleFirstRow = 1;
public int getVisibleFirstRow () {
                return visibleFirstRow;
     public void setVisibleFirstRow (int vfr) {
                this.visibleFirstRow = vfr;
KIndly suggest, what is missing? Points assured.

I have just noticed that the problem page had a error icon in the bottom left corner of IE, when I clicked this the description is 'Can't set focus on the item because it disabled, or of type that does not accept focus...etc'.
I have code that enables/disables the buttons in the header fragment, and when I comment out the call to this in the page init() method, the error is no longer displayed and the table functions as expected.
I will continue to investigate what I have to do to resolve the problem and still provided the necessary functionality.

ITS for Netweaver Stack10

Currently I have configured ITS with EP6SP2 to display the iview using WebGui.I am planning to upgrade EP60 SP2 to Netweaver Stack 10.
To use webgui iViews with Netweaver Stack10, do I need to keep ITS or can I remove ITS for the current webgui transactions.

Hi,
Just one comment regarding this thread. After migration from EP6 SP2 to NW04 SR1, one should upgrade directly to SP11 and not SP10. Please have a look at the documentation for further details.
Regards,
Aviad

DB connect error in pre-migration check (EP5.0 SP6- EP6 SP16)

Hello,
I am working on migration (EP 5.0 SP 6--> EP 6.0 SP 16).
I have created a EP 5 System ,While I am checking for connectivity, (http://nw04:5000/sp) it displays an error message. Here is a string I have used for connection.
URL: jdbc:sap:sqlserver://btep-5:1433;DatabaseName=TTPSys
Driver Class Name: com.sap.portal.jdbc.sqlserver.SQLServerDriver
<b>Error message start:</b>----
Test connection to source DB failed, please check Database parameters in EP5.0 system
exception occured - could not check P310_SUPPORTED_LANGUAGES
Tue Aug 08 17:01:31 GMT+05:30 2006 : java.lang.ClassNotFoundException
at com.sapportals.utilities.analyzer.deploy.JarClassLoader.findClass(JarClassLoader.java:82)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at com.sap.portal.ep5tonw04migration.premigration.checkDBConnection.createConnection(checkDBConnection.java:82)
at com.sap.portal.ep5tonw04migration.premigration.checkDBConnection.checkConnectionToDB(checkDBConnection.java:58)
at com.sap.portal.ep5tonw04migration.premigration.checkDBConnection.analyze(checkDBConnection.java:30)
at com.sapportals.utilities.analyzer.PluginManager.analyze(PluginManager.java:281)
at com.sapportals.utilities.analyzer.PluginManager.run(PluginManager.java:995)
at java.lang.Thread.run(Thread.java:534)
Tue Aug 08 17:01:31 GMT+05:30 2006 : null
<b>Error message END:</b>----
Does any one have idea what could be the reason?
Regards
Sunil Kulkarni

Hello Nageshwar,
the likely root cause of this issue is the lack of permissions for the user on the shadow instance.
Please review note #592514 and check your users' rights accordingly.
Best regards,
Tomas Black

Migrating from WLS 8.1 SP5 to Sp6

We have successfully runned WLS 8.1 SP5
When we were migrating from SP5 to SP6 in starting logs had been occured strange errors:
<Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named edx.servman.databasePool should not point to the Pool edxUserConnectionPool, Poo
l edxUserConnectionPool has already been referenced by the another TxDataSource.>
<Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named edx.user.databasePool should not point to the Pool edxUserConnectionPool, Pool e
dxUserConnectionPool has already been referenced by the another TxDataSource.>
<Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named jdbc.ecs_serial_trans should not point to the Pool edxUserConnectionPool, Pool e
dxUserConnectionPool has already been referenced by the another TxDataSource.>
All these DSources have been running on SP5 on the same pool. But this config doesn't work on SP6. What is issue?

Anton Gavazuk wrote:
We have successfully runned WLS 8.1 SP5
When we were migrating from SP5 to SP6 in starting logs had been occured strange errors:
<Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named edx.servman.databasePool should not point to the Pool edxUserConnectionPool, Poo
l edxUserConnectionPool has already been referenced by the another TxDataSource.>
<Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named edx.user.databasePool should not point to the Pool edxUserConnectionPool, Pool e
dxUserConnectionPool has already been referenced by the another TxDataSource.>
<Jul 6, 2007 3:01:49 PM EEST> <Error> <JDBC> <BEA-001263> <Data Source named jdbc.ecs_serial_trans should not point to the Pool edxUserConnectionPool, Pool e
dxUserConnectionPool has already been referenced by the another TxDataSource.>
All these DSources have been running on SP5 on the same pool. But this config doesn't work on SP6. What is issue?Hi. This is a known issue with 81sp6. Ask support for the patch
for CR308071. We document that it is forbidden to have multiple
XA datasources pointing to the same pool, and we now enforce that,
but the bug is that we were also preventing mulitple datasources
to non-XA pools as well.
Joe

Role Migration EP60 NW04

Hello,
its mybe an easy question, but i dont find an answer in the manual :-(.
i would upload some SAP BW roles to the Enterprise Portal.
In EP 5.0 i know there was a tool named "Role Migration".
So i search this forum where this is located now.
All Postings say that there mus be an entry under "System Administration - Transport"
But in my Portal there isnt only:
Export
Import
Upload von Content und Aktionen
Unification-Synchronisation
Does anybody know where i can find the "Role Upload"?
Best Regards,
Patrick

hi John,
it is very strange :-/.
I take a look in an other NW04 SP9 Portal and it has your entrys. My Portal didnt have this. I have the Super Administrator role assigned.
Never seen this before that an menu entry are lost.
Best regards,
Patrick
> Hi Patrick,
> When I log on to my SP9 portal, under System
> tem Administration > Transport, I have the following
> entries in the detailed navigation.
>
> Export
> Import
> Upload Content and Actions
> Unification Synchronization
> Role Upload
> Content Mirroring.
>
> Acording to your note I assumed that you only had the
> first four entries. The fifth entry on mine is the
> Role upload. Are you logged on as the super
> administrator or just system administrator?
>
> John

NW04s-BW Migration help!

I am looking for NW04s-BW Migration documents and process, What exactly role of BW consultant. Suggest me and send me some doc's to [email protected],
Advance Thanks
Kris

DST
Check this link
Frequently Asked Questions in SAP NW 7.0 - Enterprise Data Warehousing, Reporting, Query & Analysis and Business Planning [original link is broken]
Also check your mail
Thnaks
Sat

Migrate EP 5 SP6 to NW04s

Similar Messages

Maybe you are looking for