JSR 168 consumer vs iPlanet 4.1

Hi,
Does anyone have experience with implementation of JSR 168 consumer in iPlanet 4.1? Is it supported by Plumtree?
Thanks
Tomas

Similar Messages

JSR-168 Consumer question

Hi,
I am new to plumtree portal but have used some other JSR-168 compliant portals such as exo and websphere. I want to reuse some of the portlets I created in plumtree portal. It seems installing the JSR-168 consumer on the portal server and remote server is a good way to achieve that.
Are there any concerns with installing the JSR-168 consumer on the portal server side? Any performance pennalties, compatibility issue etc? I am going to bring this up to our portal admin once I can get more information regarding it here.
Thanks
-Chengmin

test
<chengmin ding> wrote in message news:[email protected]..
Hi,
I am new to plumtree portal but have used some other JSR-168 compliant
portals such as exo and websphere. I want to reuse some of the portlets I
created in plumtree portal. It seems installing the JSR-168 consumer on
the portal server and remote server is a good way to achieve that.
Are there any concerns with installing the JSR-168 consumer on the portal
server side? Any performance pennalties, compatibility issue etc? I am
going to bring this up to our portal admin once I can get more information
regarding it here.
Thanks
-Chengmin

Consuming web services in a jsr 168 portlet best practices.

I am building portlets (jsr 168 api in Websphere Portal 6.0 using web service client of Rational). Now needed some suggestions on caching the web services data on the portlet. We have a number of portlets (somewhere around 4 or 5) on a portal page which basically rely on a single wsdl Lotus Domino Web Service.
Is there a way I can cache the data returned by webservice so that I dont make repeated calls to the webservice on every portlet request. Any best practices/ideas on how I could do avoid multiple web service calls would be appreciated ?

Interestingly, as it often happens with Oracle portal, this has started working without me doing anything special.
However, the session events my listener gets notified of are (logically, as this portlet works via WSRP) different from user sessions. The problem I'm trying to solve now is that logging off (in SSO) doesn't lead to those sessions being destroyed. They only get destroyed after timeout specified in my web.xml (<session-config><session-timeout>30</session-timeout></session-config>). On the other hand, when they do expire, the SSO session may still be active, in which case the user gets presented with the infamous "could not get markup" error message. The latter is unacceptable in our case, so we had to set session-timeout to a pretty high value.
So the question is, how can we track when the user logs off. We have found the portal.wwctx_sso_session$ and portal.WWLOG_ACTIVITY_LOG1$ (and ...2$) tables, but no documentation for them. However, the real problem with using those tables is that there's no way we could think of to match the portlet sessions with SSO sessions/actions listed in the tables. (Consider situation when someone logs in from two PCs.)
Any ideas?

Remote Inter Portlet Communication for JSR 168

Hi All,
We are stuck in a big problem using JSR 168 as remote portlets. We will be relieved if someone can suggest few ideas on this. I will provide the scenario which we are trying now.
We have two portlets namely portlet A and portlet B which are Java(JSR 168) type portlets. These two portlets are offered as remote and they reside in the producer application. We have consumed these two portlets in our consumer application.
The portlet A is triggering an event and portlet B is listening to the event triggered by portlet A. Currently we are trying to implement this functionality using Ajax. We tried to use customEventUrl tag in our jsp belonging to portlet A and we finally figured out that customEventUrl will not work in Remote portlets. We are not sure as how to pass the information from remote portlet A to remote portlet B. Please let us know your thoughts about this as whether the implementation is really possible when using Remote portlets.
IMPORTANT NOTE: The event handling and the configuration code that we have made in the above scenario is working perfectly for non-remote java portlets. The problem is occurring only when we consume them in the consumer application.
Thanks
Vijay

