Deploy JSR 168 Compliant to JBoss Portal or other portal containers

Hi
Has anyone tried to deploy JSR-168 portlets developed using Jdeveloper on any other Portal containers like JBoss Portal or SAP Portal?
I am having difficulty in running the JSR 168 portlets developed using ADF faces on JBoss.
Any help is much appreciated.

Yes. You can find more information here:
http://www.oracle.com/technology/products/ias/portal/standards.html

Similar Messages

  • Anyone deployed JSR 168 compliant portlet in SunONE Portal Server 6.1?

    Hi,
    Anyone deployed JSR 168 compliant portlet in SunONE Portal Server 6.1?
    Thanks
    Tanmoy

    Try following command
    pdeploy deploy -u uid=amadmin,ou=People,dc=INDIA,dc=ORGNAME,dc=COM -w adminadmin -p adminadmin -g -v -f PORTALBASE/config/portlet/usermapping.properties C:\HelloWorld\dist\HelloWorld.war
    Thanks

  • Deploying JSR-168 compliant Portlets on an Enterprise Portal

    Hello,
       This is Sitaram Nanduri.We r new to NetWeaver Developer Studio.We have to write JSR-168 compliant Portlets that will be deployed on NetWeaver Enterprise Portal.Please guide me how can i deploy Portlets in NWDS EP.Thank u.

    Hi,
    -Users are not developers, they are end-users managers and business analists and they want to create their own operations dashboard.
    -Just imagine that our main application can produce portlets that display the weather information of just one city (I know the portlets could have a preference that may allow users change the city they want to see). the main appliction can assamble a war'ed jsr-168 portlet that displays the weather of that city, that war'ed jsr-168 portlet could also be put in the deployment path of weblogic, our app can do that without problems, end-users don't have any idea of what is going on behind the scenes.
    -Imagine for example that we want to see one and only one city weather information in each portlet, so managers can assamble a dashboard of cities wheather portlets. One manager may want to see the weather of just two cities (two portlets), a second manager four cities (four portlets) and so on, any number of portlets.
    -In the above scenario I still don't see how I can add to each manager portal any number of jsr-168 portlets without pre-configuring an specific number of federated portlets in the portal.
    Thank you!

  • Deploy JSR 168 on oracle application portal 10.1.4

    We have Oracle Application Portal 10.1.4 and have been deploying Oracle PDK portlet on it.
    Now we decide to standardize things and use JSR 168 portlets and follow some framework.
    As a first step, I developed one JSR 168 in jdeveloper and deployed on a OC4J standalone and then register this on actual portal server through WSRP.
    Registration was successful, but the JSR 168 portlet does not work perfectly as it couldn't load/locate some resources (javascript file and image file). I even tried URL rewriting, but doesn't work!
    I then deployed the jsr168 portlet directly to oracle portal AS. the deployment was successful but I was unable to get the WSDL in the browser. when I try to access the WSDL for example http://myserver.com/application_name/portlets?WSDL it prompts me with 'resource not available'.
    Can someone put some light on this issue.
    thanks in advance.
    Best Regards
    Edited by: user9515104 on Nov 30, 2010 8:10 PM

    Make sure that you have all the required patches installed if you want to use JSR-168 portlets in the Portal container. Check Note 335911.1 - Master Note for OracleAS Portal PDK / WSRP Patches
    Thanks,
    EJ

  • Problems with the article Building JSR 168-Compliant Portlets with Sun Java

    i try to make my first portlet with the article Building JSR 168-Compliant Portlets with Sun Java Studio Enterprise
    But when start the portlet simulator in the sun java studio i have an error. I did all that the article says. Please help me!!
    Thanks and sorry for my english
    Errors generated by provider instance - see log output
    Error in provider method getContent(): com.sun.portal.providers.ProviderException: JSPProvider.processJSPFile(): jsp=HarnessPortletContent.jsp, java.lang.NullPointerException
    Message: Locale string - es_ES
    Message: Obtained client type - html.
    Message: Got session property "filePath" = "null".
    Message: Locale string - es_ES
    Message: Got String property "contentPage" for channel "HarnessPortletChannel" = "HarnessPortletContent.jsp".
    Message: Locale string - es_ES
    Message: Obtained client type - html.
    Message: Client path - null
    Message: Obtained template path: C:\Documents and Settings\jbonardi\jstudio_6ee_user\ps\desktop\default\HarnessPortletChannel\HarnessPortletContent.jsp
    Message: Set session property "javax.portlet.http_session_id" to object "BC7F955E23394EF2EA8772E8B60F1CC4".
    Message: Got localized String property "title" for channel "HarnessPortletChannel" = "HarnessPortletProvider".
    Message: Boolean property "isEditable" for channel "HarnessPortletChannel" does not exist.
    Message: Got localized String property "description" for channel "HarnessPortletChannel" = "HarnessPortletProvider".
    Message: String property "helpURL" for channel "HarnessPortletChannel" exists.
    Message: Got String property "helpURL" for channel "HarnessPortletChannel" = "desktop/usedesk.htm".
    Message: Locale string - es_ES
    Message: Got String property "docroot" for channel "HarnessPortletChannel" = "/portalserver/docs/".
    Message: Got String property "contentPage" for channel "HarnessPortletChannel" = "HarnessPortletContent.jsp".
    Message: Boolean property "showExceptions" for channel "HarnessPortletChannel" does not exist.
    Message: Locale string - es_ES
    Message: Obtained client type - html.
    Message: Client path - null
    Message: Obtained template path: C:\Documents and Settings\jbonardi\jstudio_6ee_user\ps\desktop\default\HarnessPortletChannel\HarnessPortletContent.jsp
    Message: Locale string - es_ES
    Message: Obtained client type - html.
    Message: Client path - null
    Message: Obtained template most specific path: C:\Documents and Settings\jbonardi\jstudio_6ee_user\ps\desktop\default\HarnessPortletChannel\HarnessPortletContent.jsp
    Message: Obtained client type - html.
    Message: Got collection property "hasHelpByMimeType" for channel "portlet_GoogleSearchPortlet.
    Message: Got localized String property "title" for channel "portlet_GoogleSearchPortlet" = "__Portlet__portlet.GoogleSearchPortlet".
    Message: Boolean property "isEditable" for channel "portlet_GoogleSearchPortlet" exists.
    Message: Got String property "entityIDPrefix" for channel "portlet_GoogleSearchPortlet" = "portlet|GoogleSearchPortlet".
    Message: Got session property "javax.portlet.portletc.renderParams.portlet|GoogleSearchPortlet|portlet_GoogleSearchPortlet" = "null".
    Message: Got session property "javax.portlet.portletc.portlet|GoogleSearchPortlet|portlet_GoogleSearchPortlet.isTarget" = "null".
    Message: Set session property "javax.portlet.portletc.portlet|GoogleSearchPortlet|portlet_GoogleSearchPortlet.isTarget" to object "false".
    Message: Obtained client type - html.
    Message: Collection property "roleMap" for channel "portlet_GoogleSearchPortlet" does not exist.
    Message: Collection property "userInfoMap" for channel "portlet_GoogleSearchPortlet" does not exist.
    Message: Boolean property "showExceptions" for channel "HarnessPortletChannel" does not exist.
    Error: Error in provider getContent()
    <<<<<<<< Stack Backtrace:
    com.sun.portal.providers.ProviderException: JSPProvider.processJSPFile(): jsp=HarnessPortletContent.jsp, java.lang.NullPointerException
         at com.sun.portal.providers.jsp.JSPProvider.processJspFile(JSPProvider.java:880)
         at com.sun.portal.providers.jsp.JSPProvider.processJspFile(JSPProvider.java:777)
         at com.sun.portal.providers.jsp.JSPProvider.getContent(JSPProvider.java:546)
         at com.sun.portal.harness.HarnessPortletProvider.getContent(Unknown Source)
         at com.sun.portal.harness.ProviderHarness.createContent(Unknown Source)
         at com.sun.portal.harness.ProviderHarness.initProvider(Unknown Source)
         at com.sun.portal.harness.ProviderHarness.getHarness(Unknown Source)
         at org.apache.jsp.desktop_0005cdefault_0005charness_0005cPSSimTarget$jsp._jspService(desktop_0005cdefault_0005charness_0005cPSSimTarget$jsp.java:73)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet$JspServletWrapper.service(IDEJspServlet.java:173)
         at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet.serviceJspFile(IDEJspServlet.java:246)
         at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet.service(IDEJspServlet.java:339)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:683)
         at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574)
         at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:497)
         at org.apache.jsp.PSSim$jsp._jspService(PSSim$jsp.java:84)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet$JspServletWrapper.service(IDEJspServlet.java:173)
         at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet.serviceJspFile(IDEJspServlet.java:246)
         at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet.service(IDEJspServlet.java:339)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
         at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:226)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:213)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
         at org.netbeans.modules.web.monitor.catalina.MonitorValve.invoke(MonitorValve.java:148)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:644)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2349)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
         at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:644)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:171)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:644)
         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:469)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:644)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1040)
         at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1151)
         at java.lang.Thread.run(Thread.java:534)
    java.lang.NullPointerException
         at com.sun.portal.harness.HarnessPortletProvider.doGetContent(Unknown Source)
         at _jspsC_0003a._Documents_00020and_00020Settings._jbonardi._jstudio_6ee_user._ps._desktop._default._HarnessPortletChannel._HarnessPortletContent_jsp._jspService(_HarnessPortletContent_jsp.java:215)
         at com.sun.portal.providers.jsp.jasper3.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sun.portal.providers.jsp.JspServletWrapper.service(JspServletWrapper.java:182)
         at com.sun.portal.providers.jsp.JSPProvider.processJspFile(JSPProvider.java:863)
         at com.sun.portal.providers.jsp.JSPProvider.processJspFile(JSPProvider.java:777)
         at com.sun.portal.providers.jsp.JSPProvider.getContent(JSPProvider.java:546)
         at com.sun.portal.harness.HarnessPortletProvider.getContent(Unknown Source)
         at com.sun.portal.harness.ProviderHarness.createContent(Unknown Source)
         at com.sun.portal.harness.ProviderHarness.initProvider(Unknown Source)
         at com.sun.portal.harness.ProviderHarness.getHarness(Unknown Source)
         at org.apache.jsp.desktop_0005cdefault_0005charness_0005cPSSimTarget$jsp._jspService(desktop_0005cdefault_0005charness_0005cPSSimTarget$jsp.java:73)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet$JspServletWrapper.service(IDEJspServlet.java:173)
         at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet.serviceJspFile(IDEJspServlet.java:246)
         at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet.service(IDEJspServlet.java:339)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:683)
         at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574)
         at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:497)
         at org.apache.jsp.PSSim$jsp._jspService(PSSim$jsp.java:84)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet$JspServletWrapper.service(IDEJspServlet.java:173)
         at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet.serviceJspFile(IDEJspServlet.java:246)
         at org.netbeans.modules.tomcat.tomcat40.runtime.IDEJspServlet.service(IDEJspServlet.java:339)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
         at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:226)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:213)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
         at org.netbeans.modules.web.monitor.catalina.MonitorValve.invoke(MonitorValve.java:148)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:644)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2349)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
         at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:644)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:171)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:644)
         at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:469)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:644)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
         at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:646)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:483)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
         at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1040)
         at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1151)
         at java.lang.Thread.run(Thread.java:534)
    >>>>>>>>
    Message: Got String property "width" for channel "HarnessPortletChannel" = "thick".

    You�ve got to unmount the portal server fs from your project, disable the portlet builder plugin (Tools->options->,,,PortletBuilder) then erase the ps folder inside your ide profile and then start the portlet builder module again. Try to simulate it again and it should work.
    Regards,
    Pablo.

  • 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

  • How to deploy JSR 168 Portlet war into Weblogic Portal Server?

    Hello experts!
    I have the installed Oracle WebLogic Portal 10.3.2 with Examples.
    And I want to deploy my jsr-168 portlet.
    Now I could to import this portlet by docs:
    http://download.oracle.com/docs/cd/E15919_01/wlp.1032/e14245/deployment.htm#i1047336
    How can I add the web application as a WSRP producer using WebLogic Portal Administration Console?
    What should I do?

    Hello Kevin,
    my answers:
    Are there any error or warning messages on the application server console when you deploy the generated EAR?When I checked the Auto-deploy checkbox and press Perform Import on the Import Tool page, I had:
    Import Successful... Generated EAR:C:\Oracle\Middleware\wlportal_10.3\samples\domains\portal\helloApp.ear
    But helloApp had the Warning status (Health column) on the Deployment page of the WL Server Administration Console
    Health Information:
    Name: AsyncProliferation
    Health: OK
    Reason: MDB application helloApp is connected to messaging system.
    Name: MessageBufferBean
    Health: Warning
    Reason: MDB application helloApp is NOT connected to messaging system.
    Name: MessageBufferTopicBean
    Health: Warning
    Reason: MDB application helloApp is NOT connected to messaging system.
    If I did NOT check the Auto-deploy checkbox and then install on the Deployment page, I had:
    Messages
    All changes have been activated. No restarts are necessary.
    The deployment has been successfully installed.
    But helloApp had the Warning status (Health column) too.
    Also, earlier you said that you were using WLP 10.3.2, but this issue sounds very similar to something
    that happened in a previous version of WLP, so I just want to check with you again that you're using WLP 10.3.2, correct?Yes, I am using WLP *10.3.2*
    WEB-INF/weblogic.xml ... , WEB-INF/wsrp-producer-config.xml ...
    If you find these files in the generated WAR inside the generated EAR, can you post their contents here?
    weblogic.xml content:
    <?xml version="1.0" encoding="UTF-8"?>
    <weblogic-web-app xmlns="http://xmlns.oracle.com/weblogic/weblogic-web-app">
    <library-ref>
    <library-name>wlp-framework-full-web-lib</library-name>
    </library-ref>
    <library-ref>
    <library-name>wlp-framework-struts-1.2-web-lib</library-name>
    </library-ref>
    <library-ref>
    <library-name>struts-1.2</library-name>
    </library-ref>
    <session-descriptor>
    <cookie-name>JSESSIONID_hello</cookie-name>
    </session-descriptor>
    </weblogic-web-app>
    wsrp-producer-config.xml content:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsrp-producer-config xmlns="http://www.bea.com/servers/weblogic/wsrp-producer-config/9.0">
    <service-config>
    <registration secure="false" required="true"/>
    <service-description secure="false"/>
    <markup secure="false" rewrite-urls="true" transport="string"/>
    <portlet-management secure="false" required="true"/>
    </service-config>
    <supported-locales>
    <locale>en</locale>
    <locale>en-US</locale>
    </supported-locales>
    <requiredUserProperties properties="specified"/>
    </wsrp-producer-config>

  • 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

  • Deploying JSR 168 portlets

    We are working with Oracle Application Server Portal (10.1.4), we built a few JSR 168 portlets that we need to deploy and make them work on the Oracle portal, but I cant find information on how to do this task.
    Please give tell me how to do it or where do I find this information.
    I already reviewed Portal Developer's Guide for this version.

    The documentation about the development of this type of portlets can be found at: http://download-west.oracle.com/docs/cd/B14099_14/portal.1014/b14135/pdg_java_intro.htm#sthref858, items 6.4.2.1 Creating a Portlet, to 6.4.2.4 Registering and Viewing Your Portlet but the document makes reference to calling your portlet as "http://myserver.com:8888/my-portlet/portlets?WSDL", but that would be for a PDK-Java portlet and second, the option for WSRP registration is not there Figure 6-28 Register Provider Page.
    What should I do to publish my standard JSR 168 portlets on the Oracle Portal.

  • Deploying JSR-168 Portlet has an intrinsic portlet to ALUI

    How can I proceed to deploy a JSR-168 portlet to work has an intrinsic portlet in ALUI?

    Hello,
    This is the WebLogic Portal forum; for the WebCenter Interaction (formerly ALUI) forum see:
    WebCenter - Interaction
    If you post your question there, I imagine you can get an answer. Unfortunately, I don't know enough about WCI/ALUI to help you out.
    Kevin

  • 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

  • Multiple JSPs with JSR 168-compliant Java portlet

    Hi,
    I have an application with multiple JSPs that I'm trying to run in a portlet. Looks like a JSR 168 Java Portlet is the best way to do that. I want to avoid using proprietary PDK Portlet route.
    A few questions:
    1. Is there any sample of that available with multiple JSPs?
    2. More specifically, if I have a form element in one jsp, can I specify another JSP in the action element, or do I have to use an actionURL or renderURL?
    3. Also, how can I can debug my Java portlet from JDeveloper?
    Thanks.
    - Anupam

    Hi,<br>
    I'm building a JSR 168 Java portlet. I've been trying to pass params from my JSP using actionURL in my jsp, like so:<br><br>
    <FORM METHOD="POST" ACTION="<portlet:renderURL/>">
    <TABLE BORDER="0" CELLPADDING="4" CELLSPACING="0" BGCOLOR="#eeeeee">
    <TR>
    <TD ALIGN="right">
    <FONT FACE="Arial" SIZE="-1 ">User Name:</FONT>
    </TD>
    <TD>
    <INPUT NAME="userName" SIZE="12" MAXLENGTH="32">
    </TD>
    </TR>
    <TR>
    <TD>
    <INPUT NAME="action" SIZE="12" TYPE="hidden" value="Login">
    </TD>
    </TR>
    </TABLE>
    </FORM>
    <br><br>
    I find that in my processAction, I can see value of "action" parameter but not the value the user enters in the portlet for "userName".<br><br>
    Any idea why? I must be doing sthing wrong, dunno what.<br><br>
    Also, if I use renderURL instead of actionURL, I don't even see "action" getting passed. Is that expected?<br><br>
    Thanks

  • Java Portlet (JSR 168) development with Portal

    Hello,
    We have been trying to dive back into Portal development lately. The release of 9.0.4 with support for standards-based portlets has convinced us to begin looking at 9iAS Portal as a practical portal product. We have a development environment setup with a workin 9.0.4 portal.
    Digging through the available docs on the portal studio site, I have come across a couple documents alluding to the installation of a portlet-container. Now, I have already downloaded the JSR 168 framework files. It seems that a good portion of this 'portlet container' consists of these files.
    The problem is that the documentation that is available is nothing more than a step by step set of instructions for setting up an OC4J instance with this 'portlet container', configuring an Oracle database for portlet customizations, and deploying a sample ear into the OC4J instance.
    This does nothing for me.
    What I want is documentation that indicates the requirements necessary to make a JSR-168 compliant portlet (even a 'hello world') exposed through portal with the least amount of effort, and with no references to proprietary tools. I would like to see instructions that are tailored towards a generic J2EE provider, not an OC4J one. I already have a very functional set of tools that should be able to accomodate a JSR-168 producer. We have had many problems with OC4J leading us to try to avoid it at all costs.
    Any ideas?
    Thanks!
    -Sean

    Hello
    I am probably not clear.
    In the OracleAS Portal architecture Java portlet are remote from the portal middle tier.
    In the non standard world (JPDK Portlet), the Portal Middlet tier use SOAP over HTTP to call the portlets.
    In the Standard world (JSR-168), the Portal Middle Tier will use WSRP (Web Service Remote Portlet) to call the portlets. When you use the Oracle JSR-168 container inside OC4J, these portlets are automatically accessible over remotely using WSRP.
    So, as you can see the Portal Middle Tier needs to support WSRP to be able to use JSR-168 portlet. And OracleAS 10g 904 does not currently support WSRP registration. It is why we have the "OracleAS Portal Verification Service for WSRP", to allow you to test your portlet.
    To be able to use JSR-168 (with WSRP) portlet on you internal Portal you'll have to install the OracleAS Portal Standard Developer Preview that will be available soon.
    Hope that clarify my previous statements.
    Regards
    Tugdual Grall

  • 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

Maybe you are looking for