PK84600: THE WIMDATAGRAPH.XSD SHOULD BE THE DEFAULT FOR CONFIGMODEL DURING THE WMM TO VMM MIGRATION.

Fixes are available

APAR status

Closed as program error.

Error description

IBM WebSphere Application Server V7.0


The problem is a virtual member manager (VMM) issue.  The error
is occurring because after the WebSphere memory manager (wmm)
to vmm migration the file specified in the wimconfig.xml
file for the dynamicModel element is wimextension.xsd:

<config:dynamicModel xsdFileName="wimextension.xsd"/>

In V6.1 this worked because the wimextension.xsd contained:

<xsd:include schemaLocation="wimdatagraph.xsd"/>

and in V6.1 the file wimdatagraph.xsd was in the profile.  The
wimdatagraph.xsd is now read only data and should only exist in
the application server install root, this is a change in VMM
for V7.

Local fix

Before executing portal-post-upgrade, open the files in
<AppServerRoot>/etc/wim/migration

wimconfig_fed_la_db.xml
wimconfig_ldap_ad.xml
wimconfig_ldap_dm.xml
wimconfig_ldap_ids.xml
wimconfig_ldap_nds.xml
wimconfig_ldap_so.xml

and change

    <config:dynamicModel xsdFileName="wimextension.xsd"/>

to
    <config:dynamicModel xsdFileName="wimdatagraph.xsd"/>

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0                                 *
****************************************************************
* PROBLEM DESCRIPTION: After migration from Websphere Member   *
*                      Manager (WMM) to Virtual Member         *
*                      Manager (VMM), wimextension.xsd         *
*                      cannot be loaded                        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
After migration from VMM to WMM, the file specified in the
wimconfig.xml file for the dynamicModel element is
'wimextension.xsd':

   <config:dynamicModel xsdFileName="wimextension.xsd"/>

If the application server profile is not stored in the default
location, VMM fails to start with the following error:

[4/2/09 21:50:30:429 EDT] 00000054 UserRegistryI E
SECJ0331E: The
registry implementation file
com.ibm.ws.wim.registry.WIMUserRegistry
cannot be initialized because of the following exception

com.ibm.websphere.wim.exception.InitializationException:
CWWIM0502E  The  'http://www.ibm.com/websphere/wim' virtual
member manager model package   was not found in the specified

'/opt/IBM/wpnext/wp_profile/config/cells/rtpil/wim/model/wimexte
nsion.xsd'.

Problem conclusion

The problem has been fixed.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.5.  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
PK84600
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-04-13
Closed date
2009-05-06
Last modified date
2009-05-08

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

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":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK84600: THE WIMDATAGRAPH.XSD SHOULD BE THE DEFAULT FOR CONFIGMODEL DURING THE WMM TO VMM MIGRATION.

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?