PK36953: MANAGEPROFILES COMMAND INCLUDING FEDERATION IS UNABLE TO CONNECT TO THE DMGR

6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Solaris
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for HP-UX
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Linux
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for Windows
6.1.0.7 WebSphere Application Server V6.1 Fix Pack 7 for AIX
6.1.0.7: WebSphere Application Server V6.1 Fix Pack 7 for i5/OS
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
6.1.0.9: WebSphere Application Server V6.1 Fix Pack 9 for Solaris

APAR status

• Closed as program error.

Error description

• After applying fixpack 3 (6.1.0.3) onto WebSphere Application
  server 6.1, the manageprofiles command is unable to connect to
  the Deployment Manager (Dmgr), when inline federation is
  requested or defaulted.  The following message is displayed:
  
  ----------------------------------------------------------------
  The following validation errors were present with the command
  line arguments: dmgrHost: Unable to connect to the deployment
  manager on the specified hostname and port.
  ----------------------------------------------------------------
  

Local fix

• Breaking the processing up into two steps can be used as a
  circumvention:
  1. Use manageprofiles.sh to create the wanted profile WITHOUT
     inline federation of the new profile into the cell
     (i.e. federateLater="true").
  2. Follow with an addNode.sh to do the federation as a separate
     step. addNode is able to connect to the Dmgr without problem.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users who have upgraded to WebSphere     *
  *                 Application Server fixpack 6.1.0.3 or        *
  *                 higher and have attempted to federate a      *
  *                 managed node to an existing deployment       *
  *                 manager using the manageprofiles command.    *
  ****************************************************************
  * PROBLEM DESCRIPTION: Federation of a managed node fails      *
  *                      when using the manageprofiles command.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When trying to federate a managed node to an exisiting
  deployment manager using the manageprofiles command, you
  received a validation message stating "Unable to connect to
  the deployment manager on the specified hostname and port".
  

Problem conclusion

• This issue is now resolved. You will be able to successfully
  federate a managed node to an existing deployment manager.
  
  The fix for this APAR is currently targeted for inclusion
  in fixpack 6.1.0.7.
  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 is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• PROFILE  TOOL
  

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