Converting JSR 168 portlets ( .portlet files in WL Workshop) to .war format

We are using WebLogic Workshop to create JSR 168 Portlets. These portlets
should be deployed to the Application infra strutcture using BroadVision
portal Admin tool, which takes portlet applications only in .war format. so
We are looking for a functionality which would convert .portlet from WLW to
war format.
How do we go about for the same?
Waiting for inputs and suggestions,
Thanks & Regards,
Swamy

Similar Messages

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

How to convert JSR-168 compliant Portlets into SAP iviews

Hi All,
Its very urgent requirement for me...
<b>How to convert JSR-168 compliant Portlets into SAP Enterprise Portal supported iViews in SAP NetWeaver 2004 or 2004s.</b> Can you please tell me any tools are available for conversion or is there any another procedure to achieve this problem.
At last can we ach
Each answer will be awarded with points.
Regards
Sreedhar G

Hi Sreedhar,
Is there anyway to display Standard Business packages content in IBM websphere portal.If there is anyway please let me know.
thanks,
Anil

How to convert JSR 168 compliant Portlets into SAP supported iViews.

Hi,
How to convert JSR 168 compliant Portlets into SAP supported iViews in SAP NetWeaver 2004.
Thanks & Regards
Siva

Guys,
JSR is not supported untill NW05. Please check this
/thread/176954 [original link is broken]
Akhilesh

JSR 168 portlets

Hi,
Once again I find myself struggling to keep on top of the bleeding edge of Portal technology - I remember developing PL/SQL portlets in WebDB 3.0 Beta when there was no documentation not too many years ago!
I am working with a client that wants to make some "legacy" PL/SQL portlet applications portable to SAP Portal. SAP NetWeaver support for JSR 168 is planned in the near future, and the client wants to be able to publish the portlets there. The existing applications are deployed in Oracle Portal and consist of 30 PL/SQL, along with a few bits of custom java / servlet functionality for file upload and download. Some of these portlets have very complex functionality both clientside (javascript) and serverside (SQL).
Am I correct in assuming that these will have to be redeveloped as JSR 168-compliant JSP portlets...?
From what I can gather there shouldn't be too many restrictions, but I was wondering if anyone else has gone through or is going through this kind of process and/or has any tips or suggestions?
Thanks for your assistance,
Mark Austin

Hi,
Yes. You should convert these portlets to jsr 168 portlets. But there is no tool available in Oracle Portal to convert these portlets to jsr 168 portlets.
Thanks,
Sharmila

Control Height Of Region Containing JSR-168 Portlet

We are in the process of converting some portlets from Oracle Reports to JSR-168. Our intitial portal page would contain the Oracle Reports portlets within the height of the region. The same output created by a JSR-168 portlet causes the region to grow vertically, which pushes the regions below it down thereby creating large gaps.
The Oracle Reports portlet would have a scrollbar that allows the user to see all of the content hidden below the bottom of the region. No matter what css I apply, I cannot make the same thing happen with the JSR-168 portlet.
Does anyone have any tips for constraining the vertical size of the regions so that they do not grow to accommodate all of the content but instead produce a scrollbar?

Andre,
When you drag a project folder over to a portal, workshop doesn't
scan/detect the folder contents and create portlets accordingly. So, you
are creating the wrong portlet type.
In this case, you need to create the portlet via the file wizard. Just
right-click on the directory where you want the portlet to live and
select 'New->Portlet' to get the wizard. Then, select the portlet type:
'Java Portlet'.
-robert
Andre Ranvik wrote:
Is there anybody who has experience with deploying JSR 168 portlets on WLS 8.1SP2
that have been "handcoded". The portlets I am trying to deploy are these:
http://developers.sun.com/prodtech/portalserver/reference/techart/jsr168/#2
I have tried to manually import the individual folders/files, modified the portlet.xml,
and dropping the folder containing the jsp's onto a portal within Workshop. I
respond "yes" to the question whether I want it to create a portlet. The problem
is that it doesn't recognize this to be a JSR 168 portlet (or it doesn't support
it??).
I have also tried to deploy a portlet within a WAR file, but no such luck.
Support for JSR 168 implies that one would expect support for deploying JSR 168
portlets developed on other platforms.
I am hoping for a step-by-step set of instructions on how this can be accomplished.
Thanks a bunch!
Andre Ranvik

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>

JSR-168 Portlet code generation 'hangs' in JDev 10.1.3.2.0/JDK 1.6

