Deploying JSR168 Portlet's into Portal

Hi,
I developed a simple ADF portlet's in Jdev 11g. I also deployed into integrated WLS (as shown in Oracle's developer guide) and the URL http://host:port/context-root/portlets/wsrp2?WSDL shows WDSL correctly
Now I want to deploy the same portlet into an external Weblogic Server 10.3. I created and uploaded the .war file and deployed via weblogic console.
The deploy seemed to finish correctly because I see in the console my web application deployed but I don't see the wsdl (in http://externawlshost:port/context-root/portlets/wsrp2?WSDL).
Until the WSDL is visible I can't add the producer to Oracle Portal.
Do I need to do something else in the deploy process?
Thank You,
Andre

Hi All,
I am facing the same issue. My ADF portlet application got deployed successfully into integrated weblogic server and can access the WSDL end point also.
But when I am trying to deploy it to an external weblogic through weblogic console, could not able to access the WSDL url.
Can anbody tell me what could be the issue. Do I need to have a WSRP container in my weblogic? If so, how to install it?
--Abhijit

Similar Messages

Deploy jsr168 portlet issue by jsr168import.jsp

hi,guys
I got a question.
I want to deploy some 168 portlet to weblogic portal,so I follow the document.
after perform import done,show me the message,it means successful.then I open a tab of browse
(http://localhost:7001/rssportlet/producer?wsdl)
put the wsdl address URL,it was show me the wsdl content.
but when I create new producer,in the second step,I can't see the portlet,it means no portlets for me.
(2. View Producer's Portlets,I can't see my deployed portlet)
what wrong with my operated.
hope you can help me ,thank you so much.
regards
aris

Hello again,
I should mention that as a workaround, you can use the JSR168 import tool as it exists in WLP 10.3 and have it generate but not deploy the EAR file for you. Inside the EAR you should find a directory named the same as your original WAR file with a WEB-INF/ subdirectory. You should be able to copy all of the generated configuration files out of this WEB-INF/ directory. Go back to the root level directory of the EAR (which has a subdirectory named the same as your original WAR file), expand your original WAR file there so that it overwrites the WAR directory, then copy the configuration files you saved off back into the WEB-INF directory. Finally, jar up the EAR file again and it should be ready to deploy.
Kevin

Problem deploying JSR168 portlets; Tomcat, Win2003

Dear All,
Am having some problems deploying the JSR168 portlets on Tomcat 4.1 and Win2003.
This is on Windows, and I have to manually deploy it per the instructions...
So far I__
1. Exploded the .war and added ptjsr168 to pthome.xml per the sparse installation pdf;
2. stopped tomcat, deleted the cache (contents of the work directory), restarted.
3. verified that the application appears in the work directory
but get the error,
/PtPortletContainer/portlet/RssPortlet/mode/view
descriptionThe requested resource (/PtPortletContainer/) is not available.
...when I try to browse there to get the correct URL tp paste into the remote server, something like:
http://portlets.mycustomer.com:8080/ptjsr168/
The extension to this in the web service is, by default:
/PtPortletContainer/portlet/RssPortlet/mode/view
I may be typing the URL wrong, for all I know. Something simple.
Any ideas?
Cheers,
Rob

You can verify whether your portlet works correctly by testing it on OpenPortal Portlet Container(https://portlet-container.dev.java.net). Or if you think the issue is with Pluto Portal I would recommend posting your issue on the Pluto Portal mail alias.

Error deploying ALBPM portlets in WebLogic Portal

Hi, I have a problem when I try to deploy ALBPM workspace portlets in WebLogic Portal
<28/01/2009 18h11min47s BRST> <Error> <HTTP> <BEA-101214> <Included resource or file "/workspaceWeb/framework/skeletons/text/flowlayout.jsp" not found from requested resource "/workspaceWeb/BPMPortal.portal".>
I copied framework folder into web project but the problem persists. I've used the WLP 10.1. This could be a version issue?
Regards
Rogerio Cruz

Hi,
I see this messages below of ActionsMenu, Worklist and InstanceDetail portlets. The URL generated first is:
http://localhost:7001/workspaceWeb/BPMPortal.portal?_nfpb=true&_pageLabel=BPMPortal_portal_page_7
but when I type this URL in browser, is "redirected" to the following:
http://localhost:7001/workspaceWeb/BPMPortal.portal?_nfpb=true&_pageLabel=BPMPortal_portal_page_7*#wlp_BPMPortal_portal_page_7*
and the '404' pages are shown
I'm using BPM Enterprise for WebLogic Server 604 build 94433
Regards
Rogerio Cruz

Deploy jsr168 portlet in weblogic

Hi,
I'm developing a jsr168 portlet that I would like to be able to deploy in the Weblogic Portal (among others).
The problem is, after much searching, that I can't figure out how to do it.
In Websphere I just deploy the .war file through the portal administration web interface and away I go.
In jetspeed2 I just drop the .war file in the deploy folder and it gets deployed.
Is there anything similar for Weblogic?
I've currently got 8.1 SP4 installed.
I've seen and even tried the portletPreparer tool but I can't get it to work (dependencies on bea classes that I can't find).
Any help or tips on how to deploy a portlet in a .war file would be greatly appreciated.
Cheers,
Eric

Hi,
Generally while creating a jar file for deplyong a EJB on an App Server, create a folder called META-INF and copy all your xml files to this folder
this command could be part of your build.xml if ur using ant
mkdir build build\META-INF
copy *.xml build\META-INF
Then compile ur java files and then create the required jar or ear file for deployment.
Rgds,
Seetesh

Getting error while working with jsr168 portlet in weblogic portal 10.1

Hi,
I have configured jsr168 portlet to display RSS feed.I am not getting any error when I have logged in for 2 to 3 times. It's displaying fine.After that when I again login I am getting this error.
I am not knowing what's the problem is?Let me know.
java.lang.NullPointerException at com.bea.portlet.container.UserInfo.getAllProperties(UserInfo.java:149) at com.bea.portlet.container.UserInfo.updateUserInfo(UserInfo.java:117) at com.bea.portlet.container.AppContainer.invokeRender(AppContainer.java:704) at com.bea.netuix.servlets.controls.content.JavaPortletContent.fireRender(JavaPortletContent.java:249) at com.bea.netuix.servlets.controls.content.JavaPortletContent.renderInternal(JavaPortletContent.java:156) at com.bea.netuix.servlets.controls.content.JavaPortletContent.beginRender(JavaPortletContent.java:103) at com.bea.netuix.servlets.controls.application.laf.ContentControlRenderer.beginRender(ContentControlRenderer.java:48) at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326) at com.bea.netuix.nf.UIControl.render(UIControl.java:582) at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486) at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146) at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62) at jsp_servlet._framework._skeletons._pcagreen.__flowlayout._jspService(__flowlayout.java:290) at weblogic.servlet.jsp.JspBase.service(JspBase.java:34) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175) at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454) at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130) at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72) at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65) at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:326) at com.bea.netuix.nf.UIControl.render(UIControl.java:582) at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:486) at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146) at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62) at jsp_servlet._framework._skeletons._pcagreen.__gridlayout._jspService(__gridlayout.java:292) at weblogic.servlet.jsp.JspBase.service(JspBase.java:34) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175) at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528) at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454) at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:130) at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72) at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65) at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:481) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361) at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:208) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:162) at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388) at com.bea.netuix.servlets.manager.UIServlet.processControlTree(UIServlet.java:301) at com.bea.netuix.servlets.manager.PortalServlet.service(PortalServlet.java:927) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at com.documentum.web.servlet.CompressionFilter.doFilter(CompressionFilter.java:108) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at com.documentum.web.env.WDKController.processRequest(WDKController.java:95) at com.documentum.web.env.WDKController.doFilter(WDKController.java:83) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at com.documentum.web.env.PortalRequestFilter.doFilter(PortalRequestFilter.java:92) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:336) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at com.bea.portal.tools.servlet.http.HttpContextFilter.doFilter(HttpContextFilter.java:60) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200) at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Edited by jhansi.mandalapu at 05/05/2008 11:20 PM
Edited by jhansi.mandalapu at 05/05/2008 11:30 PM

