Are EP5 Java iViews Supported on EP7?

Hi,
Can anyone tell me whether our Java iViews, some of which are still in EP5 format Eclipse projects, are still supported and will run without modification on EP7?
If not, do we need to import them in NWDS for EP6, and then from NWDS for EP6 to NWDS for EP7?
Or can we import EP5 PARs directly into EP7 NWDS?
Cheers,
Steve

Hello Steve,
Ofcourse it is always recommanded to import EP5 project to corresponding NWDS (EP6/7) and compile the sources against the target EP-Version(EP6/7) .
This ensures that all classes you are using are still available on the target system.
So if your target system is EP7 then you need not check with NWDS EP6, you can directly import into NWDS EP7 and then add the EP7 sources to compile.
I am sure you will see some classes/methods depricated or missing!!
Greetings,
Praveen Gudapati
p.s. Points are always welcome for helpful answers

Similar Messages

  • What are the Java iView 'Help' possibilities?

    Hi all,
    Currently we are investigating what the possibilities are of the 'Help' option for iViews.
    If I understand correctly, you can have only one help link included in the context menu.
    However, according to common UI preconceptions, it would make more sense to have a separate Help icon, instead of having it as a menu item under the Options icon (ie. help is available right away, plus you immediatly see whether help is available or not)
    Regarding this I have two questions:
    Would it be possible to have a Help icon next to the Options icon in the iView tray?
    And if so, would it then be possible to have multiple links in a help dropdown if a user clicks that help icon?
    Any input is greatly appreciated!
    Thanks in advance,
    Robin van het Hof

    Not sure if it helps, but we are using the standard iView help link now that SAP have kindly re-instated the functionality in the next round of EP support packs (see OSS note 875858).  This method allows you to specify a URL to whatever help files you like in each iView.
    I agree with Michael that the standard iView help is a little hard for users to find when it's buried in the options menu.  To get around that issue we have created our own iView tray icon image in the universal yellow question mark style, and loaded it up with the portal theme editor.  I would show you what I meant if we could include images in SDN posts
    Regards,
    John

  • When Java 1.5 will be supported for EP7.0?

    Hi!
    We have 2 questions:
    1) When Java 1.5 will be supported for EP7.0?
    2) When will EP7.1 be released? And, EP7.1 would need Java 1.5?
    Thanks! Points!

    Hi,
    1) When Java 1.5 will be supported for EP7.0?
    >> Never. NW 7.0 uses NW Java AS 7.0 which is compatiple with Java 1.4 only
    2) When will EP7.1 be released? And, EP7.1 would need Java 1.5?
    >> currently NW CE 7.1 is released and a member of the NW 7.1 family. PI 7.1 is also released but full NW 7.1 will be announced at Q2 2008, but not sure when will ve GA. Ofcource this release will be the one which is fully compatiple with Java 1.5
    regards

  • 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

  • Java iView Runtime errorr when trying to connect on portal

    Hi experts,
    when we try to connect to our portal ( .../irj/portal ) ;
    we always get following error :
    " Java iView Runtime
    Copyright 2002 SAP AG. All rights reserved.
    An exception occured while processing your request.
    If this situation persists, please contact your system administrator. "
    We looked on others threads and SAPnotes, but as we are running on EP7 SP15 , none of them seem to be adapted ...
    The only interesting logs we found in defayltTrace.trc are :
    com.sapportals.portal.prt.dispatcher.DispatcherException: Could not find connection portal#
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:530)#
    at java.security.AccessController.doPrivileged(Native Method)#
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)#
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)#
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    at com.sap.engine.services.servlets_jsp.server.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:386)#
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)#
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)#
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)#
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)#
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)#
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)#
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)#
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
    at java.security.AccessController.doPrivileged(Native Method)#
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)#
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)#
    Do you have any idea on how we can resolve this issue ?
    Regards !

    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,

  • Java iview development

    Hi Friends
    I am very new to this area and directly starting with EP6.
    I have requirement to development java iviews(content) for EP6 ,but I am not getting a pointer how to develop it,if there is sample app available(java code) and how to develop with J2ee engine will be very useful to me.
    I looked at iviewstudio and there all the material deal with EP5 and tomcat but my requirement is for EP6 and there is nothing existing in SDN for EP6 content development, there are some presentations but they also talk about EP5.
    Can I develop java iview as content in NWDI and J2EE engine(EP6) directly or do I need to install tomcat.
    ANy sample code(tutorial) and a basic example with step by step procedure and also describing what all interfaces, portal classes I need to use to develop(EP6 + J2ee + NWdi) it.
    ANy help is highly appreciated.
    regards
    Rohit

    Hi All
    I downloaded pdk 6.0 SP6 and trying to install it in portal through SDM but it is giving following exception.
    ===========================================================================
    Deployment started Wed Oct 13 22:48:21 IST 2004
    ===========================================================================
    Starting Deployment of com.sap.pct.pdk.pct.epa
    Aborted: development component 'com.sap.pct.pdk.pct.epa'/'sap.com'/'SAP AG'/'630.20040715121826.0000':
    Caught exception during module deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/com.sap.pct.pdk.pct.epa.. Reason: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception while deploying: java.lang.NullPointerException', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception while deploying: java.lang.NullPointerException; nested exception is:      com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception while deploying: java.lang.NullPointerException', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception while deploying: java.lang.NullPointerException
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineSingleModuleOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment of com.sap.pct.pdk.pct.epa finished with Error (Duration 4837 ms)
    =========================================================
    Has anybody experienced this.
    ANy pointers will be helpful.
    regards
    Rohit

  • Java-iViews-Errors in BP for CRM

    After importing BP 6.0 for CRM 4.0, the Java iViews (e.g. Today's Activities or My Tasks) don't work. Instead we get an error like this:
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : N/A
    Component Name : N/A
    com/sap/pct/crm/generics/context/CRMContextException.
    Exception id: 08:52_11/10/04_0004
    See the details for the exception ID in the log file
    The WAS and ITS iViews of the BP are running fine and the import log of the BP says the iViews are correctly installed.
    Is there something wrong with the JCO?

    Hi Marko,
    I don't know the BP, but this exception clearly states that within the method <i>getPage</i> within the class <i>ListPortalComponent</i> a <i>CRMContextException</i> is referenced (probably should be thrown), which in fact does not exist within the classpath.
    <i>If</i> I would have the BP at hand (and you have, that's your advantage), just check if the class exists. If not, you could try a workaround and check the cause for the exception, if you achieve that it should not be thrown, the JVM won't complain...
    Is the BP delivered within one or within several PAR's? If it takes several PAR's, maybe <i>CRMContextException</i> is in one, <i>ListPortalComponent</i> in another PAR and no SharingReference could be set (but I wouldn't call this very probable for the common package <i>com/sap/pct/crm/generics</i>; nevertheless, it's an idea).
    Just try to analyze around this...
    Hope it helps
    Detlev
    PS: You didn't mark your question as question?!

  • Problem in creating iview template in EP7.0

    Hi,
    I getting the below message even after creating the iview template in EP7.0
    "No templates to display. You are not assigned to any existing templates."
    Created through:
    content Admin --> portal content --> <folder>new --> iview --> seleting "Portal component - create an iView from a portal component contained in a deployed portal archive (PAR file)" <next> --> seleting "com.sap.portal.appintegrator.sap" <next> --> webdynpro <next> --> finish.
    Open object for editing...--> Object is a Template to Yes.
    Result :
    content Admin --> portal content --> <folder>new --> iview --> seleting "iview template- create an iView from an existing iView template" <next> which displays the same message.
    "No templates to display. You are not assigned to any existing templates."
    Rgrds,
    Suri.

    Hi,
    do have the right permissions? You can check this using the Permission Editor (Applications, PCD)
    What role are you assigned to? Content Administrator? System Administrator or even Super Administrator?
    Doesthe same error occur when you're logged in as Super Administrator?
    br,
    Tobias

  • 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 at the time of logon

    Hi All
    i am getting the below error page instead of Portal log on Page.
    At the same time when i am connecting to the NWA it is opening successfully,
    There I am getting the login Page also.
    But when i am trying http://<Server>:50000/irj/portal.
    i am getting below error.
    Java iView Runtime
    Copyright 2002 SAP AG. All rights reserved.
    An exception occured while processing your request.
    If this situation persists, please contact your system administrator.
    I have not touch the portal logon Page.
    Neither i have modified any standard Portal page.
    Kindly help me with you valuable suggestion and document.
    It is effecting the business process of client.
    Prashant krishen

    Hi Robin,
    Thanks for immediate response.
      Please help me to find out the log.
    i am using this path :
    http://<Server>/irj/servlet/prt/portal/prtroot/com.sap.portal.runtime.admin.logviewer.defau
    But here in the default trace there are so many default trace file like
    defaultTrace.0.trc ;
    defaultTrace.1.trc ;
    defaultTrace.2.trc ;
    defaultTrace.3.trc
    defaultTrace.4.trc ;
    defaultTrace.5.trc ; 
    in all the file date has not been maintained. That is why i am not able to send you the exact log .
    kindly help me to find the log .
    thanx in Advance.

  • Java iview htmlb & jco question

    hello all,
    I am writing an Java iView to pull some data from an
    R/3 table & displaying that as a LINE chart.
    I've already got the portion of getting data from R/3
    by creating a shim function that returns the table.
    Now i want to display that using htmlb.Chart
    I can seet the JCO.Table as my JCOChartModel easily enough
    however the Table returns to me multiple rows
    (data that will be used elsewhere) but there are only
    two rows i want to use as the source for the Chart.
    Is there any way to limit the Chart to those two rows
    or do i need to (in my opinion wastefully) create
    a Vector and duplicate the data from those two
    rows to use for Chart?

    Hi Srivatsan,
    I need to write a java iview to pull some data from an R3 table.  But I dont know how :S
    I did something with jco in EP 5, but now with EP 6 I'm confused with the term JCA. 
    What do you do to connect to R3 ?  Could you share your code ?
    Thanks and regards from Mexico !!!
    Diego

  • 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

  • Unable to expand the dropdown in the Webdynpro Java iview in Portal

    Dear Experts,
    We have a lot of Webdynpro java application iview in portal in production system.All the dropdowns present in those iviews are not expanding in production system.
    But we are able to expand & select the same webdynpro java iview applications in Quality system.
    We are using Internet Explorer for viewing the iviews.
    Can anyone help me to provide a solution to the issue.
    Regards,
    Krishna Balaji T

    Hi Micheal,
    The issue had been solved by myself.
    Regards,
    Krishna Balaji T

  • API - method for Webdynpro Java iview functionality of Print

    I know.. you would love to post me with n different blogs and forums discussion about how to print from webdynpro java application.
    But lets read before what i am looking for..
    There is standard "Print" function available on webdynpro for java iview.. and layout and all its just fine for us. though we want to trigger this event from a screen button. as going to iview properties is very user friendly.
    I was looking for some iview api which can help me.. We are on NW 7.01 SP6 at the moment. And this is for standard ESS applications.
    Thanks a lot for your inputs.
    Regards,
    Sudhir

    Hi
    You can write Java program for printing. Call the java class from screen (button or Url). Also you can write the content to XMl file.open the xml file in action. so that u will get print preview and print option.

  • Accessing Webdynpro Java iview functionality for print from webdynpro code

    I know.. you would love to post me with n different blogs and forums discussion about how to print from webdynpro java application.
    But lets read before what i am looking for..
    There is standard "Print" function available on webdynpro for java iview.. and layout and all its just fine for us. though we want to trigger this event from a screen button. as going to iview properties is very user friendly.
    I was looking for some iview api which can help me.. We are on NW 7.01 SP6 at the moment. And this is for standard ESS applications.
    Thanks a lot for your inputs.
    Regards,
    Sudhir

    Hi
    You can write Java program for printing. Call the java class from screen (button or Url). Also you can write the content to XMl file.open the xml file in action. so that u will get print preview and print option.

Maybe you are looking for