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

Similar Messages

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

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

JSR 168 API question

Hi,
How can i forward the request to another "Page" using JSR 168 ?
Where can i find JSR-168 code examples other than the one shipped with JSR168-Struts
bea package ?
Thanks

Carl,
The portlet API does not support the use case you're looking for. The
API has no notion of pages.
WebLogic portlet container, however, does support this use case. Try
using render:pageUrl as in the following example
Click ">here</a> to to goto
page X.</p>
where pageX is the definition label of that page.
Subbu
Carl Samson said the following on 12/08/2003 08:15 AM:
Hi,
How can i forward the request to another "Page" using JSR 168 ?
Where can i find JSR-168 code examples other than the one shipped with JSR168-Struts
bea package ?
Thanks

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?

JSR 168 portlets packaging question

Hello,
I have a bunch of Java (JSR 168, using Spring MVC) portlets (PortletOne, PortletTwo...PortletN) that I created as individual Portal Web projects and are contained in a Portal EAR project. This portal EAR is my deployment unit and also consists of another Portal Web project (Assembly.war) that holds a app.portal file where I plan to assemble all these Java portlets and use it to create a desktop. The reason for having all the individual portlets in web projects of their own is to be able to export them as a unit and use it elsewhere either as a shared library or package it within another EAR file as the need arises.
my application.xml looks somewhat like this:
<?xml version="1.0" encoding="UTF-8"?>
<application id="Application_ID" version="1.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd">
     <display-name>MyEar</display-name>
     <module id="WebModule_1">
          <web>
               <web-uri>Assemby.war</web-uri>
               <context-root>appname</context-root>
          </web>
     </module>
     <module id="WebModule_2">
          <web>
               <web-uri>PortletOne.war</web-uri>
               <context-root>PortletOne</context-root>
          </web>
     </module>
     <module id="WebModule_3">
          <web>
               <web-uri>PortletTwo.war</web-uri>
               <context-root>PortletTwo</context-root>
          </web>
     </module>
</application>But since all these WAR files are at the same level I cannot reference the context definitions and the controllers for the portlets defined in each of these portlet WAR files (PortletOne, PortletTwo,...) from the common web project that holds the app.portal file in Assembly.war. I tried to define a custom classloader structure in weblogic-application.xml and put the assembly war file at a lower level but the app even fails to deploy with IllegalAccessError as soon as a context for each of the war files is registered by the hot deploy process. Moreover, when I deploy the EAR file, the portlets defined in each of the WAR files do not appear in the Resources library when viewed from the Portal Administration console.
Any suggestions how to assemble these individual portlets into a common web project, while still keeping them packaged within the same EAR file? Alternate approaches are welcome too.
I have already considered deploying these portlet WAR files as Weblogic J2EE shared libraries. But with this approach, the overall application response time is very slow in spite of exhausting all tuning options and also cannot pre-compile JSPs in the shared libraries.
Is importing the JSR-168 portlets using the import utility as WSRP portlets a viable option? Will I be able to share session variables across portlets, fire and handle events and be able to pre-compile the JSP in idividual portlets?
Edited by: shyam6190 on Aug 13, 2009 1:25 PM

Hello,
Perhaps the multiple nested classloaders involved with the shared libraries approach is slowing it down- if that is the case, it would be hard to fix.
Using WSRP should work for you; there is a bit more complexity but if you have relatively simple portlets, use the correct JSR168 tags and methods (or the Spring bridge does), it shouldn't be too hard to get to work. The IDE may be able to help you with that; you can create a new portlet of type "remote portlet" in your aggregated webapp, and a wizard will walk you through the steps. If you use local proxy mode, the portlet's individual WSDL URL will be the URL to each portlet's webapp on localhost.
The WSRP configuration can also be done dynamically in the Portal Admin Tools, and even using a specialized JSR168 import tool, but both of these options would only create database instances of portals and portlets in your aggregating webapp. This would be fine if your aggregated EAR never needs to move to a different deployment environment, but if you require portability of the EAR to another environment it complicates packaging, as database information is also required. If you happen to be using WLP version 10.3, I believe there is a bug which prevents the specialized JSR168 import tool from working, but the tool is documented here:
http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/prodOps/deployment.html#wp1047337
Since all the WSDL URLs will point only to the localhost, when you package the aggregated WAR file it should deploy properly to any servers. Information about the local proxy mode, which should improve performance for your configuration, is described here:
http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/federation/Chap-Best_Practices.html#wp1010714
Hope this helps!
Kevin

JSR-168 vs Page Flow question

Hi,
I i use JSR-168 to do my Portlets instead of page flow, which functionnality/features
will i loose ?
Thanks

Two main features
* Managing flow: WLW can help manage flow for pageflows, but with JSR168
portlets, you need to create the flow programmatically.
* Databinding: Pageflows support advanced databinding features, and
these features are not part of the spec defining JSR168 portlets.
Subbu
Carl Samson said the following on 12/08/2003 07:12 AM:
Hi,
I i use JSR-168 to do my Portlets instead of page flow, which functionnality/features
will i loose ?
Thanks

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

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

