PQ69242: CREATING A CLONE ON A NEW NODE WILL NOT START SINCE THE ENTERPRISE APPLICATION NAME IS CHANGED ON 2ND NODE.

 Fixes are available

4.0.6: WebSphere Application Server Version 4.0 Fix Pack 6
System Management Component Cumulative Fix for 4.0.2/4.0.3/4.0.4 /4.0.5



APAR status
Closed as program error.

Error description
If you have a sever group with enterprise application installed
to it and try to create a new clone on a new node, their are
problems starting the clone.  The directory name for the
enterprise application is changed so they will have to manually
change this to make it work.
Local fix
When creating a new clone on a new machine use the admin console
which works fine.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of wscp.  *
****************************************************************
* PROBLEM DESCRIPTION: After creating a clone from server      *
*                      group (with enterprise app installed)   *
*                      on a new node, this clone will not      *
*                      start since the enterprise app name     *
*                      is changed on 2nd node.                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If user has a sever group with enterprise application
installed to it and creates a clone on a new node, there will
problems starting the clone because the directory name for the
enterprise application has been changed.  This is wscp problem
and does not affect other admin clients.
Problem conclusion
Modify code in ServerGroupScriptCmdHandler.java so that path
name is preserved and wscp now behaves like admin console and
XMLConfig with regard to this aspect of clone creation.
Temporary fix
Temporary fix will be available in WebSphere system mgmt.
cumuative eFixes dated 10Jan03 or later.
Comments
APAR information
APAR number PQ69242
Reported component name WEBSPHERE AE SO
Reported component ID 5630A2202
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-12-17
Closed date 2003-01-21
Last modified date 2003-01-21

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
WSCP          

SRLS

Fix information
Fixed component name WEBSPHERE AE SO
Fixed component ID 5630A2202

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ69242
IBM Group: Software Group
Modified date: Jan 21, 2003