Yes, I know JDK 1.6 is not officially supported by JDeveloper 10.1.3.2.0.....
However up until now stability has been reasonably fair of the IDE - beside the occasional 'out-of-synch' status of JDeveloper, which so it seems still hasn't but fully resolved (and which I am familiar with). When creating a JSR 168 portlet using the wizard, the wizard completes without an error - but the sources never get generated. What I'm seeing is the message: "Building source index for project "Portlets.jpr" on the left-hand side of the statusbar and a progress-bar on the right-hand side with the label: "Scanning sources". This "never" ends and the only thing left to do is restart JDeveloper.
Any ideas whether this is JDK 1.6 related?

Have tried this with JDK 1.5 setting, but no luck. I'm guessing this problem is more related to the fact I'm using Windows Vista than JDK 1.6. Last week I was able to generate JSR 168 portlet code on a file system that was pre-Vista formatted. Last weekend I reinstalled my machine and formatted my hard drives using Vista... I'm guessing that somehow this results in problems generated the sources.
Or is this too far fetched...?

How to deploy a JSR-168 Portlet in Weblogic?

I am running WLS 8.1 with the advanced JSR-168 support installed (not yet running
SP2). I have a JSR-168 portlet war that I had been testing in the JSR-168 reference
implementation (pluto). Can someone please point me to the instructions on how
to now import my portlet war into Workshop so that I can add it to my Weblogic
portal?
Thanks!
-David

You cannot simply "deploy" a JSR 168 portlet into Weblogic using a WAR file in
my experience. This is what I did to achieve deployment of a JSR 168 portlet in
BEA WLS 8.1SP2:
* File | New | Portlet | Java Portlet
* Just type in the name of your view class name when asked for it.
This creates a "YourAppName.portlet" file, which I believe Bea requires for any
Portlet in order to make it available for use in their portals.
* Add your files (*.jar, *.java *.jsp, etc).
* Modify WEB-INF/portlet.xml to include all required descriptor elements that
you have in your WAR file (keep in mind that there is only one portlet.xml for
all portlets in a single web application)
I was unable to use redirects for some reason, but it worked fine with include.
"David" <[email protected]> wrote:
>
I am running WLS 8.1 with the advanced JSR-168 support installed (not
yet running
SP2). I have a JSR-168 portlet war that I had been testing in the JSR-168
reference
implementation (pluto). Can someone please point me to the instructions
on how
to now import my portlet war into Workshop so that I can add it to my
Weblogic
portal?
Thanks!
-David

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

Error : Content not available in jsr 168 portlet in sun one portal 7.1

I deployed jsr 168 portlet in Sun one portal and i have added that portlet ot one channel. But i am unable to see the content of that portlet
NewPortlet
ERROR: Content is not available
In the log file i am getting a null pointer exception
java.lang.NullPointerException
     at com.sun.portal.portletappengine.impl.RequestResponseFactoryImpl.<init>(RequestResponseFactoryImpl.java:111)
     at com.sun.portal.portletappengine.PortletAppEngineServlet.init(PortletAppEngineServlet.java:121)
     at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1099)
     at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:931)
     at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4183)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:4535)
     at com.sun.enterprise.web.WebModule.start(WebModule.java:241)
     at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:827)
     at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:811)
     at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:646)
     at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1331)
     at com.sun.enterprise.web.HttpServiceWebContainer.loadWebModule(HttpServiceWebContainer.java:867)
     at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1040)
     at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:160)
     at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:246)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:918)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:905)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:427)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:139)
     at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:288)
     at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:155)
     at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:258)
     at com.sun.enterprise.deployment.phasing.StartPhase.runPhase(StartPhase.java:87)
     at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:71)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:639)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:361)
     at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:396)
     at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:703)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:305)
     at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:360)
     at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
     at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
     at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
     at $Proxy1.invoke(Unknown Source)
     at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:272)
     at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:38)
     at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:92)
     at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:69)
     at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:94)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:767)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:264)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:178)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
     at com.sun.enterprise.web.connector.httpservice.HttpServiceProcessor.process(HttpServiceProcessor.java:235)
     at com.sun.enterprise.web.HttpServiceWebContainer.service(HttpServiceWebContainer.java:2114)
Please provide some help

Hi,
Thanks for bringing this issue. Yes, the message should be SEVERE. This will be fixed.
You may also want to subscribe to [email protected] and bring up any issues, enhancements.
Regards,
Deepak

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

Problems with JSR 168 Portlets

