PK79946: FEDERATED NODE MIGRATION CHANGING OS FROM MICROSOFT WINDOWS TO UNIX OR LINUX FAILS TO CONNECT TO THE DEPLOYMENT MANAGER

Fixes are available

APAR status

Closed as program error.

Error description

WASPostUpgrade of the federated node that is being migrated from
a Microsoft Windows style Operating System to a linux or unix
style Operating System fails when attempting to connect to the
deployment manager with security enabled:

MIGR0380E: The JMX connection is not established with the
deployment manager node pvc9356111.austin.ibm.com, using
connector type of SOAP on port 8879. The WASPostMigration
program is now closing. No changes are made to the local
Application Server environment.
com.ibm.websphere.management.exception.ConnectorException:
ADMC0016E: The system cannot create a SOAP connector to
connect to host pvc9356111.austin.ibm.com at port 8879.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of WebSphere Application Server V7.0  *
*                  who are migrating a federated node from a   *
*                  Microsoft Windows based system to a Unix    *
*                  or Linux based system.                      *
****************************************************************
* PROBLEM DESCRIPTION: The migration of federated nodes        *
*                      fails with a reference to a bad or      *
*                      missing key file.                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The migration incorrectly resolves Microsoft Windows style path
information on the unix system during WASPostUpgrade.  This
causes the keyfiles to not be found during the connection to
the DeploymentManager which causes the migration to fail.

If the dmgr process is running and accessible from the machine
the federated node is being migrated to, and the migration of
the federated node terminates because of a failed connection
to the deployment manager, then this APAR may be at fault.

Problem conclusion

Migration file path processing has been hardened to support
platform agnostic formatting.  Now paths can be specified with
any combination of either path separator (/ or \), and the
Microsoft Windows-style root drive letter (for example, C:\) is
now correctly added or removed as needed when converting
between OS types.

The fix for this APAR is currently targeted for inclusion in
fixpack 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
PK79946
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
2009-02-03
Closed date
2009-03-18
Last modified date
2009-03-18

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":"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:
24 October 2021

Tips

PK79946: FEDERATED NODE MIGRATION CHANGING OS FROM MICROSOFT WINDOWS TO UNIX OR LINUX FAILS TO CONNECT TO THE DEPLOYMENT MANAGER

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?