Hello Ashwin,
What version of WebLogic Portal are you using? And is this the same for both the consumer and producer?
If you are using WLP 10.3.2 I would highly recommend using JSR286 portlets (the next version of the Java Portlet (JSR168) specification) and the JSR286-standard eventing. The JSR286 eventing model is actually much cleaner and easier to understand than the WLP-proprietary support for events in JSR168 portlets.
However, if you are using a version of WLP prior to 10.3.2 and can't upgrade, JSR168-style events are your only choice. I can give you examples, but they all look very similar to the examples in the online documentation.
When events work between portlets locally, but not over WSRP, the usual problems are:
- There is one or more of "onlyIfDisplayed", "sourceDefinitionLabels" or "sourceInstanceLabels" attributes declared on the handle*Event element in the .portlet file. These attributes restrict when the portlet should receive an event, and they usually don't work the way you think when running over WSRP. It is best to not use these attributes for portlets which are going to be used over WSRP.
- A payload is being sent with the event which is not actually serializable. If serialization of the event payload (which is required for versions of WLP prior to 10.3.2 for WSRP) fails, the event will not be delivered to the portlet.
- The producer may be configured to not accept events. Check your producer's WEB-INF/wsrp-producer-config.xml file; the "service-config" element should either not have an "offer-extensions" attribute, or this attribute's value should be "true".
- The events may be getting sent during a portlet lifecycle other than processAction or handleEvent. There is no way for WSRP to handle events which have been sent during preRender or render, so it simply doesn't work.
- In the case of JSR168 portlets, if you have a backing file on the portlet (in addition to the portlet implementation as well), that may not work in some circumstances over WSRP. It is best to have the event handlers be in the portlet implementation class and avoid the use of backing files for JSR168 portlets.
If none of those things help you, my suggestion would be to post a sample .portlet file for one of the portlets that is supposed to be receiving the event, as well as the method signature in that portlet's implementation class that is supposed to be receiving the event, and the code which is sending the event that is supposed to be received.
Kevin

JSR-168 and Request Parameters

Hi!
I'm creating a portlet application; right now it only has one portlet in it. The landing page for my portlet (view mode) has the following form code:
    <FORM action="<portlet:renderURL/>">
        I'm thinking of a number between 1 and 10.<BR><BR>
        <I>What is it?</I>
        <INPUT name="<portlet:namespace/>number" type="text" size="10" />
        <INPUT name="submit" type="submit" value="Guess!!" />
    </FORM>When I submit this form, I see the parameter in my browser's URL window prefixed with the portlet namespace:
   http://host:port/portal/page/portal/portalpage?__ns36_5643_36_1_1_number=3&submit=Guess%21%21Here is how I'm trying to get the "number" parameter in the Java class associated with this jsp:
            String number = (response.getNamespace()+"number");I have also tried with
            String number = response.getParameter("number");In both cases the variable number gets assigned the null value.
How can I capture parameters sent by a form on a JSP page on the portlet's Java class?
I am developing this portlet application with JDeveloper 10.1.3.3.0.4157 and deploying to Oracle Application Server 10.1.2.0.2 with a wsrp-compliant container. Portlet is consumed in Oracle Portal 10.1.4.
Thank you for your response.

I'm sorry; I typed it wrong:
It's
String number = request.getParameter("number");However, if you're referring to the namespace, then the way I have on my book (Portlet Programming, Effectively Using the JSR-168 Standard, by Cameron McKenzie) is really
(response.getNamespace()+"number")

Oracle Portal WSRP messing things up for Tapestry JSR-168 portlet?

