ISR Form Java Iview problem.

Hello,
We are having an ESS Iview named "Hire External Applicant" in Portal.
This iview has been customised.
I found that to construct this iview "5.     Request Form as Java iView in Enterprise Portal 5.0" section from ISR Cookbook is been used.
i.e. Created a request form using java iview.
This iview is being used in two places :
1. Create
2. Update.
Now Create is working fine.
But when this iview is accessed from Update section...i.e. user press update button:
the customized section in java iview is not getting updated.
Where this problem could be.

There is a new form section in existing standard form.
This section contains 4 new customized checkboxes.
When create button is pressed the values from these checkboxes is properly getting updated in R/3.
But when Update is pressed, these values are passing blank "As if nothing is selected" to R/3 module.
But at the time of Update button, all existing standard fields in form are getting updated.
I think that in case of update, these check boxes are not mapped properly to R/3 System.
I opened the par file in NWDS, and found that there is no code for mapping of values, and moreover same iview is working fine while create button is pressed.
Please guide me as of where could be problem.
Edited by: Saurabh Agarwal on Sep 17, 2010 4:57 PM

Similar Messages

  • Java iview problem

    hello together,
    my problem ist that i don't know if every iview has one profile-file (of course i can create more than one) or is there one profile-file for each person who uses this iview. i want to store personal data which influence the layout and content of the iview (every user has its own layout/content, but there is only one iview).
    where does the portal save the personalized data??
    i think, every user of the iview uses the same profile-file, but the runtime knows how to fill the profile depending for example on the userID.
    help would be great.
    thanks
    daniel

    sorry, i have vergotten one question:
    is it possible to use the built-in personalization with an input-field which has the type file. i want that users can select local files on their pc and store the path in the profile-file.
    ok, now it's really complete.
    daniel

  • WD Java iView & Dynamic Navigation Problem

    Hi,
    I'm trying to use a WebDynpro Java iView in Dynamic Navigation but have the following display problem:
    When I navigate to the page for which I've added the iView to the dynamic navigation, only the WebDynpro iView (from the navigation) is shown. You can see the page in its correct form being loaded but as soon as the navigation iView seems to be loaded/ing it replaces the full lower part of the screen (navigation and content panel).
    If I use a plain URL iView in the dynamic navigation the behaviour is as expected.
    But if I add a WebDynpro iView or even a page containing that iView I get the strange behaviour again.
    I'm running NW04s SP7.
    Any ideas?
    Do I have to set some properties on the WebDynpro iView?
    I've tried a couple of things but none did work so far.
    Thanks & Regards
    Markus

    Hi Henrik,
    Sorry for the late reply but I'm just back from vacation.
    No, I have not found a solution. I decided to go for an integrated application instead (Main WD application that bundles navigation with other applications). That works but of course is not as "nice".
    Have you come across some solution yet?
    Kind Regards
    Markus

  • Problem in logging onto portal "Java iView Runtime " error

    Hi,
    We are getting the following message when trying to logon to the portal.
    "Java iView Runtime
    Version : 5.0.200212121529
    (c) 2001 SAP Portals
    The following exception occured while processing your request:
    com.sapportals.portal.prt.runtime.PortalRuntimeException: delegatedplugin
    Exceptions details :
    com.sapportals.portal.prt.runtime.PortalRuntimeException: delegatedplugin
         at com.sapportals.portal.prt.portalconnection.sapnative.DelegatedPlugIn.handleRequest(DelegatedPlugIn.java:1044)
         at com.sapportals.portal.prt.portalconnection.sapnative.PortalPlugIn.handleRequest(PortalPlugIn.java:132)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:635)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
         at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:672)
         at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:314)
         at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
         at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1288)
         at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
         at com.inqmy.core.cluster.impl3.ParserRunner.run(ParserRunner.java:30)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    Caused by: javax.naming.NameNotFoundException: PortalLicense not found
         at com.sapportals.portal.prt.service.jndi.PortalServiceProviderContext.lookup(PortalServiceProviderContext.java:58)
         at com.sapportals.portal.prt.service.jndi.PortalServiceProviderContext.lookup(PortalServiceProviderContext.java:65)
         at javax.naming.InitialContext.lookup(InitialContext.java:345)
         at com.sapportals.portal.prt.portalconnection.sapnative.DelegatedPlugIn.handleRequest(DelegatedPlugIn.java:240)
         at com.sapportals.portal.prt.portalconnection.sapnative.PortalPlugIn.handleRequest(PortalPlugIn.java:132)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:635)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:126)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.inqmy.services.servlets_jsp.server.RunServlet.runSerlvet(RunServlet.java:149)
         at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.startServlet(ServletsAndJspImpl.java:833)
         at com.inqmy.services.httpserver.server.RequestAnalizer.checkFilename(RequestAnalizer.java:672)
         at com.inqmy.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:314)
         at com.inqmy.services.httpserver.server.Response.handle(Response.java:173)
         at com.inqmy.services.httpserver.server.HttpServerFrame.request(HttpServerFrame.java:1288)
         at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
         at com.inqmy.core.cluster.impl3.ParserRunner.run(ParserRunner.java:30)
         at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:148)
    If this situation persists, please contact your system administrator"
    Tried restarting the portal servers but the problem still persists.
    Request you to please suggest the solution for the same.

    Hi Sireesha,
    When it is working last time.
    Are any changes made to portal recently
    may be it is a permission issue in security zones.
    Below links may help you.
    http://help.sap.com/saphelp_nw04s/helpdata/en/25/85de55a94c4b5fa7a2d74e8ed201b0/content.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/ee/acd8403e37762ae10000000a155106/content.htm
    Raghu

  • Error while submitting ISR form

    Folks,
    I am getting the error when I am submitting ISR form
    <b>com.sap.tc.webdynpro.progmodel.context.ContextException:  is not a valid name for a node or attribute
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.validateName(NodeInfo.java:948)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.addChild(NodeInfo.java:308)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.addChild(NodeInfo.java:374)
         at com.sap.pcui_gp.isr.isrprocessevent.FcISRProcessEvent.createGenericContext(FcISRProcessEvent.java:1294)
         at com.sap.pcui_gp.isr.isrprocessevent.FcISRProcessEvent.adjustContext(FcISRProcessEvent.java:1745)
         at com.sap.pcui_gp.isr.isrprocessevent.FcISRProcessEvent.callIsrProcessEvent(FcISRProcessEvent.java:321)
         at com.sap.pcui_gp.isr.isrprocessevent.wdp.InternalFcISRProcessEvent.callIsrProcessEvent(InternalFcISRProcessEvent.java:1079)
         at com.sap.pcui_gp.isr.isrprocessevent.FcISRProcessEventInterface.callIsrProcessEvent(FcISRProcessEventInterface.java:125)
         at com.sap.pcui_gp.isr.isrprocessevent.wdp.InternalFcISRProcessEventInterface.callIsrProcessEvent(InternalFcISRProcessEventInterface.java:380)
         at com.sap.pcui_gp.isr.isrprocessevent.wdp.InternalFcISRProcessEventInterface$External.callIsrProcessEvent(InternalFcISRProcessEventInterface.java:504)
         at com.we.mss.rec.req.buttonsreview.VcCustomButtonsReview.onEvent(VcCustomButtonsReview.java:225)
         at com.we.mss.rec.req.buttonsreview.wdp.InternalVcCustomButtonsReview.onEvent(InternalVcCustomButtonsReview.java:192)
         at com.we.mss.rec.req.buttonsreview.VcCustomButtonsReviewInterface.onEvent(VcCustomButtonsReviewInterface.java:164)
         at com.we.mss.rec.req.buttonsreview.wdp.InternalVcCustomButtonsReviewInterface.onEvent(InternalVcCustomButtonsReviewInterface.java:148)
         at com.we.mss.rec.req.buttonsreview.wdp.InternalVcCustomButtonsReviewInterface$External.onEvent(InternalVcCustomButtonsReviewInterface.java:228)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:439)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:354)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.access$1300(FPMComponent.java:71)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.raiseSaveEvent(FPMComponent.java:805)
         at com.we.mss.rec.req.buttonsreview.VcCustomButtonsReview.submitForm(VcCustomButtonsReview.java:205)
         at com.we.mss.rec.req.buttonsreview.wdp.InternalVcCustomButtonsReview.submitForm(InternalVcCustomButtonsReview.java:184)
         at com.we.mss.rec.req.buttonsreview.ButtonsReviewView.onActionSubmit(ButtonsReviewView.java:151)
         at com.we.mss.rec.req.buttonsreview.wdp.InternalButtonsReviewView.wdInvokeEventHandler(InternalButtonsReviewView.java:159)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)<b></b></b>

    We have enabled the looging and here is the log trace
    <b>#1.5#0016356AB5FA006F0000008D00001D5C000430826F70B48E#1179236680474#System.err#sap.com/tckw_tc#System.err#Guest#2####6de0e3d002ea11dc81050016356ab5fa#SAPEngine_Application_Thread[impl:3]_3##0#0#Error##Plain###May 15, 2007 8:44:40 AM      com.sap.kw.framework.FrontController [SAPEngine_Application_Thread[impl:3]_3] Path: Caught java.lang.RuntimeException: FATAL ERROR: Could not load E:
    usr
    sap
    ADS
    JC01
    j2ee
    cluster
    server0
    apps
    sap.com
    tckw_tc
    servlet_jsp
    SAPIKS2
    root
    WEB-INF
    ApplConfig.xml
         at com.sap.kw.framework.XMLConfiguration.<init>(XMLConfiguration.java:52)
         at com.sap.kw.actions.ApplConfig.init(ApplConfig.java:83)
         at com.sap.kw.framework.FrontController.init(FrontController.java:197)
         at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)
         at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
         at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: java.io.FileNotFoundException: E:
    usr
    sap
    ADS
    JC01
    j2ee
    cluster
    server0
    apps
    sap.com
    tc~kw_tc
    servlet_jsp
    SAPIKS2
    root
    WEB-INF
    ApplConfig.xml (The system cannot find the file specified)
         at java.io.FileInputStream.open(Native Method)
         at java.io.FileInputStream.<init>(FileInputStream.java:106)
         at java.io.FileInputStream.<init>(FileInputStream.java:66)
         at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:69)
         at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:156)
         at java.net.URL.openStream(URL.java:913)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:201)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:263)
         at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
         at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
         at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
         at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
         at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:151)
         at com.sap.kw.framework.XMLConfiguration.<init>(XMLConfiguration.java:49)
         ... 9 more</b>

  • Java iview Runtime error in Portal Logon

    hi
    I login portal with
    http://<ipaddress>:50000/irj/portal
    Java iView Runtime
    An exception occured while processing your request.
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
    If this situation persists, please contact your system administrator.
    Can any one help me,,,how to sort this error.
    Regards
    sushma

    Hi Sushma,
    It seems that there are problems with permissions in Security Zones.
    Check this links below to know more:
    http://help.sap.com/saphelp_nw04/helpdata/en/25/85de55a94c4b5fa7a2d74e8ed201b0/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/ee/acd8403e37762ae10000000a155106/content.htm
    Thanks
    Mihir

  • Java Iview Runtime error after logon

    Hello,
    we are facing some problem regarding our EP 7.0 SP13. We have an anonymous page as our home page, with some anonymous ivews, like "help", "news", etc and one iview with authentication set to default where users log into the portal and access to the private section of the portal.
    That ivew does a redirection to /irj/portal and since the user is athenticated it will led him to the private home. The problem is that after logon, a Java iview runtime error appears, and users must refresh the browser to access the private section. (user is logged before the error appears).
    We have checked this is not happening with users with "super admin" o "content admin" role. They are able to log into the portal, and redirection is working fine. So we think there can be some problem with security zones or authentication somewhere in the portal, but since this is the standard logon component i don´t know why is this not working.
    We have checked that the redirection is working, and we have made some tests with different kind of iviews like KM iviews, URL iviews, pictures, etc. Only admin users are able to log in correctly, the others get the java iview runtime error, so we think the problem is with to standard logon...
    Here goes a trace of our problem (defaultrace.trc):
    #1.5 #000802B3F434005C00000434000024680004646E64997E00#1236325203820#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection#
    #1.5 #000802B3F434005C00000435000024680004646E64998C55#1236325203820#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:304)#
    #1.5 #000802B3F434005C00000436000024680004646E64998E05#1236325203820#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)#
    #1.5 #000802B3F434005C00000437000024680004646E6499900A#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5 #000802B3F434005C00000438000024680004646E64999183#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)#
    #1.5 #000802B3F434005C00000439000024680004646E649992D1#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    #1.5 #000802B3F434005C0000043A000024680004646E6499941A#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)#
    #1.5 #000802B3F434005C0000043B000024680004646E6499955B#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    #1.5 #000802B3F434005C0000043C000024680004646E64999690#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)#
    #1.5 #000802B3F434005C0000043D000024680004646E6499984F#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)#
    #1.5 #000802B3F434005C0000043E000024680004646E6499999C#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)#
    #1.5 #000802B3F434005C0000043F000024680004646E64999AEB#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)#
    #1.5 #000802B3F434005C00000440000024680004646E64999C2F#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)#
    #1.5 #000802B3F434005C00000441000024680004646E64999D76#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)#
    #1.5 #000802B3F434005C00000442000024680004646E64999EDA#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)#
    #1.5 #000802B3F434005C00000443000024680004646E6499A01D#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)#
    #1.5 #000802B3F434005C00000444000024680004646E6499A15E#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)#
    #1.5 #000802B3F434005C00000445000024680004646E6499A30A#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)#
    #1.5 #000802B3F434005C00000446000024680004646E6499A479#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
    #1.5 #000802B3F434005C00000447000024680004646E6499A5B7#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5 #000802B3F434005C00000448000024680004646E6499A718#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
    #1.5 #000802B3F434005C00000449000024680004646E6499A855#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
    #1.5 #000802B3F434005C0000044A000024680004646E6499B6CC#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: PortalRuntimeException#
    #1.5 #000802B3F434005C0000044B000024680004646E6499B86B#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:284)#
    #1.5 #000802B3F434005C0000044C000024680004646E6499BA7E#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     ... 20 more#
    #1.5 #000802B3F434005C0000044D000024680004646E6499CB8B#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.core.PortalRequestManagerException: PortalRuntimeException#
    #1.5 #000802B3F434005C0000044E000024680004646E6499CD54#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:143)#
    #1.5 #000802B3F434005C0000044F000024680004646E6499CE9B#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#
    #1.5 #000802B3F434005C00000450000024680004646E6499CFDD#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)#
    #1.5 #000802B3F434005C00000451000024680004646E6499D130#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ContentExceptionHandler.handleException(ContentExceptionHandler.java:100)#
    #1.5 #000802B3F434005C00000452000024680004646E6499D277#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ContentExceptionHandler.handlePortalRuntimeException(ContentExceptionHandler.java:27)#
    #1.5 #000802B3F434005C00000453000024680004646E6499D512#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.handleRequestException(PortalRequestManager.java:917)#
    #1.5 #000802B3F434005C00000454000024680004646E6499D677#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:803)#
    #1.5 #000802B3F434005C00000455000024680004646E6499D7F3#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)#
    #1.5 #000802B3F434005C00000456000024680004646E6499D943#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     ... 20 more#
    #1.5 #000802B3F434005C00000457000024680004646E6499EB58#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###Caused by: java.lang.UnsupportedOperationException: this implementation does not support getComponentContext()#
    #1.5 #000802B3F434005C00000458000024680004646E6499ECFD#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.service.hook.RedirectNode.getComponentContext(RedirectNode.java:50)#
    #1.5 #000802B3F434005C00000459000024680004646E6499EE40#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:343)#
    #1.5 #000802B3F434005C0000045A000024680004646E6499EF97#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:238)#
    #1.5 #000802B3F434005C0000045B000024680004646E6499F0E1#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#
    #1.5 #000802B3F434005C0000045C000024680004646E6499F21D#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     ... 27 more#
    can anyone help us with this problem?
    Thanks in advance

    The problem was solved, it was a permission problem.
    The anonymous role which allow access to the anonymous section of the portal was assigned to anonymous user, but it hasn´t everyone permission. So anonymous users were able to see anonymous pages, but when they login they lose the role, and java iview error happened, unless they had admin rights.
    Solved assigned by assigning everyone to that role.
    Thanks

  • Connectivity between "SAP Connector and Java Iview".

    hi Experts,
    I have written a Java iview, and trying to connect r/3 by the java Iview, i am not able to track where i am goin wrong ?? Please help.
    Is there anyway to check whether the connectivity is been established or not.I am really confused.
    Code is :-
    package com.rr.ess.DynPage;
    import com.sapportals.connector.connection.IConnection;
    import com.sapportals.connector.execution.functions.IInteraction;
    import com.sapportals.connector.execution.functions.IInteractionSpec;
    import com.sapportals.connector.metadata.functions.IFunction;
    import com.sapportals.connector.metadata.functions.IFunctionsMetaData;
    import com.sapportals.htmlb.Button;
    import com.sapportals.htmlb.Form;
    import com.sapportals.htmlb.GridLayout;
    import com.sapportals.htmlb.Image;
    import com.sapportals.htmlb.InputField;
    import com.sapportals.htmlb.TextView;
    import com.sapportals.htmlb.Tray;
    import com.sapportals.htmlb.enum.InputFieldDesign;
    import com.sapportals.htmlb.enum.TrayDesign;
    import com.sapportals.htmlb.event.Event;
    import com.sapportals.htmlb.page.DynPage;
    import com.sapportals.htmlb.page.PageException;
    import com.sapportals.portal.htmlb.page.PageProcessorComponent;
    import com.sapportals.portal.ivs.cg.ConnectionProperties;
    import com.sapportals.portal.ivs.cg.IConnectorGatewayService;
    import com.sapportals.portal.ivs.cg.IConnectorService;
    import com.sapportals.portal.prt.component.IPortalComponentProfile;
    import com.sapportals.portal.prt.component.IPortalComponentRequest;
    import com.sapportals.portal.prt.resource.IResource;
    import com.sapportals.portal.prt.runtime.PortalRuntime;
    import com.sun.corba.se.spi.legacy.connection.Connection;
    import javax.resource.cci.MappedRecord;
    import javax.resource.cci.RecordFactory;
    public class TestDynPage extends PageProcessorComponent {
      public DynPage getPage() {
         return new TestDynPageDynPage();
      public static class TestDynPageDynPage extends DynPage {
          Tray mytray;             
          Image Logo;
          InputField myinputfield;
          Button mybutton;
          Button defaultbutton;
          TextView text;
          GridLayout mygrid;
          String message;
          String Str = new String();
          * Initialization code executed once per user.
         public void doInitialization() {
              IPortalComponentRequest request = (IPortalComponentRequest) this.getRequest();
              IPortalComponentProfile profile = request.getComponentContext().getProfile();
              this.message = profile.getProperty("mymessage");
              if(this.message=="")
                   this.message = profile.getProperty("defaultmessage");         
          * Input handling code. In general called the first time with the second page request from the user.
         public void doProcessAfterInput() throws PageException {
         IPortalComponentRequest request = (IPortalComponentRequest) this.getRequest();
         IPortalComponentProfile profile = request.getComponentContext().getProfile();     
         InputField myinput = (InputField)getComponentByName("input");
         if(myinput != null)
              message = myinput .getValueAsDataType().toString();
         try{
              getConnection(request,"P35");
         catch(Exception e)
         public IConnection getConnection(IPortalComponentRequest request,String alias)
                        throws Exception {
                   IConnectorGatewayService cgService =
                   (IConnectorGatewayService) PortalRuntime.getRuntimeResources().getService(IConnectorService.KEY);
                   ConnectionProperties prop =     new ConnectionProperties(request.getLocale(),request.getUser());
                   IConnection connection = cgService.getConnection("P35",request);      
                   getSAPdata(connection);                              
                        return cgService.getConnection("P35", prop);                    
         public void getSAPdata(IConnection client) throws Exception {
                        /* Start Interaction * */
              try{          
                   IInteraction ix = client.createInteractionEx();
                                  IInteractionSpec ixspec = ix.getInteractionSpec();               
                                  ixspec.setPropertyValue("Name", "HRMSS_RFC_EP_READ_PHOTO_URI");
    //                              Create IFunction instance
                                  IFunctionsMetaData functionsMetaData = client.getFunctionsMetaData();
                                  IFunction function = functionsMetaData.getFunction("HRMSS_RFC_EP_READ_PHOTO_URI");
    //                              CCI api only has one datatype: Record     
                                  RecordFactory recordFactory = ix.getRecordFactory();
                                  MappedRecord importParams      = recordFactory.createMappedRecord("CONTAINER_OF_IMPORT_PARAMS");
    //                              Set scalar values
                                  importParams.put("PERNR", "1012");
    //                              Get scalar values               
                                  System.out.println("Invoking... " + function.getName());
                                  MappedRecord exportParams = (MappedRecord) ix.execute(ixspec, importParams);
                                  String scalar = (String)exportParams.get("URI");
                                  Str = scalar;     
                finally {
                   if (client != null) {
                        try {
                        client.close();
                        //("* Iview: Closing connection ok.");
                        client = null;
                              } catch (Exception e) {
                          //     logMsg("* Iview: Error closing connection.");
          * Create output. Called once per request.
         public void onPersonalise(Event event) throws PageException
         IPortalComponentRequest request = (IPortalComponentRequest)this.getRequest();
         IPortalComponentProfile profile = request.getComponentContext().getProfile();
         profile.setProperty("mymessage",this.message);
         profile.store();
         public void onDefault(Event event) throws PageException
              IPortalComponentRequest request = (IPortalComponentRequest)this.getRequest();
              IPortalComponentProfile profile = request.getComponentContext().getProfile();
              this.message = profile.getProperty("defaultmessage");
              profile.setProperty("mymessage","");
              profile.store();
         public void doProcessBeforeOutput() throws PageException {    
           // create your GUI here....
           IPortalComponentRequest  req= (IPortalComponentRequest)getRequest();
           //IResource rs = req.getResource(IResource.IMAGE,"images/CAR1.jpg");
           IResource rs = req.getResource(IResource.IMAGE,Str);
           Logo = new Image(rs.getResourceInformation().getURL(req),"Logo");
           Form myForm = this.getForm(); // get the form from DynPage      
           myinputfield = new InputField("Input");
           myinputfield.setDesign(InputFieldDesign.STANDARD);
           mybutton = new Button("mybutton");
           mybutton.setText("Personlise");
           mybutton.setOnClick("Personalise");
           defaultbutton = new Button("Default");
           defaultbutton.setText("Default");
           defaultbutton.setOnClick("Default");
           text = new TextView("fgfdg"+Str);
           mytray = new Tray();
           mytray.setDesign(TrayDesign.BORDER);
           //mytray.addComponent(Logo);
           form.addComponent(Logo);
           mygrid = new GridLayout(3,2);
           mygrid.setCellPadding(2);
           mygrid.addComponent(1,1,myinputfield);
           mygrid.addComponent(2,1,mybutton);
           mygrid.addComponent(3,1,defaultbutton);
           mygrid.addComponent(3,2,text);
           mytray.addComponent(mygrid);
           myForm.addComponent(mytray); 
    Points would be awarded to helpful answers.
    Regards,
    Sanjyoti.

    hi Prashant,
    Thanks for your reply.
    I am able to see the Iview with all the components(textfield,buttons).
    But the image is not displayed. and I am not able to check whether the connectivity is been established.
    in this part of code
    text = new TextView("fgfdg"+Str);
    I am assigning the value of "Str", which i get from R/3 to "text",
    but in the iview the value of "Str" is not displayed.
    Regards,
    Sanjyoti

  • F4 / Help Functionality for input field in custom java iView

    Hi,
    As we see many F4 help on each input field in a transaction, how can we mimic the same functionality in a Custom Java iView. For example, ME23N, you can search a PO based on some criteria, when i create a new custom java iview using BAPI_PO_DISPLAY, how can provide that F4 or help functionality to the Purchase Order field.
    Your help is really appreciated.
    Thanks,
    Vijay

    Hi Vijay,
    the F4 Help functionality is always of big concern when you're switching from a R/3 or ABAP-SAP GUI environment to a webfront end. First of all: the convinience you're used to of creating a seach help and adding it to your data fields is gone, i.e. the current development status in the portal/java/webdynpro implies that you have to do most of the work on your own. Simple value helps might not be a problem, but complex ones are (as the one you've described). Here is a link to a tutorial in Java-webdynpro, maybe it gives you an idea:
    https://www.sdn.sap.com/sdn/developerareas/webdynpro.sdn?page=TutWD9_OVS.htm
    Regards,
    Ulli

  • Java Iview runtime after patch SPS11 for the logon page

    Hi Everybody,
    I have a big problem. I have upgrade my portal from SPS06 to SPS11 with JSPM and now when i try to open the logon page of the portal, i have this message :
    Java iView Runtime
    Version : 7.00.200702010738
    + Copyright 2002 SAP AG. All rights reserved.
    An exception occured while processing your request.
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
    com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:304)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         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:160)
         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:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: PortalRuntimeException
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:284)
         ... 24 more
    Caused by: java.lang.AbstractMethodError: com.sapportals.portal.prt.service.laf.LAFService.getRelativeThemePartURL(Lcom/sapportals/portal/prt/component/IPortalComponentRequest;Ljava/lang/String;)Ljava/lang/String;
         at com.sapportals.portal.htmlb.HTMLBService.onHeadTagBegin(HTMLBService.java:145)
         at com.sapportals.portal.htmlb.HTMLBService.doDocumentHook(HTMLBService.java:133)
         at com.sapportals.portal.prt.service.document.DocumentHookMulticaster.doDocumentHook(DocumentHookMulticaster.java:111)
         at com.sapportals.portal.prt.service.document.DocumentHookMulticaster.doDocumentHook(DocumentHookMulticaster.java:111)
         at com.sapportals.portal.prt.service.document.DocumentHookService.doDocumentHook(DocumentHookService.java:133)
         at com.sapportals.portal.prt.service.document.DocumentHookServiceNew.doDocumentHook(DocumentHookServiceNew.java:289)
         at com.sapportals.portal.prt.connection.PortalHook.doDocumentHook(PortalHook.java:824)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:795)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         ... 24 more
    If this situation persists, please contact your system administrator.
    Somebody could help me please?

    Hi,
    I think the problem is with memory configurations.
    please refer note : 723909 and change the respective configurations in config tool.
    Then save  and restart your system .it will work.
    Do reward points if useful.
    Regards,
    Srujana.

  • Portal Eventing between WDP Java iView & non-WDP iView

    Dear Experts,
    I have 1 Web DynPro Java iView and 1 non-Web DynPro (using JSPDynPage and JSP) iView, both attached to a page. When Web DynPro Java iView fire a portal raise event, the portal iView did not execute the javascript function tied to the event subscribed.
    Here is the code snippet which reside in the Web DynPro Java iView that is used to fire the event
    String param = "test";
    WPortalEventing.fire("urn:com.company.Test1", "TestEvent", param);
    This the code snippet that is in the jsp page
    function notifyTest(param){ 
          // code to print param value is here
    EPCM.subscribeEvent("urn:com.company.Test1", "TestEvent", notifyTest);
    Note:
    1. When Web DynPro Java iView fire the portal event the entire page is refreshed, including the non-WDP iView.
    2. When EPCM is replaced with window.top.EPCM, the page is refreshed, it is totally hanged with progress bar.
    Can anyone help to solve this problem?
    Edited by: CloudSOmnislash on Apr 8, 2009 6:06 PM

    Kumar, Rui,
    I have all my code inside a web dynpro component. All that I have in dynpro to work with (or that's what I know so far) is a WDPortalEventing object that I can use to access the fire, subscribeEvent and unsubscribeEvent methods. I still haven't found a way to get to the actual EPCM object that the Portal runtime gives you through javascript. And even if I get there, how am I supposed to write javascript in my dynpro code and later pass the value stored in the client data bag to the web dynpro context ?
    Simon,
    I had tried a small app yesterday and it didn't work when the iViews were not assigned to the same page. I will see if I can change my code anymore and get it working. I will make fresh posts to this thread as and when I find anything that works. In the mean time, if you have webdynpro iViews that talk to each other across pages, do let me know how you are doing it!
    Thanks for your replies...
    - Navneet.

  • Portal Eventing between Web DynPro Java iView and non-Web DynPro iView

    Dear Experts,
    I have 1 Web DynPro Java iView and 1 non-Web DynPro (using JSPDynPage and JSP) iView, both attached to a page. When Web DynPro Java iView fire a portal raise event, the portal iView did not execute the javascript function tied to the event subscribed.
    Here is the code snippet which reside in the Web DynPro Java iView that is used to fire the event
    String param = "test";
    WPortalEventing.fire("urn:com.company.Test1", "TestEvent", param);
    This the code snippet that is in the jsp page
    function notifyTest(param)
         // Code to print param value here
    EPCM.subscribeEvent("urn:com.company.Test1", "TestEvent", notifyTest);
    Note:
    1. When Web DynPro Java iView fire the portal event the entire page is refreshed, including the non-WDP iView.
    2. When EPCM is replaced with window.top.EPCM, the page is refreshed, it is totally hanged with progress bar.
    Can anyone help to solve this problem?

    hi
    Please write the below code snippet in ur jsp for notifyTestjavascriptfunction
    function notifyTest( eventObj ) {
         eventParameter=eventObj.dataObject;
         // code to print the parameter "eventParameter"
    Thanks
    Harsimran

  • Need Information on ISR forms

    Hi All,
    I came across ISR forms in my organisation and need to give a short presenstaion on it.. Can any one let me know what is it and what are its advantages and dis advantages.. Is SAP still support these forms? Are they replaced by EP? Need your suggestions.
    Thanks
    Rajeev

    Pavan,
      Use two different Webdynpro views and define outbound and inbound plug between these two and share the session data with the component controller. Once the user submits the data validate it with the back end and if it is validated call fire the outbound plug and your second view would display the new adobe form. Hope this would solve your problem. I have designed few applications as I described above. If it doesn't work for you please let me know.
    Thanks!
    Surya.

  • Java iView Runtime error when try connectin to portal

    H, iin my VC i have filled in the address of my portal http://address:50000
    Then i click the traffic light icon, and giving me a popup
    windows that saying Java iView Runtime
    I wonder what could be wrong, i have deployed the portal content and visual composer sda.
    And i'm using super user

    In fact we're not quite sure on what exactly caused the problem ...
    What we did was :
    - deploy from NWDS of Webdynpros ... but we don't see how an apllication deployment may has caused a such big issue
    - we also enabled 2 services in the portal : Activity Reporting service and Activity data Collector ... may enabling these 2 services have cause this global issue ?
    Thanks for your quick response,
    Regards,

  • ISR Form is hanging after converting to ZCI

    Hi experts,
    We are on EP7 ECC 6.0 SP9. We have recently converted few ISR forms (SAP delivered forms for PCR) to ZCI. The form is hanging when clicked on 'Review Form' . Earlier before changing the forms to ZCI at least we used to go to the next screen when clicked on 'Review Form' but now the form is just hanging.
    Did anyone come across this issue?
    Can you please let me know what needs to be done?
    Thanks
    Phani

    Hi Anto,
    I have already installed ACF on my pc but still the Adobe form is hanging. I even changed installed new version of Adobe reader 8.0 (earlier it was 7.0.9) but same result.
    We are currently on EP7 ECC 6.0 SP9. I have adobe reader 7.0.9 version.
    When I revert back the SAP Standard SAP form to 'unknown layout' I could at least go to the next step but when I covert to ZCI, I am facing this problem. Right now I really don't understand the reason .. I am stuck with this.
    Do you have any ideas?
    Thanks
    Phani

Maybe you are looking for

  • Ipod mini not playing songs

    Help Have had Ipod mini for 18 months and since downloading latest ipod software it is being v temperamental! If you choose an album to play it will start then immediately skip through all songs to end and go back to menu. This is happening on existi

  • Polygonal lasso not working in PS 2014 with OS X 10.10

    The polygonal lasso is not working when using Photoshop CC 2014 with the new Mac OS X 10.10 Beta. Anyone else notice this problem? It still works fine in regular Photoshop CC.

  • Error while parsing AS2 message: AUTHENTICATION_ERROR #

    Hi Experts,   While a Trdae Partner is trying to send a file through AS2 Seeburger, we are getting this error, "Error while parsing AS2 message: AUTHENTICATION_ERROR # " in Seeburger tool and could not able to receive the file from the Trade Partner.

  • Help setting up small home network with PC and an imac!!!?

    I have an imac in my room, and my mother has a JP PC in her room across the house. We have a router and modem on her computer(I connect to the internet through the router signal) I just recently bought a new printer. It is a wifi printer. I was told

  • ITunes won't join CD tracks

    I am using iTunes 10.1.1.4. I have previously been able to join tracks of audiobook CDs but all of a sudden, the option to join CD tracks is constantly greyed out. anybody know why this is happening, or do I have to reinstall iTunes?