Skip to Content
author's profile photo Former Member
Former Member

Customizing EP Logon Page fails with iView not found

Hello,

I'm trying to customize my EP logon page following the instructions in the next web pages to modify all the related files:

http://help.sap.com/saphelp_nw70/helpdata/en/23/c0e240beb0702ae10000000a155106/frameset.htm

But after restarting the portal and I visit the logon page, I get the following error in the browser:

======

Portal Runtime Error

An exception occurred while processing your request

Exception id: 07:57_31/01/08_15713950

See the details for the exception ID in the log file.

======

And in the defaultTrace file appears the error below:

======

#1.5^H#76A0F9DFAA42007500000019000CA08C00044508DB1EB86A#1201804245120#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal

#Guest#0####a2aef0d0d02a11dcbf2076a0f9dfaa42#SAPEngine_Application_Thread[impl:3]_25##0#0#Error#1#/System/Server#Java###An er

ror occured during authscheme computation.

#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: iView not found: com.ics.portal.runtime.logon.certlogon

at com.sapportals.portal.prt.deployment.DeploymentManager.getPropertyContentProvider(DeploymentManager.java:1937)

at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:222)

at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)

at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:387)

at com.sapportals.portal.prt.service.authenticationservice.AuthenticationService.getLogonIView(AuthenticationService.

java:233)

at com.sapportals.portal.prt.service.hook.SecurityHookService.doNodeHook(SecurityHookService.java:154)

at com.sapportals.portal.prt.connection.PortalHook.doNodeHook(PortalHook.java:469)

at com.sapportals.portal.prt.pom.factory.ComponentNodeFactory.newInstance(ComponentNodeFactory.java:138)

at com.sapportals.portal.prt.pom.factory.ComponentNodeFactory.newInstance(ComponentNodeFactory.java:50)

at com.sapportals.portal.prt.pom.PortalNode.createComponentNode(PortalNode.java:275)

at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:617)

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

at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)

at java.security.AccessController.doPrivileged1(Native Method)

at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))

at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)

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.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)

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

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

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

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

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

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

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

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessio

nMessageListener.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.doPrivileged1(Native Method)

at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))

======

Does anybody has a clue?

Thanks in advance.

Roger Allué i Vall.

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Feb 01, 2008 at 04:11 AM

    Hi Xavier,

    I would recomend you to do these steps.

    1. Import the Par inside NWDS ( Make sure u have the Jars inside the Lib).

    2. Do the modification.

    3. try to Deploy using some different name.

    4. Check the deployed using portalapp.xml ( defualt component).

    5.Now if it looks fine you can proceed ahead by changing the autheschemes.xml

    Refer to this blog

    Modifying The Logon Par(or customising the Logon Screen)

    Thanks

    Pankaj

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 01, 2008 at 06:38 AM
    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.