JSR 168 APIs

Dear All,
We are trying to get content from IBM Websphere Portal v5.1 and display in our SAP portal . The content in IBM portal is stored in portlets . IBM recommended us to call their JSR 168 API's to just grab the content. We only want the content not the formatting. We cannot use URL iviews as their URL has not only the content but also a navigation panel , and we do not want the navigation panel.
I believe our Portal EP 7.0 can support JSR 168 compliant API from some of the information we found in SDN . But we are not able to locate the any how to guide on how to call such API from SAP whether from ABAP or Java we have no idea. Does anyone have something like a How to guide/ even sample code on how to call JSR 168 API or how can I proceed with this.
Best Rgds

hey you need to set up federated portal network(FPN) to establish this.i had done this before. i you only want webshpere portal content to be displayed in SAP EP, then implementing FPN alone wil do.if you want to dispay the content from SAP EP in IBM websphere then you need to do some coding in portal side to make your application jsr168 compliant
Message was edited by:
jeyasingh samuel Durairaj

Similar Messages

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

How to debug jsr 168 portlet in jdeveloper 10.1.3.4

Does anyone know how to locally debug a jsr 168 portlet in jdeveloper 10.1.3.4.
When I click on run it asked for a start page so I supply the view.jsp page.
The following error occurs on the page:
500 Internal Server Error
java.lang.NullPointerException at helloworld.html._view._jspService(_view.java:61) [helloworld/html/view.jsp] at com.orionserver[Oracle Containers for J2EE 10g (10.1.3.4.0) ].http.OrionHttpJspPage.service(OrionHttpJspPage.java:59) at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:462) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:122) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:111) at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260) at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:234) at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:29) at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:879) at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298) at java.lang.Thread.run(Thread.java:595)
This is the first jsr 168 portlet I have tried.
Previously we have been created portlets using the Oracle PDK. Those portlets are easy to debug because the wizard creates an index.jsp page for the start page.
If anyone can provide some insight to my issue it would be greatly appreciated.
Thanks,

Is this a portlet you built from scratch using the JSR 168 APIs, or is this a JSF Portlet using the JSF Portlet Bridge. If the latter, you can debug your JSF application. If the former, you can do remote debugging (let me know if you need information on this).
Hope this helps,
Peter

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?

Converting PDK Portlet calls to JSR 168 portlet calls

Hi,
I am working on making Worklist 10.1.3 portlets WSRP compatible. For that i am converting PDK java calls to equivalent JSR 168 API calls ... I have made some changes and stuck on few things .
Can anyone help me equivalent JSR of these calls .
NOT DONE :--
String actionParam = PortletRendererUtil.getEditFormParameter(pReq);
PortletRendererUtil.submitEditData(pReq, data);
String myURL = pReq.getRenderContext().getPageURL(); // Gets the URL of the page that invoked this portlet.
prevPgURL = UrlUtils.parameterizeLink(renderRequest, UrlUtils.PAGE_LINK, wlPgStartKey+"="+prevPgStart); //Adds new parameters to an existing link
String portletKey = pReq.getPortletInstance().getInstanceName(); // Gets the Portal generated name of the PortletInstance.

Nisabhar,
You could try the [url http://forums.oracle.com/forums/forum.jspa?forumID=14]OAS Portal Forum, as your question doesn't have anything to do with JDeveloper.
John

JSR 168 and UIX.

Hi,
Iam a newbie working on an JSR 168 app that makes an existing portlets as JSR 168 compatible. The portlets was orginaly developed usign the JPDK api and to incorporate standards we are making it as JSR 168 compatible.
We used the UIX pages as the front end for showing portlet content. Is it possible to leverage the existing UIX pages using the JSR 168 API. For Rendering the UIX content we used the JPDK classes like the RenderManager , PortletContainerRenderer etc.
As i understand JSR 168 provides the RenderRequest which represents the request sent to the portlet to handle a render. Can this RenderRequest be used to display UIX pages.
Just wanted to know a couple of things.
a) JPDK providers RenderManager , PortletContainerRenderer etc are there equivalents in the JSR 168 API
b) Difference between the RenderRequest of the JSR and the PorletRenderRequest class .
At a brief Iam looking for an equivalents of in the JSR 168 API which can accomplish this.
Thanks
Mouli

