Operating Systems: i5/OS
             Personalize the table of contents and search results

 

Migrating bootstrap addresses

 

WebSphere Application Server versions 5 and 6.0.x support foreign cell bindings, but support is limited to a single bootstrap address and you cannot configure foreign cell bindings in the console. The single bootstrap address used in versions 5 and 6.0.x has been deprecated, replaced in version 6.1 by a list of bootstrap addresses. Configure server clusters for failover support as needed.

 

Overview

When a version 5 or 6.0.x cell is migrated to version 6.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 version 6.0.x, continue to use the single bootstrap address setting to create bindings in the name space.

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

 

Procedure

  1. Edit your version 5.x or 6.0.x foreign cell binding scripts, replacing bootstrapAddress with bootstrapAddresses, the list property introduced in version 6.1.

    The bootstrap address properties are in the context of the ForeignCell class. The fully qualified name for the version 5.x or 6.0.x property now deprecated is the following: 

    topology.cell:Cell/foreignCells/bootstrapAddress

    The fully qualified name for the bootstrap address list property introduced in version 6.1 is the following: 

    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 version 5 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 name space.

Nodes running at a version later than version 6.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.

 

What to do next

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 added in version 6.1 only display and update the bootstrap address list that is new in version 6.1. They do not change the single bootstrap address configuration setting. If you use the console to edit a foreign cell binding configuration that existed when the cell was initially migrated, and you 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 version 5 or 6.0.x continue to use the single bootstrap address configuration setting to bind foreign cell bindings in the name space.

}
Foreign cell bindings

 

Related tasks


Configuring foreign cell bindings
Using naming