Upgrading DataPower Gateway Service

Use these instructions when upgrading DataPower Gateway Service in a non-Kubernetes environment, during upgrade of API Connect.

Before you begin

Ensure you have completed the upgrade of the API Connect subsystems (Management service, Developer Portal, Analytics) before upgrading DataPower Gateway. Upgrading the Management service before the DataPower Gateway ensures that any new policies and capabilities will be available to a previously registered Gateway service.

To review API Connect upgrade on VMware, see Upgrading from 2018 to the latest 10.0.1.x-eus on VMware or Upgrading from 10.0.1.1-eus to the latest 10.0.1.x-eus on VMware or Upgrading to 10.0.1.8-eus on VMware.

Note: For API Connect Version 10.x, DataPower and API Connect releases can be within one fix pack of each other. For example, API Connect 10.0.1.n runs with DataPower Gateway 10.0.1.n, 10.0.1.n-1, or 10.0.1.n+1.

Important exception: Version 10.0.1.4-eus is not backwards compatible with 10.0.1.3. For example, API Connect 10.0.1.4-eus is not compatible with DataPower Gateway 10.0.1.3. If you deployed API Connect 10.0.1.4-eus, you must deploy either DataPower Gateway 10.0.1.4 or DataPower Gateway 10.0.1.5.

However, before you install, best practice is to review the latest compatibility support for your version of API Connect. To view compatibility support, follow the instructions in IBM API Connect Version 10 software product compatibility requirements to access API Connect information on the Software Product Compatibility Reports website. Once you access information for your version of API Connect, select Supported Software > Integration Middleware, and view the list of compatible DataPower Gateway versions.

About this task

  • The DataPower Gateway Service in a non-Kubernetes environment can be on either a physical appliance or in a virtual DataPower deployment.
  • The upgrade of DataPower Gateway Service in a non-Kubernetes environment, for use in API Connect deployments in a VMware environment, does not use the API Connect Install Assist program (apicup). Use DataPower Gateway instructions in the following steps.
Note: To upgrade the DataPower Gateway Service in a Kubernetes environment, do not use the following procedure. Instead, see Upgrading to 10.0.1.8-eus on Kubernetes or Upgrading 2018 to the latest 10.0.1.x-eus on native Kubernetes.

Procedure

  1. Ensure that the DataPower Gateway firmware version you plan to install is compatible with the API Connect management server version.
  2. When upgrading a high-availability cluster, ensure that you meet the requirements:
    • Gateways must be updated one at a time.
    • Before starting the upgrade, a single gateway must be running as primary for all gateway-peering definitions.
    • When upgrading multiple gateways, the primary gateway must be upgraded last.

    To determine which gateway is running as primary, use either the show gateway-peering-status command in the DataPower CLI, or use the Gateway Peering Status display in the WebGUI in the API Connect application domain. To move the primary to the DataPower on which you're currently working, you can issue the gateway-peering-switch-primary <peering-object-name> command.

  3. Ensure that your deployment includes an NTP server to synchronize time between each of the DataPower Gateways.
    See Managing the NTP service.
  4. Ensure that you have set a unique System Identifier for each version 10 DataPower gateway. See Initializing the DataPower Gateway.
  5. Follow the upgrade instructions on the DataPower Gateway documentation. See Installation operations.
    Note:
    • If upgrading a cluster (high-availability) deployment, ensure that you have identified which gateway is running a primary in gateway-peering definitions, and that you upgrade that gateway last.
    • For troubleshooting help with DataPower operator v1.2.0 deployments, see IBM DataPower Operator documentation.