Thanks Brad !!!
It works...
earlier I had entitlements set only on Employee Portal and Calendar in the tree structure Community_repository > Calendar > EmployeePortal > Calendar.
It didnt work and throwed that error.
After your suggestion I set entitlements on groupware.calendar.appointment to create, view, update, delete and instantiate to true.
It worked, thanks for your help.
-Win

How to deploy jsr168 war file into Webcenter Portal

I want to intergated a jsr168 war file with Web Center Portal. I only install WebCenter Portal without JDeveloper and Content. So how should I deploy it?
Thank you!
Regards,
Jugela

You have the weblogic domain right ? Opent the enterprise manager in browser by hitting the below url -
http://<Admin Server address>:<port>/em
login with credentials.
From deployments end,you can install the war file which will targeted to WC_Portlet server.
After that register the portlet WSRP url with your application and use it.
The above suggest is without the intervention of jdeveloper /webcenter.
Regards,
Hoque

Deploying web dynpro application into portal

hi
I have created a simple example in webdynpro in Netweaver developer studio, and I have deployed it into the portal whose version is EP6 SP9.
where can I see that deployed webdynpro application(in my case it is WebDynpro_Basics.ear) in the portal.
Can any one tell me the navigation part in the portal.
thanks
krish

Hi Krish,
You will find the deployed webdynpro application in webdynpro content administrator. You have to access it using portal administrator user-ID. the url is:
http://<hostname>:<J2EE engine port>/webdynpro/welcome
If you want to display the webdynpro application as an iView in the portal have a look at the following link.
http://help.sap.com/saphelp_nw04/helpdata/en/d8/6ee03fc2269615e10000000a155106/frameset.htm
Regards,
Aniket

