Preserving a v5.1 gateway when migrating a cell
When we 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 we must preserve our v5.1 gateway configurations before migrating the cell.
WebSphere Application Server v5.0 is no longer supported, so we should migrate any existing gateways running in v5.0 application servers to run on application servers at the current level of the product.
Before we choose whether to preserve or migrate our v5.1 gateways, we should be aware of the context and restrictions 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 running on v5.1 application servers even if we migrate the cell from v5.1 or v6 to v7.0 or later. However when we migrate a cell, any previously configured gateway on any v5.1 application server in the cell is replaced with an empty gateway. Therefore we must preserve our v5.1 gateway configurations before migrating the cell.
To preserve v5.1 gateways and application servers when migrating a cell to a later version. For information about how to save and restore the v5.1 gateway configurations, see the WAS v5.1 topic: Back up and restore a gateway configuration.
Tasks
- Save the v5.1 gateway configurations.
- Migrate the cell to the later version without also migrating the application servers, by referring to the documentation about migrating deployment managers.
- Restore the v5.1 gateway configurations to the v5.1 application servers within the cell on the later version.