<img alt="Liferay" src="http://cdn.www.liferay.com/osb-theme/images/custom/heading.png" width="146" height="36" />

Hello,

I have installed liferay 4.3.3 on WebSphere 6.1 and it works. But I cannot deploy any more plugins. I tried hot deploy through the Plugin Installer but this did not work, it reports that the plugin was installed successfully but it merely copies the .war over to the specified directory and the portlet (or theme etc) does not become available (not in the list of plugins).

I have tried direct deployment to WebSphere but again, the Portal container just ignores it. I tried to build/deploy the liferay source but in app.server.properties websphere is not included, not sure how to proceed there.

Has anyone been able to deploy portlets to WebSphere after installing liferay, either with autodeployment or manually? I see quite a few topics on WebSphere but not really any solutions, is liferay not fully supported there?

Any pointers would be appreciated.

Thank you
John.

RE: Deployment of plugins on WebSphere 6.1

November 2, 2007 2:03 PM

Answer

LIFERAY STAFF

Rank: Regular Member

Posts: 187

Join Date: February 7, 2007

Hey John,

The problem is that IBM now includes their own portlet container within all of their application servers. This prevents a 3rd party container (like Liferay) from picking it up.

Please see this IBM PK: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg1PK34915

They basically say you have to add a context parameter to the plugin's web.xml file which tells their portlet container to ignore it.

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

November 5, 2007 8:40 AM

Answer

John K Johnson

Rank: New Member

Posts: 5

Join Date: October 29, 2007

Unfortunately that did not work. Liferay still ignores this portlet. I cannot see it in the Plugins list and I cannot add it to a page from "Add Content".

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

November 9, 2007 7:15 AM

Answer

Joel Kozikowski

Rank: Expert

Posts: 405

Join Date: June 27, 2006

Have you tried the stuff listed on the Wiki Hot Deploy Troubleshooting?

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

December 12, 2007 4:01 PM

Answer

Jared Eaton

Rank: New Member

Posts: 3

Join Date: November 29, 2007

The troubleshooting wiki basically says the hot deploy won't work with WebSphere:

"There are some containers, such as Oracle Application Server and WebSphere®, which do not define a hot deploy folder. Unfortunately, these containers do not work with Liferay's hot deploy system. But this does not mean that you cannot install plugins on these containers. Some users have had success deploying plugins manually using the application server's deployment tools. On some containers, Liferay is able to pick up the portlet plugins once they get deployed to the container manually, especially if you add it to the same Enterprise Application project that was created for Liferay."

I'm in the same boat, trying to get custom themes deployed in WebSphere. As the wike article said, "some users have had success deploying plugins manually using the application server's deployment tools." Are there any of those users out there who can provide some insight?

je

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

December 12, 2007 4:02 PM

Answer

JR Houn

LIFERAY STAFF

Rank: Expert

Posts: 488

Join Date: November 19, 2007

Hi John-
Hope you don't mind my moving your thread into a more appropriate category.
jr

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

April 7, 2008 1:42 PM

Answer

Jim Leslie

Rank: New Member

Posts: 17

Join Date: November 14, 2006

We are experiencing the same issue. We can run Liferay with no problems, but there is no way to add a new portlet, even after following the suggested tips

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

April 10, 2008 9:26 PM

Answer

LIFERAY STAFF

Rank: Regular Member

Posts: 187

Join Date: February 7, 2007

You should be able to deploy plugins on WebSphere via the following steps:

1. Open (unzip) the plugin and edit the web.xml file
2. Add a context parameter called "com.ibm.websphere.portletcontainer.PortletDeploymentEnabled" and set it to "false"

<context-param>
<param-name>com.ibm.websphere.portletcontainer.PortletDeploymentEnabled</param-name>
<param-value>false</param-value>
</context-param>

3. Save the file and zip the plugin back up as a .war file again, with the same file name.
4. Deploy the portlet or theme to WebSphere using WebSphere's tools, not Liferay's plugin installer. Add the war file to the same ear that portal-web is in.
5. Liferay should register the portlet or theme plugin.

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

May 9, 2008 1:21 PM

Answer

shivaz s sekhon

Rank: New Member

Posts: 4

Join Date: December 3, 2007

Rich Sezov:

You should be able to deploy plugins on WebSphere via the following steps:

4. Deploy the portlet or theme to WebSphere using WebSphere's tools, not Liferay's plugin installer. Add the war file to the same ear that portal-web is in.
5. Liferay should register the portlet or theme plugin.

hi Rich,

You mention that deploy the portlet using webshpere tool. Could you please elaborate which tools to use. are you talking about the application installer? also how can we add the war to the same ear where poral-web is? is this a manual step.

we would really appreciate if you could please elaborate the steps to deploy the portlet using websphere.

Thanks in Advance!!
Regards,
Shivaz

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

May 9, 2008 1:31 PM

Answer

LIFERAY STAFF

Rank: Regular Member

Posts: 187

Join Date: February 7, 2007

Hey Shivaz,

I'm operating completely on memory right now, because I current don't have an installation of WebSphere to work with. So please bear with me.

The WebSphere Admin Console is the web based tool which I've used before. As I recall, you can open up an EAR (which gets automatically generated by the server to encapsulate a .war when you deploy it) and deploy other .war files into it. As I remember, WebSphere calls this an Enterprise Application. When you deploy Liferay, WebSphere will create an EAR wrapper around it, and the Liferay .war will run from within that. I don't remember the exact steps, but you can use the console to deploy another .war file into the Enterprise Application WebSphere has generated as a wrapper.

Hopefully, this is a little more clear. I wish I could give you the exact steps, but that's the best I can do right now.

--Rich

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

May 21, 2008 4:46 PM

Answer

Rank: Regular Member

Posts: 190

Join Date: February 26, 2007

Hi Rich !!

I have Liferay 4.3.6 + Websphere 6.1 + SQL Server 6.1 and it works well.
but I have not been able to install any plugin.
I have followed your steps, but this does not work for me.
there was any formal documentation of Liferay for this problem?
can you help me with this problem ?

thanks

greetings from Colombia !!

Jonathan

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

June 10, 2008 5:38 AM