I've been trying to consume a Tapestry JSR-168 portlet in Oracle Portal 10.1.4. However a very simple tapestry page is (already) failing. This page displays some boilerplate text and a form component including one text input item. Upon display the following stacktrace is shown:
06/03/03 14:42:58 webmodule: [id=3230371113264,1] EXCEPTION THROWN: Uncaught exception
org.apache.hivemind.ApplicationRuntimeException: Invalid URL "wsrp_rewrite?wsrp-urlType=blockingAction&wsrp-mode=wsrp%3Aview&wsrp-windowState=wsrp%3Anormal&wsrp-secureURL=false/wsrp_rewrite" [context:/WEB-INF/Home.page, line 5, column 59]
     at org.apache.tapestry.engine.RequestCycle.renderPage(RequestCycle.java:380)
     at org.apache.tapestry.portlet.PortletRendererImpl.renderPage(PortletRendererImpl.java:70)
     at $PortletRenderer_109c058b59f.renderPage($PortletRenderer_109c058b59f.java)
     at $PortletRenderer_109c058b59e.renderPage($PortletRenderer_109c058b59e.java)
     at org.apache.tapestry.portlet.PortletHomeService.service(PortletHomeService.java:80)
     at $IEngineService_109c058b58a.service($IEngineService_109c058b58a.java)
     at org.apache.tapestry.services.impl.EngineServiceInnerProxy.service(EngineServiceInnerProxy.java:77)
     at org.apache.tapestry.services.impl.EngineServiceOuterProxy.service(EngineServiceOuterProxy.java:66)
     at org.apache.tapestry.engine.AbstractEngine.service(AbstractEngine.java:248)
     at org.apache.tapestry.services.impl.InvokeEngineTerminator.service(InvokeEngineTerminator.java:60)
     at $WebRequestServicer_109c058b559.service($WebRequestServicer_109c058b559.java)
     at $WebRequestServicer_109c058b558.service($WebRequestServicer_109c058b558.java)
     at $WebRequestServicer_109c058b557.service($WebRequestServicer_109c058b557.java)
     at $WebRequestServicer_109c058b556.service($WebRequestServicer_109c058b556.java)
     at org.apache.tapestry.portlet.RenderRequestServicerToWebRequestServicerBridge.service(RenderRequestServicerToWebRequestServicerBridge.java:49)
     at $RenderRequestServicer_109c058b551.service($RenderRequestServicer_109c058b551.java)
     at $RenderRequestServicer_109c058b550.service($RenderRequestServicer_109c058b550.java)
     at $RenderRequestServicer_109c058b54b.service($RenderRequestServicer_109c058b54b.java)
     at $RenderRequestServicer_109c058b54a.service($RenderRequestServicer_109c058b54a.java)
     at org.apache.tapestry.portlet.ApplicationPortlet.render(ApplicationPortlet.java:161)
     at oracle.webdb.wsrp.server.Server.getMarkup(Unknown Source)
     at oracle.webdb.wsrp.WSRP_v1_Markup_PortType_Tie.invoke_getMarkup(WSRP_v1_Markup_PortType_Tie.java:98)
     at oracle.webdb.wsrp.WSRP_v1_Markup_PortType_Tie.processingHook(WSRP_v1_Markup_PortType_Tie.java:495)
     at com.sun.xml.rpc.server.StreamingHandler.handle(StreamingHandler.java:230)
     at com.sun.xml.rpc.server.http.ea.JAXRPCServletDelegate.doPost(JAXRPCServletDelegate.java:153)
     at com.sun.xml.rpc.server.http.JAXRPCServlet.doPost(JAXRPCServlet.java:69)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
     at oracle.webdb.wsrp.server.ContextFilter.doFilter(Unknown Source)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:285)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:126)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
Caused by: oracle.webdb.wsrp.server.ContainerIllegalArgumentException: Invalid URL "wsrp_rewrite?wsrp-urlType=blockingAction&wsrp-mode=wsrp%3Aview&wsrp-windowState=wsrp%3Anormal&wsrp-secureURL=false/wsrp_rewrite"
     at oracle.webdb.wsrp.server.PortletResponseImpl.encodeURL(Unknown Source)
     at oracle.webdb.wsrp.server.RenderResponseImpl.encodeURL(Unknown Source)
     at org.apache.tapestry.portlet.PortletWebResponse.encodeURL(PortletWebResponse.java:60)
     at $WebResponse_109c058b636.encodeURL($WebResponse_109c058b636.java)
     at $WebResponse_109c058b51e.encodeURL($WebResponse_109c058b51e.java)
     at org.apache.tapestry.engine.RequestCycle.encodeURL(RequestCycle.java:207)
     at $IRequestCycle_109c058b63f.encodeURL($IRequestCycle_109c058b63f.java)
     at $IRequestCycle_109c058b53a.encodeURL($IRequestCycle_109c058b53a.java)
     at org.apache.tapestry.portlet.PortletLink.getURL(PortletLink.java:68)
     at org.apache.tapestry.portlet.PortletLink.getURL(PortletLink.java:126)
     at org.apache.tapestry.form.FormSupportImpl.render(FormSupportImpl.java:490)
     at org.apache.tapestry.form.Form.renderComponent(Form.java:250)
     at org.apache.tapestry.AbstractComponent.render(AbstractComponent.java:617)
     at org.apache.tapestry.BaseComponent.renderComponent(BaseComponent.java:92)
     at org.apache.tapestry.AbstractComponent.render(AbstractComponent.java:617)
     at org.apache.tapestry.AbstractPage.renderPage(AbstractPage.java:275)
     at org.apache.tapestry.engine.RequestCycle.renderPage(RequestCycle.java:366)
     ... 36 more
