Problems with Installing predeployed portlets

rklo...@de.ibm.com

unread,

Apr 9, 2008, 12:27:56 PM4/9/08

to

Hi everyone, 
 
I have problems installing portlets that have been predeployed via an EAR file on WAS 
 
Steps: 
 
1. Deploy an EAR file with multiple portlet WAR files via the WAS Admin (EAR is started and 
deployed on the correct server, e.g. WebSphere_Portal). 
2. Execute an xmlaccess script for installing the predeployed portlets. The xmalaccess script (see attachment) 
returns with a success message, both the web modules and the portlets are visible within the WP Admin Console, their state is not inactive). 
 
Problem: 
 
When the page is requested, the portlets are unavailable (i.e. not started and not installed) and the following execption is thrown: 

<strike>09.04.08 16:55:04:743 CEST</strike> 00000038 ServletWrappe A SRVE0242I: <a href="http://www-128.ibm.com/developerworks/forums/">wps</a> [/wps] [/skins/html/EHCP_border/Control.jsp]: Initialization successful. 
<strike>09.04.08 16:55:09:540 CEST</strike> 00000038 WAS5Admin W com.ibm.wps.pe.mgr.appserveradmin.WAS5Admin startImpl EJPPH0015W: Web Module CLIENTING_Portlets is not started. The application is not installed. 
<strike>09.04.08 16:55:09:602 CEST</strike> 00000038 PortletRender E com.ibm.wps.engine.tags.PortletRenderTag doStartTag EJPEJ0066E: The portlet could not be rendered. 
javax.portlet.UnavailableException: WebApplication is not available 
at com.ibm.wps.pe.om.definition.impl.WebApplicationDefinitionImpl.getWebAppContext(WebApplicationDefinitionImpl.java:354) 
at com.ibm.wps.pe.om.definition.impl.WebApplicationDefinitionImpl.getServletContext(WebApplicationDefinitionImpl.java:183) 
at com.ibm.wps.pe.om.definition.impl.ServletDefinitionImpl.getRequestDispatcher(ServletDefinitionImpl.java:234) 
... 
 
Caused by: org.apache.pluto.PortletContainerException: EJPPG0017E: Web application for context root CLIENTING_Portlets is unavailable. 
at com.ibm.wps.pe.om.definition.impl.WebApplicationDefinitionImpl.getWebAppContext(WebApplicationDefinitionImpl.java:355) 
... 168 more 
 
Setup: WP 6.0.1, WAS 6.0.2.17, JSR 168 Portlets, JSF 1.1 

In Portal V5.x is was possible to active/deactive portlets via the WP admin portlets (a link in the state column). 
This feature does not seem to be available in WP 6 anymore. Is there another way to active/deactivate a portlet via the admin portlets ? 

Any help would be highly appreciated.

Jim Barnes

unread,

Apr 9, 2008, 2:52:31 PM4/9/08

to

well there is active from wp, and then active from was admin console, you can activate it if it is stopped like after a deploy, but you cannot deactivte. Only option is to do it via xmlaccess. Have you made sure the app is started in was and on the right server? 
 
 
IBM Certified System Administrator -- WebSphere Portal V6.0, V5.1, V5.0 
IBM Certified Solution Developer -- WebSphere Portal V5.1, v6.0 
 
The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM

rklo...@de.ibm.com

unread,

Apr 10, 2008, 4:15:19 AM4/10/08

to

The Enterprise Application (EAR file) ist started via WAS admin console on the right server (WebSpere_Portal) 
 
Both the web modules and the portlets contained within the EAR file are visible within the WP Admin Console after 
executing the predeploy xmlaccess script. Their state is not displayed, i.e. they seem to be active. 
 
When explicitly trying to activate the portlets(after the predeployment)via the following xmlaccess script (same 
as sample script in the WP InfoCenter): 
 
<pre>
<?xml version="1.0" encoding="UTF-8"?> 
<request 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:noNamespaceSchemaLocation="PortalConfig_1.4.xsd" 
type="update" 
create-oids="true"> 
<portal action="locate"> 
</web-app> 
<web-app action="update" active="true" uid="clienting.portletApp.webmod"> 
<portlet-app action="update" active="true" uid="clienting.portletApp"> 
<portlet action="update" active="true" name="clienting.KitQuickLinksPortlet"/> 
<portlet action="update" active="true" name="clienting.ExternalLinksPortlet"/> 
<portlet action="update" active="true" name="clienting.ContactHistoryPortlet"/> 
<portlet action="update" active="true" name="clienting.KitPortlet"/> 
</portlet-app> 
</web-app> 
</portal> 
</request> 
</pre>
 
the following exception occurs: 
 
