Preserving a V5.1 gateway when migrating a cell
When you migrate a cell to a later version, any previously configured gateway on any V5.1 application server in the cell is replaced with an empty gateway. Therefore you must preserve the V5.1 gateway configurations before you migrate the cell.
WAS V5.0 is no longer supported, so you should migrate any existing gateways that are running in V5.0 appservers to run on appservers at the current level of WAS ND.
Before you choose whether to preserve or migrate the V5.1 gateways, you should be aware of the context and restrictions that are described in Coexistence: Preserve or migrate a V5.1 gateway. To migrate a gateway, see Migrate a V5.1 Web services gateway configuration.
Because a cell in a later version can contain application servers at different versions, we can continue to use V5.1 gateways that are running on V5.1 appservers even if you migrate the cell from V5.1 or V6 to V7.0. However when you migrate a cell, any previously configured gateway on any V5.1 appserver in the cell is replaced with an empty gateway. Therefore preserve your V5.1 gateway configurations before you migrate the cell. To preserve V5.1 gateways and application servers when migrating a cell to a later version, complete the following steps. For information about how to save and restore the V5.1 gateway configurations, see the WAS V5.1 topic: Backing up and restoring a gateway configuration.
- Save the V5.1 gateway configurations.
- Migrate the cell to the later version without also migrating the appservers, by referring to the documentation about migrating dmgrs.
- Restore the V5.1 gateway configurations to the V5.1 application servers within the cell on the later version.
Last updated Nov 10, 2010 8:23:07 PM CST