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

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

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

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

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.

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

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

Control Height Of Region Containing JSR-168 Portlet

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

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

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

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

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

JSR 168 support on production environment??

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

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

JSR-168 Support

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

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

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

Deploying JSR-168 Portlet has an intrinsic portlet to ALUI

Similar Messages

Maybe you are looking for