Hi!, I�m working with JSR 168 Portlets and after successfully deploying it into the portal (6.2) I�m not able to get any content. I�ve already made a war (I couldn�t make the studio 5u1, (PB 2) simulate it :( ), and it seems to be correctly deployed inside appsrv (7). I placed some JSP�s and HTML�s and they are available from a browser but not from the portal. The first error I got was Channel time out but then I managed to get Content not Available. It seems that the portal is not able to reach the JSP�s but I�m not sure. Is there any restriction about folders with this or just by deploying the war makes everything? Is it necessary to set the files inside the portal folder? I�ve read the manuals many times and I can�t find a suitable tutorial (the only I got is one to make a provider or a channel :( ), nor a detaliled how to. I�ll thank any advice.
Cheers , Pablo.

Hi, Thanks for answering, the log says the following:
2004/04/28 12:13:32.372 ART | null | WARNING | Thread-74 | {default={bookmarkContentPage=|/bookmarkportlet/content.jsp, bookmarkEditPage=|/bookmarkportlet/edit.jsp, bookmarkHelpPage=|/bookmarkportlet/help.jsp, targets=|Sun home page=http://www.sun.com|Oracle home page=http://www.oracle.com|AOL home page=http://www.aol.com, windowPref=|all_new}, isReadOnly={bookmarkContentPage=false, bookmarkEditPage=false, bookmarkHelpPage=false, targets=false, windowPref=false}} (original) | -
2004/04/28 12:13:32.373 ART | null | WARNING | Thread-74 | Loading __Portlet__bookmarkContentPage value is |/bookmarkportlet/content.jsp | -
2004/04/28 12:13:32.380 ART | null | INFO | Thread-75 | PortletContainer.invokePAE(): invoking:
app name /portletsamples
portlet name NotepadPortlet
action RENDER | -
2004/04/28 12:13:32.399 ART | null | WARNING | Thread-75 | {default={contentPage=|/notepad/content.jsp, editPage=|/notepad/edit.jsp, helpPage=|/notepad/help.jsp, categories=, displayMax=|5}, isReadOnly={contentPage=false, editPage=false, helpPage=false, categories=false, displayMax=false}} (original) | -
2004/04/28 12:13:32.400 ART | null | WARNING | Thread-75 | Loading __Portlet__contentPage value is |/notepad/content.jsp | -
2004/04/28 12:13:32.405 ART | null | INFO | Thread-76 | PortletContainer.invokePAE(): invoking:
app name /portletsamples
portlet name WeatherPortlet
action RENDER | -
2004/04/28 12:13:32.424 ART | null | WARNING | Thread-76 | {default={zip=|95054, unit=|F, contentPage=|/weather/weatherView.jsp, editPage=|/weather/weatherEdit.jsp, helpPage=|/weather/weatherHelp.jsp}, isReadOnly={zip=false, unit=false, contentPage=false, editPage=false, helpPage=false}} (original) | -
2004/04/28 12:13:32.425 ART | null | WARNING | Thread-76 | Loading __Portlet__zip value is |95054 | -
2004/04/28 12:13:32.426 ART | null | WARNING | Thread-76 | {default={zip=|95054, unit=|F, contentPage=|/weather/weatherView.jsp, editPage=|/weather/weatherEdit.jsp, helpPage=|/weather/weatherHelp.jsp}, isReadOnly={zip=false, unit=false, contentPage=false, editPage=false, helpPage=false}} (original) | -
2004/04/28 12:13:32.427 ART | null | WARNING | Thread-76 | Loading __Portlet__unit value is |F | -
2004/04/28 12:13:32.466 ART | null | WARNING | Thread-74 | {default={bookmarkContentPage=|/bookmarkportlet/content.jsp, bookmarkEditPage=|/bookmarkportlet/edit.jsp, bookmarkHelpPage=|/bookmarkportlet/help.jsp, targets=|Sun home page=http://www.sun.com|Oracle home page=http://www.oracle.com|AOL home page=http://www.aol.com, windowPref=|all_new}, isReadOnly={bookmarkContentPage=false, bookmarkEditPage=false, bookmarkHelpPage=false, targets=false, windowPref=false}} (original) | -
2004/04/28 12:13:32.467 ART | null | WARNING | Thread-74 | Loading __Portlet__targets value is |Sun home page=http://www.sun.com|Oracle home page=http://www.oracle.com|AOL home page=http://www.aol.com | -
2004/04/28 12:13:32.468 ART | null | WARNING | Thread-74 | {default={bookmarkContentPage=|/bookmarkportlet/content.jsp, bookmarkEditPage=|/bookmarkportlet/edit.jsp, bookmarkHelpPage=|/bookmarkportlet/help.jsp, targets=|Sun home page=http://www.sun.com|Oracle home page=http://www.oracle.com|AOL home page=http://www.aol.com, windowPref=|all_new}, isReadOnly={bookmarkContentPage=false, bookmarkEditPage=false, bookmarkHelpPage=false, targets=false, windowPref=false}} (original) | -
2004/04/28 12:13:32.469 ART | null | WARNING | Thread-74 | Loading __Portlet__windowPref value is |all_new | -
2004/04/28 12:13:32.745 ART | null | WARNING | Thread-75 | {default={contentPage=|/notepad/content.jsp, editPage=|/notepad/edit.jsp, helpPage=|/notepad/help.jsp, categories=, displayMax=|5}, isReadOnly={contentPage=false, editPage=false, helpPage=false, categories=false, displayMax=false}} (original) | -
2004/04/28 12:13:32.745 ART | null | WARNING | Thread-75 | Loading __Portlet__categories value is | -
2004/04/28 12:13:32.746 ART | null | WARNING | Thread-75 | {default={contentPage=|/notepad/content.jsp, editPage=|/notepad/edit.jsp, helpPage=|/notepad/help.jsp, categories=, displayMax=|5}, isReadOnly={contentPage=false, editPage=false, helpPage=false, categories=false, displayMax=false}} (original) | -
2004/04/28 12:13:32.747 ART | null | WARNING | Thread-75 | Loading __Portlet__displayMax value is |5 | -
2004/04/28 12:22:38.703 ART | null | INFO | Thread-81 | PortletContainer.invokePAE(): invoking:
app name /SUNONEPortlets
portlet name MGPortletSUNONE
action RENDER | -
2004/04/28 12:22:38.740 ART | null | INFO | Thread-82 | PortletContainer.invokePAE(): invoking:
app name /portletsamples
portlet name JSPPortlet
action RENDER | -
2004/04/28 13:12:31.240 ART | null | INFO | Thread-93 | PortletContainer.invokePAE(): invoking:
app name /SUNONEPortlets
portlet name MGPortletSUNONE
action RENDER | -
2004/04/28 13:12:31.279 ART | null | INFO | Thread-94 | PortletContainer.invokePAE(): invoking:
app name /portletsamples
portlet name JSPPortlet
in the file portletcontainer.log, I don�t understand that about DNS or proxy if I�m trying to render a local JSP. I�ve just deployed the JSP inside the portlet application war file. What do the pipes "|" mean?, is that the mistake?. Thanks in advance!!, Pablo :)

How to DEPLOY and ACCESS JSR 168 portlet in weblogic server

I installed Web Logic Server 10.3, Web Logic Portal 10.3 and Workshop 10.3 on my system. I created a sample portal application in workshop and able to see the output with the help of workshop.
1. I imported JSR 168 portlet in "Import Utility" and able to see the deployed war in Deployments folder of "Weblogic Server Administration Console", but unable to test that deployed portlet. That Deployed portlet was unable to see in "Weblogic Portal Administration Console"
2. How can i import JSR 168 portlet from workshop and view that portlet?
3. How can i import JSR 168 portlets from "Weblogic Portal Administration Console" and view them?
Please help me out with the solutions and procedures...
Thanking you in advance,
Bhargavi Javvadi.

Create a WAR file for your Web app
Put it where the Weblogic 8.1 docs tell you to.
Restart Weblogic server.
%

How to deploy existing JSR-168 portlet in WLP 10.0?

I have a JSR-168 portlet packaged in a .war file and am trying to deploy in WLP 10.0. This seems like a common question that looks to be covered thoroughly for version 8.0 in the link:
[url http://dev2dev.bea.com/pub/a/2004/09/deployJava81sp3.html]
Those instructions no longer work, the tool is referencing classes that don't seem to exist in 10.0 and so it won't run.
I am currently attempting to move the pieces by hand into a new Workshop Web Project, but was hoping that by now there would be an easier way.
Any suggestions?

I stumbled across the answer after I had manually merged the portlet into an existing web project. It is actually pretty straight forward.
1. Right click on the web project, select import.
2. You will be presented with three options - war file, ear file, import.... The ware war file option is so tempting, but it is not what you want. Choose Import... to get a longer list of options.
3. Under "Other" you will see "Portlet from Archive".
This does exactly what I wanted, with the exception of the web.xml. The files are not merged, you can either skip it or overwrite it. Small price to pay for the convenience.

Converting JSR 168 portlets ( .portlet files in WL Workshop) to .war format

Similar Messages

Maybe you are looking for