Hi Mouli,
In case of JPDK always you will get single request i.e., HttpServletRequest from the portlet.you can get the PortletRenderRequest from HttpServletRequest.
Way to get PortletRenderRequest from HttpServletRequest :
===========================================
PortletRenderRequest portletRenderRequest=(PortletRenderRequest)oHttpServletRequest.getAttribute("oracle.portal.PortletRenderRequest");
[NOTE : you need to import the following class.
import oracle.portal.provider.v2.render.PortletRenderRequest;]
In case of JSR 168 generally you will get two kinds of request ie., RenderRequest & ActionRequest.Where PortletRequest is the parent interface for this two interfaces.
For Ex.whenever the portlets first time loaded on portalpage the portlet will get RenderRequest & it will create its own portlet markup.When ever you perform any operation in any portlet then it will have ActionRequest & remaining portlets will have RenderRequest.
Please feel free to ask anything related to portal technology..Let me know if i specified anything wrong.....
Thanks & Regards.,
Bala S Murugan.,
sendrequestgetresponse At Gmail Dot Com
http://balamurugan-portlets.blogspot.com/

Is it possiable to use "ALI SCRIPTING FRAMEWORK API " in JSR 168 Portlets?

Hi,
Is it possiable to use "ALI SCRIPTING FRAMEWORK API " in JSR 168 Portlets.
With Regards
Dheeraj Sai

If you want to use (let say it's possible) "ALI SCRIPTING FRAMEWORK API" in JSR 168 then these porlets are not "JSR-168" compatible anymore. So you automatically lost the main benefit of JSR-168 portlet - works over different portal vendors.
I guess if you have decided use JSR-168 you did this for reasons. Then stay this way and don't use any proprietary technologies.
By the way, this topic may help:
http://forums.bea.com/bea/message.jspa?messageID=500025455&tstart=0
Edited by Bryazgin at 05/18/2007 6:36 AM

Portlet API: JSR 168 / 286 vs Vendor Extensions

Currently evaluating Websphere 5.1 vs WebLogic 8.1 Portal software.
It seems like both IBM and BEA push you towards using their Portal extensions as "value add" features. I am really interested in sticking to JSR 168 for portability.
Does anyone have any experience with these tools developing JSR 168? I would appreciate your observations about using the vendor extensions vs JSR 168 support in these tools. Please add any comments on other portal software you have had success with.
Any idea when will JSR 286 come out with final spec?
Message was edited by:
java@finance

sorry.Correction.I am using Oracle portal 10.1.4 .
-Vid-

Error while deploying a JSR 168 portlet developed in JDeveloper 10.1.3.2

When deploying a JSR 168 portlet created using JDeveloper 10.1.3.2 (Web Center Suite edition), I get the error :
"Shared library "oracle.wsrp" could not be found."
Error Log:
---- Deployment started. ---- Sep 20, 2007 9:31:42 AM
Target platform is Oracle Application Server 10g 10.1.3 (PolestarAppServerConnection).
Wrote WAR file to C:\Projects\eAlliance\JSR168\ViewController\deploy\jsr168.war
Wrote EAR file to C:\Projects\eAlliance\JSR168\ViewController\deploy\jsr168.ear
Backing up generic archive file :/C:/Projects/eAlliance/JSR168/ViewController/deploy/jsr168_generic.ear
Creating WSDLs for the WSRP Application
WSDLs for the WSRP Application have been created
Uploading file jsr168.ear ...
Uploading file jsr168.ear ...
Application Deployer for jsr168 STARTS.
Copy the archive to /home/soahome/orasoa/j2ee/home/applications/jsr168.ear
Initialize /home/soahome/orasoa/j2ee/home/applications/jsr168.ear begins...
Unpacking jsr168.ear
Done unpacking jsr168.ear
Unpacking jsr168.war
Done unpacking jsr168.war
Initialize /home/soahome/orasoa/j2ee/home/applications/jsr168.ear ends...
Starting application : jsr168
Initializing ClassLoader(s)
application : jsr168 is in failed state
Operation failed with error:
Shared library "oracle.wsrp" could not be found.
Deployment failed
Elapsed time for deployment: 39 seconds
#### Deployment incomplete. #### Sep 20, 2007 9:32:21 AM
Steps To recreate the error:
1)Create a new Application in JDeveloper
2)Click "New" in "ViewController" and click on WebTier->Portlets->Standards based(JSR 168) from the wizard.
3)Go thru JSR 168 Portlet wizard steps 1 thru' 8 accepting all defaults.
4)Click "New" in "ViewController" and click on General->Deployment Profiles->WAR File from the wizard.
5)Enter a name and hit OK. Then in the "WAR Deployment Profile Properties" page, select "Specify J2EE Web Context Root" and enter the name similar to what is in the "Enterprise application name" text box in the same screen. Hit OK.
6)Right click on the deploy file created under "Resources" and select "Deploy to AppServer" (I am deploying to a remote 10.1.4 Portal Server that has already been configured in my connections tab.
7)Note the above noted error message in the Deployment Log tab.
Can you give me any suggestions?
Thanks,
Bipin Raj

