PI18870: NODE FEDERATION OF NON-IBMI TO IBMI DMGR FAILS

8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as duplicate of another APAR.

Error description

• Scenario: federating a WAS Node on AIX to WAS dmgr on IBM i, the
  WAS versions are ND 8551.
  
  Here is the error from addNode.sh on AIX. It says
  com.ibm.websphere.xdProductVersion=null.
  
  ./addNode.sh g006020t.cn.ibm.com 8879 -user wasadmin -password
  password -includeapps -noagent
  ADMU0116I: Tool information is being logged in file
  
  /view1/conn/IBM/WebSphere/AppServer/profiles/testwas/logs/addNod
  e.log
  ADMU0128I: Starting tool with the testwas profile
  CWPKI0308I: Adding signer alias "CN=g006020t.cn.ibm.com,
  OU=Root" to local
             keystore "ClientDefaultTrustStore" with the following
  SHA digest:
  
  32:0A:DE:B2:FF:D3:B2:40:07:A4:EA:4E:BA:CE:BC:EC:F7:58:16:95
  CWPKI0308I: Adding signer alias "ihs" to local keystore
             "ClientDefaultTrustStore" with the following SHA
  digest:
  
  77:3E:85:BB:52:78:EE:91:D5:2C:C1:C2:53:6B:68:2D:AE:AA:A4:68
  CWPKI0308I: Adding signer alias "filenet_8880" to local keystore
             "ClientDefaultTrustStore" with the following SHA
  digest:
  
  D5:4E:DE:DD:B2:71:65:65:98:75:3C:E9:80:95:5F:88:23:A8:DA:56
  CWPKI0308I: Adding signer alias "fncs" to local keystore
             "ClientDefaultTrustStore" with the following SHA
  digest:
  
  2F:32:13:C0:59:4F:4E:23:54:80:3B:30:68:37:E3:6C:8A:56:D1:5E
  ADMU0001I: Begin federation of node ilotusaix1Node02 with
  Deployment Manager at
             g006020t.cn.ibm.com:8879.
  ADMU0009I: Successfully connected to Deployment Manager Server:
             g006020t.cn.ibm.com:8879
  
  
  ADMU0027E: An error occurred during federation WXDO7901E: The
  node has not been
             added because com.ibm.websphere.xdProductVersion=null
  on the
             deployment manager node is incompatible with
             com.ibm.websphere.xdProductVersion=8.5.5.1 on the
  node.; rolling
             back to original configuration.
  ADMU0211I: Error details may be seen in the file:
  
  /view1/conn/IBM/WebSphere/AppServer/profiles/testwas/logs/addNod
  e.log
  ADMU0113E: Program exiting with error:
  
  com.ibm.websphere.management.exception.AdminException:
             javax.management.MBeanException: Exception thrown in
             RequiredModelMBean while trying to invoke operation
             checkNodeAndDmgrCompatibility, resulting from:
  
  com.ibm.websphere.management.exception.AdminException:
  WXDO7901E:
             The node has not been added because
             com.ibm.websphere.xdProductVersion=null on the
  deployment manager
             node is incompatible with
  com.ibm.websphere.xdProductVersion=8.5.5.1
             on the node.
  ADMU1211I: To obtain a full trace of the failure, use the -trace
  option.
  ADMU0211I: Error details may be seen in the file:
  
  /view1/conn/IBM/WebSphere/AppServer/profiles/testwas/logs/addNod
  e.log
  

Local fix

• na
  

Problem summary

Problem conclusion

Temporary fix

Comments

• See PI25712
  

APAR Information

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

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

Fix information

Applicable component levels