|
Home > Archive > WebSphere Portal Server > October 2004 > Activate Portlet Fails for all Lotus Collab Portlets (EnablePortlet)?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Activate Portlet Fails for all Lotus Collab Portlets (EnablePortlet)?
|
|
| justin@spicer.com.au 2004-08-03, 2:49 am |
| I finally wrestled all of the v6.5.1.1 LCC portlets into my v5.0.2.1 Portal Server cluster, after manually installing each .war file (the deploy.sh task kept failing).
However, now they all appear in my portlets list, but when i try to activate any of them, i get the following error:
--------------------------------------------------------
APPA0027E: Activate portlet failed.
com.ibm.portal.WpsException: APPA0027E: Activate portlet failed. at com.ibm.wps.portlets.managePortlets.ManagePortlets.enablePortlet(ManagePortlets.java:610) at com.ibm.wps.portlets.managePortlets.ManagePortlets.doView(ManagePortlets.java:120) at org.a
pache.jetspeed.portlet.PortletAdapter.service(PortletAdapter.java:154) at org.apache.jetspeed.portlet.Portlet._dispatch(Portlet.java:744) at org.apache.jetspeed.portlet.Portlet.access$100(Portlet.java:88) at org.apache.jetspeed.portlet.Portlet$Context.cal
lPortlet(Portlet.java:899) at com.ibm.wps.pe.pc.legacy.cmpf.impl.PortletFilterManager.doFilter(PortletFilterManager.java:253) at org.apache.jetspeed.portlet.Portlet.dispatch(Portlet.java:636) at org.apache.jetspeed.portlet.Portlet.doPost(Portlet.java:516)
PECM0009E: Application Descriptor EnablePortlet must be active to execute command com.ibm.lotus.rp.1.
com.ibm.wps.command.portlets.ParentNotActivatedException: PECM0009E: Application Descriptor EnablePortlet must be active to execute command com.ibm.lotus.rp.1. at com.ibm.wps.command.portlets.AbstractPortletsCommand.throwParentNotActiveException(AbstractP
ortletsCommand.java:97) at com.ibm.wps.command.portlets.EnablePortletCommand.execute(EnablePortletCommand.java:146) at com.ibm.wps.portlets.managePortlets.ManagePortlets.enablePortlet(ManagePortlets.java:608) at com.ibm.wps.portlets.managePortlets.ManageP
ortlets.doView(ManagePortlets.java:120) at org.apache.jetspeed.portlet.PortletAdapter.service(PortletAdapter.java:154) at org.apache.jetspeed.portlet.Portlet._dispatch(Portlet.java:744) at org.apache.jetspeed.portlet.Portlet.access$100(Portlet.java:88) at
org.apache.jetspeed.portlet.Portlet$Context.callPortlet(Portlet.java:899) at com.ibm.wps.pe.pc.legacy.cmpf.impl.PortletFilterManager.doFilter(PortletFilterManager.java:253)
--------------------------------------------------------
This seems to suggest there's a "parent" portlet called "EnablePortlet", that has to be activated first. I can't find anything called that? Also, all my other (non-lcc) portlets activate fine.
Any ideas?
| |
| justin@spicer.com.au 2004-08-12, 8:48 pm |
| IBM got back to me on this one, asking me to install a bunch of efixes, as follows:
<----------snipped from IBM reply---------------->
PQ87808, PQ85982, PQ87167 (pre-req PQ85982), PQ87875, and PQ89044, they can be downloaded from Portal support website at
http://www-306.ibm.com/software/gen...portal/support/
WARNING: you have to open some of the ".jar" files to get the real installable ".jar" files inside.
Try to download the newest PUI (Portal Update Installer) on the same page as well. To install these fixes, you need to install them on all the nodes individually, and on the ND (Dmgr) with "WasDM=true" (read the PUI document for details).
After applying those fixes above, install PQ89573 and PQ91463, attached in this mail (since they are not on the web site yet), the same way as those above. Also same warning applies.
With these fixes in place, the deployment of portlets using XMLaccess is basically three step process:
1. Install the portlets onto the main node;
2. Synchronization
3. Manually activate the portlets, either through WPS GUI, or through an XML file.
<----------snipped from IBM reply---------------->
I did all that, but still could not activate the lcc portlets. In the end I moved to WPS 5.0.2.2, re-installed the lcc portlets, and voila, they activated themselves, and are now working fine.
Hope this helps.
Juz.
| |
| bousch 2004-10-20, 7:49 am |
| Did you try to activate your PortletApplication first? It is not possible to activate a portlet if the portletApplication is inactive. |
|
|
|
|