Answer

Rank: Junior Member

Posts: 39

Join Date: June 2, 2008

I am also stuck with this......

Have you made any progress?
Thanks

Ora

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

June 10, 2008 6:09 AM

Answer

Rank: Regular Member

Posts: 190

Join Date: February 26, 2007

Hi, no yet !!

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

June 10, 2008 6:15 PM

Answer

Rank: Regular Member

Posts: 190

Join Date: February 26, 2007

Hi !!!!!!

the solution is add other property

<listener>
<listener-class>com.liferay.portal.kernel.servlet.PortletContextListener</listener-class>
</listener>

in the web.xml file of your portlet application.

Hence, in your web.xml file have 2 properties

<context-param>
<param-name>com.ibm.websphere.portletcontainer.PortletDeploymentEnabled</param-name>
<param-value>false</param-value>
</context-param>

<listener>
<listener-class>com.liferay.portal.kernel.servlet.PortletContextListener</listener-class>
</listener>

I Am using, Websphere 6.1 (FIX PACK 17), MS SQL SERVER, Liferay Portal 4.3.6 and I can deploy portlet on Liferay now emoticon

(remember put the plugin portlet (.war) into the same EAR of Liferay)

Thanks to Jane Han for the solution (http://www.liferay.com/web/liferayhj/profile)

Greeting from Colombia
Jonathan

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

June 11, 2008 7:37 AM

Answer

Rank: Junior Member

Posts: 39

Join Date: June 2, 2008

Thanks a lot, you have helped me see my portlet under the relevant category, but I still have a problem that is preventing me from adding the portlet to the portal. I think it is somehow related to to the jdbc datasource.

I am running with websphere 6.1.15 and liferay 5.0.1.

I followed the steps you described, and added one of my own (step 5):
2)In RAD, create new EAR file then import liferay-portal-5.0.1.war to this new EAR with context root /.
3)Import my portlet into same EAR then add following code to the web.xml of this portlet.
<context-param>
<param-name>com.ibm.websphere.portletcontainer.PortletDeploymentEnabled</param-name>
<param-value>false</param-value>
</context-param>
<listener>
<listener-class>com.liferay.portal.kernel.servlet.PortletContextListener</listener-class>
</listener>
4) Deploy EAR file which contains two war to Websphere (tried both from RAD and by exporting from RAD to ear file and deploying it).
5)go to the Resource references of the liferayEar and map the the ear to the resources defined in liferay documentation (jdbc/LiferayPool and mail/MailSession)
6)Start app server

The result is :
1. I see an error on the console:
[6/11/08 16:35:51:640 IDT] 00000030 VirtualHost I SRVE0250I: Web Module <null> has been bound to default_host[*:9094,*:80,*:9468,*:5081,*:5080,*:443].
[6/11/08 16:35:51:671 IDT] 00000030 WebGroup A SRVE0169I: Loading Web Module: weatherportlet_ibm_rad.war.
[6/11/08 16:35:51:859 IDT] 00000030 SystemOut O - Registering portlets for weatherportlet_ibm_rad.war
[6/11/08 16:35:51:859 IDT] 00000030 SystemOut O - 1 portlets for weatherportlet_ibm_rad.war are ready for registration
[6/11/08 16:35:51:890 IDT] 00000030 SystemOut O - 1 portlets for weatherportlet_ibm_rad.war registered successfully
[6/11/08 16:35:51:890 IDT] 00000030 Helpers W NMSV0611E: A Referenceable.getReference() returns null.
Object to bind: com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource@b42ae199
Referenceable object: com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource

[6/11/08 16:35:51:999 IDT] 00000030 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file C:\Program Files\IBM\WebSphere\AppServer\profiles\jacada_cycle10_1_ibm\logs\ffdc\server1_00000030_08.06.11_16.35.51_0.txt
[6/11/08 16:35:52:124 IDT] 00000030 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\Program Files\IBM\WebSphere\AppServer\profiles\jacada_cycle10_1_ibm\logs\ffdc\server1_00000030_08.06.11_16.35.51_0.txt
[6/11/08 16:35:52:124 IDT] 00000030 Helpers W NMSV0604E: Exception thrown in Referenceable.getReference().
[6/11/08 16:35:52:140 IDT] 00000030 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream file C:\Program Files\IBM\WebSphere\AppServer\profiles\jacada_cycle10_1_ibm\logs\ffdc\server1_00000030_08.06.11_16.35.52_0.txt
[6/11/08 16:35:52:156 IDT] 00000030 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\Program Files\IBM\WebSphere\AppServer\profiles\jacada_cycle10_1_ibm\logs\ffdc\server1_00000030_08.06.11_16.35.52_0.txt
[6/11/08 16:35:52:156 IDT] 00000030 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream file C:\Program Files\IBM\WebSphere\AppServer\profiles\jacada_cycle10_1_ibm\logs\ffdc\server1_00000030_08.06.11_16.35.52_1.txt
[6/11/08 16:35:52:156 IDT] 00000030 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\Program Files\IBM\WebSphere\AppServer\profiles\jacada_cycle10_1_ibm\logs\ffdc\server1_00000030_08.06.11_16.35.52_1.txt
[6/11/08 16:35:52:171 IDT] 00000030 Helpers W NMSV0610I: A NamingException is being thrown from a javax.naming.Context implementation. Details follow:
Context implementation: com.ibm.ws.naming.jndicos.CNContextImpl
Context method: bind
Context name: 10Node09Cell/nodes/10Node09/servers/server1
Target name: java_liferay:jdbc/LiferayPool
Other data: Object to bind: com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource@b42ae199
Exception stack trace: javax.naming.NamingException: com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getReference() returned null in violation of the JNDI API
at com.ibm.ws.naming.util.Helpers.processJavaObjectForBinding(Helpers.java:583)
at com.ibm.ws.naming.jndicos.CNContextImpl.doBind(CNContextImpl.java:2237)
at com.ibm.ws.naming.jndicos.CNContextImpl.bind(CNContextImpl.java:534)
at com.ibm.ws.naming.util.WsnInitCtx.bind(WsnInitCtx.java:210)
at javax.naming.InitialContext.bind(InitialContext.java:371)
at com.liferay.portal.kernel.servlet.PortletContextListener.portalInit(PortletContextListener.java:76)
at com.liferay.portal.kernel.util.PortalInitableUtil.init(PortalInitableUtil.java:38)
at com.liferay.portal.kernel.servlet.PortletContextListener.contextInitialized(PortletContextListener.java:93)
at com.ibm.ws.wswebcontainer.webapp.WebApp.notifyServletContextCreated(WebApp.java:645)
at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:311)
at com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:290)
at com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:90)
at com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java:157)
at com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:665)
at com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.java:618)
at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:335)
at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:551)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1303)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1138)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:569)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:817)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:949)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$1.run(ApplicationMgrImpl.java:1486)
at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:4040)
at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:4137)
at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:245)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:1491)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:62)
at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:265)
at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1089)
at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:971)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:231)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:238)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:802)
at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1081)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:974)
at com.ibm.ws.management.commands.AdminServiceCommands$InvokeCmd.execute(AdminServiceCommands.java:251)
at com.ibm.ws.console.core.mbean.MBeanHelper.invoke(MBeanHelper.java:239)
at com.ibm.ws.console.appdeployment.ApplicationDeploymentCollectionAction.execute(ApplicationDeploymentCollectionAction.java:537)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1486)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:528)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1074)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1009)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:118)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:771)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:679)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:539)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:321)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1070)
at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:273)
at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.java:319)
at com.ibm.isclite.container.controller.InformationController.processForwardConfig(InformationController.java:206)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1486)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:528)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1074)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1009)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
at com.ibm.ws.console.core.servlet.WSCUrlFilter.setUpCommandAssistence(WSCUrlFilter.java:792)
at com.ibm.ws.console.core.servlet.WSCUrlFilter.continueStoringTaskState(WSCUrlFilter.java:363)
at com.ibm.ws.console.core.servlet.WSCUrlFilter.doFilter(WSCUrlFilter.java:229)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:771)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:679)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:539)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:744)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1455)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:115)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:263)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.determineNextChannel(SSLConnectionLink.java:1002)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.readyInboundPostHandshake(SSLConnectionLink.java:691)
at com.ibm.ws.ssl.channel.impl.SSLConnectionLink$MyHandshakeCompletedCallback.complete(SSLConnectionLink.java:392)
at com.ibm.ws.ssl.channel.impl.SSLUtils.handleHandshake(SSLUtils.java:823)
at com.ibm.ws.ssl.channel.impl.SSLHandshakeIOCallback.complete(SSLHandshakeIOCallback.java:70)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)

