PQ80132: When migrating from WSAS 4.0.x to 5.0.x, WASPostUpgrade script does not copy template of resources.xml to server config dir. | |||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Problem occurred after running the WASPostUpgrade script when migrating from WSAS 4.0.x to 5.0.x. Customer attempted to configure a new server level datasource on their newly migrated server. When they restarted WebSphere, they received an error similar to the following in the SystemOut.log: [10/20/03 13:21:36:375 EDT] 798d58 ResourceMgrIm E WSVR0017E: Error encountered binding the J2EE resource, myDatasource, as jdbc/myDatasource from file:///opt/WebSphere50/AppServer/config/cells/myCellNetwork/nod es/myNode/servers/myServer/resources.xml com.ibm.ws.runtime.component.binder.ResourceBindingException: invalid configuration passed to resource binding logic. REASON: Invalid Configuration! The DataSource: myDatasource has a null RelationResourceAdapter property. Root cause of the problem was that the template file for the resources.xml was not placed in the <WSAS_HOME>\config\cells\<cell_name>\nodes\<node_name> \servers\<server_name> directory for each newly migrated server.Local fix Workaround: After running the WASPostUpgrade script, copy the resources.xml from the <WSAS_HOME>\config\templates\default\nodes\servers\server1 directory to the <WSAS_HOME>\config\cells\<cell_name>\nodes\<node_name> \servers\<server_name> directory for each newly migrated server.Problem summary **************************************************************** * USERS AFFECTED: Users of WebSphere Application Server * * that migrate from WebSphere v3.5.x * * or v4.0.x Advanced to v5.0.x with multiple * * servers configured. * **************************************************************** * PROBLEM DESCRIPTION: After running WASPostUpgrade the user * * was not able to add new resources at * * the server level. * **************************************************************** * RECOMMENDATION: * **************************************************************** After running WASPostUpgrade the user was not able to add new resources at the server level, because the resources.xml template was not laid down at the server level during migration. This happens with servers other than server1.Problem conclusion Code was added to lay down the resources.xml template whenever a new server is created.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00S
Software edition:
Reference #: PQ80132
IBM Group: Software Group
Modified date: Nov 12, 2003
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.