The high availability manager supports multihomed hosts, which means that WebSphere Application Server processes can communicate with each other even if they are running on different versions of the product. If you are running Version 6.0.2 and later processes that need to communicate with each other, you need to consider there are high availability manager-related issues.
Before you begin
Know the version levels of the processes that need to communicate with each other. If Version 6.0.1.2 processes exist, see Interoperating with Version 6.0.1.2 processes for additional considerations.Why and when to perform this task
When processes are created on Version 6.0.2 or later nodes, the host name field in the DCS_UNICAST_ADDRESS endpoint is set to an asterisk. When you use an asterisk in the host name field, multihome support allows the high availability manager to open and accept connections using any IP address that is valid for that machine.As you add Version 6.0.2 nodes and create servers into a mixed-release cell, you must set the host name field of the DCS_UNICAST_ADDRESS for all processes on the new nodes, including the node agent, to one of the two values previously specified. You must then restart the Version 6.0.2 processes to pick up the new value.
To change the host name field for a process:
Steps for this task
Result
All of the processes can communicate with each other.What to do next
If Version 6.0.2 processes are not configured properly, the Version 6.0 and Version 6.0.1 processes might not start or might not be able to connect to the Version 6.0.2 processes.HMGR0024W: An error was encountered while looking up the IP address for the host name of a core group member. The host name is * and the server name is myCell01\myCellManager01\dmgr. The member is excluded from the core group.
This message indicates that the host name for another process in the core group is an asterisk.
HMGR0218I: A new core group view is installed. The core group is defaultCoreGroup. The view identifier is (8:0.spoletoCell01\ spoletoCellManager01\dmgr). The number of members in the new view is 2.
Related reference
Configuring a core group transport