[6/11/08 16:35:52:171 IDT] 00000030 SystemOut O - Unable to dynamically bind the Liferay data source: com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getReference() returned null in violation of the JNDI API
[6/11/08 16:35:52:171 IDT] 00000030 VirtualHost I SRVE0250I: Web Module <null> has been bound to default_host[*:9094,*:80,*:9468,*:5081,*:5080,*:443].
[6/11/08 16:35:52:171 IDT] 00000030 ApplicationMg A WSVR0221I: Application started: liferayEar

2. my weatherPortlet is added to the correct category which is great, but when trying to dreag it I get:"Error 404: SRVE0190E: File not found: /WeatherPortlet/invoke " in the content of the portlet.

Any ideas?

Thanks
Ora

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

June 11, 2008 8:52 AM

Answer

Rank: Regular Member

Posts: 190

Join Date: February 26, 2007

Hello Ora,
I have the same problem, I am trying to solve the problem setting the com.ibm.ws.webcontainer.invokefilterscompatibility property to true. check this link
and this

if you can solve the problem, please tell me.

Greetings for colombia

Jonathan

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

June 11, 2008 10:41 PM

Answer

Rank: Junior Member

Posts: 39

Join Date: June 2, 2008

Hi Jonathan,

As you suspected, setting the property didnt help me. And the thing is, I am running with 6.1.15 which shouldnt have this problem to start with.

I hope we find a solution. as soon as I make any progress I will update you.

Thanks
Ora

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

June 19, 2008 9:18 AM

Answer

shivaz s sekhon

Rank: New Member

Posts: 4

Join Date: December 3, 2007

Jonathan Alexander Diosa:

I Am using, Websphere 6.1 (FIX PACK 17), MS SQL SERVER, Liferay Portal 4.3.6 and I can deploy portlet on Liferay now emoticon

(remember put the plugin portlet (.war) into the same EAR of Liferay)

Jonathan

hi Jon,

you said that "put the plugin portlet(*war) into the same EAR of liferay." could you please elaborate on how to achive this. Also did you install the liferay first on websphere and then installed the portlet(.war). A step by step instaruction would be really helpful.

Appreciate you help!!!

Thanks and Regards,
Shivaz

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

June 20, 2008 1:37 AM

Answer

Lohitha TN Acharya

Rank: New Member

Posts: 2

Join Date: June 19, 2008

Hi All,
I am able to run portlet on Websphere 6.1.

I added these things to my portlet's web.xml. I created portlet called FirstPortlet.