06/03/03 14:42:58 webmodule: [id=3230371113264,1] WARNING: Unable to process client request: Invalid URL "wsrp_rewrite?wsrp-urlType=blockingAction&wsrp-mode=wsrp%3Aview&wsrp-windowState=wsrp%3Anormal&wsrp-secureURL=false/wsrp_rewrite"
org.apache.hivemind.ApplicationRuntimeException: Invalid URL "wsrp_rewrite?wsrp-urlType=blockingAction&wsrp-mode=wsrp%3Aview&wsrp-windowState=wsrp%3Anormal&wsrp-secureURL=false/wsrp_rewrite" [context:/WEB-INF/Home.page, line 5, column 59]
     at org.apache.tapestry.engine.RequestCycle.renderPage(RequestCycle.java:380)
     at org.apache.tapestry.portlet.PortletRendererImpl.renderPage(PortletRendererImpl.java:70)
     at $PortletRenderer_109c058b59f.renderPage($PortletRenderer_109c058b59f.java)
     at $PortletRenderer_109c058b59e.renderPage($PortletRenderer_109c058b59e.java)
     at org.apache.tapestry.portlet.PortletHomeService.service(PortletHomeService.java:80)
     at $IEngineService_109c058b58a.service($IEngineService_109c058b58a.java)
     at org.apache.tapestry.services.impl.EngineServiceInnerProxy.service(EngineServiceInnerProxy.java:77)
     at org.apache.tapestry.services.impl.EngineServiceOuterProxy.service(EngineServiceOuterProxy.java:66)
     at org.apache.tapestry.engine.AbstractEngine.service(AbstractEngine.java:248)
     at org.apache.tapestry.services.impl.InvokeEngineTerminator.service(InvokeEngineTerminator.java:60)
     at $WebRequestServicer_109c058b559.service($WebRequestServicer_109c058b559.java)
     at $WebRequestServicer_109c058b558.service($WebRequestServicer_109c058b558.java)
     at $WebRequestServicer_109c058b557.service($WebRequestServicer_109c058b557.java)
     at $WebRequestServicer_109c058b556.service($WebRequestServicer_109c058b556.java)
     at org.apache.tapestry.portlet.RenderRequestServicerToWebRequestServicerBridge.service(RenderRequestServicerToWebRequestServicerBridge.java:49)
     at $RenderRequestServicer_109c058b551.service($RenderRequestServicer_109c058b551.java)
     at $RenderRequestServicer_109c058b550.service($RenderRequestServicer_109c058b550.java)
     at $RenderRequestServicer_109c058b54b.service($RenderRequestServicer_109c058b54b.java)
     at $RenderRequestServicer_109c058b54a.service($RenderRequestServicer_109c058b54a.java)
     at org.apache.tapestry.portlet.ApplicationPortlet.render(ApplicationPortlet.java:161)
     at oracle.webdb.wsrp.server.Server.getMarkup(Unknown Source)
     at oracle.webdb.wsrp.WSRP_v1_Markup_PortType_Tie.invoke_getMarkup(WSRP_v1_Markup_PortType_Tie.java:98)
     at oracle.webdb.wsrp.WSRP_v1_Markup_PortType_Tie.processingHook(WSRP_v1_Markup_PortType_Tie.java:495)
     at com.sun.xml.rpc.server.StreamingHandler.handle(StreamingHandler.java:230)
     at com.sun.xml.rpc.server.http.ea.JAXRPCServletDelegate.doPost(JAXRPCServletDelegate.java:153)
     at com.sun.xml.rpc.server.http.JAXRPCServlet.doPost(JAXRPCServlet.java:69)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
     at oracle.webdb.wsrp.server.ContextFilter.doFilter(Unknown Source)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:285)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:126)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
