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

Similar Messages

  • IPC with JSR 168 portlets and WebLogic Portal 9.2.3

    I have seen examples in this forum indicating that you can implement IPC in JSR 168 portlets by doing the following:
    1. Fire a custom event in the processAction() method of one portlet.
    2. Handle the custom event in another portlet that is listening for the event.
    3. The listening portlet should contain a method such as
    processMyCustomEvent(ActionRequest req, ActionResponse resp, Event event)4. The method is mapped as a handler for the custom event in the listening portlet's +.portlet+ file:
    <netuix:javaPortlet definitionLabel="jsr168EventPortlet" title="JSR168 event portlet">
       <netuix:handleCustomEvent event="myCustomEvent" eventLabel="customEventOne" filterable="true" description="custom event handler">
          <netuix:invokeJavaPortletMethod  method="processMyCustomEvent" />
       </netuix:handleCustomEvent>
    </netuix:javaPortlet>However, the examples I've found in this forum seem to pertain only to installations of WebLogic Portal 10.x or higher.
    Does this JSR 168 IPC approach work for WebLogic Portal 9.2.3?
    (The example provided in the WL Portal 9.2.3 documentation uses a Backing File to handle the event instead of invoking a method in the portlet class itself.)
    Any clarification that can be provided would be much appreciated. Thanks.
    Edited by: user13297286 on Jun 15, 2010 2:02 PM

    Hello,
    Yes, JSR168 portlet IPC is supported in WLP 9.2, and you can use the "invokeJavaPortletMethod" (recommended) or the invokeBackingFileMethod in the .portlet file to configure your portlet to receive events.
    Kevin

  • 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

  • WSRP or JSR-168 Portlets with PDK-Java

    Is it possible to create WSRP or JSR-168 compliant portlets with PDK-Java or Bi beans?
    Thanks,

    When PDK-Java was designed 4-5 years ago, there was no portlet standard on the horizon. While from an architecture point of view PDK-Java is very similar to WSRP, it uses a proprietary protocol. Therefore you can't expose PDK-Java portlets through WSRP.
    You can, however, leverage the BI-beans in JSR 168 portlets, just like in any other Java environment.
    Peter

  • 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...?

  • Deploying JSR-168 portlets error in Weblogic Portal 9.2MP2

    Hello,
    We're using WebLogic 9.2MP2 and ALBPM 5.7 SP2 enterprise server standalone. We want display in our portal the In-Box to the user as a JSR-168 portlet.
    We are following the steps in the following guide:
    http://edocs.bea.com/albsi/docs57/adminguide/jsr-168/ad_jsr168_wl92_deployingalbpmjsr168portlets.htm
    but when we try to add a new remote producer using the WebLogic Portal Administrator Console we get this error ( in the "Find producer" step):
    com.bea.jsptools.portal.helpers.wsrp.AddProducerControlException: java.rmi.RemoteException: Remote method invocation failed: weblogic.xml.crypto.wss.WSSecurityException: Unable to add security token for identity.; nested exception is:
         weblogic.xml.crypto.wss.WSSecurityException: Unable to add security token for identity
         at com.bea.jsptools.portal.helpers.wsrp.AddProducerHelper.getProducerForWsdl(AddProducerHelper.java:712)
         at com.bea.jsptools.portal.helpers.wsrp.AddProducerHelper.access$100(AddProducerHelper.java:61)
         at com.bea.jsptools.portal.helpers.wsrp.AddProducerHelper$FindProducers.producerWsdl(AddProducerHelper.java:249)
         at com.bea.jsptools.portal.helpers.wsrp.AddProducerHelper$FindProducers.run(AddProducerHelper.java:235)
         at portalTools.definitions.portletProducers.wizard.AddProducerWizardController.runAction(AddProducerWizardController.java:566)
         at portalTools.definitions.portletProducers.wizard.AddProducerWizardController.doIfValid(AddProducerWizardController.java:542)
         at portalTools.definitions.portletProducers.wizard.AddProducerWizardController.selectProducerAction(AddProducerWizardController.java:172)
         at sun.reflect.GeneratedMethodAccessor956.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
         at java.lang.reflect.Method.invoke(Method.java:615)
         at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:878)
         at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:808)
         at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:477)
         at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:305)
         at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:335)
         at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:51)
         at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
         at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:95)
         at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2042)
         at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:90)
         at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2114)
         at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
         at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:554)
         at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:851)
         at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:630)
         at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:157)
         at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
         at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1169)
         at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:688)
         at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:144)
         at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:107)
         at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:99)
         at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:180)
         at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:168)
         at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:222)
         at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:178)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:351)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:361)
         at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:128)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:339)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:330)
         at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:162)
         at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:137)
         at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:370)
         at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:229)
         at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:183)
         at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:221)
         at com.bea.netuix.servlets.manager.PortalServlet.service(PortalServlet.java:600)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         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.bea.jsptools.servlet.PagedResultServiceFilter.doFilter(PagedResultServiceFilter.java:82)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:251)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3243)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    Caused by: java.rmi.RemoteException: Remote method invocation failed: weblogic.xml.crypto.wss.WSSecurityException: Unable to add security token for identity.; nested exception is:
         weblogic.xml.crypto.wss.WSSecurityException: Unable to add security token for identity
         at com.bea.wsrp.proxy.WseeProxy.dispatch(WseeProxy.java:274)
         at com.bea.wsrp.proxy.WseeProxy.sendMessage(WseeProxy.java:131)
         at com.bea.wsrp.proxy.WseeProxy.dispatch(WseeProxy.java:103)
         at com.bea.wsrp.proxy.ProxyBase.invoke(ProxyBase.java:438)
         at $Proxy83.getServiceDescription(Unknown Source)
         at com.bea.wsrp.client.ProducerAgentImpl.getServiceDescription(ProducerAgentImpl.java:93)
         at com.bea.wsrp.client.ProducerAgentImpl.getServiceDescription(ProducerAgentImpl.java:55)
         at com.bea.jsptools.portal.helpers.wsrp.ProducerRegistryControlImpl.getServiceDescription(ProducerRegistryControlImpl.java:205)
         at com.bea.jsptools.portal.helpers.wsrp.ProducerRegistryControlBean.getServiceDescription(ProducerRegistryControlBean.java:133)
         at com.bea.jsptools.portal.helpers.wsrp.AddProducerHelper.getProducerForWsdl(AddProducerHelper.java:704)
         ... 80 more
    Caused by: weblogic.xml.crypto.wss.WSSecurityException: Unable to add security token for identity
         at weblogic.wsee.security.wss.SecurityPolicyDriver.processIdentity(SecurityPolicyDriver.java:175)
         at weblogic.wsee.security.wss.SecurityPolicyDriver.processOutbound(SecurityPolicyDriver.java:73)
         at weblogic.wsee.security.WssClientHandler.processOutbound(WssClientHandler.java:69)
         at weblogic.wsee.security.WssClientHandler.processRequest(WssClientHandler.java:53)
         at weblogic.wsee.security.WssHandler.handleRequest(WssHandler.java:72)
         at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:127)
         at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:100)
         at weblogic.wsee.ws.dispatch.client.ClientDispatcher.dispatch(ClientDispatcher.java:101)
         at com.bea.wsrp.proxy.WseeProxy.dispatch(WseeProxy.java:236)
         ... 89 more
    and this is the content of the wsdl
    <s0:definitions name="" targetNamespace="urn:oasis:names:tc:wsrp:v1:wsdl">
    <s0:import location="http://esmadaix01:7001/fportlets/producer/wsrp-1.0/markup?WSDL/wlp_wsrp_v1_bindings.wsdl" namespace="urn:bea:wsrp:ext:v1:bind"/>
    <s0:import location="http://esmadaix01:7001/fportlets/producer/wsrp-1.0/markup?WSDL/wsrp_v1_bindings.wsdl" namespace="urn:oasis:names:tc:wsrp:v1:bind"/>
    <s1:Policy s2:Id="ProducerDefaultPolicy">
         <s1:All>
         <wssp:Identity>
         <wssp:SupportedTokens>
    <wssp:SecurityToken TokenType="http://docs.oasis-open.org/wss/2004/01/oasis-2004-01-saml-token-profile-1.0#SAMLAssertionID">
         <wssp:Claims>
    <wssp:ConfirmationMethod>sender-vouches</wssp:ConfirmationMethod>
    </wssp:Claims>
    </wssp:SecurityToken>
    </wssp:SupportedTokens>
    </wssp:Identity>
    </s1:All>
    </s1:Policy>
    <wsp:UsingPolicy s0:Required="true"/>
    <s0:service name="WSRPService">
    <s0:port binding="s3:WSRP_v1_Markup_Binding_SOAP" name="WSRPBaseService">
    <s4:address location="http://esmadaix01:7001/fportlets/producer/wsrp-1.0/markup"/>
    </s0:port>
    <s0:port binding="s3:WSRP_v1_ServiceDescription_Binding_SOAP" name="WSRPServiceDescriptionService">
    <s4:address location="http://esmadaix01:7001/fportlets/producer/wsrp-1.0/serviceDescription"/>
    </s0:port>
    <s0:port binding="s3:WSRP_v1_Registration_Binding_SOAP" name="WSRPRegistrationService">
    <s4:address location="http://esmadaix01:7001/fportlets/producer/wsrp-1.0/registration"/>
    </s0:port>
    <s0:port binding="s3:WSRP_v1_PortletManagement_Binding_SOAP" name="WSRPPortletManagementService">
    <s4:address location="http://esmadaix01:7001/fportlets/producer/wsrp-1.0/portletManagement"/>
    </s0:port>
    <s0:port binding="s5:WLP_WSRP_v1_Markup_Ext_Binding_SOAP" name="WLP_WSRP_Ext_Service">
    <s4:address location="http://esmadaix01:7001/fportlets/producer/wsrp-wlp-ext-1.0/markup"/>
    </s0:port>
    </s0:service>
    </s0:definitions>
    I don't know what to do..., please help!!
    Thanks in advance for your help.

    I also have a similar problem with ALSB, I'm trying to call a service which is signed with usernameToken, i created a service account, and passed the remote username and password, but unfortunatily i get the follownig error:
    <Dec 24, 2007 10:49:52 AM GST> <Info> <Server> <BEA-002605> <Adding address: 83.
    110.15.81 to licensed client list>
    <Dec 24, 2007 10:50:00 AM GST> <Warning> <netuix> <BEA-423430> <The portal <dire
    ctive.page> element has been deprecated. You can set the page encoding on the <n
    etuix:desktop> element.>
    <Dec 24, 2007 10:50:02 AM GST> <Warning> <netuix> <BEA-423420> <Redirect is exec
    uted in begin or refresh action. Redirect url is jsp/login/index.jsp.>
    <Dec 24, 2007 10:50:07 AM GST> <Info> <JMX> <BEA-149505> <The administration ser
    ver was unable to establish JMX Connectivity with the Server1 at the JMX Service
    URL of <none>.>
    <Dec 24, 2007 10:50:09 AM GST> <Notice> <Stdout> <000000> <nl.ikarus.nxt.priv.im
    ageio.icoreader.lib.ICOReader loaded, version: 0.06.064 build: 691>
    <Dec 24, 2007 10:50:24 AM GST> <Info> <Health> <BEA-310002> <54% of the total me
    mory in the server is free>
    <Dec 24, 2007 10:50:25 AM GST> <Warning> <netuix> <BEA-423430> <The portal <dire
    ctive.page> element has been deprecated. You can set the page encoding on the <n
    etuix:desktop> element.>
    <Dec 24, 2007 10:50:40 AM GST> <Info> <ALSB Security> <BEA-387027> <Message-leve
    l access control policy grants access to proxy "Fadia/ADTA/PSMine", operation "S
    endSMS", message-id: 7380087946135603967-36ae4590.1170ae9bb75.-7ff3, subject: Su
    bject: 3
    Principal = class weblogic.security.principal.WLSUserImpl("weblogic")
    Principal = class weblogic.security.principal.WLSGroupImpl("Administrato
    rs")
    Principal = class weblogic.security.principal.WLSGroupImpl("IntegrationA
    dministrators")
    .>
    <Dec 24, 2007 10:50:40 AM GST> <Error> <ALSB Security> <BEA-387024> <An error oc
    urred during web service security outbound request processing [error-code: Fault
    , message-id: 7380087946135603967-36ae4590.1170ae9bb75.-7ff3, proxy: Fadia/ADTA/
    PSMine, target: Fadia/ADTA/BSsmsMINE, operation: SendSMS]
    --- Error message:
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soa
    penv:Header/><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><
    faultstring>Unable to add security token for identity</faultstring></soapenv:Fau
    lt></soapenv:Body></soapenv:Envelope>
    weblogic.xml.crypto.wss.WSSecurityException: Unable to add security token for id
    entity
    at weblogic.wsee.security.wss.SecurityPolicyDriver.processIdentity(Secur
    ityPolicyDriver.java:175)
    at weblogic.wsee.security.wss.SecurityPolicyDriver.processOutbound(Secur
    ityPolicyDriver.java:73)
    at weblogic.wsee.security.WssClientHandler.processOutbound(WssClientHand
    ler.java:69)
    at weblogic.wsee.security.WssClientHandler.processRequest(WssClientHandl
    er.java:53)
    at weblogic.wsee.security.WssHandler.handleRequest(WssHandler.java:72)
    at com.bea.wli.sb.security.wss.WssOutboundHandler$1.run(WssOutboundHandl
    er.java:140)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    147)
    at com.bea.wli.sb.security.wss.WssOutboundHandler.processRequest(WssOutb
    oundHandler.java:138)
    at com.bea.wli.sb.security.wss.WssHandlerImpl.doOutboundRequest(WssHandl
    erImpl.java:901)
    at com.bea.wli.sb.context.BindingLayerImpl.createTransportSender(Binding
    LayerImpl.java:487)
    at com.bea.wli.sb.pipeline.PipelineContextImpl.doDispatch(PipelineContex
    tImpl.java:501)
    at com.bea.wli.sb.pipeline.PipelineContextImpl.dispatch(PipelineContextI
    mpl.java:488)
    at stages.routing.runtime.RouteRuntimeStep.processMessage(RouteRuntimeSt
    ep.java:127)
    at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMes
    sage(StageMetadataImpl.java:319)
    at com.bea.wli.sb.pipeline.RouteNode.doRequest(RouteNode.java:108)
    at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:68)
    at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextIm
    pl.java:834)
    at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:194)
    at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProces
    sor.java:75)
    at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:669)
    at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:668)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    147)
    at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.ja
    va:666)
    at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessage
    Sender.java:265)
    at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMe
    ssageSender.java:86)
    at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessage
    Sender.java:124)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    147)
    at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageS
    ender.java:127)
    at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.
    java:404)
    at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:163)
    at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceE
    JBBean.java:138)
    at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestS
    ervice_sqr59p_EOImpl.java:427)
    at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invok
    e(Unknown Source)
    at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:17
    4)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef
    .java:335)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef
    .java:252)
    at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_921_WLStub.i
    nvoke(Unknown Source)
    at com.bea.wli.sb.console.test.TestServiceClient.invoke(TestServiceClien
    t.java:178)
    at com.bea.wli.sb.console.test.actions.DefaultRequestAction.invoke(Defau
    ltRequestAction.java:117)
    at com.bea.wli.sb.console.test.actions.DefaultRequestAction.execute(Defa
    ultRequestAction.java:70)
    at org.apache.struts.action.RequestProcessor.processActionPerform(Reques
    tProcessor.java:419)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201
    (PageFlowRequestProcessor.java:95)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunn
    er.execute(PageFlowRequestProcessor.java:2042)
    at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionI
    nterceptors.wrapAction(ActionInterceptors.java:90)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processAct
    ionPerform(PageFlowRequestProcessor.java:2114)
    at com.bea.wli.common.base.SBConsoleRequestProcessor.processActionPerfor
    m(SBConsoleRequestProcessor.java:78)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.ja
    va:224)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInt
    ernal(PageFlowRequestProcessor.java:554)
    at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(Pa
    geFlowRequestProcessor.java:851)
    at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(A
    utoRegisterActionServlet.java:630)
    at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageF
    lowActionServlet.java:157)
    at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionSe
    rvlet.java:241)
    at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
    at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServ
    let.java:130)
    at com.bea.wli.common.base.SBConsoleActionServlet.doGet(SBConsoleActionS
    ervlet.java:58)
    at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlow
    Utils.java:1169)
    at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.exec
    uteAction(ScopedContentCommonSupport.java:688)
    at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.proc
    essActionInternal(ScopedContentCommonSupport.java:144)
    at com.bea.portlet.adapter.scopedcontent.StrutsStubImpl.processAction(St
    rutsStubImpl.java:76)
    at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiAct
    ionHandler.java:99)
    at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedActi
    on(NetuiContent.java:180)
    at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedActi
    on(NetuiContent.java:168)
    at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackD
    ata(NetuiContent.java:222)
    at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:178)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:351)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
    ava:361)
    at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:128)
    at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
    at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:339)
    at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:330)
    at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:162)
    at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:137)
    at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java
    :370)
    at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:229)
    at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:183)
    at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileS
    ervlet.java:221)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:124)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run
    (StubSecurityHelper.java:223)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecuri
    tyHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.jav
    a:283)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:42)
    at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsF
    ilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.ja
    va:42)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
    n.run(WebAppServletContext.java:3243)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    121)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppS
    ervletContext.java:2003)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletC
    ontext.java:1909)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.j
    ava:1359)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    >
    PLEASE PEASE HELP

  • 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

  • JSR-168 portlet dependencies

    Hi..
    I'm using Jdeveloper 11g to create JSR-168 portlets to deploy it on LifeRay. LifeRay installs portlets but it gives an java.lang. ClassCastException sun.java2d.HeadlessGraphicsEnvironment.
    The portlets Contains JSPX/ADF Faces view.Is this a dependency problem should I install new software to get it working?
    The server which hosts liferay contains JDK 1.5 only. Do I have to install other software inorder to deploy portlets.
    Thanks
    Feras Odeh

    Don't know if this is going to work... I wanted to try this myself but never got the time :)
    Were did you deploy your ADF portlets? Did you try to deploy them on the same application server as liferay (tomcat, weblogic,...?) or do you have a weblogic server were you deploy your portlet producer and then register the portlets with liferay using wsrp?
    I don't know if ADF portlets will even work in liferay because webcenter and liferay have a completly different way of rendering the portlet. I think webcenter portlets (ADF) will not work in liferay for this but i have not tried it yet.

  • WSRP (jsr-168) portlets no edit/help buttons appear

    Hi,
    I have some jsr-168 portlets that I wrote that work on other portal software (like uPortal). They have both help and edit buttons (specified in the portlet.xml and handlers written into the portlet code) and you can click them and see both the help and edit modes of the portlets. However, when I put these portlets on Oracle Portal (10.1.2/10.1.4), the edit/help (or personalize) buttons don't show up. I even tried to use the sample portlets from sun, like the BookmarkPortlet, etc, and they have the same problem.
    Any ideas?
    Thanks,
    -Mike M.

    Hi,
    I dont see anything obvisouly wrong with what you are doing. I suspect the var attribute though. Can you try out this sample
    ">view</a><br>
    <a href="
    <portlet:renderURL windowState="maximized" portletMode="help"/>">help</a><br>
    Thanks,
    Sharmila

  • JSR 168 Portlet and PORTLET_SCOPE session variables

    Hi,
    I have a JSR-168 portlet that is putting session variables on the PortletSession. I have some variables that use "PORTLET_SCOPE" for that particular portlet. This works fine if I add the portlet directly on a page, no problems. Its able to retrieve and put variables on the PortletSession with PORTLET_SCOPE and retrieve them properly.
    The problem comes when when I have my JSR-168 portlet on a page, then select "Publish Page as Portlet", and then add that page (that contains the JSR-168 Portlet) to another page. Now, when I try to retrieve a variable that was put on the PortletSession w/ PORTLET_SCOPE, it returns null. So its like variables put on the PortletSession with PORTLET_SCOPE doesn't work properly if you add it as a page onto another page.
    In case that wasn't clear, let's say I have Page1 which contains my JSR-168 portlet and I selected "Publish Page as a Portlet."
    If I go to Page1, it works fine, no problems at all.
    Now, I have Page 2. I add Page 1 to Page 2. NOW, the Portlet on Page 1 doesn't work properly and I've narrowed it down to a problem with the PortletSession when PORTLET_SCOPE is used. Has anyone else run into this problem? I'm guessing the problem is the fact that page is published as a portlet and PORTLET_SCOPE doesn't work properly. Is this a bug or expected behavior?? If so, is there a workaround?
    Thanks in advance.

    Frank,
    The taglib is not in the classpath of the Portal server. We access other methods of the ftl taglib, like <f:webResources relativePath='js/myScripts.js' />at places higher up in the JSP and it has no problems with those ftl taglib calls.
    If I understand correctly, since the Portal is hosting a remote portlet, the Portal is only getting html from the remote portlet producer, not the actual JSP to compile into a web page. If that is true, the Portal never sees the taglib code, just the html that is produced from it - so it would not need the taglib in its classpath.
    There is something special about the "invoke" method of the taglib where it makes a call back to the Enterprise server. I think when it tries to go back to the Enterprise server, the Portal server has a problem with it.
    Thanks.
    Edited by marshallbenfield at 08/15/2007 6:02 AM
    Edited by marshallbenfield at 08/15/2007 6:03 AM

  • 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>

  • 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

  • JSR 168 portlets packaging question

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

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

  • JSR 168 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

  • 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.
    %

