Custom logon module not called by the portal

Hi, all.
I need some help urgently on this new portal requirement. There are some sensitive ESS/MSS iviews that we need to give the users an additional logon challenge. The normal ESS/MSS iviews will be using SSO. This one will still use SSO, but have to pass the userid/password challenge.
We have decided to use the authentication scheme. Also, the "form" logon stack has been modified with only one logon module, which is our customized one. To create the java project, jar and library, we are following the link: http://help.sap.com/saphelp_nw04s/helpdata/en/46/3ce9402f3f8031e10000000a1550b0/frameset.htm
Here's the extract of our authscheme.xml:
        <authscheme name="certlogon">
            <authentication-template>
                client_cert
            </authentication-template>
            <priority>21</priority>
            <frontendtype>2</frontendtype>
            <frontendtarget>com.sap.portal.runtime.logon.certlogon</frontendtarget>
        </authscheme>
        <authscheme name="coo_secure">
            <authentication-template>
                form
            </authentication-template>
            <priority>40</priority>
            <frontendtype>2</frontendtype>
            <frontendtarget>com.sap.portal.runtime.logon.basicauthentication</frontendtarget>
        </authscheme>
        <authscheme name="basicauthentication">
            <authentication-template>
                ticket
            </authentication-template>
            <priority>20</priority>
            <frontendtype>2</frontendtype>
            <frontendtarget>com.sap.portal.runtime.logon.basicauthentication</frontendtarget>
        </authscheme>
The authscheme is called coo_secure. When a user clicks on the iviews with the coo_secure authscheme, a userid/pwd prompt pops up. But it does not accept whatever I type in. From the defaulttrace, I do not see any hint that our customized logon module was ever called.
Is there anyway to turn on portal tracing to see what is going on?
Thanks,
Jonathan.

Hi Jonathan,
Did you solved the problem with the custom logon module?
We have a very similar scenario. I followed below help site to implement a custom logon module for particular iviews.
http://help.sap.com/saphelp_nw70/helpdata/EN/54/f91fba71ae48309e4267b4a36fa47b/frameset.htm
and also the documentation:
SAP Netweaver Developers Guide - Integrating Security Functions
But I am not able to get my own custom login module with the custom authscheme running.
If I access my specific IViews that requires additional custom authentication I get the portal login page again. After giving login data I get the error message:
Java iView Runtime
An exception occured while processing your request.
If this situation persists, please contact your system administrator.
If you solved your problem, can you please share the solution with me?
Thanks,
Regards,
Yasar

