APAR status
Closed as program error.
Error description
Federating a WebSphere Application Server V7 node augmented with the OSGi applications feature and/or the JPA 2.0 feature with a WebSphere Application Server V8 deployment manager fails in the addNode command with an AdminException. For the OSGi Applications feature: com.ibm.websphere.management.exception.AdminException: addNode validation has failed. The OSGi Applications feature is installed on this node, but is not installed on the Deployment Manager. The Deployment Manager must also have the OSGi Applications feature installed. The node has not been added. For the JPA 2.0 feature: com.ibm.websphere.management.exception.AdminException: addNode validation has failed. The JPA 2.0 feature is installed on this node, but is not installed on the Deployment Manager. The Deployment Manager must also have the JPA 2.0 feature installed. The node has not been added.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server Feature * * Pack * * for OSGi Applications and JPA 2.0 users and * * WebSphere Application Server version 8.0 * * users * * that want to set up mixed cell * * environments * **************************************************************** * PROBLEM DESCRIPTION: AdminException is thrown from the * * addNode * * command for a node augmented with the * * Feature Pack for OSGi applications and * * JPA 2.0 * **************************************************************** * RECOMMENDATION: * **************************************************************** A WebSphere Application Server version 7 node augmented with the Feature Pack for OSGi Applications and JPA 2.0 does not recognise a WebSphere Application Server version 8 deployment manager as a valid federation target. As a consequence the addNode command fails with an AdminException. Depending on whether the OSGi applications feature, the JPA 2.0 feature or both are installed either of two error messages may be displayed: com.ibm.websphere.management.exception.AdminException: addNode validation has failed. The JPA 2.0 feature is installed on this node, but is not installed on the Deployment Manager. The Deployment Manager must also have the JPA 2.0 feature installed. The node has not been added. com.ibm.websphere.management.exception.AdminException: addNode validation has failed. The OSGi Applications feature is installed on this node, but is not installed on the Deployment Manager. The Deployment Manager must also have the OSGi Applications feature installed. The node has not been added.
Problem conclusion
The fix for this APAR is currently targeted for inclusion in fix pack 1.0.0.7. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss? rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM35835
Reported component name
JPA OSGI FEATUR
Reported component ID
5724J0857
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-03-29
Closed date
2011-07-19
Last modified date
2011-07-19
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
JPA OSGI FEATUR
Fixed component ID
5724J0857
Applicable component levels
R700 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 September 2020