Caused by: oracle.webdb.wsrp.server.ContainerIllegalArgumentException: Invalid URL "wsrp_rewrite?wsrp-urlType=blockingAction&wsrp-mode=wsrp%3Aview&wsrp-windowState=wsrp%3Anormal&wsrp-secureURL=false/wsrp_rewrite"
     at oracle.webdb.wsrp.server.PortletResponseImpl.encodeURL(Unknown Source)
     at oracle.webdb.wsrp.server.RenderResponseImpl.encodeURL(Unknown Source)
     at org.apache.tapestry.portlet.PortletWebResponse.encodeURL(PortletWebResponse.java:60)
     at $WebResponse_109c058b636.encodeURL($WebResponse_109c058b636.java)
     at $WebResponse_109c058b51e.encodeURL($WebResponse_109c058b51e.java)
     at org.apache.tapestry.engine.RequestCycle.encodeURL(RequestCycle.java:207)
     at $IRequestCycle_109c058b63f.encodeURL($IRequestCycle_109c058b63f.java)
     at $IRequestCycle_109c058b53a.encodeURL($IRequestCycle_109c058b53a.java)
     at org.apache.tapestry.portlet.PortletLink.getURL(PortletLink.java:68)
     at org.apache.tapestry.portlet.PortletLink.getURL(PortletLink.java:126)
     at org.apache.tapestry.form.FormSupportImpl.render(FormSupportImpl.java:490)
     at org.apache.tapestry.form.Form.renderComponent(Form.java:250)
     at org.apache.tapestry.AbstractComponent.render(AbstractComponent.java:617)
     at org.apache.tapestry.BaseComponent.renderComponent(BaseComponent.java:92)
     at org.apache.tapestry.AbstractComponent.render(AbstractComponent.java:617)
     at org.apache.tapestry.AbstractPage.renderPage(AbstractPage.java:275)
     at org.apache.tapestry.engine.RequestCycle.renderPage(RequestCycle.java:366)
     ... 36 moreAny of you got any clue whether this is an issue of Tapestry, or of Oracle Portal. I'm guessing it is Oracle Portal messing things up, as it is Oracle which gets mentioned in the stacktrace as cause.
Thanks.

My mistake! The error was a result of a badly formatted portal.xml

(Why) do I need a JSR-168 Portlet container?

Probably I'm missing something essential here, but whey do I need a JSR-168 portlet container? Suppose I'm using Tapestry 4 to write my JSR-168 compliant portlets, can they be consumed "directly" by a WSRP Portal server?

Because:
"A portlet container runs portlets and provides them with the required runtime"
"environment. A portlet container contains portlets and manages their lifecycle. "
"It also provides persistent storage for portlet preferences. A portlet container"
"receives requests from the portal to execute requests on the portlets hosted by it."
"A portlet container is not responsible for aggregating the content produced by the"
"portlets. It is the responsibility of the portal to handle the aggregation."

JSR-168 Portlets will work on SAP NetWeaver ?

Hi,
I would like to confirm with you whether JSR-168 Portlets will work on SAP NetWeaver platform or they work on specific versions of SAP NetWeaver and I would appreciate if you could kindly confirm on these points.
As per my knowledge it supports SAP NetWeaver '05'.
Is the SAP NetWeaver '05' version available for SAP Service Marketplace?
Or do they provide any plug-in to support JSR-168 portlets.
So please provide me detailed information for the above query and that would be greatly appreciated.
Thanks & Regards
Siva