Does the \j2ee\home\shared-lib directory contain a directory oracle.wsrp?
Does the <OC4J_HOME>/j2ee/home/config/server.xml file contain a shared-lib declaration for oracle.wsrp?
<shared-library name="oracle.wsrp" version="1.0">
<code-source path="wsrp-container.jar"/>
<code-source path="wsrp-types.jar"/>
<code-source path="wsrp-jaxb.jar"/>
<code-source path="jaxb-api.jar"/>
<code-source path="jaxb-impl.jar"/>
<code-source path="jaxb-libs.jar"/>
<code-source path="namespace.jar"/>
<code-source path="xsdlib.jar"/>
<code-source path="relaxngDatatype.jar"/>
<import-shared-library name="oracle.gdk"/>
<import-shared-library name="oracle.xml"/>
<import-shared-library name="oracle.jdbc"/>
<import-shared-library name="oracle.cache"/>
</shared-library>

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

Developing Portals using JSR Compiant API and struts

Hi,
I am using Oracle AP Portal server 10.1.4 for development and all the existing portals are developed using Oracle PL/SQL. We have to convert all of them into JSR 168 Compliant (JPS API ) portlets using struts framework.
Could you provide us ideas or code snippets or sample applications?
It will be appreciated your responses as soon.
Thanks
Suren

I may end up having to do that, but I'm trying to keep my solution set as it is as I apply a print layout using tiles to each of the reports and I would like to keep things that way if I can.
I just noticed something interesting that I had not seen before, and that is in the PDF there is text rendered for the tiles tag <tiles:getAsString name="title" /> which tells me that the HttpURLConnection is getting the tiles attributes, but where it is failing is on the <tiles:insert attribute="body" /> tag. That at least narrows the problem down to the tiles:insert line specifically and not tiles overall.

Mysterious JSF Error In JSR 168 Portlets

Hey everyone. I'm working with a rudimentary JSF application that I'm trying to surface in a JSR 168 portlet, and I'm running into a mysterious stack trace in our Portlet logs. I can deploy and surface the portlet just fine, but the following exception occurs when I put the portlet in VIEW mode:
Caused by: java.lang.UnsupportedOperationException
at javax.faces.context.FacesContext.getELContext(FacesContext.java:137)
at com.sun.faces.application.ApplicationImpl.createValueBinding(ApplicationImpl.java:467)
at com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.pageBean(ViewHandlerImpl.java:697)
at com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.pageBean(ViewHandlerImpl.java:676)
at com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.renderView(ViewHandlerImpl.java:284)
...We're using the Apache JSF portlet bridge, but have noticed the same results using the Sun bridge. In any event, the exception is being thrown by a private method (getELContext) in the JSF API. I've been unable to gain any insight on what this exception means through Googling and stepping through the bridge code. Can anyone shed some light on what may be wrong?
Thanks,
Joe

