PK76879: CUSTOM PROFILE METADATA.XML FOR CLUSTER CONTEXT MISSING RESOURCES CHILD-DOCUMENT-NAME

Fixes are available

APAR status

Closed as program error.

Error description

AdminConfig.getid() does not work for custom profiles in cluster
resources

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V6.1 and V7.0                               *
****************************************************************
* PROBLEM DESCRIPTION: The metadata.xml file is missing        *
*                      cluster context resource                *
*                      child-document-name property            *
****************************************************************
* RECOMMENDATION:  Edit the metadata.xml file to include the   *
*                  cluster context for custom profiles.        *
****************************************************************
AdminConfig.getid() does not work for custom profiles in a
cluster resource because of a missing metadata.xml cluster
context resource property. There are no errors in the logs or
error output from wsadmin, just an empty string is returned.

Problem conclusion

To prevent the return of an empty string when using the
AdminConfig.getid() command on custom profiles with cluster
resources, the metadata.xml file was edited to include the
cluster context resource child-document-name property.

The fix for this APAR is currently targeted for inclusion in
fixpacks 6.1.0.23 and 7.0.0.3.  Please refer to the Recommended
Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Please note that profiles created prior to 6.1.0.23 and
7.0.0.3 will need to be manually fixed by customers.  Please
see the temporary fix section.

Temporary fix

This problem can be fixed by the customer by updating the
metadata.xml file located in the profile's config/.repository/
directory.  Stop all servers and node agents for the node.

Locate the section below in the metadata.xml file.

<root-document-type>Cluster</root-document-type>
<child-document-names>
  <child-document-name>Cluster</child-document-name>
  <child-document-name>Variables</child-document-name>
  <child-document-name>Resources-PME-502</child-document-name>
  <child-document-name>Library</child-document-name>
  <child-document-name>Name Bindings</child-document-name>
</child-document-names>

Insert a 'Resources' child-document-name entry into the
existing five entries so that the section looks like -

<root-document-type>Cluster</root-document-type>
<child-document-names>
  <child-document-name>Cluster</child-document-name>
  <child-document-name>Variables</child-document-name>
  <child-document-name>Resources</child-document-name>
  <child-document-name>Resources-PME-502</child-document-name>
  <child-document-name>Library</child-document-name>
  <child-document-name>Name Bindings</child-document-name>
</child-document-names>

Save and close the file.  Start all nodes and servers.

Comments

APAR Information

APAR number
PK76879
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-12-03
Closed date
2008-12-18
Last modified date
2009-12-09

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"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:
28 December 2021

Tips

PK76879: CUSTOM PROFILE METADATA.XML FOR CLUSTER CONTEXT MISSING RESOURCES CHILD-DOCUMENT-NAME

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?