Hi Siva,
JSR-168 will be available with the next major version of SAP NetWeaver, which should be out next year. For the time being, there's a preview of the J2EE stack that will be part of the next NW version. You can download it here: https://www.sdn.sap.com/irj/sdn/downloads?rid=/library/uuid/da699d27-0b01-0010-99b0-f11458f31ef2
Note: this preview supports the JSR-168 as runtime. However, it does not include portal, so you can't actually "consume" the portlet components. However, if you have portlets available, you can at least try deployment to the web container...
Hope that helps!

Support of JSR 168 and JSR 286 portlets

Hi,
As far as I know there is no direct support for JSR 168 compliant portlets in the SAP portal. Remote portlets can be consumed using WSRP. I was wondering whether the SAP portal will provide direct support for JSR 168 or even JSR 286 portlets in future releases?
Regards,
Kevin

Hi Kevin,
Long time ago SAP promised to implement JSR 168. Nowadays, you don't find much official documentation stating SAP portal is JSR168 compliant.
SAP introduced the Federated Portal Network (Consumer and Producer portals), also with WSRP support.
Check:
cheers,
Noë

WSRP/JSR-168 for production?

Maybe I'm missing something, but from my little research on the use of WSRP/JSR-168 within Portal, all indications are this is not ready for production use. Meaning, if I use JDeveloper (or some other tool) I cannot deploy production quality Portlets based on these standards within Portal 10g (9.0.4). Is this correct, or did I miss something?
Given this, my only choice is to use the JPDK if I wish to develop Java based portlets.
Thanks...
Dean

Hi all,
Even i am also looking for if any body has consumed the JSR168 portlet on
OracleAs Portal 10g Release 2.
I have found some article where it is mentioned that
Production Support for JSR 168 and WSRP
Once upgraded to Oracle Portal 10.1.4, a repository only upgrade on top of OracleAS 10.1.2.0.2, your portal version provides production support for building and consuming standards-based portlets. Oracle portal provides a Java Portlet Wizard within Oracle JDeveloper to build JSR 168 portlets and publish those portlet to Oracle's container or any portlet standards container. You can then consume JSR 168 portlet with Oracle Portal through WSRP. Oracle Portal also supports consuming any portlet through WSRP as well as JPDK portlets.
U can read the complete details here:-
http://www.oracle.com/technology/products/ias/portal/html/pdk_1014_new_features.html
Thnx
~Neeraj Sidhaye
[email protected]
[email protected]

JSR-168/WSRP iViews

Hi,
I have the following doubts to be cleared.It would be of great help if someone knows abt these and revert back ASAP.
1) How many iViews currently exist? Is there a directory of available iViews?
2) Is SAP planning to provide today's iView functionality as JSR-168/WSRP portlets together with the new release (or later)?
3) Would it make sense to create JSR-168/WSRP portlets by reusing existing iViews? I.e. is the iView Java code customizable? Would that be a feasible approach in order to provide iView-like functionality through JSR-168 or WSRP portlets?
4)Any other alternatives to expose iView-like functionality through a non-SAP portal? If so, what would that look like?
Regards.....

Hi Christian,
1) This question is independent of WSRP/JSR, right? --> So, you mean, how many iViews in general.. There is no list published by SAP giving an overview of available iViews. However, you could get a little overview when checking out the business packages currently available offered by SAP and partners.
https://www.sdn.sap.com/sdn/contentportfolio.sdn
2) SAP is not planning to provide all the functionality in a JSR168/WSRP-compliant manner. SAP will support WSRP by the end of this year with the next NetWeaver release. However, this does not mean that the existing content will be available via WSRP. Some might be, but to which extent, cannot be said for sure now. JSR is intended to be supported next year, meaning that the NetWeaver Portal will be able to consume JSR168-compliant portlets, but not provide all the existing content in JSR168 format.
3) You are not allowed to modify iViews delivered by SAP. If you intend to modify iViews, which you created on your own, it depends on how much effort you want to spend on it and how long you can wait with your projects since both standards are not supported at the moment yet with the current SP releases.
4) Please a bit more specific about what you mean with iView-like functionality. In general, to leverage the full functionality of SAP iViews you always need the full NetWeaver Portal framework. There are some scenarios of how to integrate the SAP EP into the WebSphere Portal. Check out the docs here on SDN.
Kind regards,
Thomas

