Error deploying new portal logon page

Hi Gurus,
I'm getting an error deploying my new portal logon page. I've made teh necessary changes to the portal.logon.par.bak file. I've rename it and made the necessary changes in config tool. i've created a new autoscheme_test.xml file and have assigned it accordingly. After restarting the portal, i'm getting the error message below trying to launch the portal :-
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
The exception was logged. Inform your system administrator..
See the details for the exception ID in the log file
Any ideas? Are there any other setting that i need to do aside from teh autosceme file. thanks

Hi Johan,
There are two lib files which you need to paste while you import the file in the NWDS.Just check for the steps through this weblog
the jar files name are
com.sap.portal.runtime.logon_api.par
umelogonbase.jar
(when you unzip you can find the files at PORTAL-INFlib)
Modifying The Logon Par(or customising the Logon Screen)
Thanks
Pankaj

Similar Messages

  • Error on Portal Logon Page

    Hi Experts,
    We are getting exception while calling the Portal URL.
    Recently, we changed the password policy and made some customizations on the com.sap.portal.runtime.logon.par file.
    After that when I tried to access the Logon page, it gave an exception.
    I even replaced the customized logon par file with the original one but it did not help.
    Please note that I deployed the logon par file with the same name, so I did not have to make any changes in the authschemes.xml file.
    So ideally when I replaced the customized PAR file with the original one, it should have worked out.
    Can it be because of some UME property "Password Policy change" or something like that which has been changed by our Basis team  in the Config tool and which is creating issues now.
    Is there any connection between the UME property and the Portal Logon page? I know that UME comes into picture once the user clicks on Login button after entering the login credentials but does it also come in picture at the portal logon page call?
    We are not able to trace out the root cause as both Password Policy Change and deployment of PAR was done parallely due to which we are confused about the cause of the issue.
    Please find below the trace against the exception ID:
    #1.5 #5CF3FC5B7E1C00670000000300001B400004ACA7F25E4315#1315737232519#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#Guest#0##n/a##8b1ef68fdc6111e0a5840000061bff66#SAPEngine_Application_Thread[impl:3]_24##0#0#Error##Java###04:03_11/09/11_102498150 An error occured in iView: N/A in component: N/A##
    #1.5 #5CF3FC5B7E1C00660000000100001B400004ACA7F2896FC1#1315737235348#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#0##n/a##184d79b1dc6111e087880000061bff66#SAPEngine_Application_Thread[impl:3]_8##0#0#Error##Plain###Shutting down Application Brokerage...#
    #1.5 #5CF3FC5B7E1C00660000000800001B400004ACA7F2940472#1315737236039#com.sap.portal.prt.runtime.broker#sap.com/irj#com.sap.portal.prt.runtime.broker#Guest#0##n/a##184d79b1dc6111e087880000061bff66#SAPEngine_Application_Thread[impl:3]_8##0#0#Error#1#/System/Server#Java###[PortalServiceItem.release] exception caught releasing com.sap.netweaver.coll.appl.rtc|RTCClientPollingService
    [EXCEPTION]
    #1#java.lang.NullPointerException
         at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging.unsubscribe(RTMFMessaging.java:1040)
         at com.sap.ip.collaboration.core.api.rtmf.core.cluster.ClusterSystemManager.unsubscribe(ClusterSystemManager.java:133)
         at com.sap.ip.collaboration.core.api.semantic.services.RTCBaseService.destroy(RTCBaseService.java:146)
         at com.sapportals.portal.prt.core.broker.PortalServiceItem.release(PortalServiceItem.java:389)
         at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1159)
         at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
         at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
         at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
         at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
         at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
         at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
         at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
         at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
         at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
         at com.sapportals.portal.prt.core.broker.ApplicationItem.releaseDependents(ApplicationItem.java:223)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.releaseDependents(PortalApplicationItem.java:1156)
         at com.sapportals.portal.prt.core.broker.ApplicationItem.release(ApplicationItem.java:476)
         at com.sapportals.portal.prt.core.broker.PortalApplicationItem.release(PortalApplicationItem.java:1194)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.releaseAllItems(PortalAppBroker.java:575)
         at com.sapportals.portal.prt.core.broker.PortalAppBroker.shutdown(PortalAppBroker.java:680)
         at com.sapportals.portal.prt.runtime.Portal.shutdown(Portal.java:725)
         at com.sapportals.portal.prt.core.PortalCoreInitializer.shutdown(PortalCoreInitializer.java:111)
         at com.sapportals.portal.prt.dispatcher.PortalInitializer.shutdown(PortalInitializer.java:164)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.destroy(Dispatcher.java:651)
         at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.destroyServlets(WebComponents.java:731)
         at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadDestroyer.run(ApplicationThreadDestroyer.java:62)
         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:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    #1.5 #5CF3FC5B7E1C006F00000002000016140004ACA819F31491#1315737896495#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#Guest#0##n/a##1647a148dc6311e0aaaa0000061bff66#SAPEngine_Application_Thread[impl:3]_9##0#0#Error##Java###04:14_11/09/11_102498150 An error occured in iView: N/A in component: N/A##
    #1.5 #5CF3FC5B7E1C007000000000000016140004ACA81A149C1D#1315737898689#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Guest#0##n/a##18319b2cdc6311e092af0000061bff66#SAPEngine_Application_Thread[impl:3]_14##0#0#Error#1#/System/Server#Java###An error occured during authscheme computation.
    [EXCEPTION]
    #1#com.sapportals.portal.prt.component.PortalComponentException: Error in init method
    Component : com.sap.portal.runtime.logon.certlogon
         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.prt.service.authenticationservice.AuthenticationService.getLogonIView(AuthenticationService.java:233)
         at com.sapportals.portal.prt.service.hook.SecurityHookService.doNodeHook(SecurityHookService.java:177)
         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:235)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)
         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:117)
         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:1060)
         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:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.ume.component.logon.SAPMLogonCertComponent of Portal Component com.sap.portal.runtime.logon.certlogon because: Linkage error while loading implementation class
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
         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)
         ... 33 more
    Caused by: java.lang.NoClassDefFoundError: com/sap/security/core/logonadmin/IAccessToLogic
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:219)
         at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
         ... 37 more
    Thanks & Regards.
    Anurag

    Hi,
    Check if your portalapp.xml has an entry "<property name="ClassName" value="com.sapportals.portal.ume.component.logon.SAPMLogonComponent"/>"
    If it is there, then I feel that this is an issue with jar files not getting imported properly.
    Just try including these two jars (umlogonbase.jar and com.sap.portal.runtime.logon_api.jar) from
    usr\sap\J2E\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.runtime.logon\lib
    and copy manually to the lib folder under PORTAL-INF in your project.
    Regards,
    Vijay.

  • Portal Logon page repeating/ redirecting to itself on first attempt

    All,
    Apologies in advance if this is not the appropriate forum.  We are in the process of migrating a NW7.0SPS13/EP7.0SPS13 installation from a remote site to a local site with a database only UME and SSO to an ECC6.0 backend.  The new target installation has picked up a rather odd behavior.  When loggin onto the portal, the logon page repeats/refreshes/redirects to itself with valid ID and password with no error message.  The only apparent action is the clearing of the password field.
    My only clue so far is the absence of this script in the http trace on the initial logon attempt which shows up on the second attempt:
    http://<host>:51100/irj/portalapps/com.sap.portal.httpconnectivity.httpauthentication/scripts/CAManagerScript.js
    I did find this related thread and attempted the suggestions with no luck:
    Re: portal logon page coming again
    I felt this might be the best place to post question since this may be an authentication/connectivity issue.
    Thanks in advance,
    Lee

    You are correct, we are not implementing SPNego but at this point I will take any suggestions that might be conceptually related...
    We are attempting to migrate/clone the entire server (OS,J2EE,MSSQL05...) from a remote hosted environment to a local network environment.
    I checked the Everyone, Authenticated, and Anonymous groups for the correct roles/Java permissions and all seems to be in-line with the correctly functioning remote system with correct user assignment.
    With some further log filtering I was able to where find this error:
    The default keystore view [TicketKeystore] does not exist. Authentication stack: [ticket]. The possible reasons for that problem are: keystore does not exist or the user has no permission to read from the keystore view. You can delete the TicketKeystore and restart the engine so that the engine automatically re-creates it.
    I suspect the SAPLogonTicketKeystore was recreated incorrectly...  I will have the migration team recreate it again.  FWIW, I am unfamiliar with the process of assigning user access to this object as the error suggests.
    Thanks for the suggestions...

  • Adding a button/link in the portal logon page

    Hi,
    I am new to the portal related things. I am a web dynpro developer and familiar with the Java coding.
    Now, i got a requirement to modify the portal logon page as below:
    Need to insert one extra button/hyper link to reset the password.
    when user clicks on this button, i need to call an RFC in R/3 by passing the entered user name. That RFC will generate a new password and send a mail to the respective email address(maintained in a custom table in R/3 itself).
    If the user-id is wrong i need to show the error message returned from the RFC.
    If the return-code of RFC is success, then need to show an information message conveying that the password reset was successful and refer to your mail inbox.
    Please suggest me the best approach on this scenario.
    I already imported the PAR file for logon page and can see the project in NWDS.
    Note: we are using EP 7, NW2004s and R/3 is ECC 5.0
    Thanks & Regards,
    Kiran Chennapai

    The Funktion Prem is suggesting can be turned on/off through the UME Properties which can be changed through the Config Tool.
    More help under : http://help.sap.com/saphelp_nw04/helpdata/en/0b/50ad3e1d1edc61e10000000a114084/content.htm
    Regards,
    Kai

  • How to put portal logon page CE 7.3 ui.war file in NWDI Track

    Hi,
    We are using sap portal CE 7.3 in our project. I have customized portal logon page. for this I have downloaded ui.war file from portal server in my local machine that is on my desktop and this ui.war file i have imported in my NWDS and done the required modification.
    Now I have to put this development that is modified ui.war in my NWDI track which is currently lying on my local machine Desktop, please let me know how to transport this ui.war file and ear project associated with this war file into NWDI track.
    because from NWDI track only this customized logon portal page has to go to QA and Prd system.This is strict client requirement.
    Please help me.
    Thanks

    Hi Arush,
    Instead of importing the war file into NWDI track,you can create new web module project  in NWDI using New-->Development Infrastructure-->DC-->Java EE-->WebModule and copy paste the WebContent folder Jsp's and xml files which are inside the ui.war in your local machine. Then for this web module you can create ear file for deploying .I have done in this way it worked.
    Regrads,
    Srinivasan V

  • How to redirect the portal Logon page..IMP

    Hi Frndz..
    I want to know how i can change the Portal default logon page, means when ur giving url on browser like
    http://host:port/irj/portal it  will directs us to default portal logon page that we r familiar.
    As per my requirement when we call the url ( http://host:port/irj/portal) it should call a custom JSP(fancy screen with AJAX&XML) page that i made ,   from this page i need to access portal .
    So i want  to  use this custom JSP page as my portal logon page .
    Thanks in Advance
    Regards
    Rajesh

    Hi Check the following,
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/62/601e1eebf54ca6a97e2873c8c63517/content.htm
    Siddharth

  • Accessing KM Document Iview which contain .exe file from Portal logon page.

    Dear All,
    I was trying to access the KM document ivew(where I uploaded an .exe file in KM and created an ivew for that) in my portal logon page which is customized.
    I am calling the ivew through an html command "href".
    Now my issue is, while clicking on that link, that exe file is opening with the full portal ivew path name without any extension.
    But the actual exe file of same size which is uploaded is getting downloaded and saved with out any extension. I always have to change the name and give .exe extension for that to open properly.
    So, can some one suggest me how to open the actual exe file with the extension?
    Cheers,
    Anu.

    Sorry Tom!
    Your problem seems to be different, I've no idea.
    But we already fixed our problem, I forgot to post. Here's our solution:
    The solution was to create a KM Docs iView with anonymous authentication schema pointing to the download file. Then we created an URL iView pointing to this KM Doc with appending the filename AGAIN to the URL (because otherwise the iView ID will appear as filename). In the page a hyperlink now is pointing to the URL iView and after clicking it, the download starts with the correct filename.

  • Different portal logon pages with same url.

    Hi all,
    Im doing portal logon page customization . My requirement is when a user give the portal link in his browser he should get the portal logon page according to the country language..for example if he opens the portal from india he should get English text and if he opens the portal from japan he should get the japanese text in the portal logon page.
    thanks
    Rajeev B

    Rajeev,
    Its possible to have the different logon pages for the same portal.
    Its also possible for the same ulr but different parameters.
    You can do customization on portal logon page.
    For example:
    Consider that the url http://myep:50000/irj/portal is currently using to access the portal.
    You can pass addintional parameter on this url and fetch them into logon page, display the pages based on the values that you have fetched.
    for example http://myep:50000/irj/portal/myparam
    Have a lot at this link,
    Displaying Different Login Pages Based On The Sales Organization
    Ram

  • Activating Security Policy at Portal Logon Page

    Hi @ll,
    Iu2019m not able to activate the password security policy check at portal logon page. For this purpose, I have already checked the Enforce Password Security Policy at Logon (System Administration->System Configuration->UME Configuration->Security Policy) and restarted the server too. But it is failed to appear at logon page.
    Plesae suggest me to resolve this problem.
    Thanks
    Gautam Singh

    Hi Gautam Singh,
    You say you are customizing the portal logon screen. Are you doing a simple modification by just changing UME properties as described in [Logon Screen Customization|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/43/fc3ae22adb025fe10000000a1553f7/frameset.htm] or are you actually changing .par files and creating your own logon application?
    Are you using config tool, the user management configuration Web Dynpro UI, or visual admin  to change the properties?
    Have you assigned the UME actions Logon_Help and Selfregister_User to the Anonymous Users group?
    -Michael

  • Error Deploying Sample Portal from Development Guide

    I am going through creating a New Portal from WebLogic Portal 7 Development
    Guide and I am running into the following problem.
    After completing Step 2: Create the New Portal, when I try to Hot Deploy the
    application, I get the following error.
    Hot deploy failed with the following message:
    Unable to add module: NewPortalWebApp to application descriptor for:
    portalApp.
    The log has the following information..
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    portlets\Portlet1.portlet to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\tools.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\webflow-extensions.wfx to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\user_account.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\portal.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\security.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\NewPortal.portal to sync list.
    Attempting sync...
    Sync complete.
    Searching for portalApp application descriptor...
    Found it.
    Error - please check log for details.

    That's great, Mike, you're welcome. I'm glad it's working for you. Thanks for letting me know.
    -Scott
    Mike Friesen wrote:
    I'm sorry you were right.. I tried it and everything works... thanks..
    Mike
    "Scott Ellis" <[email protected]> wrote in message
    news:[email protected]...
    Hi Mike,
    I hear what you are saying and I believe you. But the error you describedis the known issue related to Internet access
    (down to the exact line numbers in the stack trace). Is it possible yourconnection was down last time you attempted
    hot-deploy?
    If you are sure your Internet connection is up, I would recommend tryinghot-deploy again. If it still does not work,
    something very strange is going on. At that point I would recommendtrying the workaround anyway or escalating the issue
    to BEA Support.
    Now my curiosity is piqued so I hope you'll let me know either way.
    Best Regards,
    Scott Ellis
    BEA Systems
    Mike Friesen wrote:
    yes..
    "Scott Ellis" <[email protected]> wrote in message
    news:[email protected]...
    Can you please try something for me? Paste the following URL into abrowser:
    http://java.sun.com/dtd/application_1_3.dtd
    Does it come up?
    Thanks,
    Scott
    Mike Friesen wrote:
    Actually, my computer does have internet access, so I don't think that
    is
    the problem.
    Mike
    "Scott Ellis" <[email protected]> wrote in message
    news:[email protected]...
    Hi Mike,
    I would bet that you are working on a machine that doesn't have
    Internet
    access, correct?
    The problem is that the EBCC is trying and failing to access the J2EEapplication descriptor
    dtd from Sun's website.
    If you can't get Internet access, here is the workaround:
    - save the attached file to your harddrive (just save it to c:\)
    - edit the application.xml file for your project as follows:
    - first copy the entire DOCTYPE declaration and save it somewhere
    in
    a
    separate text file (in case want to revert back to it later)
    - edit the DOCTYPE declaration so that it looks like this:
    <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EEApplication 1.3//EN' 'file:///application_1_3.dtd'>
    ( notice that the java.sun.com web address is replaced with the URI
    to
    the file on your harddrive)
    - save your changes and hotdeploy will work with or without Internetaccess
    Thanks,
    Scott Ellis
    BEA Systems
    Mike Friesen wrote:
    I am going through creating a New Portal from WebLogic Portal 7
    Development
    Guide and I am running into the following problem.
    After completing Step 2: Create the New Portal, when I try to Hot
    Deploy
    the
    application, I get the following error.
    Hot deploy failed with the following message:
    Unable to add module: NewPortalWebApp to application descriptor for:
    portalApp.
    The log has the following information..
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    portlets\Portlet1.portlet to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\tools.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\webflow-extensions.wfx to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\user_account.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\portal.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\security.wf to sync list.
    Adding file:
    C:\bea\user_projects\myNewdomain\beaApps\portalApp-project\application-sync\
    webapps\PortalWebApp\NewPortal.portal to sync list.
    Attempting sync...
    Sync complete.
    Searching for portalApp application descriptor...
    Found it.
    Error - please check log for details.
    <!--
    Copyright (c) 2000 Sun Microsystems, Inc.,
    901 San Antonio Road,
    Palo Alto, California 94303, U.S.A.
    All rights reserved.
    Sun Microsystems, Inc. has intellectual property rights relating to
    technology embodied in the product that is described in this document.
    In particular, and without limitation, these intellectual property
    rights may include one or more of the U.S. patents listed at
    http://www.sun.com/patents and one or more additional patents or
    pending patent applications in the U.S. and in other countries.
    This document and the product to which it pertains are distributed
    under licenses restricting their use, copying, distribution, and
    decompilation. This document may be reproduced and distributed but
    may
    not be changed without prior written authorization of Sun and its
    licensors, if any.
    Third-party software, including font technology, is copyrighted and
    licensed from Sun suppliers.
    Sun, Sun Microsystems, the Sun logo, Java, JavaServer Pages, Java
    Naming and Directory Interface, JDBC, JDK, JavaMail and and
    Enterprise JavaBeans are trademarks or registered trademarks of Sun
    Microsystems, Inc. in the U.S. and other countries.
    Federal Acquisitions: Commercial Software - Government Users Subjectto
    Standard License Terms and Conditions.
    DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
    CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
    WARRANTY OF MERCHANTABILITY, FITNESS FOR FOR A PARTICULAR PURPOSE OR
    NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
    DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
    Copyright (c) 2000 Sun Microsystems, Inc.,
    901 San Antonio Road,
    Palo Alto, California 94303, E'tats-Unis.
    Tous droits re'serve's.
    Sun Microsystems, Inc. a les droits de proprie'te' intellectuels
    relatants a` la technologie incorpore'e dans le produit qui est
    de'crit
    dans ce document. En particulier, et sans la limitation, ces droits de
    proprie'te' intellectuels peuvent inclure un ou plus des brevets
    ame'ricains e'nume're's a` http://www.sun.com/patents et un ou les
    brevets plus supple'mentaires ou les applications de brevet en attente
    dans les E'tats-Unis et dans les autres pays.
    Ce produit ou document est prote'ge' par un copyright et distribue'
    avec des licences qui en restreignent l'utilisation, la copie, la
    distribution, et la de'compilation. Ce documention associe n peut
    e^tre reproduite et distribuer, par quelque moyen que ce soit, sans
    l'autorisation pre'alable et e'crite de Sun et de ses bailleurs de
    licence, le cas e'che'ant.
    Le logiciel de'tenu par des tiers, et qui comprend la technologie
    relative aux polices de caracte`res, est prote'ge' par un copyright et
    licencie' par des fournisseurs de Sun.
    Sun, Sun Microsystems, le logo Sun, Java, JavaServer Pages, Java
    Naming and Directory Interface, JDBC, JDK, JavaMail et and
    Enterprise JavaBeans sont des marques de fabrique ou des marques
    de'pose'es de Sun Microsystems, Inc. aux E'tats-Unis et dans d'autres
    pays.
    LA DOCUMENTATION EST FOURNIE "EN L'E'TAT" ET TOUTES AUTRES CONDITIONS,
    DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT
    EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS
    NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A
    L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE
    CONTREFAC,ON.
    -->
    <!--
    This is the XML DTD for the J2EE 1.3 application deployment
    descriptor. All J2EE 1.3 application deployment descriptors
    must include a DOCTYPE of the following form:
    <!DOCTYPE application PUBLIC
    "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
    "http://java.sun.com/dtd/application_1_3.dtd">
    -->
    <!--
    The following conventions apply to all J2EE deployment descriptor
    elements unless indicated otherwise.
    - In elements that contain PCDATA, leading and trailing whitespace
    in the data may be ignored.
    - In elements whose value is an "enumerated type", the value is
    case sensitive.
    - In elements that specify a pathname to a file within the same
    JAR file, relative filenames (i.e., those not starting with "/")
    are considered relative to the root of the JAR file's namespace.
    Absolute filenames (i.e., those starting with "/") also specify
    names in the root of the JAR file's namespace. In general, relative
    names are preferred. The exception is .war files where absolute
    names are preferred for consistency with the servlet API.
    -->
    <!--
    The application element is the root element of a J2EE application
    deployment descriptor.
    -->
    <!ELEMENT application (icon?, display-name, description?, module+,
    security-role*)>
    <!--
    The alt-dd element specifies an optional URI to the post-assembly
    version of the deployment descriptor file for a particular J2EEmodule.
    The URI must specify the full pathname of the deployment descriptor
    file relative to the application's root directory. If alt-dd is not
    specified, the deployer must read the deployment descriptor from the
    default location and file name required by the respective component
    specification.
    Used in: module
    -->
    <!ELEMENT alt-dd (#PCDATA)>
    <!--
    The connector element specifies the URI of a resource adapter archive
    file, relative to the top level of the application package.
    Used in: module
    -->
    <!ELEMENT connector (#PCDATA)>
    <!--
    The context-root element specifies the context root of a web
    application.
    Used in: web
    -->
    <!ELEMENT context-root (#PCDATA)>
    <!--
    The description element is used to provide text describing the parent
    element. The description element should include any information that
    the application ear file producer wants to provide to the consumer of
    the application ear file (i.e., to the Deployer). Typically, the tools
    used by the application ear file consumer will display the description
    when processing the parent element that contains the description.
    Used in: application, security-role
    -->
    <!ELEMENT description (#PCDATA)>
    <!--
    The display-name element contains a short name that is intended to be
    displayed by tools. The display name need not be unique.
    Used in: application
    Example:
    <display-name>Employee Self Service</display-name>
    -->
    <!ELEMENT display-name (#PCDATA)>
    <!--
    The ejb element specifies the URI of an ejb-jar, relative to the top
    level of the application package.
    Used in: module
    -->
    <!ELEMENT ejb (#PCDATA)>
    <!--
    The icon element contains small-icon and large-icon elements that
    specify the file names for small and a large GIF or JPEG icon images
    used to represent the parent element in a GUI tool.
    Used in: application
    -->
    <!ELEMENT icon (small-icon?, large-icon?)>
    <!--
    The java element specifies the URI of a java application clientmodule,
    relative to the top level of the application package.
    Used in: module
    -->
    <!ELEMENT java (#PCDATA)>
    <!--
    The large-icon element contains the name of a file
    containing a large (32 x 32) icon image. The file
    name is a relative path within the application's
    ear file.
    The image may be either in the JPEG or GIF format.
    The icon can be used by tools.
    Used in: icon
    Example:
    <large-icon>employee-service-icon32x32.jpg</large-icon>
    -->
    <!ELEMENT large-icon (#PCDATA)>
    <!--
    The module element represents a single J2EE module and contains a
    connector, ejb, java, or web element, which indicates the module type
    and contains a path to the module file, and an optional alt-ddelement,
    which specifies an optional URI to the post-assembly version of the
    deployment descriptor.
    The application deployment descriptor must have one module element for
    each J2EE module in the application package.
    Used in: application
    -->
    <!ELEMENT module ((connector | ejb | java | web), alt-dd?)>
    <!--
    The role-name element contains the name of a security role.
    The name must conform to the lexical rules for an NMTOKEN.
    Used in: security-role
    -->
    <!ELEMENT role-name (#PCDATA)>
    <!--
    The security-role element contains the definition of a security
    role. The definition consists of an optional description of the
    security role, and the security role name.
    Used in: application
    Example:
    <security-role>
    <description>
    This role includes all employees who are authorized
    to access the employee service application.
    </description>
    <role-name>employee</role-name>
    </security-role>
    -->
    <!ELEMENT security-role (description?, role-name)>
    <!--
    The small-icon element contains the name of a file
    containing a small (16 x 16) icon image. The file
    name is a relative path within the application's
    ear file.
    The image may be either in the JPEG or GIF format.
    The icon can be used by tools.
    Used in: icon
    Example:
    <small-icon>employee-service-icon16x16.jpg</small-icon>
    -->
    <!ELEMENT small-icon (#PCDATA)>
    <!--
    The web element contains the web-uri and context-root of a web
    application module.
    Used in: module
    -->
    <!ELEMENT web (web-uri, context-root)>
    <!--
    The web-uri element specifies the URI of a web application file,
    relative to the top level of the application package.
    Used in: web
    -->
    <!ELEMENT web-uri (#PCDATA)>
    <!--
    The ID mechanism is to allow tools that produce additional deployment
    information (i.e., information beyond the standard deployment
    descriptor information) to store the non-standard information in a
    separate file, and easily refer from these tool-specific files to the
    information in the standard deployment descriptor.
    Tools are not allowed to add the non-standard information into the
    standard deployment descriptor.
    -->
    <!ATTLIST alt-dd id ID #IMPLIED>
    <!ATTLIST application id ID #IMPLIED>
    <!ATTLIST connector id ID #IMPLIED>
    <!ATTLIST context-root id ID #IMPLIED>
    <!ATTLIST description id ID #IMPLIED>
    <!ATTLIST display-name id ID #IMPLIED>
    <!ATTLIST ejb id ID #IMPLIED>
    <!ATTLIST icon id ID #IMPLIED>
    <!ATTLIST java id ID #IMPLIED>
    <!ATTLIST large-icon id ID #IMPLIED>
    <!ATTLIST module id ID #IMPLIED>
    <!ATTLIST role-name id ID #IMPLIED>
    <!ATTLIST security-role id ID #IMPLIED>
    <!ATTLIST small-icon id ID #IMPLIED>
    <!ATTLIST web id ID #IMPLIED>
    <!ATTLIST web-uri id ID #IMPLIED>

  • To redirect the Enterprise portal logon page

    Hi all,
    Due to a certain requirement from the client, I need to redirect the logon page, immediately after the user authentication in portal.
    At present once the user key in the credentials, it is taken to the portal home page http://...../irj/portal.
    Now because of the requirement, instead of the initial home page, i want to redirect user to another page.
    e.g http://..../irj/KMdocument/....  .  I would be storing the new page location in KM of portal.
    Please suggest me a solution to redirect the initial start page in portal.
    If you need more details, please let me know.
    Thanks
    Namit.

    Hi chander,
    Could you help me to know, where should I change the windows features, like toolbar = 0 etc. as you have mentioned in your message???
    Also a little more explaintion on the issue for all:
    User would you the link http://someadd/irj/portal... he would get the normal login screen, where he would enter the username and password.Once he has entered his credentials, he needs to be redirected to another html page or if we can change the initial screen windows features it should be fine.
    Please help me on this...
    Thanks
    Namit

  • How to create a complete custom portal logon page.

    Hi Frndz,
    I want to create a new logon page i.e completely customized(not to customize com.sap.portal.runtime.logon.par), this is to make my portal as  a EFP(Xternal facing portal).
    Regards
    Rajesh

    Hi,
    Yes i agree with that i have to use PAR for logon.
    Let assume that i have created PAR file called "MyLogon.par" in this i have JSP file "Welcome.jsp" .
    In this JSP when we click on Logon Button it should lunch the portal screen, which action i should place in FORM of JSP action.
    If u go to SAPs  "umLogPage.jsp" in the FORM attribute
    can i use same piece of code in my custom jsp , to logon to portal.
    Is there any another way to logon to portal.
    Regrds
    Rajesh.

  • Support link in Portal logon page not working

    Hi All,
    We are using the ´support´ link on the logon page of our Portal. When we click the support link, the system asks for UserId and e-mail adress. When we fill this in correctly, the system responds by displaying "New password sent to e-mail adress".
    However, the password is not reset or anything and we still have to logon with the original old password. Where can this problem be rooted and where do I start to look for the cause of this.
    We are using CUA and this is set on ECC 6.0 production system.
    Message was edited by:
            Jan Laros

    Hai Laros,
    I have gone through this issue...
    I think your Portal is EP 7.0 SP12..
    For logon page weare using two jar files umelogonbase.jar and com.sap.portal.runtime.logon_api.jar
    There is some change in code of umelogonbase.jar file  in SP12  
    com.sap.security.core.sapmimp.logon.logonbean method getLogonHelp
    In SP12
       public boolean getLogonHelp()
            boolean rc = mySAPProperties.getBoolean("ume.logon.logon_help", true);
            if(!rc)
                rc = checkPermission("LOGON_HELP");
            return rc;
    private static boolean checkPermission(String permissionName)
            String METHOD = "checkPermission";
            boolean hasPermission = false;
            if(trace.bePath())
                trace.entering("checkPermission", new Object[] {
                    permissionName
            try
                boolean flag1;
                try
                    IUser user = UMFactory.getAuthenticator().getLoggedInUser();
                    if(user == null)
                        user = AnonymousUser.getInstance().getAnonymousUser();
                    if(trace.beDebug())
                        String userName = user != null ? user.getName() : "no user";
                        trace.debugT("checkPermission", "The current user is [{0}].", new Object[] );
                    if(user != null)
                        LogonApplicationPermission permission = new LogonApplicationPermission(permissionName);
                        hasPermission = user.hasPermission(permission);
                    } else
                        trace.errorT("checkPermission", "The current user is null.");
                    boolean flag = hasPermission;
                    return flag;
                catch(UMException umex)
                    flag1 = false;
                return flag1;
            finally
                if(trace.bePath())
                    trace.exiting("checkPermission", new Boolean(hasPermission));
    In SP10 code was
      public boolean getLogonHelp()
            return mySAPProperties.getBoolean("ume.logon.logon_help", true);
    In your jsp page
    if ( logonBean.getLogonHelp() ){
    //code
    logonBean.getLogonHelp() retuning true because of  additional <b>LogonApplicationPermission</b> checking....  
    I think you got my point....
    With reagrds
    Eldose
    Eldose

  • Error creating new portal from docs

    Hello,
    I've been trying for several days now to create a new Portal from the
    "Customizing Portals and Portlets" document
    (http://e-docs.bea.com/wlp/docs40/portal/devbasic.htm).
    I get all the way to "Verify Your Deployment" without issue. I can even
    verify the data synchronization using the data repository browser.
    When I go to http://localhost:7501/insevoportal (or /InsevoPortal or
    /InsevoPortal12, different attempts) all I get is the following in the
    server console:
    <Jul 16, 2002 2:27:34 PM MDT> <Notice> <WebLogicServer> <Started
    WebLogic Admin
    Server "portalServer" for domain "portalDomain" running in Production Mode>
    PortalPersistenceManager: portal 'portal/insevoportal' not found
    <Jul 16, 2002 2:29:37 PM MDT> <Error> <HTTP>
    <[WebAppServletContext(-15219959,in
    sevoportal,/insevoportal)] Servlet failed with ServletException
    javax.servlet.ServletException: Received a null Portal object from the
    PortalManager.
    at
    com.bea.portal.appflow.servlets.internal.PortalWebflowServlet.setupPortalRequest(PortalWebflowServlet.java:194)
    Can somebody please help me understand what is going on? I've been
    stuck for days now...
    Thanks in advance!
    David McDaniel

    David,
    Did you get any errors or warnings when you ran a sync?
    You can run a sync from the command line as well as from the EBCC. See the
    sync.cmd and syncApplication.cmd for details. Also, launching the EBCC with
    an open console window may give you some more information, as well as
    checking the EBCC log.
    Sincerely,
    Daniel Selman
    "David McDaniel" <[email protected]> wrote in message
    news:[email protected]...
    Daniel,
    Thanks for the response!
    I believe I have sync'd the application. I go to the portalDataSync web
    app, choose "Data Repository" link.
    Then I click the View icon for the Master Data Repository.
    Under there, I see things like:
    /webapps/InsevoPortal12/InsevoPortal12.portal
    /webapps/InsevoPortal12/portal.wf (and security.wf, tools.wf,
    user_account.wf, webflow-extensions.wfx)
    Looks about the same as the stockportal list. *** EXCEPT ** I don't see
    my Portlet in my list. Is that because it has no workflow? I can see
    the portlet in the EBCC.
    In the stockportal, I see portlet2.wf and portlet3.wf. I don't see any
    portlet wfs in my app.
    Any help is appreciated. I will consider 7.0.
    Regards,
    David
    Daniel Selman wrote:
    David,
    This usually means that you haven't synced the data to the correct
    application. When you go to the DataSync WebApp *for your portal
    application* do you see the portal and portlet files under the
    Portal/Portlet DataRepository?
    Sincerely,
    Daniel Selman
    "David McDaniel" <[email protected]> wrote in message
    news:[email protected]...
    Hello,
    I've been trying for several days now to create a new Portal from the
    "Customizing Portals and Portlets" document
    (http://e-docs.bea.com/wlp/docs40/portal/devbasic.htm).
    I get all the way to "Verify Your Deployment" without issue. I can even
    verify the data synchronization using the data repository browser.
    When I go to http://localhost:7501/insevoportal (or /InsevoPortal or
    /InsevoPortal12, different attempts) all I get is the following in the
    server console:
    <Jul 16, 2002 2:27:34 PM MDT> <Notice> <WebLogicServer> <Started
    WebLogic Admin
    Server "portalServer" for domain "portalDomain" running in Production
    Mode>
    PortalPersistenceManager: portal 'portal/insevoportal' not found
    <Jul 16, 2002 2:29:37 PM MDT> <Error> <HTTP>
    <[WebAppServletContext(-15219959,in
    sevoportal,/insevoportal)] Servlet failed with ServletException
    javax.servlet.ServletException: Received a null Portal object from the
    PortalManager.
    at
    com.bea.portal.appflow.servlets.internal.PortalWebflowServlet.setupPortalReq
    uest(PortalWebflowServlet.java:194)
    Can somebody please help me understand what is going on? I've been
    stuck for days now...
    Thanks in advance!
    David McDaniel

  • Portal Logon Page Functionality

    Hi,
         I am new to the portal world.
    I am trying to customize the logon page. I read the weblogs that describe the process.I wanted to know the functionality of the logon page ie: how the authentication takes place and the role of the various packages imported at the beginning of the jsp file.
       Please help me in understanding the functionality.
    Thnx,
    Pravesh Puria.

    There are Login Modules which handles the authentication job.You can configure different types of authentications like LDAP, Active Directory or other 3rd party modules. . For detailed information visit
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/8c/f03541c6afd92be10000000a1550b0/frameset.htm">Login Modules and Login Module Stacks</a>
    However, if you just want to customize logon page, you don't need to deal with login modules. If you want to add extra functionality, please give more details.
    Regards
    Abdul.

Maybe you are looking for