Deploying ADF/JDeveloper portlets in WebSphere Portal

I'd like to use ADF/JDeveloper to build my application, but my customer is already heavily invested on a WebSphere Portal deployment platform. The JDeveloper/ADF documentation has extensive information on creating portlets in various ways, but they all seem focused exclusively on deploying in an Oracle platform. I have tried both the "Standards-Based" as well as the "JSF Portlet Bridge". I have tried to deploy the portlets in WebSphere Portal using both the generated WAR file, as well as by registering the WSRP producer. None work.
With the WAR file, WebSphere Portal seems to import the WAR file just fine, and I can add a portlet to a page, but the portlet always shows as "unavaiable"
With the WSRP producer, I can get something to show in the page, but the functionality within the portlet doesn't seem to work.
I've searched extensively, but cannot locate any documentation or use cases for deploying portlets from JDeveloper into WebSphere Portal. Does anyone have any thoughts?

Dvohra21, again, I apreciate the effort, but I think you're missing the fundamental question.
You've given me two types of articles/links. Some are generic WebSphere Portal documentation about deploying a portlet from a WAR file. Others are Oracle articles about who to generate portlets in JDeveloper, with examples deploying in Oracle/WebLogic servers. Unfortunately I don't have a problem with either of those.
I CAN deploy a portlet WAR file in WebSphere Portal, and sucessfully add it to a Portal page. I have done that with multiple WAR files generated from Rational Application Developer.
I CAN produce a WAR file from JDeveloper, following the instructions in the same resources you included, plus a few others.
The problem is, the WAR file from JDeveloper, does not successfully run on WebSphere Portal. I create a simple Hello World portlet in JDeveloper, and I can generate a WAR file from it, and seemingly deploy to WebSphere Portal. However when I add it to a Portal page, it always displays only a blank box with the text "This portlet is unavailable". This is in the same exact portal page, where the portlet created with Rational Application Developer shows up just fine right along side it.
Bottomline is, although there is a great deal of information an demos about generating portlets from JDeveloper within an Oracle environment, I could not find a SINGLE ONE, that goes through an end to end scenario where it is deployed in WebSphere Portal. Nothing in this forum, nothing in Oracle docs, and nothing I can find on a Google search.

