Migrate bootstrap addresses

WAS Vs 5 and 6.0.x support foreign cell bindings, but support is limited to a single bootstrap address and we cannot configure foreign cell bindings in the console. The single bootstrap address used in Vs 5.x and 6.0.x has been deprecated, replaced in V6.1 and later by a list of bootstrap addresses. Set server clusters for failover support as needed.

When a V5.x or 6.0.x cell is migrated to V6.1 or later, foreign cell binding configurations initially are left unchanged to maintain compatibility with existing wsadmin scripts. All nodes in the migrated cell, including those later than V6.0.x, continue to use the single bootstrap address setting to create bindings in the namespace.

This page describes how to migrate any V5.x or 6.0.x bootstrap addresses to use V 6.1 or later foreign cell bindings. V6.1 and later foreign cell bindings enable you to specify more than one bootstrap address and enhance failover support.

 

1. Edit the V5.x or 6.0.x foreign cell binding scripts, replacing bootstrapAddress with bootstrapAddresses, the list property in V6.1 and later.

   The bootstrap address properties are in the context of the ForeignCell class. The fully qualified name for the V5.x or 6.0.x property now deprecated...

   topology.cell:Cell/foreignCells/bootstrapAddress
   

   The fully qualified name for the bootstrap address list property in V6.1 and later...

   topology.cell:Cell/foreignCells/bootstrapAddresses
   

   Version 6.1 and later foreign cell binding scripts should use the bootstrap address list property, bootstrapAddresses.

2. Run the convertScriptCompatibility command to convert each single bootstrap address configuration to a new bootstrap address list configuration containing that single bootstrap address.

 

Results

In the migrated cell, nodes still running V5 or 6.0.x will use one of the addresses in the bootstrap address list configuration, but no particular one, to create a foreign cell binding in the namespace.

Nodes running at a version later than V6.0.x ignore the old single bootstrap address setting in preference for the bootstrap address list. If the convertScriptCompatibility command encounters a foreign cell binding configuration with the old single bootstrap address and the newer bootstrap address list both set, the old single bootstrap address is removed and the bootstrap address list is left unchanged.

 

Next steps

Click Environment > Naming > Foreign cell bindings > foreign_cell_binding_name > Bootstrap addresses in the console and examine the collection on the Bootstrap addresses page to see if single bootstrap addresses migrated to the bootstrap address list.

Console foreign cell binding panels in V6.1 and later only display and update the bootstrap address list. They do not change the single bootstrap address configuration setting. If we use the console to edit a foreign cell binding configuration that existed when the cell was initially migrated, and we have not yet run the convertScriptCompatibility command, the updated binding configuration contains both the original single bootstrap address and whatever list of bootstrap addresses you configure in the console. In the migrated cell, nodes still running at V5.x or 6.0.x continue to use the single bootstrap address configuration setting to bind foreign cell bindings in the namespace.

Foreign cell bindings

 

Related tasks

Set foreign cell bindings
Use naming