Similar Messages

  • How to call a Bapi or RFC from a custom logon module

    Can you provide an example of how to call a bapi or rfc from a custom logon module? (used to authenticate in portal)

    Hello all,
    Is it possible to use SAP JRA instead?
    We have a Connector deployed on the WebAS 6.40. From an EJB (Webservice) it is possible to lookup the connector, but if i try to lookup the connector from a custom LoginModule, i get the following error:
    Path to object does not exist at java:comp, the whole lookup name is java:comp/env/eis/SAPJRA_CRMDC.#
    The whole lookup in LoginModule looks
    try
                   initialcontext    = new InitialContext();
                   connectionFactory = (ConnectionFactory) initialcontext.lookup("java:comp/env/eis/SAPJRA_CRM");
              } catch (Exception ex)
                   location.errorT(ex.getMessage());
    Regards Oliver

  • CallbackHandler for custom logon module

    Hi Experts,
    we are using a custom logon module in a J2EE application.
    When creating the LoginContext object the following parameters are necessary:
    new LoginContext(String stackName, CallbackHandler callbackHandler)
    In local development we created SAPJ2EECallbackHandler (package com.sap.security.core.logon.imp), but we cannot do this when working with the NWDI, as DC com.sap.security.core.sda cannot be added (I was reading it's part of the design).
    Which callback handler class can be used instead?
    Thanks for your help,
    Ingo

    Hi Jonathan,
    Did you solved the problem with the custom logon module?
    We have a very similar scenario. I followed below help site to implement a custom logon module for particular iviews.
    http://help.sap.com/saphelp_nw70/helpdata/EN/54/f91fba71ae48309e4267b4a36fa47b/frameset.htm
    and also the documentation:
    SAP Netweaver Developers Guide - Integrating Security Functions
    But I am not able to get my own custom login module with the custom authscheme running.
    If I access my specific IViews that requires additional custom authentication I get the portal login page again. After giving login data I get the error message:
    Java iView Runtime
    An exception occured while processing your request.
    If this situation persists, please contact your system administrator.
    If you solved your problem, can you please share the solution with me?
    Thanks,
    Regards,
    Yasar

  • New JAAS Logon Module that calls RFC: Urgent

    I want to build a new logon module that extends AbstractLoginModule.
    I want to call an RFC in ECC using JCA in this logon module. The purpose of this RFC call is to read the users roles in the backend, if they have a certain role I will dynamically assign them a portal group using the UME API.
    which method in the Logon Module (AbstractLoginModule) should I make the call to the RFC? (initialize(), login(), commit(), etc.)
    Does anybody have any examples of how to make the RFC call from a custom logon module using JCA?
    Edited by: K Ferguson on Nov 3, 2008 5:39 PM

    [link at...|http://help.sap.com/saphelp_nw2004s/helpdata/en/17/d609b48ea5f748b47c0f32be265935/content.htm]

  • New JAAS Logon Module that calls RFC

    I want to build a new logon module that extends AbstractLoginModule.
    I want to call an RFC in ECC using JCA in this logon module. The purpose of this RFC call is to read the users roles in the backend, if they have a certain role I will dynamically assign them a portal group using the UME API.
    which method in the Logon Module (AbstractLoginModule) should I make the call to the RFC?  (initialize(), login(), commit(), etc.)
    Does anybody have any examples of how to make the RFC call from a custom logon module using JCA?

    Hi K,
    I tend to put the bulk of the logic for my login modules in the login() method - although usually this is for checking authentication rather than assigning roles/groups.
    Have you thought about using UME type ABAP to map ECC roles to Portal Groups? If you then need to write a login module to handle, say, LDAP authentication, then at least it is doing what it should be - i.e. authentication, and the heavy-lifting to do with JCA, roles, etc is handled by SAP-standard code.
    For sample JCA code, there is some in the [Universal Worklist Wiki|https://wiki.sdn.sap.com/wiki/display/BPX/DeveloperStudioProject+Files] - just download and extract the Devlopment Component there (don't forget to remove the .gif extension - a hack I used to get a Zip file into the Wiki).  The file SapRfc.java gives you a user-friendly way of calling RFCs using JCA. To see it in use, see AbsenceApproval.java - the method getWorkitemDescription() is a good example to look at.
    The only downside of the SapRfc.java library is that the constructor takes a IPortalComponentRequest object as an argument (allowing you to use a Portal System Alias), and you don't really have access to one of those in a JAAS module. You will have to modify this code to take a set of ConnectionProperties instead (see the documentation [Using the SAP System Connector|http://help.sap.com/saphelp_nw04/helpdata/en/89/8a185c148e4f6582560a8d809210b4/frameset.htm]).
    Really, the component you want to develop might be better deployed as a Portal component. Your users would access this component first of all, and when it completes it would forward them on to the Portal proper.
    Hope this helps,
    Darren

  • Custom login module - Not invoked...

    Hi All
    I have developed a custom login module and the necessary configuration steps in VA are performed. However, the custom login module is not called...
    1. Developed a Java DC as a Child DC in a Library DC.
    2. Added all the relevant jars needed as Used DC and Public Parts as required. Also updated the provider.xml with relevant references.
    3. Build and Deployed. (No errors found here..)
    4. In VA - Created a new Login Module.... updated the property LoginModuleClassLoaders to library:xyz where xyz is the name of the folder for deployed sda as found in cluster\j2ee\serverx\bin\ext...next updated the config tool for the same.... next modified the sap.com/irj*irj authentication as:
    Basic - Requisite
    CustomModule - Optional.
    Then performed server restart. Yet, login module not called. Any ideas as to where I am going wrong..?? (In my login module, just trying to retrieve the user name and change their attributes like lastname etc... )
    Thanks
    Deepak

    Issue solved....
    Had forgot to add the module to the ticket stack...

  • h:CommandLink : Action event not called on the first click

    Hi,
    I am facing a problem here.
    I have a JSF page:
    When I first load the page, I have few text boxes and dropdowns. With out doing anything If I click the <h:commandLink I call an action in my pagecode.
    But the problem is on the very first load of the page, without doing anything if I click on the command link action event in my pagecode is not called, but If I click on the link the second timethe pagecode actionevent is called.
    So I think tried submitting the form in the JSF page onclik of the commandlink it works in my Local IBM RAD. But doesnot work in the WebSphere Portal.
    So can you tell me if I can submit the form atleast once when the page loads for the first time
    This is my command link:
    <tr>
    <td colspan="2" align="center">
    <h:commandLink styleClass="commandLink" id="lnkBtnCreateUser" action="#{pc_Createuser.doLnkBtnCreateUserAction}">
    <hx:graphicImageEx styleClass="graphicImageEx" id="imgBtnCreateUser" value="/theme/images/btnCreateUser.gif" style="border:0;cursor:pointer" onclick="return onFormSubmit();"></hx:graphicImageEx>
    </h:commandLink>
    </td>
    </tr>
    function onFormSubmit(){
    //enabling all the disable components
    So can anybody please help me on this. Why exactly the pageCode action event is not called for the very first click ???

    seems that a prependID="false" attribute in the respective form was causing the trouble. At least it's working now that I've deleted it.
    I introduced it, because last time the component ID's messed up the output of the error/success messages ("j_id:xxx isn't that of a usefull information to the enduser).
    Edited by: stger on Apr 9, 2008 5:41 PM

  • SSO logon not possible; logon tickets not activated on the server

    When I am on RWB
    1)  click "component monitoring" ->"display all"
    2) click "CCMS"
    I get a popup says:
    "SSO logon not possible; logon tickets not activated on the server"
    I find some threads about this on SDN but they are about
    EP. My case is PI7.0SP08.
    Please advise how to overcome this issue?
    Thanks w/ points.
    Message was edited by:
            jennifer lee

    hI,
    do you have the follwoing in our SXMB_ADM if not add them.
    SXMB_ADM->IntegrationEngine configuratin-> edit the speicifc configuratin then add the follwoing
    Category:RUNTIME Parameters: logging Value:1
    If its done. check this alos...whether your browser settings will accept the cookies or not. for SSO logon ticket method you need to have cookies accepted by our browser so check it. in internet page slect TOOLS ->internet options then ckeck for cookies settings.
    How to Enable Single-Sign-On for XI 3.0 at:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/69d95112-0d01-0010-8297-fa31feea26e0
    /people/alexander.bundschuh/blog/2007/01/16/principal-propagation-in-sap-xi
    http://help.sap.com/saphelp_nw2004s/helpdata/en/5c/b7d53ae8ab9248e10000000a114084/content.htm
    regards
    manoj kumar

  • Custom playbar does not display in the list of available widgets

    I followed the steps described in the "Skins" page of the Captivate 5 help outlined here:
    http://help.adobe.com/en_US/captivate/cp/using/WSc1b83f70210cd101126156ac11c7f147d6b-8000. html
    Now my problem is, that my custom playbar is not displayed in the list of available playbars (neither in the Project->Skin Editor->Playbar nor in the list of widgets). If I just duplicate one of the existing playbar files in Gallery/Widgets/Playbars it's listed without problems.
    I use Flash CS5 to edit the playbar and tried to publish it as AS3 and AS2 - no success.
    Are there special settings I need to set in the publishing settings to get my playbar in the list? Anything else I'm missing?!
    Thanks,
    Peter

    Try putting the swf for the playbar in ...\Adobe Captivate 5\en_GB\Gallery\Playbars\AS3\

  • The Favorite iView does not appear in the Portal

    The Favorite iView does not appear in the Portal - instead I get the following runtime error:
    com.sap.portal.pcm.Title - An exception occurred while processing your request
    When I look it up in the log file - I get the following:
    Date : 06/092008
    Time : 7:58:50:500
    Message : 07:58_04/06/08_3852950
    EXCEPTION
    com.sapportals.portal.prt.component.PortalComponentException: Error in init method
    Component : com.sap.netweaver.coll.appl.ui.room.CollaborationDetailedNavigation
    at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
    at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:271)
    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.pb.PageBuilder.createIviewProfile(PageBuilder.java:443)
    at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
    at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:233)
    at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:635)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
    at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:815)
    at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:703)
    at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
    at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
    at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
    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.doPrivileged(Native Method)
    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.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.navigation.CollaborationNavTree of Portal Component com.sap.netweaver.coll.appl.ui.room.CollaborationDetailedNavigation because: Could not instantiate implementation class
    at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:269)
    at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
    at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
    at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
    at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
    ... 35 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: http://PortalApplicationItem._prepare: com.sap.netweaver.coll.appl.ui.room
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem._refresh(PortalApplicationItem.java:507)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.getCoreLoader(PortalApplicationItem.java:1360)
    at com.sapportals.portal.prt.core.broker.PortalComponentItem.getClassLoader(PortalComponentItem.java:569)
    at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getClassLoader(PortalComponentItemFacade.java:102)
    at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
    ... 39 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: http://PortalApplicationItem._prepare: com.sap.km.application
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
    ... 44 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: http://PortalApplicationItem._prepare: com.sap.km.cm.ui.flex
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
    ... 45 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: http://PortalApplicationItem._prepare: com.sap.netweaver.bc.crt
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
    ... 46 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: http://PortalApplicationItem._prepare: com.sap.portal.runtime.config.component
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
    ... 47 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during start of application: SAPJ2EE::library:com.sap.tc.di.scm.transport_api
    at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:323)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
    ... 48 more
    Caused by: com.sapportals.portal.prt.core.broker.SAPJ2EELibraryNotFoundException: Could not find Library SAPJ2EE::library:com.sap.tc.di.scm.transport_api
    at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:277)
    ... 49 more
    Severity : Error
    Category :
    Location : com.sap.portal.prt.runtime
    Application : sap.com/irj
    Thread : ThreadPRT-Async 1,5,PRT-Async
    Datasource : 1212584461125:E:\usr\sap\DEP\JC00\j2ee\cluster\server0\log\defaultTrace.trc
    Message ID : 00145E336A6A0091000000010000098C00044ED6CA463F40
    Source Name : com.sap.portal.prt.runtime
    Argument Objs : com.sapportals.portal.prt.component.PortalComponentException: Error in init method
    Component : com.sap.netweaver.coll.appl.ui.room.CollaborationDetailedNavigation
    at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
    at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:271)
    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.pb.PageBuilder.createIviewProfile(PageBuilder.java:443)
    at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
    at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:233)
    at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:635)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
    at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:815)
    at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:703)
    at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
    at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
    at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
    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.doPrivileged(Native Method)
    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.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.navigation.CollaborationNavTree of Portal Component com.sap.netweaver.coll.appl.ui.room.CollaborationDetailedNavigation because: Could not instantiate implementation class
    at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:269)
    at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
    at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
    at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
    at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
    ... 35 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: http://PortalApplicationItem._prepare: com.sap.netweaver.coll.appl.ui.room
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem._refresh(PortalApplicationItem.java:507)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.getCoreLoader(PortalApplicationItem.java:1360)
    at com.sapportals.portal.prt.core.broker.PortalComponentItem.getClassLoader(PortalComponentItem.java:569)
    at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getClassLoader(PortalComponentItemFacade.java:102)
    at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
    ... 39 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: http://PortalApplicationItem._prepare: com.sap.km.application
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
    ... 44 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: http://PortalApplicationItem._prepare: com.sap.km.cm.ui.flex
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
    ... 45 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: http://PortalApplicationItem._prepare: com.sap.netweaver.bc.crt
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
    ... 46 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: http://PortalApplicationItem._prepare: com.sap.portal.runtime.config.component
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
    ... 47 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during start of application: SAPJ2EE::library:com.sap.tc.di.scm.transport_api
    at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:323)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
    ... 48 more
    Caused by: com.sapportals.portal.prt.core.broker.SAPJ2EELibraryNotFoundException: Could not find Library SAPJ2EE::library:com.sap.tc.di.scm.transport_api
    at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:277)
    ... 49 more
    Arguments : com.sapportals.portal.prt.component.PortalComponentException: Error in init method
    Component : com.sap.netweaver.coll.appl.ui.room.CollaborationDetailedNavigation
    at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
    at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:271)
    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.pb.PageBuilder.createIviewProfile(PageBuilder.java:443)
    at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
    at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:233)
    at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:635)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
    at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:815)
    at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:703)
    at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
    at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
    at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
    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.doPrivileged(Native Method)
    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.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.navigation.CollaborationNavTree of Portal Component com.sap.netweaver.coll.appl.ui.room.CollaborationDetailedNavigation because: Could not instantiate implementation class
    at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:269)
    at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
    at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
    at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
    at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
    ... 35 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: http://PortalApplicationItem._prepare: com.sap.netweaver.coll.appl.ui.room
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem._refresh(PortalApplicationItem.java:507)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.getCoreLoader(PortalApplicationItem.java:1360)
    at com.sapportals.portal.prt.core.broker.PortalComponentItem.getClassLoader(PortalComponentItem.java:569)
    at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getClassLoader(PortalComponentItemFacade.java:102)
    at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
    ... 39 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: http://PortalApplicationItem._prepare: com.sap.km.application
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
    ... 44 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: http://PortalApplicationItem._prepare: com.sap.km.cm.ui.flex
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
    ... 45 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: http://PortalApplicationItem._prepare: com.sap.netweaver.bc.crt
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
    ... 46 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: http://PortalApplicationItem._prepare: com.sap.portal.runtime.config.component
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
    ... 47 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during start of application: SAPJ2EE::library:com.sap.tc.di.scm.transport_api
    at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:323)
    at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
    ... 48 more
    Caused by: com.sapportals.portal.prt.core.broker.SAPJ2EELibraryNotFoundException: Could not find Library SAPJ2EE::library:com.sap.tc.di.scm.transport_api
    at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:277)
    ... 49 more
    Dsr Component : n/a
    Dsr Transaction : c1bb8390323511dd980100145e336a6a
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 1
    Relatives :
    Resource Bundlename :
    Session : 52
    Source : com.sap.portal.prt.runtime
    ThreadObject : ThreadPRT-Async 1,5,PRT-Async
    Transaction :
    User : Administrator

    Amir ,
    Check this link , I t will help you
    http://help.sap.com/saphelp_nw04s/helpdata/en/1e/62eae2357c4596bda2476d0a6503e3/frameset.htm
    Set the property "Add to Favourites" to Yes
    Portal Content -> Content provided by SAP -> End user Content -> Standard Portal User -> Default Framework page ---> Edit Object
    Open the Page Title Bar -> Search for the property -> Show 'Add to Browser Favorites'
    and set this property to Yes.
    Now refresh the page. It will show this option.
    Koti Reddy

  • EP log type INFO not written to the portal.log file

    All the log.info (where log is of type PortalRuntime Logger) statements in my code are not written  to the portal.log file.
    I have configured the portal_logger to log ALL but it seems to log only the FATAL and WARNING messages and not the INFO ones.I am on EP6 SP2
    Thanks
    Sid

    Let me rephrase my question.
    In the portal logs configuration (Sys Adm - Monitoring - Logging Console - portal_logger ) if you select ALL, should it not log messages of all types ( ERROR WARNING INFO )? When I select ALL for the portal_logger the portal.log doesn't display the log messages of type INFO (only the once of type ERROR or WARNING).

  • VERY URGENT, I CAN NOT ENTER IN THE PORTAL

    Hi,
    yesterday i changed the number of sessions in the visual administrator, Visual Administrator->services->Security Provider ->properties -> sessions_size,  from 200 to 1 and now we can not enter in the portal even from visual administrator.
    any idea please??

    Hi did you tried implementing the solution given in
    Unable to login to Visual Admin
    Also go to this path and check
    if No body can log into the portal until this account is disabled and a new super admin is created.                                             
    Information about portal setup and configuration can be found on
    help.sap.com --> Netweaver --> EP6 =< NW04                                             
    Specifically look into the Administration Guide --> User Admin section on how to create a super admin user and disable sap*.                                             
    I am trying my level best to help you, also please open an OSS message with SAP in the meantime.

  • Problem URL-IView - is not display in the Portal Content Area

    Hi!
    I have a problem. My URL-IView is not displayed in the Portal Content Area. The setting "launch in new window " is  "display in Portal Content Area". What can I do that the URL -IVIiew is not display in a separate window.
    Can anyone help me???
    Thank you very much
    regards

    Hi.
    You have to add your URL iView to a page. See URL iview - The page cannot be found for details.
    Best regards,
    Aliaksandr Zhukau

  • SSO not working for a custom WDA application that runs in the Portal

    I have a Portal system (Java stack, NW04s) that has an iView of type webDynpro ABAP. The custom Web Dynpro ABAP application resides on another system (ABAP stack, running ECC6). We have configured the trust relationship between the Portal and the ECC system as per
    http://help.sap.com/saphelp_nw04s/helpdata/en/61/42897de269cf44b35f9395978cc9cb/content.htm
    We know this is working since we are able to run ESS. However, for the custom WebDynpro ABAP application, when calling it for the first time, a logon screen shows up. How can we get rid of it? what are we missing to have SSO work for the custom WebDynpro application?

    Please check this link:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d35bb690-0201-0010-988a-d669c8530518
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.highlightedcontent?documenturi=%2fhelp%2fsdn_help_nw04s%2fsaphelp_nw04s%2fhelpdata%2fen%2f5e%2f6c85c3edf942f39349a1e337434d29%2fcontent.htm
    Hope it helps.
    Regards,
    Mona

  • Custom application is not working after the support package upgrade.

    Hi SDN Folks,
    I have upgraded the portal from SP09 to SP25 successfully. But after the upgrade our custom application is not behaving as before. When we submit anything in the custom page its returning to home page. No error in the log files also.
    Custom application is a devoloped in webdynpro java.
    Kindly suggest.
    regards,
    Mahesh.N.R

    Hi Sita,
    Currently I canot take help form the developers, please let me know where i ca checkwhether the custom URLs are set to home page.
    regards,
    Mahesh.N.R

Maybe you are looking for