<servlet>
<servlet-name>first</servlet-name>
<servlet-class>com.liferay.portal.kernel.servlet.PortletServlet</servlet-class>
<init-param>
<param-name>portlet-class</param-name>
<param-value>com.ibm.first.FirstPortlet</param-value>
</init-param>
<load-on-startup>0</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>first</servlet-name>
<url-pattern>/first/*</url-pattern>
</servlet-mapping>
<context-param>
<param-name>com.ibm.websphere.portletcontainer.PortletDeploymentEnabled</param-name>
<param-value>false</param-value>
</context-param>
<listener>
<listener-class>com.liferay.portal.kernel.servlet.PortletContextListener</listener-class>
</listener>

then I created war. Deployed using websphere admin console with the context root similer to url mapping.

After this I was able to add to page and it started working on portal page:-)

Regards
Lohith

Maria Teresa sanchez jaen

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

June 23, 2008 8:22 AM

Answer

Rank: Junior Member

Posts: 44

Join Date: May 13, 2008

Hi Lohitha!!!!!!!!

Have you installed any portlet? and work?

I try to install the portlet example "sample-jsp-portlet-5.0.0.1.war"
and I add the portlet, but I have the Msg 404 ERROR:/sample-jsp-portlet/invoke "

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

June 24, 2008 6:59 AM

Answer

Rank: Regular Member

Posts: 190

Join Date: February 26, 2007

Hi shivaz,
yes I first installed the liferay application (liferay-4xx.war), then when you install this WAR application Websphere create a new EAR file, for example "liferay-4xx_WAR or liferay-4xx_EAR" you can see that name in the list of applications of websphere.
next for install the plugins, you select this EAR and select the option "UPDATE", next you select install or update one module, and next you need to select the name of the application and the context path.

that is all

greetings from colombia
Jonathan

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

June 25, 2008 5:04 AM

Answer

Lohitha TN Acharya

Rank: New Member

Posts: 2

Join Date: June 19, 2008

Hi Maria,

I am able to deploy and run the portlet on liferay. I was able to run the sample jsp portlet too. I did modification to web.xml to deploy the portlet.

I am attaching web.xml here. Please replace the web.xml to the war with the attached web.xml

After installing portlet using websphere admin console. goto Enterprise Applications and start the war.

Thanks
Lohith

Attachments:

web.xml (1.1k)

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

June 30, 2008 7:04 AM

Answer

Rank: Junior Member

Posts: 39

Join Date: June 2, 2008

Hi,

I tried following your web.xml instructions with liferay's sample_jsp_portlet and it worked. However when I tried taking sun's notepad portlet and do the same,it didnt help (I am still stuck with the "Error 404: SRVE0190E: File not found: /NotepadPortlet/invoke ").

what I tried was to:
1. add to the web.xml your recommendations
2.create lifray-display, liferay-port
3. tried adding ibm-web-bnd.xmi ibm-web-ext.xmi [someone wrote about it]

but no success emoticon

What do u think?

Thanks,
Ora

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

July 6, 2008 2:41 AM

Answer

Rank: Junior Member

Posts: 39

Join Date: June 2, 2008

managed to solve this one after all,
The problem was that the servletname should be identical to the ID of the portlet as seen in the portlet.xml.
I wasn't aware of that, i thought the servlet name is name agnostic like in a regular web.xml.

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

September 4, 2008 5:55 PM

Answer

Elena M

Rank: New Member

Posts: 3

Join Date: September 4, 2008

Hi All,

did anyone ever try to deploy portlet from an EAR that does not contain liferay portal EAR in WebSphere? I am running WebSphere 6.1 with Liferay 5.1. I can deploy a portlet and a theme successfully if they are packaged as WARs in the same EAR as portal WAR. However I need to be able to deploy other portlets from OTHER EARs that do not contain liferay portal and re-packaging is not an option for me.

Liferay has "Install Plugin" admin portlets but it works for installing portlets only for Tomcat, JBoss, etc. Any ideas if it is supposed to work in WebSphere?

Thanks in advance!

Elena

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

September 9, 2008 5:42 PM

Answer

Troy Hollenbach

Rank: New Member

Posts: 1

Join Date: September 9, 2008

Jonathan Alexander Diosa:

next you select install or update one module, and next you need to select the name of the application and the context path.

I STILL have not been able to get even the most simple example "sample_jsp_portlet" to deploy properly in WebSphere. Would anyone be able to provide the exact values that I should be using for the update process? There are two boxes that I have tried a number of different values:
"Specify the path beginning with the installed application archive file to the module to be replaced or added"
and
"Context root"

The Sample JSP actually shows under the Add Content, but when I click on it, I get a portlet with "Sample JSP" as the title with no icon and a "Sample JSP is temporarily unavailable." message in the body.

I'm missing something somewhere and can't figure it out. emoticon

Please help.

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

September 9, 2008 10:35 PM

Answer

Faisal K

Rank: Regular Member

Posts: 138

Join Date: January 9, 2008

Hi All,

I know this is not the place to ask this question, but let me ask one question, have any body deployed portlets-war in to WebSphere Server Community Edition. If then please help me what are the changes I have to make in the sample-struts-portlet.war from liferay to deploy on WebSphere set upped with liferay-5.0.1.

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

January 23, 2009 10:20 AM

Answer

LIFERAY STAFF

Rank: Regular Member

Posts: 187

Join Date: February 7, 2007

Here's how to get plugins installed in WebSphere:

1. If you don't have one already, create a portal-ext.properties file in the WEB-INF/classes folder of your Liferay installation. Add the following directive to it:

auto.deploy.dest.dir=${resource.repositories.root}/websphere-deploy

2. Create a folder called websphere-deploy inside your $LIFERAY_HOME folder. This is the folder where the Lucene index, Jackrabbit config, and deploy folders are.

3. Make sure the web.xml file inside the plugin you want to install has the following context parameter in it:

<context-param>
<param-name>com.ibm.websphere.portletcontainer.PortletDeploymentEnabled</param-name>
<param-value>false</param-value>
</context-param>

4. The WebSphere deploy occurs in two steps. You will first use Liferay's tools to "pre-deploy" the file, and then use WebSphere's tools to do the actual deployment. This is because Liferay makes deployment-time modifications to the plugins right before they are actually deployed to the application server. For other application servers, this can usually be done in one step, because Liferay can make the modifications and then copy the resulting .war file into an autodeploy folder to have it actually deployed. Because WebSphere does not have an autodeploy feature, we need to separate these two steps.

5. Deploy your .war file using Liferay's Plugin Installer or by copying it into $LIFERAY_HOME/deploy. Liferay will make its modifications and because we changed the auto.deploy.dest.dir in the first step, it will copy the resulting .war file into $LIFERAY_HOME/websphere-deploy. You will see a "copied successfully" message.

6. Use WebSphere's tools to deploy the .war file that is in $LIFERAY_HOME/websphere-deploy. Make the context root for the .war file equal to the file name (i.e., /my-first-portlet). Once the .war file is deployed, save it to the master configuration.

7. Go back to the Applications -> Enterprise Applications screen. You will see that your portlet is deployed, but not yet started. Start it.

8. Liferay will immediately recognize that the portlet has been deployed and register it. The portlet will be automatically started and registered upon subsequent restarts of WebSphere.

You may see the following exception in the log, which can be ignored as it does not affect the functioning of the portlet (i.e., the portlet can access the database normally without issues).

[1/23/09 13:01:29:646 EST] 0000001d Helpers W NMSV0610I: A NamingException is being thrown from a javax.naming.Context implementation. Details follow:
Context implementation: com.ibm.ws.naming.jndicos.CNContextImpl
Context method: bind
Context name: enterpriseNode01Cell/nodes/enterpriseNode01/servers/server1
Target name: java_liferay:jdbc/LiferayPool
Other data: Object to bind: org.springframework.jdbc.datasource.LazyConnectionDataSourceProxy@5dfe5dfe
Exception stack trace: com.ibm.ws.naming.util.CannotBindObjectException: Object is not of any type which can be bound.
at com.ibm.ws.naming.util.Helpers.processJavaObjectForBinding(Helpers.java:628)
at com.ibm.ws.naming.jndicos.CNContextImpl.doBind(CNContextImpl.java:2237)
at com.ibm.ws.naming.jndicos.CNContextImpl.bind(CNContextImpl.java:534)
at com.ibm.ws.naming.util.WsnInitCtx.bind(WsnInitCtx.java:210)
at javax.naming.InitialContext.bind(InitialContext.java:371)
at com.liferay.portal.kernel.servlet.PortletContextListener.portalInit(PortletContextListener.java:116)
at com.liferay.portal.kernel.util.PortalInitableUtil.flushInitables(PortalInitableUtil.java:39)
at com.liferay.portal.servlet.MainServlet.init(MainServlet.java:435)

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

January 23, 2009 12:02 PM

Answer

Faisal K

Rank: Regular Member

Posts: 138

Join Date: January 9, 2008

Hi Rich Sezov,

Thanks for the reply, I will try this out.

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

January 23, 2009 12:31 PM

Answer

Dark Helmet

Rank: New Member

Posts: 3

Join Date: October 28, 2007

Hi Rich,
I tried this, and still Liferay does not recognize that the portlet has been deployed and or registers it. The plugin war deploys and starts without any errors, but Liferay does not see it. Any other suggestions?

Can you describe how you have the Liferay.war deployed. Is it deployed w/o dependencies? Where are the dependencies deployed at? lib/ext? shared library? What jars all need to be deployed as dependencies?

Thanks for the help

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

January 23, 2009 1:01 PM

Answer

LIFERAY STAFF

Rank: Regular Member

Posts: 187

Join Date: February 7, 2007

Hi Jon,

An absolute requirement for this is to be running WebSphere 6.1.0.9 or higher. Otherwise, you won't be able to install any plugins at all, because IBM's Portlet Container that comes will WebSphere will interfere with Liferay's ability to see them. As of 6.1.0.9, IBM fixed this by creating the context parameter outlined in the solution above.

As far as the Liferay .war goes, I have the same configuration outlined in the Portal Administrator's Guide, starting on p. 78. All of the server installation instructions use Liferay .war without the dependencies, and put the dependencies (downloaded separately as a .zip file) on the server's global class path. This is necessary for plugins to work.

Briefly, in AppServer/lib/ext, I have:
annotations.jar
container.jar
mysql-connector-java-5.1.5-bin.jar
portal-kernel.jar
portal-service.jar
portlet-container.jar
portlet.jar

Also, as outlined on p. 79 of the Portal Administrator's Guide, you will need to copy portlet.jar and icu4j.jar into AppServer/java/jre/lib/ext. The reasons for this are outlined in the errata.

When you deploy your plugin .war via the Plugin Installer, you should get a "copied successfully" message. You then need to pick up the .war file from where it was copied and deploy it to WebSphere manually. After you deploy and save to the master configuration, you need to go and manually start it. Once you start it, as long as the .war has already passed through Liferay's deploy process AND you have the context parameter set in web.xml, Liferay should recognize it and display a "registered successfully" message. Once the portlet is registered, it will appear in the Add Application window.

I would recommend you try all of this with one of Liferay's downloadable portlets first, since they have been deployed many times without issues. You will probably have to modify the web.xml to add IBM's context parameter first, but after that it should deploy normally. Alternatively, I have attached to this message the portlet I tested this with. This is an unfinished portlet I'm working on while writing the Liferay Developer's Guide. Just take the .zip off the file name and deploy.

Attachments:

product-registration-portlet-5.2.0.1.war.zip (646.8k)

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

January 23, 2009 2:13 PM

Answer

Dark Helmet

Rank: New Member

Posts: 3

Join Date: October 28, 2007

Hi Rich,
Thanks for the response.

I am running Liferay 5.1.3 EE on WAS 6.1.0.21 setup just as the Admin Guide suggests and your directions. When I put the dependencies in the AppServer/lib/ext directory WAS gives this execption:

---- Begin backtrace for Nested Throwables
java.lang.VerifyError: class loading constraint violated (class: com/liferay/portal/model/impl/PortletImpl method: addProcessingEvent(Ljavax/xml/namespace/QName;)V) at pc: 0
at java.lang.J9VMInternals.verifyImpl(Native Method)
at java.lang.J9VMInternals.verify(J9VMInternals.java:68)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:129)
at com.liferay.portal.service.impl.PortletLocalServiceImpl._readPortletXML(PortletLocalServiceImpl.java:1216)
at com.liferay.portal.service.impl.PortletLocalServiceImpl._readPortletXML(PortletLocalServiceImpl.java:1092)
at com.liferay.portal.service.impl.PortletLocalServiceImpl.initEAR(PortletLocalServiceImpl.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy66.initEAR(Unknown Source)

I think this means that a jar from the dependencies is trying to load a class from WEB-INF/lib (portal-imp.jar?)

You don't get this error? What could I be missing?

I can get Liferay to run if I package the dependencies at the EAR level, but then the portlets don't get registered when I deploy the seperate plugins war.

Any help is appreciated.

Thanks again....

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

January 23, 2009 3:47 PM

Answer

LIFERAY STAFF

Rank: Regular Member

Posts: 187

Join Date: February 7, 2007

Hey Jon,

I think I figured this one out. There's a .jar file in the Liferay .war file called annotations.jar. Take that file and move it into AppServer/lib/ext. Once I did that, it worked normally (though I did have to report a couple of bugs in some JSPs). :-)

Let me know if that works for you.

--Rich

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

January 24, 2009 12:09 AM

Answer

Brian Chan

LIFERAY STAFF

Rank: Liferay Master

Posts: 748

Join Date: August 4, 2004

Hey Rich,

I moved annotations.jar to the global classpath and it's now part of the dependencies packages. Thanks!

http://issues.liferay.com/browse/LPS-1774

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

January 26, 2009 6:43 AM

Answer

LIFERAY STAFF

Rank: Regular Member

Posts: 187

Join Date: February 7, 2007

Thanks, Brian!

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

February 2, 2009 7:11 PM

Answer

Brian Chan

LIFERAY STAFF

Rank: Liferay Master

Posts: 748

Join Date: August 4, 2004

http://issues.liferay.com/browse/LPS-1896

I also made it so you don't need to modify web.xml anymore since we'll massage it programmatically.

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

February 17, 2009 7:02 AM

Answer

Kevin S Neibarger

Rank: New Member

Posts: 5

Join Date: February 11, 2009

Hi Rich - I noticed that with step 6 of these instructions that the files get expanded and put into a folder in websphere-deploy.

6. Use WebSphere's tools to deploy the .war file that is in $LIFERAY_HOME/websphere-deploy. Make the context root for the .war file equal to the file name (i.e., /my-first-portlet). Once the .war file is deployed, save it to the master configuration.

It doesn't actually get save as a WAR so I have to zip up the files and rename as a WAR. It works ok, but is there a way to configure this so that only a WAR gets copied to the websphere-deploy folder?

thanks,
Kevin

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

February 17, 2009 8:53 PM

Answer

LIFERAY STAFF

Rank: Regular Member

Posts: 187

Join Date: February 7, 2007

Hi Kevin,

There's actually a property you can set for this in your portal-ext.properties file:

auto.deploy.unpack.war=false

Hope this helps!

--Rich

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

April 6, 2009 12:42 PM

Answer

Henry Wong

Rank: New Member

Posts: 7

Join Date: April 6, 2009

Hi there,

I have been trying to deploy portlets in Liferay 5.2.2 running on WebSphere 6.1. This thread has been a great help. I can see the portlet I want to add in the "Add Application" dialog and successfully add it...
but I am getting the following error:

Error 404: SRVE0190E: File not found: /PentahoNewsPortlet/invoke

I noticed other people in this thread encountered similar messages but still am not clear on how to remedy it.

Here is how the entry in portlet.xml looks like:
<portlet>
<portlet-name>PentahoNewsPortlet</portlet-name>
<portlet-class>
org.pentaho.ui.portlet.HtmlPortlet
</portlet-class>
<supports>
<mime-type>text/html</mime-type>
<portlet-mode>VIEW</portlet-mode>
</supports>
<resource-bundle>
org.pentaho.locale.portlet
</resource-bundle>
<portlet-info>
<title>PentahoNewsPortlet</title>
</portlet-info>
<portlet-preferences>
<preference>
<name>location</name>
<value>http://www.pentaho.org/demo/news.php</value>
</preference>
<preference>
<name>error</name>
<value>
Welcome to the Pentaho BI Platform Demo
Portal<p/>When you are connected to the
Internet you will see current news from Pentaho
here.
</value>
</preference>
</portlet-preferences>
</portlet>

Thanks,
Henry

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

April 7, 2009 8:24 AM

Answer

LIFERAY STAFF

Rank: Regular Member

Posts: 187

Join Date: February 7, 2007

Hello Henry,

From what I understand, there are problems with the Pentaho portlets on Liferay 5.2.2. I believe they work on our Liferay 5.1.x version only at this time. So this is likely not a problem with installing the portlets on WebSphere, but with the portlets themselves.

Can you try a known working portlet from our repository as a test? That way we can eliminate any potential problems with the Pentaho portlets. Alternatively, you can attempt to install the Pentaho portlets on one of our bundles and see if they work there. Or you could download Liferay 5.1.2 and try the portlets there, and if they work, you might consider our Enterprise Edition for your installation.

Hope this helps!

--Rich

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

April 8, 2009 2:02 AM

Answer

Daniel D. Barciela

Rank: New Member

Posts: 23

Join Date: April 7, 2009

Jonathan Alexander Diosa:

Hi!
I was successful to deploy the sample portlet, but every time I try to deploy any other portlet I get this error:

[08-04-2009 9:46:57:704 BST] 00000025 ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: PortletServingServlet_/dport/*. Exception thrown : java.lang.ClassCastException: com.liferay.portlet.RenderRequestImpl incompatible with javax.portlet.PortletRequest
at com.ibm.ws.portletcontainer.core.impl.ServletInvocationListenerImpl.getInternalPortletRequest(ServletInvocationListenerImpl.java:62)
at com.ibm.ws.portletcontainer.core.impl.ServletInvocationListenerImpl.onServletStartService(ServletInvocationListenerImpl.java:32)
at com.ibm.ws.webcontainer.webapp.FireOnServletStartService.fireEvent(WebAppEventSource.java:325)
at com.ibm.ws.webcontainer.util.EventListeners.fireEvent(EventListeners.java:50)
at com.ibm.ws.webcontainer.webapp.WebAppEventSource.onServletStartService(WebAppEventSource.java:112)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1124)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1084)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:118)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:832)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:679)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:587)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481)
at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:122)
at com.ibm.ws.portletcontainer.portletserving.PortletServingExtensionProcessor.handleRequest(PortletServingExtensionProcessor.java:94)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.include(WebAppRequestDispatcher.java:639)
at com.liferay.portlet.InvokerPortletImpl.invoke(InvokerPortletImpl.java:616)
at com.liferay.portlet.InvokerPortletImpl.invokeRender(InvokerPortletImpl.java:698)
at com.liferay.portlet.InvokerPortletImpl.render(InvokerPortletImpl.java:417)
at com.ibm._jsp._render_5F_portlet._jspService(_render_5F_portlet.java:1402)
at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1143)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1084)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:118)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:832)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:679)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:587)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481)
at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:122)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:226)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.include(WebAppRequestDispatcher.java:639)
at com.liferay.portal.util.PortalImpl.renderPortlet(PortalImpl.java:2801)
at com.liferay.portal.util.PortalUtil.renderPortlet(PortalUtil.java:858)
at com.liferay.portlet.layoutconfiguration.util.RuntimePortletUtil.processPortlet(RuntimePortletUtil.java:170)
at com.liferay.portlet.layoutconfiguration.util.RuntimePortletUtil.processPortlet(RuntimePortletUtil.java:103)
at com.liferay.portlet.layoutconfiguration.util.RuntimePortletUtil.processTemplate(RuntimePortletUtil.java:281)
at com.liferay.portlet.layoutconfiguration.util.RuntimePortletUtil.processTemplate(RuntimePortletUtil.java:190)
at com.ibm._jsp._portlet._jspService(_portlet.java:796)
at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1143)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1084)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:118)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:832)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:679)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:587)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481)
at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:122)
at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:226)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.include(WebAppRequestDispatcher.java:639)
at com.liferay.portal.action.LayoutAction.includeLayoutContent(LayoutAction.java:294)
at com.liferay.portal.action.LayoutAction.processLayout(LayoutAction.java:466)
at com.liferay.portal.action.LayoutAction.execute(LayoutAction.java:195)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at com.liferay.portal.struts.PortalRequestProcessor.process(PortalRequestProcessor.java:159)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
at com.liferay.portal.servlet.MainServlet.callParentService(MainServlet.java:505)
at com.liferay.portal.servlet.MainServlet.service(MainServlet.java:732)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1143)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1084)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:118)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:832)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:679)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:587)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:321)
at com.liferay.portal.servlet.FriendlyURLServlet.service(FriendlyURLServlet.java:143)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1143)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1084)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:154)
at com.liferay.portal.servlet.filters.strip.StripFilter.processFilter(StripFilter.java:142)
at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:91)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:154)
at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:94)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:154)
at com.liferay.portal.servlet.filters.secure.SecureFilter.processFilter(SecureFilter.java:282)
at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:91)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:154)
at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:94)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:154)
at com.liferay.portal.servlet.filters.cache.CacheFilter.processFilter(CacheFilter.java:417)
at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:91)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:154)
at com.liferay.portal.servlet.filters.autologin.AutoLoginFilter.processFilter(AutoLoginFilter.java:244)
at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:91)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:154)
at com.liferay.portal.servlet.filters.sso.opensso.OpenSSOFilter.processFilter(OpenSSOFilter.java:73)
at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:91)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:154)
at com.liferay.portal.sharepoint.SharepointFilter.processFilter(SharepointFilter.java:193)
at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:91)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:154)
at com.liferay.portal.servlet.filters.virtualhost.VirtualHostFilter.doFilter(VirtualHostFilter.java:188)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:154)
at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:94)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:738)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:832)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:679)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:587)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:748)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1466)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:119)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:267)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:196)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:751)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)

[08-04-2009 9:46:57:845 BST] 00000025 SystemOut O 09:46:57,783 ERROR [jsp:165] java.lang.ClassCastException: com.liferay.portlet.RenderRequestImpl incompatible with javax.portlet.PortletRequest
at com.ibm.ws.portletcontainer.core.impl.ServletInvocationListenerImpl.getInternalPortletRequest(ServletInvocationListenerImpl.java:62)
at com.ibm.ws.portletcontainer.core.impl.ServletInvocationListenerImpl.onServletFinishService(ServletInvocationListenerImpl.java:50)
at com.ibm.ws.webcontainer.webapp.FireOnServletFinishService.fireEvent(WebAppEventSource.java:333)
at com.ibm.ws.webcontainer.util.EventListeners.fireEvent(EventListeners.java:50)
at com.ibm.ws.webcontainer.webapp.WebAppEventSource.onServletFinishService(WebAppEventSource.java:116)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1239)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1084)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:118)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:832)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:679)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:587)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481)
at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:122)
at com.ibm.ws.portletcontainer.portletserving.PortletServingExtensionProcessor.handleRequest(PortletServingExtensionProcessor.java:94)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.include(WebAppRequestDispatcher.java:639)
at com.liferay.portlet.InvokerPortletImpl.invoke(InvokerPortletImpl.java:616)
at com.liferay.portlet.InvokerPortletImpl.invokeRender(InvokerPortletImpl.java:698)
at com.liferay.portlet.InvokerPortletImpl.render(InvokerPortletImpl.java:417)
at com.ibm._jsp._render_5F_portlet._jspService(_render_5F_portlet.java:1402)

Thanks.

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

April 8, 2009 7:00 AM

Answer

LIFERAY STAFF

Rank: Regular Member

Posts: 187

Join Date: February 7, 2007

Hello,

It looks like this is the problem:

Exception thrown : java.lang.ClassCastException: com.liferay.portlet.RenderRequestImpl incompatible with javax.portlet.PortletRequest at com.ibm.ws.portletcontainer.core.impl.ServletInvocationListenerImpl.getInternalPortletRequest(ServletInvocationListenerImpl.java:62)

WebSphere 6.1 ships with the Portlet 1.0 (JSR-168) classes on its class path. These work with the embedded portlet container.

Liferay 5.x requires the Portlet 2.0 (JSR-286) classes to be on its class path. It looks like the Portlet 1.0 classes are the ones on your class path, for whatever reason. There is a way to force WebSphere to load the Portlet 2.0 classes first; please see the following link for instructions:

http://www.liferay.com/web/guest/community/wiki/-/wiki/Main/2nd%20Edition

--Rich

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

April 20, 2009 9:08 AM

Answer

Daniel D. Barciela

Rank: New Member

Posts: 23

Join Date: April 7, 2009

To force WebSphere to load the updated versions of these classes before the ones it already has, both portlet.jar (which can be found in Liferay's dependencies archive) and icu4j.jar (which can be found in Liferay's WEB-INF/lib folder) need to be copied to WebSphere/AppServer/java/lib/jre/ext.

Hi again,
Thanks a lot, that resolved that problem but now it has a new one.

[08-04-2009 17:26:18:040 BST] 00000028 ServletWrappe E SRVE0068E: Uncaught exception thrown in one of the service methods of the servlet: olamundo. Exception thrown : java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 1
at com.liferay.portlet.PortletRequestDispatcherImpl.dispatch(PortletRequestDispatcherImpl.java:184)

This is just the beginning of the error log. Do you know what can be in the origin of this? It appeared when I changed the servlet in web.xml of my portlet, before that, there was a different error with the text "Error 404: SRVE0190E: File not found: /olamundo/invoke "
I'll attach my xml files.

Thanks,
Daniel Barciela

EDIT:
Problem solved:
http://issues.liferay.com/browse/LPS-956

Attachments:

faces-config.xml (1.3k), liferay-display.xml (0.2k), liferay-portlet.xml (0.7k), portlet.xml (1.1k), web.xml (9.6k)

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

February 1, 2010 8:34 AM

Answer

Juan Parra

Rank: New Member

Posts: 1

Join Date: February 1, 2010

Hellow,

I hope that some one can help me, I install WAS 6.1 and fix to pak 29, result is 6.1.0.29. Then, I installed Liferay 5.2.3, but I need the dependency jar in a shared library not in the lib/ext folder. I created a shared library and add this jars:

D:\WebSphere\AppServer\optionalLibraries\Liferay\portal-kernel.jar
D:\WebSphere\AppServer\optionalLibraries\Liferay\portal-service.jar
D:\WebSphere\AppServer\optionalLibraries\Liferay\portlet.jar
D:\WebSphere\AppServer\optionalLibraries\Liferay\container.jar
D:\WebSphere\AppServer\optionalLibraries\Liferay\portlet-container.jar
D:\WebSphere\AppServer\optionalLibraries\Liferay\annotations.jar
D:\WebSphere\AppServer\optionalLibraries\Liferay\saw-api.jar

And configure the shared library in the Liferay EAR:

Select Application URI Shared Libraries
liferay-portal-5_2_3_war META-INF/application.xml LiferayDeps523

Select Module URI Shared Libraries
liferay-portal-5.2.3.war liferay-portal-5.2.3.war,WEB-INF/web.xml LiferayDeps523

finally, change the class loader to:

Classes loaded with application class loader first
Single class loader for application

Start the Liferay application and everything look find.

Then, I install sample-jsf-1.2-sun-facelets-portlet-5.2.0.1.war, I followed the steps, additionally, I configured additional shared libraries with this:

D:\WebSphere\AppServer\optionalLibraries\Liferay\portal-kernel.jar
D:\WebSphere\AppServer\optionalLibraries\Liferay\portal-service.jar
D:\WebSphere\AppServer\optionalLibraries\Liferay\portlet.jar
D:\WebSphere\AppServer\optionalLibraries\Liferay\container.jar
D:\WebSphere\AppServer\optionalLibraries\Liferay\portlet-container.jar
D:\WebSphere\AppServer\optionalLibraries\Liferay\log4j.jar
D:\WebSphere\AppServer\optionalLibraries\Liferay\annotations.jar
D:\WebSphere\AppServer\optionalLibraries\Liferay\liferay-icu4j.jar
D:\WebSphere\AppServer\optionalLibraries\Liferay\saw-api.jar

And add it to the sample ear, change the class loader too:

Select Application URI Shared Libraries
sample-jsf-sun-facelets-portlet_war META-INF/application.xml LiferayDepPortlets

Select Module URI Shared Libraries
sample-jsf-sun-facelets-portlet sample-jsf-sun-facelets-portlet.war,WEB-INF/web.xml LiferayDepPortlets

I stared this application and no errors in the logs:

[2/1/10 10:31:31:262 COT] 00000016 ApplicationMg A WSVR0200I: Starting application: sample-jsf-sun-facelets-portlet_war
[2/1/10 10:31:31:277 COT] 00000016 ApplicationMg A WSVR0204I: Application: sample-jsf-sun-facelets-portlet_war Application build level: Unknown
[2/1/10 10:31:42:465 COT] 00000016 WebGroup A SRVE0169I: Loading Web Module: sample-jsf-sun-facelets-portlet.
[2/1/10 10:31:49:230 COT] 00000016 config I Initializing Mojarra (1.2_08-b06-FCS) for context 'sample-jsf-sun-facelets-portlet'
[2/1/10 10:31:50:355 COT] 00000016 application I JSF1048: PostConstruct/PreDestroy annotations present. ManagedBeans methods marked with these annotations will have said annotations processed.
[2/1/10 10:31:50:621 COT] 00000016 ServletWrappe I SRVE0242I: [sample-jsf-sun-facelets-portlet_war] [/sample-jsf-sun-facelets-portlet] [1]: Initialization successful.
[2/1/10 10:31:50:808 COT] 00000016 VirtualHost I SRVE0250I: Web Module sample-jsf-sun-facelets-portlet has been bound to default_host[*:9080,*:80,*:9443,*:5060,*:5061,*:443].
[2/1/10 10:31:50:839 COT] 00000015 WebGroup A SRVE0169I: Loading Web Module: isclite.
[2/1/10 10:31:50:871 COT] 00000016 ApplicationMg A WSVR0221I: Application started: sample-jsf-sun-facelets-portlet_war

Everything looks great, but, when I use the "add application" to find the new sample portlet it doesn't exist. then I try reinstall the applications, stopping and starting everything and not work. When I put the dependency jar in lib/ext and let the default configuracion of class loader, I found the new portlet and I could put it into a page. but I really need a shared library because i have a conflict whit other jar.

Mark as an Answer

RE: Deployment of plugins on WebSphere 6.1

July 23, 2010 12:50 AM

Answer

Sebastian Boss

Rank: New Member

Posts: 1

Join Date: July 23, 2010

Hello,

Do you think it's possible to make the first step of the portlet deployment (Predeployment with the Liferay tools) and use the created WAR-Files also for other installations of Liferay (same Version) on WebSphere?