Maybe you are looking for

  • IPhoto 6 crashed after rebuilding thumbnail cache

    I, too, have had trouble with iPhoto 6, but only when I finally clicked "ok" after the endless suggestions to rebuild my thumbnail cache. The result? A loss of all my thumbnails on my eMac. My elaborate structure of albums was there, but each one was

  • Process order confirmation error

    Hi, i have set backflush in mrp2 view as always backflush for raw mat. when i do order confirmation with cork tcode, order status shows as CNF but raw mats are not withdrawn. pls note that backflush indicator is also copied in order. do i need to iss

  • Need help: Flex  record webcam problem, how to setting Brightness,Contrast,Saturation and Sharpness

    Hello, dear all Please help me! Flex  record webcam problem, how to setting Brightness,Contrast,Saturation and Sharpness? nsOutGoing=new NetStream(nc); nsOutGoing.attachCamera(m_camera); nsOutGoing.publish(filename, "record"); I want to control the B

  • How to adjust data in new profit centres

    hi experts, i have a issue, till now i have only two profit centres, i have to create one more profit centres, i need to adjust data in previous two PC's to all three profit centres ( all previous years data in PC's). what are the things to be done,

  • [REQUEST] update ibus and all its components

    ibus 1.3.9 is released 9 months ago, so it is quite old. could any TUs and DEVs update the ibus branches to git version on github? It has quite a lot of bug fixes. I think ibus is important because gnome is going to integrate it in 3.2. I really want