PM13939: Administrative agents do not enforce requirements on registered nodes.

Fixes are available

APAR status

Closed as program error.

Error description

Adding a check during registerNode and subsystem startup to make
sure products and versions between Adminagent and the node
match. Otherwise it will prevent it from happening.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server V7 users that  *
*                  have administrative agent profiles.         *
****************************************************************
* PROBLEM DESCRIPTION: Administrative agents do not enforce    *
*                      requirements on registered nodes.       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A variety of problems may occur when the administrative agent
profile is at a different version from a registered node or is
not augmented with the same set of products. For example, if a
base profile is augmented with a feature pack but the
administrative agent profile it is registered with is not,
then ability to administer feature pack specific capabilities
is not available.

Problem conclusion

The administrative agent will enforce that base profiles and
admin agent profiles must have the same set of products at the
same version numbers when a base profile registers with
adminstrative agent and when an adminstrative agent starts a
registered node.
If you already have an administrative agent at version
7.0.0.11 or earlier with a managed node that has mismatched
products or versions, when you apply 7.0.0.13 or later to the
administrative agent it will no longer start the subsystem for
the mismatched node(s).  To allow the agent to resume managing
the registered node update the node to have the same products
and versions as the administrative agents, restart the
server(s) on the node and then restart the administrative
agent.
The fix for this APAR is currently targeted for inclusion in
fixpack 7.0.0.13. 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
PM13939
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-05-06
Closed date
2010-08-11
Last modified date
2010-09-23

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PM13939: Administrative agents do not enforce requirements on registered nodes.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?