Deploy jde portlets into webcenter

can anyone enlighten us about the way to deploy JDEdwards Portlets (Self service portals) into webcenter server(weblogic),
share if you have any docs related, it will be really helpful

You'll have to consult some of the JDE documentation for setting up portlets, but the basic procedure should be this:
1) Set up your JDEdwards portlets to be served - consult the JDE documentation for making portlets availble.
2) Register the JDE portlet producer with your WebCenter application. (You'll have to do this for each environment, with a warning that you will likely need to set up secure communications between your WebCenter app / WebLogic install and your JD Edwards environment.)
3) Once the producer is set up (both JDE and any secure communications), then registered with your WebCenter app you should be able to access the JDE portlets through the resource catalog.
That's the basics - but there's quite a bit of work to do behind the basics. :-)

Deploye par file into portal

When I tried to deploye the par file into portal using file->Export->PAR file, I am getting an error says "unfortunately the upload of your PAR was not sucessfule. ....
Error message: Upload seems to have faild" ... Because of this I am not able to upload the PAR file to portal. Any Idea? Please help
Pages: 1 Back to Thread List
Threads: [ Previous | Next ]

I tryied to do it manaulay and able to upload it. but when I run it, I am getting some error says
An exception occurred while processing a request for :
iView : com.flightsafety.hr.EmployeeAddressChange.EmployeeAddressChangenew
Component Name : com.flightsafety.hr.EmployeeAddressChange.EmployeeAddressChangenew
Internal error: empty page context.
Exception id: 10:14_10/01/07_0214_6394050
See the details for the exception ID in the log file
Have any Idea?

JSR168 portlet packaging?

