cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Portal can not be used after uploading par file?

Go to solution
xinjiang_li
Active Participant

on ‎01-26-2010 5:21 AM

0 Kudos

Hi,gurus,

We wanna modify the logon screen of portal,so we download a par file(com.sap.portal.runtime.logon.par) from service market.

But after we uploaded it into server(system administration->support->portal runtime->administration console),the portal can not be accessed,but nwa can be accessed.Then we checked out the defaulttrace.trc,it gave the error like below:

-

Exception ID:01:00_26/01/10_0008_1186950

[EXCEPTION]

com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component

Component : com.sap.portal.runtime.logon.default

Component class : com.sapportals.portal.ume.component.logon.SAPMLogonComponent

User : Guest

at com.sap.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:831)

at com.sap.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:285)

at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)

at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:149)

at com.sap.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)

at com.sapportals.portal.ume.component.logon.SAPMLogonCertComponent.doContent(SAPMLogonCertComponent.java:33)

at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:200)

at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)

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:95)

at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher.service(RequestDispatcherFactory.java:298)

at com.sap.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:269)

at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)

at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:149)

at com.sap.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)

at com.sap.portal.prt.pom.PortalNode.service(PortalNode.java:618)

at com.sap.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:273)

at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)

at com.sap.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:149)

at com.sap.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:622)

at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:203)

at com.sap.portal.prt.dispatcher.DispatcherServlet.service(DispatcherServlet.java:133)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)

at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:144)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doCached(RequestDispatcherImpl.java:517)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:356)

at com.sap.portal.navigation.Gateway.service(Gateway.java:145)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)

at com.sap.portal.http.EnrichNavRequestFilter.doFilter(EnrichNavRequestFilter.java:49)

at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:441)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)

at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)

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.ResponseLogWriter.process(ResponseLogWriter.java:60)

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.MemoryStatisticFilter.process(MemoryStatisticFilter.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.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)

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:425)

at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)

at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)

Caused by: java.lang.NoClassDefFoundError: com/sap/engine/applications/security/logon/LogonApplicationPermission

at com.sap.security.core.sapmimp.logon.SAPMLogonLogic.initBeans(SAPMLogonLogic.java:378)

at com.sap.security.core.sapmimp.logon.SAPMLogonLogic.executeRequest(SAPMLogonLogic.java:149)

at com.sapportals.portal.ume.component.logon.SAPMLogonComponent.doContent(SAPMLogonComponent.java:37)

at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:200)

at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)

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:95)

at com.sap.portal.prt.core.RequestDispatcherFactory$PortalComponentRequestDispatcher.service(RequestDispatcherFactory.java:298)

at com.sap.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:269)

... 67 more

Caused by: java.lang.ClassNotFoundException: com.sap.engine.applications.security.logon.LogonApplicationPermission

-

Loader Info -

ClassLoader name: [sap.com/com.sap.portal.runtime.logon]

Living status: alive

Direct parent loaders:

[system:Frame]

[service:servlet_jsp]

[service:ejb]

[library:tcepbcprtc~api]

[library:tcepbcprtc~basis]

[sap.com/com.sap.portal.themes.lafservice]

[sap.com/com.sap.portal.usermanagement]

Resources:

D:\usr\sap\C21\J00\j2ee\cluster\apps\sap.com\com.sap.portal.runtime.logon\servlet_jsp\com.sap.portal.runtime.logon\root\WEB-INF\lib\com.sap.portal.runtime.logon_api.jar

D:\usr\sap\C21\J00\j2ee\cluster\apps\sap.com\com.sap.portal.runtime.logon\servlet_jsp\com.sap.portal.runtime.logon\root\WEB-INF\lib\umelogonbase.jar

-

at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:274)

at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:243)

at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:363)

... 76 more

-

Any help will be appreciated,thanks in advance.

Edited by: xinjiang li on Jan 26, 2010 1:22 PM

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

former_member206159
Active Contributor
‎01-26-2010 5:55 AM
0 Kudos

Search in SDN how to modify a logon par file.

My suggestion is to deploy the original par file using NWDS to restore the sytem. Also in NWDS make sure that you have proper jar files added.

In future don't deploy the logon par file with the standard name. Instead of that you deploy with custom name.

and use that name in your authschem.xml in visual admin.

Raghu

Show replies
Show replies
xinjiang_li
Active Participant
‎01-29-2010 2:05 AM
0 Kudos

Hi,

This was solved by deleting relavant apps in configtool and importing them from another portal server.

But I think it only needs a small configuration if I wanna change the default language of logon screen,while don't need to upload the par files.Any ideas?

andre_condne
Explorer
‎01-30-2010 3:14 PM
0 Kudos

Hi,

A good and common practice is not to modify the orginal par file. Furthermore download the original par file from the Portal, then import the par file into NWDS, then create a new par file (with your own namespace) and re-deploy it to the Portal after you finished the modification. After this you will use the config tool to point the original logon page to the custom logon page.

The benefits will be:

1. You wont modify the original par file which you may need you to restore in the case that there are errors in the modification

2. It is relatively update/upgrade safe. You might be able to apply SPS packages without getting your modification overwritten.

Regards,

Andre

Answers (0)

Ask a Question