<pre>
<request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" build="wp601_194" type="update" version="6.0.1.0" xsi:noNamespaceSchemaLocation="PortalConfig_6.0.1.xsd"> 
<status element="<a href="http://www-128.ibm.com/developerworks/forums/">web-app</a>" result="failed"> 
<message id="EJPXA0067E">com.ibm.wps.command.xml.XmlCommandException: EJPXA0067E: The following configuration data is needed to create a web-app resource: url. <a href="http://www-128.ibm.com/developerworks/forums/">web-app</a></message> 
</status> 
</request> 
</pre>
 
when adding the <url> pointing to the WAR file directory: 
 
<pre><url>file://localhost/D:/ibm/WebSphere/profiles/wp_profile/installedApps/cell01/CLIENTING_KIT_PortletsEAR.ear/CLIENTING_Portlets</url></pre>

the following exception occurs: 
 
<pre>
 
<request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" build="wp601_194" type="update" version="6.0.1.0" xsi:noNamespaceSchemaLocation="PortalConfig_6.0.1.xsd"> 
<status element="<a href="http://www-128.ibm.com/developerworks/forums/">web-app 1_4QESU6F10010F02JCIVHL20GS1</a>" result="failed"> 
<message id="EJPXA0043E">com.ibm.wps.command.xml.XmlCommandException: EJPXA0043E: An error occurred while creating or updating the resource. <a href="http://www-128.ibm.com/developerworks/forums/">web-app 1_4QESU6F10010F02JCIVHL20GS1</a></message> 
<message id="EJPPD0030E">com.ibm.wps.command.applications.AppDeployException: EJPPD0030E: It is not allowed to update the predeployed EAR file CLIENTING_Portlets with the WAR file CLIENTING_Portlets. The error occurred in command UpdateWebApplication.</message> 
</status> 
</request> 
</pre>

What URL is supposed to be used within the activate xmlaccess script ?

Jim Barnes

unread,

Apr 10, 2008, 7:30:47 AM4/10/08

to

I think your url should look like this 
file://localhost/D:/ibm/WebSphere/profiles/wp_profile/installedApps/cell01/CLIENTING_KIT_PortletsEAR.ear/CLIENTING_Portlets.war 
 
it needs to point to the base war directory.

rklo...@de.ibm.com

unread,

Apr 10, 2008, 8:55:16 AM4/10/08

to

The url is correct, I have change the standard value of the <web-uri> element within the EAR's application.xml from CLIENTING_Portlets.war to CLIENTING_Portlets. I have also tried the standard value and it does not work. 
 
For some reason portal thinks that the portlets are not actually installed/activated (even so the WP admin portlets 
says they are). 
 
What I do not understand is why does the xmlaccess server require the <url> element within the activate script ? The sample script within the WP InfoCenter is supposed to do without: 
 
http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/topic/com.ibm.wp.exp.doc/wps/admxmsmp.html?noframes=true#admxmsmp__activateportlet

rklo...@de.ibm.com

unread,

Apr 10, 2008, 9:46:27 AM4/10/08

to

Oops, I have posted a wrong error message in the previous post (2008 07:44:52 AM): 
 
The error message when executing the activatePortlets xmlaccess script with the <url> element is:

<status element="<a href="http://www-128.ibm.com/developerworks/forums/">web-app</a>" result="failed"> 
<message id="EJPXA0043E">com.ibm.wps.command.xml.XmlCommandException: EJPXA0043E: An error occurred while creating or updating the resource. <a href="http://www-128.ibm.com/developerworks/forums/">web-app</a></message> 
<message id="EJPPF0181E">com.ibm.wps.command.applications.AppAlreadyExistsException: EJPPF0181E: Error occurred. The id=clienting.addresssearch.portletApp already exists for stored standard portlet application clienting.addresssearch.portletApp in the XML element portlet-app CLIENTING_Portlets_AddressSearch.war. 
WrappedException is: com.ibm.wps.pe.mgr.exceptions.DuplicateAppException: EJPPF0181E: Error occurred. The id=clienting.addresssearch.portletApp already exists for stored standard portlet application clienting.addresssearch.portletApp in the XML element portlet-app CLIENTING_Portlets_AddressSearch.war.</message> 
<message id="EJPPF0181E">com.ibm.wps.pe.mgr.exceptions.DuplicateAppException: EJPPF0181E: Error occurred. The id=clienting.addresssearch.portletApp already exists for stored standard portlet application clienting.addresssearch.portletApp in the XML element portlet-app CLIENTING_Portlets_AddressSearch.war.</message>

rklo...@de.ibm.com

unread,

Apr 21, 2008, 10:34:35 AM4/21/08

to

The element in the the predeployPortlets.xml script is wrong, a leading slash is missing:

/CLIENTING_Portlets

When adding a slash, the portlets are properly activated within WP.