From the JSR168 spec, (which is similar to how other portals seem to behave
with their proprietary APIs), a JSR168 portlet application appears to be a
WAR with a portlet.xml and web.xml conforming to the requirements of the
spec, that can then be installed in any portal.
From my superficial knowledge based on skimming the WL8.1 portal docs
recently, WL portlet development appears to be done within a Portal WAR such
that the portlet(s) are just components of the portal war itself.
How are these two supposed to work together in the WLP env? Say I develop a
couple JSR168 portlets in my own Java environment (emacs :-) and then WAR
them up and install them into Jetspeed-2 and another 168 compliant portal
when available (eg, IBM's 5.something). I believe those would accept my
portlet WAR and keep them in that WAR and just reference them from their
Portals. How would WL8.1.x handle such development (outside of Workshop/WL)
and deployment to a WL8.1.x portal? Do I have to merge my JSR168 based
portlet WAR (and thus a web.xml and portlet.xml merge) into the Portal WAR
(eg, if I want to ship a script to deploy my portlet WAR into an existing
WL8.1 portal?) or will WL8.1.x be able to reference a Portlet WAR outside of
a Portal WAR?
TIA - a confused potential portlet developer...

I agree with what Joe said...
BTW, I (and I assume Joe) think JSR168 is a good thing - and it's great that
WLP has the first prototype of it out there - don't get me wrong, I like it,
I'd just prefer if it were easier to deploy to given portlets coming in from
multiple sources being added into an existing portal. From Joe's case, he
probably doesn't want to have to merge the portlet.xml files. From my case
as a supplier of portlets, I'd rather not have to have to create different
install tools/docs/procedures for my customers for each portal vendor now
that I can have standard portlets based on JSR168...
"Joe C." <[email protected]> wrote in message
news:[email protected]...
You can always import any arbitrary webapp using the WLW as a portalproject
I'm not sure that solves my problem or the one ISV was talking about(which
I assume is the same).
I am not talking about importing a webapp (containing portlets or nto) and
making it be my portal.
- Assume I'm already developing a portal with some in-house developed
portlets.
- I want to get 3 JSR168 portlets from SAP (just picked a random vendorout
of the air) and add them to my portal.
- I want to get 2 JSR168 portlets from Siebel (ditto)
- And I need one Domino portlet from that other 3 letter vendor (ditto)
- Each of those vendors is likely to build JSR168 portlets that can be
installed/used in any JSR168 compliant portal, so they can stop buildingall
the various per-vendor proprietary API portlets.
- Each of those vendors needs to package up their portlets for
shipping/install.
- Given that JSR168 describes the Web App layout for packaging a portlet,
each of those vendors is likely to package their portlets up in a WAR.
- Some JSR168 compliant portals (I believe) will be able to just install
those WARs and use them as is from the Portal WAR and drop them on pages.
- WLP 8.1 appears to require that I unpack/extract those WARs and mergethe
portlet.xml and contents of each of those WARs with my existing Portal WAR
that I want to add those portlets to. Tell me why this is better?
To your earlier comments made here:
The pitfall of this approach is that webapps depend on each other towork correctly
Well yeah, I expect my portal to depend on my portlets - of course.
which is against the spirit of webapps.I disagree - EARs depend on the WARs within them. Cooperating WARs can
depend on each other too.
A deployer should be able to deploy/undeploy any webapp withoutaffecting the functionality of other
webapps - which would be case in the model you describe.Of course, if you remove a portlet that a portal depends on, I wouldexpect
it to break .
In addition, there are security issues that the deployer must be awareof.
Of course. That's the case with any J2EE deployment no matter how many
EARs/WARs you're deployiing.
"Subbu Allamaraju" <[email protected]> wrote in message
news:[email protected]...
Joe,
You can always import any arbitrary webapp using the WLW as a portal
project, and during that process you'll have the opportunity to
automatically update the descriptors (and also adding the correct jar
files). There is no need to hand-merge descriptors unless you want to.
Subbu
Joe C. wrote:
Please tell me it's going to get better.
That would make sense if one were developing all their own portlets
for
their portals.
But I (and most people I know) as a customer, that needs to aggregate
portlets from multiple (possibly many) 3rd parties, such as the big 4
application vendors, am going to need to know how those standardJSR168
portlets work and are configured so that I can hand-merge them into my
company's portal?
As an end user it doesn't really help me that much that I can developmy
own
portlets to JSR168. The whole point of JSR168 is that portlet vendorsthat
build portlets for others to install into their portals will be able
to
build one set of portlets that can then be installed in any compliant
portal. This limitation seems to prevent that from beingcommonplace/useful
(given how few people are going to know how to do such merges - theyjust
want to install 3rd party portlets and drop them on pages). I reallyhope
Workshop provides a user friendly way to integrate such 3rd party
JSR168
portlets or WLP will be missing the whole point of having such astandard in
the first place. I agree with the ISV that started this
conversation -
please provide a means for me to install 3rd party portlets withouthaving
to hand-merge XML configuration files.
"Subbu Allamaraju" <[email protected]> wrote in message
news:[email protected]...
isv wrote:
From the JSR168 spec, (which is similar to how other portals seem to
behave
with their proprietary APIs), a JSR168 portlet application appears to
be
a
WAR with a portlet.xml and web.xml conforming to the requirements of
the
spec, that can then be installed in any portal.For all practical purposes, a portal app is a web app, with the only
differece being the portlet.xml file. So, a portal app contains
portlets
in addition to things that typically exist in a webapp.
How are these two supposed to work together in the WLP env? Say I
develop a
couple JSR168 portlets in my own Java environment (emacs :-) and thenWAR
them up and install them into Jetspeed-2 and another 168 compliantportal
when available (eg, IBM's 5.something). I believe those would accept
my
portlet WAR and keep them in that WAR and just reference them fromtheir
Portals. How would WL8.1.x handle such development (outside ofWorkshop/WL)
and deployment to a WL8.1.x portal? Do I have to merge my JSR168
based
portlet WAR (and thus a web.xml and portlet.xml merge) into thePortal
>>>
WAR
(eg, if I want to ship a script to deploy my portlet WAR into anexisting
WL8.1 portal?) or will WL8.1.x be able to reference a Portlet WARoutside of
a Portal WAR?For WLP, the unit of development/deployment is a webapp. We're aware
that some implementations (including the ones you mention) follow a
model where portal deployment involves several web apps with portlets
aggregated by a portal deployed in one of those webapps. The pitfall
of
this approach is that webapps depend on each other to work correctly -
which is against the spirit of webapps. A deployer should be able to
deploy/undeploy any webapp without affecting the functionality ofother
webapps - which would be case in the model you describe. In addition,
there are security issues that the deployer must be aware of.
Having said this, if your portlets are already bundled into a WARfile,
you need to merge the portlets into the portal webapp. Or, you couldlet
WL convert your webapp into a portal webapp. We don't intend tosupport
portlet referencing from other webapps.
Subbu

Writing a JSR168 portlet WITHOUT using Jdeveloper or "wizards"

I have a JSR168 portlet that is built using Maven (http://maven.apache.org/ if you don't know what that is).
It deploys and operates perfectly well into a portlet container such as Pluto (the standard, reference container from Apache).
Pluto supplies a Maven plugin, that takes the vanilla web.xml and other configuration e.g. portlet.xml and adds the necessary configuration to run the portlet in the container. I believe there is an Ant plugin that does exactly the same thing.
It adds the following conf to teh web.xml;
<servlet>
<servlet-name>my-portlet-name</servlet-name>
<servlet-class>org.apache.pluto.core.PortletServlet</servlet-class>
<init-param>
<param-name>portlet-name</param-name>
<param-value>my-portlet-name</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>my-portlet-name</servlet-name>
<url-pattern>/PlutoInvoker/my-portlet-name</url-pattern>
</servlet-mapping>
This is the "magic" that glues my portlet to the portlet container.
What I wish to know, is how to make my JSR168 portlet deploy into Oracle Portal 10g without EVER using JDeveloper. What is the 'magic' I have to apply to my web.xml or portlet.xml or other configuration that will men I can deploy my portlet war into the app server and make it talk turkey with the portal container. I can cope with just having a customised web.xml that I have to copy into the WAR file if need be ... if I could find some guidance what should be in that file.
It seems that every search I've done in google or though the doco we have here starts with "Start Jdeveloper and select XXX in the portlet wizard".
I do not use Jdeveloper and nor will I. I will continue to build my Java code in a correct fashion, i.e. on the command line with my standard build tools that don't involve the IDE. Don't get me wrong, I use an IDE, but one should never be mandated. In my book, "wizards" are about the worst imaginable way to get any programming task completed.

Hi Marcel
With respect, it's patently obvious that we know how to develop a portlet without Jdeveloper, because if you read the message you would have been able to discern that this is the way we are accustomed to doing it, and it's faster, easier and more portable that way. I've been doing J2EE development since the first version of the spec and well before there was an Oracle implementation of it.
You don't actually need an EAR file, as a WAR will suffice and the dcmctl command-line utility can supply everything else in its arguments (like, context-path and the like), and it allows each WAR artifact to be deployed in different times, i.e. when they are built on the integration server. I find EAR files usually too heavyweight especially as I rarely write EJBs, as opposed to using e.g. Spring.
Using the web browser is not an option for automated deployment and acceptance testing from an integration build server.
Configuring the portal side of things looks decidedly a different matter and I've not found anyway to do it from the command line, it demands the browser, which is a let-down.
It's terribly disappointing the paucity of information about automation of deployment as opposed to the positively verdant amount of presentations, tutorials and documentation that assumes top-to-bottom Oracle tooling and environment and browser-based configuration. Even where it's actually possible Oracle doesn't seem to want to tell people about it or do as I believe they should, which is regard this form of deployment and configuration as the default way to teach developers how to use their products. None of this helps build and deploy to Oracle products using test-driven development, continuous integration, and automated acceptance testing, all of which are usually regarded as essential parts of a modern developers toolkit by the best minds in the business.
So after we're left alone to discover how to do this by ourselves for a month you can forgive my disappointment at being lectured like I was some neophyte who doesn't know how to make a WAR file with textedit.

How to deploy existing JSR 168 portlets (in war file) into portal?

I have some JSR 168 portlets built and tested against another portal server that I would like to deploy in Bea portal server. They are packaged as a war file. I have a test portal and I am able to "develop" some new portlets in the Workshop but what I really want to do is just deploy the portlets as is. I have deployed the war using the web based deployment tool but I don't know how to "use" the portlets within a portal. Shouldn't this be easy? The docs don't discuss it much. Thanks for any help.
-Andrew

OK I found the answer:
http://dev2dev.bea.com/products/wlportal81/articles/deployJava81sp3.jsp

Integration of JSR-168 portlet into Portal - Complete Guide

Hi there,
the CE 7.1 is described to be compatible with JSR-168 portlets.
Our Company has developed a JSR-168 portlet which comes as a WAR-File
which can be easily included in other application server and portals (WebShpere, Apache).
But integration in SAP Netweaver fails - I am missing a complete documentation
which describes me the necessary steps to integrate a JSR-168 portlet application
into the SAP Application Server and also how to integrate the GUI into a View of the NW portal.
PLEASE HELP ME!!!
Things I tried - Things I failed:
- Imported a EAR-File into Developement Studio and tried to add it to Server
-> Message "EAR Project: ... should have the SAP specific facet in order EAR to be built."
- Deployement via "Deployement Tool" of Netweaver 2.0 (2004s) worked
and I was able to start app but no integration into NW portal view was possible
(Where is the deployement tool in NW 7.1 CE?!?!?)
- I wanted to create a PAR-File by a WAR-File but dont know how?
- I did not find any iView template which is for my portlet type.
Did anyone out there has the same probs or could help me....
Thanks on advance,
Andi-)
Edited by: Markus Sümmchen on Oct 6, 2008 1:47 PM

Hi Markus,
There is no complete guide for integration of JSR-168 portlets into a portal; however Diyan is correct.
In a nutshell, once you have deployed your portlet, you use GPAL technology in the SAP NetWeaver Portal of CE to create an iView wrapper in the PCD. All of this done by a portal content admin in the Portal Content Studio. Your deployed portet should be displayed in the "Portlets" repository within the Portal Catalog of the Portal Content Studio.
For conceptual and how-to documentation, refer to the following SAP Help Portal links:
- Generic Portal Application Layer (GPAL) Repositories: http://help.sap.com/saphelp_nwce10/helpdata/en/44/5e93dc35624ddee10000000a1553f7/frameset.htm
- Integrating Applications into the Portal: http://help.sap.com/saphelp_nwce10/helpdata/en/45/90e8bfaec26c4ee10000000a1553f7/frameset.htm
- Working with GPAL Repositories: http://help.sap.com/saphelp_nwce10/helpdata/en/44/5b96b37b6f4de1e10000000a1553f7/frameset.htm
Please let me know if this works for you.
Michael

Deploying JSR168 Portlet's into Portal

Similar Messages

Maybe you are looking for