Adding a portlet to a page fails with EJPAE0015E error message
IBM WebSphere Portal is successfully installed and configured. You create a new page in the Portal and attempt to add portlets to the page. Adding one more portlets fails with the error message: EJPAE0015E: Failed to add new portlets. This Technote will document how to resolve this error message and allow the portlet to be added to the page successfully.
The Portal v8 theme is installed with a deferred profile out-of-the-box. In a deferred profile not all capabilities are enabled by default. The message indicates that one or more module capabilities required by the portlet is not enabled in the deferred theme profile.
Any Portal 8.0 system.
Diagnosing the problem
One or more of the following messages may be presented to the end user when the issue occurs:
com.ibm.portal.WpsException: EJPAE0015E: Failed to add new portlets.
com.ibm.wps.model.controller.exceptions.nls.NlsCannotInsertNodeException: EJPNK0022E: Portlet null cannot be added as the capabilities [widget_container , 2.1] are missing.
Note: The specific capability missing may not be widget_container in all cases. However, the error message itself will show which capability is missing from the Portal system.
In certain cases a different error messages may appear when this situation occurs. Known error messages for this issue include:
- BMWPB0029E: An error occurred while customizing the page.
- Error 400: EJPNK0022E: portletname cannot be added as the capabilities [portal.livetext.hcard , 8.0] are missing.
Resolving the problem
Three options exist to resolve this issue:
1. Update theme profile for entire Portal site
To convert from a deferred profile to a full profile, run the following configuration task:
And restart the Portal server thereafter. The portlet should now be able to be added to the page successfully with the added capabilities now present in the Portal server configuration.
Note: In a cluster, this configuration task need only be run once on the primary node. However, ensure all nodes in the cluster are restarted after running this configuration task.
Note: For a custom modular theme either the WebDAV interface or XMLAccess scripting may be used to change from a deferred profile to a full profile for the entire Portal site. Refer to the Portal v8 Infocenter topic Changing the theme profile for more information on the specific steps. After committing the changes, restart the Portal server
2. Update theme profile for specific page
If it is not desirable to update the theme profile for the entire Portal site, it is possible to do so for a single page. Refer to the Portal v8 Infocenter topic Setting a profile override on a page for detailed options and steps to perform this action for a single page.
Note: In many cases, the Page Properties option typically will be the simplest method:
Select the "Full" profile from the drop-down menu and click Save. The portlet should now be able to be added to the specific page successfully with the added capabilities now present.
3. 220.127.116.11 or newer: Add the missing capabilities
WebSphere Portal 8 fixpack 1 added a new feature to further enhance theme profiles. Configuration tasks now exist to allow specific theme modules to be added to a given theme profile. Thus, rather than converting the entire Portal site from a deferred profile to a full profile, the missing modules may be added to the deferred profile.
Review the Portal v8 Infocenter topic ConfigEngine tasks for adding and removing theme modules for further details on how to add the missing capabilities.