Where is JSR-168 support?

Hi all,
I do manage to create jsr-168 jsf portlets using JSC , But one thing i failed to understand. I dont see the code as a standard jsr-168 portlet. Where is the processAction()? where is the request response object. Now i use to follow jsr-168 specs to get user information and to get portlet url.. How could i achieve this in Sun java Creator
regard
Kimi

portlet url could probably be managed in part by ((PortletContext)getFacesContext().getCurrentInstance().getExternalContext().getContext()).getRealPath("/")
to get at least the relative part of the path. In terms of the full url, not sure where you can find the server portion.
For the rest of the questions, I would love to get the answer. I can't find much documentation online on how to really extend processAction for our own uses.

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")

JSR-168 Navigation

I would like to navigate from a Portal page containing JSR-168 portlets to another similar Portal page. I have accomplished this using the EDK <pt:openerLink ...> method but I was unable to append a parameter that was visible to the portlets on the target page.
Do I need to create an Action URL with a parameter. From the processAction() method of the Portlet on the originating page I would then place the parameter into session scope and redirect from the originating Portal page to the new target portal page. (I know about the bug with session scope)?
I read the "Introduction to JSR-168 Portlets" article, and noticed the custom tag
">here</a>.
If I use this to how do I specify the new target Portal page?

I'm not sure if my question was clear. I am not trying to 'call' another portlet. I am trying to navigate from one portal page (containing JSR-168 portlets) to another page. I know that I can do this about five different ways (<pt:opener , custom tag library within the Plumtree JSR-168 war, ...).
I would like to know the most effective way to do this and pass a parameter.
According to the 1.0.3 Release Notes for JSR-168 Container 1.0.3: "Render parameters are not stored between requests. This specifically fails the Sun TCK tests using WebLogic on Unix. (Issue #37783)." What is the correct life-span of a render parameter?
Thank you! Any info is appreciated ;-)

JSR 168 and Web Services For Remote Portlets

Hi,
I have recently joined SAP.In my previous work experience I have worked extensively on the Sun Java Portal Server and was curious about the following
1.Does SAP Enterprise Portal Server support JSR 168 compliant Portlets.
2.If yes the Question that naturally follows is:Can portlets(view Components)in a SAP Portal be remote enabled?In other words does SAP portal support WSRP standards.
3.If the SAP Enterprise Portal has implemented the JSR 168 specifications then how does the architecture seperate out the Portal engine from the Portlet Container.
In other words where does the actual wrapping from a HTTPServletRequest to a Portlet Request happen?
4.The JSR 168 specifications restricts the use of IFrames and many HTML tags in the fragments that are returned by the portlets running in the Portlet Container.Is this taken care of in SAP Enterprise Portal?
5.Can WebDynpro applications be embedded in a JSR 168 compliant portlet?
6.How is parity maintaned between portlet session HTTP session and the Applications session?
7.Does SAP Portal support deployment through a par model?
Thanks and Regards
Sujeet Mishra
SAP Labs India Ltd
[email protected]

> 1.Does SAP Enterprise Portal Server support JSR 168
> compliant Portlets.
I'd like to know the answer to this question as well. I wrote an email but didn't receive any response. So i guess JSR 168 isn't supported yet?

Online chat, Aug. 12, n the Portlet Specification (JSR 168)

The Portlet Specification, JSR 168 ( http://jcp.org/en/jsr/detail?id=168 ), establishes a standard API for creating portlets. It's designed to ensure interoperability between portlets and Java-based portal servers or other Web applications that implement the specification. Learn more about the Portlet Specification, and get questions answered in this chat with Portlet Specification co-lead Alejandro Abdelnur, and Sun ONE Portal Server product manager Adam Abramski. The chat is scheduled for Tuesday, August 12, at 11 A.M.-to-noon Pacific Daylight Time (6:00 P.M.-to-7 P.M. GMT).
To join the chat on August 12, go to http://developer.java.sun.com/developer/community/chat/index.html and click on "Join the current session".

The transcript of this chat is now available at http://developer.java.sun.com/developer/community/chat/JavaLive/2003/jl0812.html

Online Chat, Aug. 12, on the Portlet Specification (JSR 168)

The Portlet Specification, JSR 168 ( http://jcp.org/en/jsr/detail?id=168 ), establishes a standard API for creating portlets. It's designed to ensure interoperability between portlets and Java-based portal servers or other Web applications that implement the specification. Learn more about the Portlet Specification, and get questions answered in this chat with Portlet Specification co-lead Alejandro Abdelnur, and Sun ONE Portal Server product manager Adam Abramski. The chat is scheduled for Tuesday, August 12, at 11 A.M.-to-noon Pacific Daylight Time (6:00 P.M.-to-7 P.M. GMT).
To join the chat on August 12, go to http://developer.java.sun.com/developer/community/chat/index.html and click on "Join the current session".

The transcript for the chat is now available at http://developer.java.sun.com/developer/community/chat/JavaLive/2003/jl0812.html

JSR-168 Consumer question

Similar Messages

Maybe you are looking for