Portlet JSR 168

hi ..
I can add navigation parameters to portlet JSR 168 by adding the parameters in oracle-portlet.xml .. where it is the only way for portlet communication .
now I create JSF Application and expose it to JSR 168 -by adding portlet.xml file - it work good but I want to add navigation parameters for this portlet , how ??
thanks

You need to deploy to a WLS and then register the WSRP producer to your consuming application.
You can read my paper about portlets: http://www.yonaweb.be/sites/default/files/ipc_0.pdf
It explains the basic on how to create and consume portlets in WebCenter 11.1.1.3

JSR 168 invocation protocol

Greetings,
I've a question about JSR 168 portlets, in many places I've read that it is considered local portlets while WSRP portlets are considered remote.
The question is does JSR 168 uses any other protocol than HTTP and if not, does the term local still apply?
regards

I'm not completely familiar with all of this but I'll give it a try :
* 1. In Oracle portal, does the concept of a "local" portlet exist where the communication between the portal and the portlet container is in memory or is it that all such communication uses remote protocols such as HTTP(S)?
Oracle Portal communicates with the producer using wsrp. There is no in memory communication when both the Portal application and the producer reside on the same server. The same applies for providers (JPDK), they use SOAP for communication.
* 2. Is there any performance gain when deploying the portal container on the same application server as the portal?
That's difficult to say. Web Apps can consume a lot of resources and could potentially affect the performance of the Portal when they reside on the same host. And heavy usage of the Portal can also affect the Web Applications. These things will not happen when they are on separate hosts with a high speed network between them.
The beauty of having a separate host for web applications is that they will not influence the Portal host, the software can be easily upgraded with affecting the Portal software much and so on.
* 3. Is there any difference between the method of communication between the portal and the two different types of containers; i.e. PDK and JSR?
Yes, PDK uses SOAP while JSR uses WSRP
* 4. Is there any significant performance gain in implementing PDK portlets over JSR portlets?
I don't have any performance figures for that.
PDK and JSR cannot be compared that easily. Whilst both allow for Portlet development in Java, the PDK is far more richer than JSR at the moment. The downside is that PDK is proprietary - it can only be used with Oracle Portal.
Hope this helps,
Erik

Is the JSR-168 portlet-container supported for 10.1.3?

And if so, what are the actions to be taken to install it on OC4J 10.1.3 standalone? I tried to install it earlier but ran into problems, see: WSRP Provider registration fails for OC4J10.1.3 container (stack), why?
I want to use OC4J 10.1.3 as my JSR-168 container, because I can (try and) deploy Tapestry 4.0 portlets in this application server, that use Java annotations. I then want to consume these portlets over WSRP - part of Portal 10.1.4

<bump count="2"/>

WSRP & JSR-168

Hello!
I'm trying to declare my portlets as remote and connect to them.
I have JSR-168 compliant portlets and I created remote portlets to them on a consumer.
But every time I submit a form the portal reverts to the initual state instead of processing my request.
I was also wondering if WebLogic processes only URLs created using the netui library?
thank in advance,
Vica

Hi all,
Even i am also looking for if any body has consumed the JSR168 portlet on
OracleAs Portal 10g Release 2.
I have found some article where it is mentioned that
Production Support for JSR 168 and WSRP
Once upgraded to Oracle Portal 10.1.4, a repository only upgrade on top of OracleAS 10.1.2.0.2, your portal version provides production support for building and consuming standards-based portlets. Oracle portal provides a Java Portlet Wizard within Oracle JDeveloper to build JSR 168 portlets and publish those portlet to Oracle's container or any portlet standards container. You can then consume JSR 168 portlet with Oracle Portal through WSRP. Oracle Portal also supports consuming any portlet through WSRP as well as JPDK portlets.
U can read the complete details here:-
http://www.oracle.com/technology/products/ias/portal/html/pdk_1014_new_features.html
Thnx
~Neeraj Sidhaye
[email protected]
[email protected]

JSR 168 consumer vs iPlanet 4.1

Similar Messages

Maybe you are looking for