hi,
When I logoff from the portal (EP6.0 SP 13)i got yes or no options to logoff from the portal. When I click on the yes option I am getting
404: Not found
The requested resource does not exist.
Details: Go to main page of this application!
Where i should get the logon page screen. Can any onehelp me.
Hi Everyone,
I tried to import support packages using SUM but failed. Details can be found in the following thread:
Re: NW7.4 import support package using SUM column store error during extraction
OS: Linux x86 64bit
NW: 7.40 BW on HANA
According to Chandra, I need to clean up the shadow tables.
But I have no idea about how to perform this.
Could anyone please give some suggestions?
Thank you!
B.R.
Carina Hu
Hi Team,
We have a custom SSO application in portal which displays all the backend systems in an iview as icons and by clicking on them the backend system opens with out prompting for login credentials.
After upgrade the iview is not opening as we get the below error message.
Error:
Caused by: com.sapportals.portal.prt.service.ServiceException: Error while retrieving service: com.sap.portal.ivs.systemlandscapeservice.oldpcm.systemlandscape
We noticed that the service "com.sap.portal.ivs.systemlandscapeservice.oldpcm.systemlandscape" is not present in the newly upgraded server (Target portal NW 7.3) where as it is present as a dependant service in 6.4 version (Source portal).
Please find below the complete error message :
at com.sap.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:786)
at com.sap.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:245)
at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:107)
at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:141)
at com.sapportals.portal.prt.core.async.IncludeItemResponse.include(IncludeItemResponse.java:197)
at com.sapportals.portal.navigation.workAreaiView.doContent(workAreaiView.java:312)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:213)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:129)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher$5.service(RequestDispatcherFactory.java:308)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:270)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher.service(RequestDispatcherFactory.java:298)
at com.sap.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:229)
at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:107)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:119)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: com.sapportals.portal.prt.service.ServiceException: Error while retrieving service: com.sap.portal.ivs.systemlandscapeservice.oldpcm.systemlandscape
at com.sap.portal.prt.service.ServiceManager.get(ServiceManager.java:270)
at com.sap.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:130)
at fi.neomore.sapautologon.DefaultSAPDataGenerator.getSAPData(DefaultSAPDataGenerator.java:65)
at fi.neomore.sapautologonapp.SAPAutoLogonApp$SAPAutoLogonAppDynPage.doProcessBeforeOutput(SAPAutoLogonApp.java:149)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:114)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:213)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:129)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher$5.service(RequestDispatcherFactory.java:308)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:270)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher.service(RequestDispatcherFactory.java:298)
at com.sap.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:229)
... 15 more
Caused by: com.sap.portal.prt.broker.PortalModuleNotFoundException: Could not retrieve portal application com.sap.portal.ivs.systemlandscapeservice.oldpcm.systemlandscape
at com.sap.portal.prt.broker.PortalAppBroker.ensurePortalModuleIsStarted(PortalAppBroker.java:640)
at com.sap.portal.prt.broker.PortalAppBroker.getPortalModule(PortalAppBroker.java:319)
at com.sap.portal.prt.service.ServiceManager.getPortalServiceItem(ServiceManager.java:416)
at com.sap.portal.prt.service.ServiceManager.get(ServiceManager.java:220)
Can you please let us know how can we get this service in NW7.3 or is it obselete in 7.3 server. If it is obselete then pls let us know the relavant service in this regard.
regards
Bharat
Hello Gurus,
We have to do an OS migration for an SAP Netweaver 7.01 portal landscape.
Source - HP-UX
Target - Linux
CPU - 8
RAM - 64GB
DB - Oracle 11.2.0.2
DB Size - 250GB
Instances - CI + 5 DIs
We tried to take do a mock, and the test export using SWPM with default options took around 14hrs. Since we're dealing with 7.01, SWPM don't support table splitting, so we had to go with default options.
We have not yet tested the import, but assuming it is going to take more than that plus have to re-install 5 dialog instances after migration it is going to take lot of time.
From the DB export log:
INFO: KMC_DBRM_CONTENT exported (250060 rows) --> about 4 hours
INFO: WCR_USERNODELOGON exported (140152955 rows) --> about 2 hours
INFO: WCR_USERNODESTAT exported (140153038 rows) --> about 3 hours
INFO: WCR_WEBCNODESTAT exported (126607380 rows) --> about 1,5 hours
Do we have any other options to do the migration of 7.01 portal system (like migrating DB with O2O and then do only java content export/import via sapinst)?
Regards,
Abhilash
Hi,
Actually I have a query regarding Big Endian and Little Endian, During the Export of Database, Target Hardware Platform need to be mention as Big Endian or Little Endian (screenshot attached). Now my concern is this, suppose we are migrating from Windows to AIX and I selected my target system as Little Endian (but ofcourse AIX memory architecture is Big Endian). Will I be able to import my DB in AIX although I mentioned my target system as Little Endian. If NO, what need to be done?
Shall I take the complete export again or with some modification we can import it in AIX.
Thanks and Regards,
Ankit Mishra
Dear All,
I have a HTML5 Application which hosted on SAP Enterprise Portal. My Application run only in the IE Standard mode, but Enterprise mode.
If the Enterprise mode is enabled, there was some rendering issue, where all the UI's are displayed in the left side
When ever i click my application url, Enterprise mode is automatically Enabled. i had to disable every time when i access my application.
I have two question.
1. Mostly Web Application must run on both the modes . why the application run only on Standard mode but enterprise mode?
When i checked about the functionality of Enterprise mode, i came to know that if the application does not work on Standard mode, enabling Enterprise mode make it work . if the application still not work, maintaining the application url in the compatablity view settings make it work.
2. I have found a way to disable the Enterprise mode from Group policy editor(gpedit.msc) and regedit.
Is there any way we can disable permanently from Browser setting? not to involve group policy editor and register edit
Appreciate your reply.
Thanks ,
Dayalan
Hi all,
I have a old portal 7.0 and a new portal in versión 7.4. Now I need transport all portal content (roles, iviews, workset, themes..., KM content) , users, groups, etc.. to this new portal.
Are there any restriction in to realize this manual content transport?
what can be the key points to consider?
Thanks and best regards
Mónica
Hi all,
We're migrating from Portal 7.0 to 7.3; all the WD Java app are migrated and working. Right now, we're facing portal app (scheduler tasks) migration.
We downloaded .par file, it was converted into .ear file, it was imported into NWDS 7.3, it was deployed and... it fails when is launched into Portal.
The error says:
"while trying to invoke the method java.util.Properties.getProperty(java.lang.String) of an object loaded from field com.sapportals.wcm.service.scheduler.SchedulerEntry.properties of an object loaded from local variable 'this'"
The code is exactly the same as in Portal 7.0.... and there it works. The only difference is that in NWDS 7.3 we added the corresponding .jar files into the project manually, for the "import" statements that failed initially:
import com.sapportals.wcm.service.scheduler.ISchedulerTask;
import javax.crypto.Cipher;
import javax.crypto.spec.SecretKeySpec;
But after that, the project compiled and we deployed it without problems.
Any idea?
Here you can see the .java code: https://www.filesanywhere.com/fs/v.aspx?v=8a6f628b60617278b197
Thx!!
Miguel.
PS: btw, the error is launched into the Portal Monitoring - Scheduler Tasks section. Can I test it directly form NWDS?
Edited by: All NorthgateArinso on Feb 10, 2012 12:46 PM
Recently upgraded EP from NW 7.0 to Nw 7.4. Now users are not able to open attachments in UWL work item. Where as attachments are visible both in preview and work item in new window
when the item is opened, attachments are opening from preview but not in the item. When the attachment in the item is clicked it is opening a blank window with url http:/xxx.xxx.xxx:5IN00/com.sap.portal.navigation.helperservice/html/child.html.
We are in the process of upgrading from Netweaver 7.0 EHP1 to Netweaver 7.3. This is a JAVA stack only upgrade on a win2008 server with an oracle 11.2.0.2 database. During the checks phase of the upgrade SUM halts when the JCE strength files are verified. SUM ask for the location of the new unlimited strength files. I went to the Oracle site and downloaded the JCE 6 unlimited strenght files as per note 1240081 unzipped the file and placed it in an accessible location. If I point SUM at the directory above the two Jar files I get an error message that states "file 'file location' not found. If I point the jce directly at the .jar file it self SUM complains "Provided archive 'file location' does not contain jce subdirectory. I have tried moved the files to the old SAPJVM location and restarting the step also, this generates the same error. Any thoughts or input on this issue would be appreciated.
Thank You.
Troy
Dear experts,
we are performin an upgrade to EHP7. We have 2 separate systems ERP 6.0 EHP 3 and portal 7.0 and the upgrade is going to achieves the EHP 7 on ERP and the NW 7.4 on portal.
Right now, we are facing an issue on the portal upgrade. On the configuration phase (on the SUM tool), and on the "Build list for the upgrade" step. The system shows an error with the patch SAP_ESS 633 (is the one that we are going to install with the upgrade), the error is the following one:
Oct 7, 2014 5:43:02 PM [Info ]: Component with name SAP_ESS, vendor sap.com, and release $(2) has predecessor with the same name in start release.
Oct 7, 2014 5:43:02 PM [Info ]: Component name SAP_ESS vendor sap.com provider SAP AG has 1 modified predecessors
Oct 7, 2014 5:43:02 PM [Info ]: Predecessor component name SAP_ESS vendor sap.com is considered modified because it has the different provider PTD
Oct 7, 2014 5:43:02 PM [Info ]: Dialog eliminator ConfirmComponentsDialogEliminator does not allow to omit dialog ConfirmComponents
Searching some information on the Internet, we have found that the error is caused by a dependency with a modification implemented on the previous package (the current on the system) SAP_ESS 600, through NWDI.
We have tried to import the SAP_ESS 633 (the newest one) on a new track on NWDI to the consolidation tab and export the SCA file. After that, we have included the new SCA file generated on NWDI in our upgrade folder and re-launch the upgrade process, but we still in the same error. After that, we have realised that our development system does not have the SAP_ESS 600 installed, but this package is already installed on quality and production environments.
We are wondering if we are doing well, i mean, if the procedure that we follow to re-generate the SAP_ESS 633 is the correct one? In that case, how can we re-generate the package SAP_ESS 633 in development environment if this system does not have the previous package installed?
can you help us please?
a lot of thanks in advance
best regards
dani
Hi,
We are upgrading our EP from version 7.0 to 7.3. To do this, several of the standard applications must be migrated to WDA. We have taken the following steps in order to do so:
After completing all these tasks, we have proceeded to test the aforementioned applications directly using the EP. However, we get the following error message:
Portal runtime error
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID 11:10_29/10/12_0004_363451350
See log file for details about this exception
Now this is what we found in the log when we recreated the exception:
Time: 2012 10 29 14:49:01:244
SourceName: com.sap.portal.sapapplication
Application: sap.com/com.sap.portal.appintegrator.sap
Location: com.sap.portal.sapapplication
User: Administrator
Session: 1
DSRTransaction: 347cbfc821fb11e2aafb000015a9d3d6
ThreadName: Thread[HTTP Worker [@485134117],5,Dedicated_Application_Thread]
Severity: Error
TZone: 0-430
CSNComponent: EP-PIN-PRT
DCComponent: tc~epbc~prtc~core
CorrelationID: 363451350000000004
DSRRootContextID: E8119D5F21FA11E296E4000015A9D3D6
DSRConnection: 347cbfc821fb11e2aafb000015a9d3d6
DSRCounter: 0
Text: Content pass of Application Integrator failed.
Component Name: 'com.sap.portal.appintegrator.sap.WebDynpro',
Context Name (iView): 'pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.wda.bp_folder/com.sap.pct.erp.ess.wda.roles/com.sap.pct.erp.ess.wda.Employee_Self_Service_WDA/com.sap.pct.erp.ess.wda.Employee_Self_Service/com.sap.pct.erp.ess.wda.Overview/com.sap.pct.erp.ess.wda.Overview',
Top Layer: 'WebDynpro/TopLayer',
Producer ID (FPN): 'null',
System Alias: 'SAP_ECC_HumanResources',
Time: 2012 10 29 14:49:01:245
SourceName: com.sap.portal.prt.connection
Application: sap.com/irj
Location: com.sap.portal.prt.connection
User: Administrator
Session: 1
DSRTransaction: 347cbfc821fb11e2aafb000015a9d3d6
ThreadName: Thread[HTTP Worker [@485134117],5,Dedicated_Application_Thread]
Severity: Error
TZone: 0-430
CSNComponent: EP-PIN-PRT
DCComponent: tc~epbc~prtc~api
CorrelationID: 363451350000000004
DSRRootContextID: E8119D5F21FA11E296E4000015A9D3D6
DSRConnection: 347cbfc821fb11e2aafb000015a9d3d6
DSRCounter: 0
Text: Exception ID:02:49_29/10/12_0013_363451350
[EXCEPTION]
com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Application name : com.sap.portal.appintegrator.sap
Component : pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.wda.bp_folder/com.sap.pct.erp.ess.wda.roles/com.sap.pct.erp.ess.wda.Employee_Self_Service_WDA/com.sap.pct.erp.ess.wda.Employee_Self_Service/com.sap.pct.erp.ess.wda.Overview/com.sap.pct.erp.ess.wda.Overview
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : Administrator
at com.sap.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:786)
at com.sap.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:245)
at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:107)
at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:141)
at com.sap.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:206)
at com.sap.portal.prt.pom.PortalNode.service(PortalNode.java:588)
at com.sap.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:233)
at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:107)
at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:141)
at com.sap.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:520)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:201)
at com.sap.portal.prt.dispatcher.DispatcherServlet.service(DispatcherServlet.java:132)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>;sap-ext-sid=<ESID[URL_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[URL_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&sap-ls-useAnimation=<User.DisableAnimation[OMIT BOOL_NEGATE SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 0. Cannot process expression <System.Access.WAS.protocol> because Invalid System Attribute:
System: 'System Alias: SAP_ECC_HumanResources, System ID: pcd:portal_content/Sistemas/com.polar.SAP_ECC_HumanResources',
Attribute: 'protocol'.
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:171)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:143)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:213)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:129)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher$5.service(RequestDispatcherFactory.java:308)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:270)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher.service(RequestDispatcherFactory.java:298)
at com.sap.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:229)
... 51 more
Caused by: com.sapportals.portal.appintegrator.ApplicationIntegratorException: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>;sap-ext-sid=<ESID[URL_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[URL_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&sap-ls-useAnimation=<User.DisableAnimation[OMIT BOOL_NEGATE SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 0. Cannot process expression <System.Access.WAS.protocol> because Invalid System Attribute:
System: 'System Alias: SAP_ECC_HumanResources, System ID: pcd:portal_content/Sistemas/com.polar.SAP_ECC_HumanResources',
Attribute: 'protocol'.
at com.sapportals.portal.appintegrator.layer.AbstractIntegrationLayer.processTemplate(AbstractIntegrationLayer.java:543)
at com.sapportals.portal.appintegrator.layer.URLTemplateProcessLayer.processLayer(URLTemplateProcessLayer.java:33)
at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:175)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:111)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:70)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:398)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher$1.service(RequestDispatcherFactory.java:168)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:270)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher.handleEvent(RequestDispatcherFactory.java:158)
at com.sap.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:242)
at com.sap.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:342)
at com.sap.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:732)
at com.sap.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:473)
... 43 more
Caused by: com.sapportals.portal.appintegrator.template_processor.TemplateParserException: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>;sap-ext-sid=<ESID[URL_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[URL_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&sap-ls-useAnimation=<User.DisableAnimation[OMIT BOOL_NEGATE SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 0. Cannot process expression <System.Access.WAS.protocol> because Invalid System Attribute:
System: 'System Alias: SAP_ECC_HumanResources, System ID: pcd:portal_content/Sistemas/com.polar.SAP_ECC_HumanResources',
Attribute: 'protocol'.
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processWholeTagExpression(TemplateProcessor.java:161)
at com.sapportals.portal.appintegrator.template_processor.compiler.TemplateCompiler.processWholeTagExpression(TemplateCompiler.java:54)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseSimpleExpression(TemplateParser.java:234)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:188)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpressionEx(TemplateParser.java:210)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:193)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpressionEx(TemplateParser.java:210)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:193)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpressionEx(TemplateParser.java:210)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:193)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseTagExpression(TemplateParser.java:170)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseTemplateExpressionPart(TemplateParser.java:97)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parse(TemplateParser.java:89)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parse(TemplateParser.java:83)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processImpl(TemplateProcessor.java:432)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.process(TemplateProcessor.java:399)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.process(TemplateProcessor.java:411)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessorService.processTemplate(TemplateProcessorService.java:55)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessorService.processTemplate(TemplateProcessorService.java:110)
at com.sapportals.portal.appintegrator.layer.AbstractIntegrationLayer.processTemplate(AbstractIntegrationLayer.java:522)
... 55 more
Caused by: com.sapportals.portal.appintegrator.template_processor.context.ContextException: Invalid System Attribute:
System: 'System Alias: SAP_ECC_HumanResources, System ID: pcd:portal_content/Sistemas/com.polar.SAP_ECC_HumanResources',
Attribute: 'protocol'.
at com.sapportals.portal.appintegrator.template_processor.context.SystemEP6Wrapper.getTerminal(SystemEP6Wrapper.java:86)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processWholeTagExpression(TemplateProcessor.java:157)
... 74 more
Time: 2012 10 29 14:49:01:258
SourceName: com.sap.portal.prt.runtime
Application: sap.com/com.sap.portal.runtime.system.hooks
Location: com.sap.portal.prt.runtime
User: Administrator
Session: 1
DSRTransaction: 347cbfc821fb11e2aafb000015a9d3d6
ThreadName: Thread[HTTP Worker [@485134117],5,Dedicated_Application_Thread]
Severity: Error
TZone: 0-430
CSNComponent: EP-PIN-PRT
DCComponent: tc~epbc~prtc~api
CorrelationID: 363451350000000004
DSRRootContextID: E8119D5F21FA11E296E4000015A9D3D6
DSRConnection: 347cbfc821fb11e2aafb000015a9d3d6
DSRCounter: 0
Text: 02:49_29/10/12_0013_363451350
[EXCEPTION]
com.sapportals.portal.appintegrator.ApplicationIntegratorException: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>;sap-ext-sid=<ESID[URL_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[URL_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&sap-ls-useAnimation=<User.DisableAnimation[OMIT BOOL_NEGATE SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 0. Cannot process expression <System.Access.WAS.protocol> because Invalid System Attribute:
System: 'System Alias: SAP_ECC_HumanResources, System ID: pcd:portal_content/Sistemas/com.polar.SAP_ECC_HumanResources',
Attribute: 'protocol'.
at com.sapportals.portal.appintegrator.layer.AbstractIntegrationLayer.processTemplate(AbstractIntegrationLayer.java:543)
at com.sapportals.portal.appintegrator.layer.URLTemplateProcessLayer.processLayer(URLTemplateProcessLayer.java:33)
at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:175)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:111)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:70)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:398)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher$1.service(RequestDispatcherFactory.java:168)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:270)
at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher.handleEvent(RequestDispatcherFactory.java:158)
at com.sap.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:242)
at com.sap.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:342)
at com.sap.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:732)
at com.sap.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:473)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:201)
at com.sap.portal.prt.dispatcher.DispatcherServlet.service(DispatcherServlet.java:132)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: com.sapportals.portal.appintegrator.template_processor.TemplateParserException: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>;sap-ext-sid=<ESID[URL_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[URL_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&sap-ls-useAnimation=<User.DisableAnimation[OMIT BOOL_NEGATE SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 0. Cannot process expression <System.Access.WAS.protocol> because Invalid System Attribute:
System: 'System Alias: SAP_ECC_HumanResources, System ID: pcd:portal_content/Sistemas/com.polar.SAP_ECC_HumanResources',
Attribute: 'protocol'.
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processWholeTagExpression(TemplateProcessor.java:161)
at com.sapportals.portal.appintegrator.template_processor.compiler.TemplateCompiler.processWholeTagExpression(TemplateCompiler.java:54)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseSimpleExpression(TemplateParser.java:234)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:188)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpressionEx(TemplateParser.java:210)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:193)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpressionEx(TemplateParser.java:210)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:193)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpressionEx(TemplateParser.java:210)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseComponenedExpression(TemplateParser.java:193)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseTagExpression(TemplateParser.java:170)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parseTemplateExpressionPart(TemplateParser.java:97)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parse(TemplateParser.java:89)
at com.sapportals.portal.appintegrator.template_processor.TemplateParser.parse(TemplateParser.java:83)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processImpl(TemplateProcessor.java:432)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.process(TemplateProcessor.java:399)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.process(TemplateProcessor.java:411)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessorService.processTemplate(TemplateProcessorService.java:55)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessorService.processTemplate(TemplateProcessorService.java:110)
at com.sapportals.portal.appintegrator.layer.AbstractIntegrationLayer.processTemplate(AbstractIntegrationLayer.java:522)
... 55 more
Caused by: com.sapportals.portal.appintegrator.template_processor.context.ContextException: Invalid System Attribute:
System: 'System Alias: SAP_ECC_HumanResources, System ID: pcd:portal_content/Sistemas/com.polar.SAP_ECC_HumanResources',
Attribute: 'protocol'.
at com.sapportals.portal.appintegrator.template_processor.context.SystemEP6Wrapper.getTerminal(SystemEP6Wrapper.java:86)
at com.sapportals.portal.appintegrator.template_processor.TemplateProcessor.processWholeTagExpression(TemplateProcessor.java:157)
... 74 more
Keep in mind that we have used the application’s URL we get from SE80 directly in the browser and it does work, but through the EP we have only received this message for every dynpro tested.
Furthermore, it would be really helpful if you could provide a list of steps or tasks we must complete in order to set up ESS and MSS for EP 7.3.
Thanks in advance,
Zaida Superlano.
Hi All,
I am in process of SAP portal upgrade.
Source: EP NW 7.0 SPS26
Target: NW 7.3 EHP1 Upgrade
OS is windows 2003 with database as MSSQL 2005.
Database to be upgraded to MSSQL 2008 with OS windows 2008.
I am at configuration phase of Upgrade where it is checking target release component list
I have manually downloaded BP* packages and retried now it is asking for remaining component as below.
UWL
wikipedia
Logoff
tc/kmc/kmc.bb.app/mossproxy
and few more.
I am not sure why is it asking for these as the required software component must be calculated by solman while generating the stack file.
Do anyone have idea what should be done for this.Might be it is no more in newer version but I am not sure, please suggest
Following the Upgrade guide I have already taken backup of database table KMC_WF_SUBSTITUTE and make it empty.
Regards
Shontu
Hi SAP experts,
i'm trying to upgrade our NW7.0 EP to NW7.3. Portal is running on WIndows 2008 R2 and MSSQL 2008, JVM6 patch 34. Downtime phase has failed with strange error:
Error while processing migration list P:\upg\java\data\mig\MIGRATIONAUSF.LST. Could not migrate some archives from migration list. Error during migration of archive P:\upg\java\data\mig\DEPLOYARCHIVES\icm_migration.sda which has been extracted to directory P:\upg\java\migtool\icm_migration. Could not execute MTI process. See log files P:\upg\java\log\JMT_FRAMEWORK_RDM_03.OUT and P:\upg\java\log\JMT_FRAMEWORK_RDM_03.ERR. Return code condition success evaluated to false for process java.exe for action RUN_MTI.
<<<<<<<<<<<<<<<<JMT_FRAMEWORK_RDM_03.OUT >>>>>>>>>>>>>>>>>>
#2.0#2011 11 25 17:10:04:811#+00#Error#com.sap.sdt.jmt.migrationtool.err#
###C000C0A8C01D00000000000677B5C22F###com.sap.sdt.jmt.migrationtool.err########Thread[main,5,main]#Plain##
com.sap.sdt.jmt.MigrationException: <Localization failed: ResourceBundle='com.sap.sdt.jmt.MigrationToolResourceBundle', ID='icm.id002', Arguments: ['cluster_data/server/ID4392653/services']> : Can't find resource for bundle java.util.PropertyResourceBundle, key icm.id002
at com.sap.sdt.migration.icm.ICMDataController.migrateEngineData(ICMDataController.java:273)
at com.sap.sdt.jmt.mc.EngineDataMigrationExecuter.executeController(EngineDataMigrationExecuter.java:70)
at com.sap.sdt.jmt.mc.AbstractMigrationControllerExecuter.executeMigrationController(AbstractMigrationControllerExecuter.java:401)
at com.sap.sdt.jmt.mc.AbstractMigrationControllerExecuter.execute(AbstractMigrationControllerExecuter.java:364)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.execute(MigrationToolImport.java:897)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.migrateEngineDataAndCfg(MigrationToolImport.java:834)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.startTool(MigrationToolImport.java:472)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.main(MigrationToolImport.java:1224)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:162)
Caused by: com.sap.sdt.jmt.MigrationException: <Localization failed: ResourceBundle='com.sap.sdt.jmt.MigrationToolResourceBundle', ID='icm.id002', Arguments: ['cluster_data/server/ID4392653/services']> : Can't find resource for bundle java.util.PropertyResourceBundle, key icm.id002
at com.sap.sdt.migration.icm.ICMDataController.migrateInstancePropertiesServer(ICMDataController.java:496)
at com.sap.sdt.migration.icm.ICMDataController.migrateEngineData(ICMDataController.java:265)
... 12 more
<<<<<<<<<<<<<<<<<<RUN_OFFLINE_MIGRATION_RDM_03.log>>>>>>>>>>>>>>>>>>>>>>>
Nov 25, 2011 5:10:55 PM [Error]: com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:883) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.
Nov 25, 2011 5:10:55 PM [Error]: com.sap.sdt.tools.procx.DefaultProcessAdapter.checkReturnCode(DefaultProcessAdapter.java:563) [Thread[main,5,main]]: Return code condition success evaluated to false for process java.exe for action RUN_MTI.
Nov 25, 2011 5:10:55 PM [Error]: com.sap.sdt.j710.enginemigration.MtiProcessAdapter.run(MtiProcessAdapter.java:106) [Thread[main,5,main]]: Could not execute MTI process. See log files P:\upg\java\log\JMT_FRAMEWORK_RDM_03.OUT and P:\upg\java\log\JMT_FRAMEWORK_RDM_03.ERR.
Nov 25, 2011 5:10:55 PM [Error]: com.sap.sdt.j2ee.tools.enginemigration.JMTMigrationProcessor.runMigration(JMTMigrationProcessor.java:396) [Thread[main,5,main]]: Error during migration of archive P:\upg\java\data\mig\DEPLOYARCHIVES\icm_migration.sda which has been extracted to directory P:\upg\java\migtool\icm_migration.
Nov 25, 2011 5:10:55 PM [Error]: com.sap.sdt.j2ee.tools.enginemigration.JMTMigrationProcessor.runMigration(JMTMigrationProcessor.java:405) [Thread[main,5,main]]: Could not migrate some archives from migration list.
Nov 25, 2011 5:10:55 PM [Error]: com.sap.sdt.j2ee.tools.enginemigration.JMTMigrationProcessor.runMigration(JMTMigrationProcessor.java:276) [Thread[main,5,main]]: Error while processing migration list P:\upg\java\data\mig\MIGRATIONAUSF.LST.
I didn't find anything related on OSS, so any thoughts would be very helpfull.
Thanks a lot,
Peter Vojtek
Hi,
I am starting this post to get benefit on the Netweaver upgrades discussion. In our organization, we are working on Proof of concept for Netweaver portal upgrade to 740 release.
I am working on building a POC system with our Quality portal java system copy and then upgrading it to latest NW 740 SP11 release.
Current environment = SAP EHP 3 for SAP Netweaver 7.0 (NW 7.02, SP15)
Could someone help me here with the upgrade documentation and steps to be considered before going into the upgrade?
I am exploring on the preparation work, but it will be helpful if someone who has upgraded their portal to 7.4 can share their experience and tips during the upgrade?
Also would like to know if there will be any dependency on migrating the ESS, MSS components which off 600 release to NW 7.4 portal environment?
Do we need to consider any prerequisite for these components during this upgrade?
Really appreciate sharing your experience and knowledge on this.
Thanks,
Prasanna
Hi Experts,
This is Kishore,
We are planning to Migrate my Database from MSSQL to Oracle 11G.
Could you please let me Know what are the Pre-steps we have to do before the actual Migration Process?
Thanks,
Kishore.
Hi Gurus,
You can maintain user details in three places rite.
1,Portal DB,
2,R/3 End
3,Configuring LDAP server.
Can you please throw some clue for the above said tyeps and differences and advantages of each and tell me how to configure LDAP Server.
If anyone have step by step document pls send it to shakthigin@yahoo.co.in
Higher points will be rewarded for useful inputs.
Thanks in Advance,
Dharani.
Hi ,
we need to do customisation on the masthead application available in portal. Now as EP 7.3 no longer supports PAR files we were looking to download an EAR file of the masthead application . We found the SAP provded masthead appliction in th efollowing location .
Content Administartion --> Portal Content Management --> Portal Content (Tab) > Portal Applications> com.sap.portal.navigation.afp.masthead
But henceforth we are unable to obtain the EAR format from this applicaton . Some suggestion will be appreciated .
Thanks ,
Sidd.
Hi SCN,
I've got a bit of a nasty problem during an upgrade.
System is running on enterprise linux 6 and with a Oracle DB 11.2.0.3
According to MOPZ:
Source release:
SBOP PC 7.5 FOR SAP NW | Add-on | |
SAP EHP1 FOR SAP NETWEAVER 7.0 | NetWeaver |
Target Release:
SBOP PC 10.0 FOR SAP NW | Add-on | |
SAP NETWEAVER 7.4 | NetWeaver |
The upgrade didn't get any farther than the calculation of the queue and then it stopped mentioning that it was missing files for RTLPOSDM to be able to calculate the queue.
Since BI_CONT was on a reasonably old version (and still with the RTLPOSDM packages included in BI_CONT) I decided to upgrade to BI_CONT 707 and RTLPOSDM 100_700. AFfer installing this, this is now the source release.
SBOP PC 7.5 FOR SAP NW SP Stack 01 (Add-on)
SAP POS DM 1.0 (Add-on)
SAP EHP1 FOR SAP NETWEAVER 7.0 11 (03/2012) (Netweaver)
When running MOPZ now I do get the following warnings, which are worrying me slightly :-)
Has anyone else come across this problem or any experience in upgrading from NW 7.0 EHP1 to NW 7.4? I've done an upgrade from a BW 7 Ehp1 to BW 7.3 Ehp1 in the past .But there was no RTLPOSDM component (logically since it was not a retail customer)
Thanks in advance for your help/tips/suggestions.
Dieter
Hi All,
I am trying to upgrade my SAP PI 7.31 Single stack (SAP PO) to SP09 using SUM (SUM10 SP10 Patch 9).
DB - MS SQL 2012
OS - windows Server 2008 R2
Issue : Unable to start the igswd.EXE in the step RESTART SYSTEM FOR JAVA-ONLY
Below is the error in the Restart Java Phase
Attaching the RESTART-SYSTEM-JAVAONLY_01.LOG for Reference.
Can someone please help me in resolving this issue?