Hey everyone. I'm working with a rudimentary JSF application that I'm trying to surface in a JSR 168 portlet, and I'm running into a mysterious stack trace in our Portlet logs. I can deploy and surface the portlet just fine, but the following exception occurs when I put the portlet in VIEW mode:
Caused by: java.lang.UnsupportedOperationException
at javax.faces.context.FacesContext.getELContext(FacesContext.java:137)
at com.sun.faces.application.ApplicationImpl.createValueBinding(ApplicationImpl.java:467)
at com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.pageBean(ViewHandlerImpl.java:697)
at com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.pageBean(ViewHandlerImpl.java:676)
at com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.renderView(ViewHandlerImpl.java:284)
...We're using the Apache JSF portlet bridge, but have noticed the same results using the Sun bridge. In any event, the exception is being thrown by a private method (getELContext) in the JSF API. I've been unable to gain any insight on what this exception means through Googling and stepping through the bridge code. Can anyone shed some light on what may be wrong?
Thanks,
Joe

JSR 168 support on production environment??

Hello Oracle people,
when are you going to support JSR168 portlets in you Oracle Portal?? Where is the money customers pay you for working? not enough? What do we do with this piece of closed source box you gave us if you can not be ahead many other open source (free) products? Can you stand the pace? you say "we support standards"... and I see you are falling behind.

you should be demanded because of the way you assure support of the JSR168 in your executive brochures... Any layer out there who can help?
Look this question and how Oracle answers:
Does Oracle Portal support JSR 168 and WSRP?
Oracle has been an active member of the standards bodies and been instrumental in the process of defining these portal interoperability standards:
* JSR-168: Defines how Java developers should write portlets using standard APIs.
* OASIS WSRP (Web Services for Remote Portlets): Defines the communication protocol between a portal application and the remote portlet./li>
Oracle fully supports the JSR 168 portlet specification. You can develop JSR 168 portlets using the Java Portlet Wizard, a JDeveloper plug-in. You can also deploy JSR 168 portlets to Oracle's or any other vendor's JSR 168 Java Portlet Container. Portlets deployed to Oracle's container are exposed to portals through WSRP, and can be registered against any portal vendor's WSRP compliant portal. The current version of Oracle Portal (Oracle Portal 10g Release 2 (10.1.2)) does not support WSRP, but you can register and test standard portlets using the OracleAS Portal Developer's Preview for Portlet Standards or the hosted WSRP compliant portal on http://portalstandards.oracle.com. You find additional information about Oracle and Portal standards on http://portalstandards.oracle.com.
When there is a simple answer: NO we do not support the JSR168 in Oracle Portal. We do a lot of other things... see this and that. But sadly our Oracle Portal does not support it, you can test a preview version but if it crashes its your problem (we proudly do very expensive closed source :).

JSR-168 Support

Do we have any plans to resume support for JSR-168 portlets to extend integration with other portal platforms besides WCI and WLP?

you should be demanded because of the way you assure support of the JSR168 in your executive brochures... Any layer out there who can help?
Look this question and how Oracle answers:
Does Oracle Portal support JSR 168 and WSRP?
Oracle has been an active member of the standards bodies and been instrumental in the process of defining these portal interoperability standards:
* JSR-168: Defines how Java developers should write portlets using standard APIs.
* OASIS WSRP (Web Services for Remote Portlets): Defines the communication protocol between a portal application and the remote portlet./li>
Oracle fully supports the JSR 168 portlet specification. You can develop JSR 168 portlets using the Java Portlet Wizard, a JDeveloper plug-in. You can also deploy JSR 168 portlets to Oracle's or any other vendor's JSR 168 Java Portlet Container. Portlets deployed to Oracle's container are exposed to portals through WSRP, and can be registered against any portal vendor's WSRP compliant portal. The current version of Oracle Portal (Oracle Portal 10g Release 2 (10.1.2)) does not support WSRP, but you can register and test standard portlets using the OracleAS Portal Developer's Preview for Portlet Standards or the hosted WSRP compliant portal on http://portalstandards.oracle.com. You find additional information about Oracle and Portal standards on http://portalstandards.oracle.com.
When there is a simple answer: NO we do not support the JSR168 in Oracle Portal. We do a lot of other things... see this and that. But sadly our Oracle Portal does not support it, you can test a preview version but if it crashes its your problem (we proudly do very expensive closed source :).

JSR 168 APIs

Similar Messages

Maybe you are looking for