After you upgrade from 7.5.x

This topic includes post-upgrade steps that you might need to perform after running sysupgrade to upgrade from API Gateway 7.5.x to 7.5.3. It contains the following topics:

Configure a different Apache Cassandra client port

If you upgraded from API Gateway 7.5.1 or later to version 7.5.3 all Cassandra hosts are updated to use port 9042 for client communication. To use a different port (for example, to use the same port as you used in your old installation), follow these steps:

  1. For each Cassandra host, update the setting native_transport_port in the CASSANDRA_HOME/conf/cassandra.yaml file. Set the value to the port number to use for client communication.
  2. Update the details for each Cassandra host in Policy Studio. Select Server Settings > Cassandra > Hosts, and update the port for each host.
Note   If you change the configuration to use the same port as you used in your old installation, you cannot leave any API Gateways in your old installation running during the apply step, as the port uses a different Cassandra protocol.

Upgrade Apache Cassandra

API Gateway7.5.3 supports Apache Cassandra versions 2.2.8 and 2.2.5. Cassandra 2.2.8 is the recommended version but Cassandra 2.2.5 is supported for backwards compatibility.

If you are upgrading from API Gateway 7.5.1 or 7.5.2 (which supported Apache Cassandra 2.2.5) and you wish to upgrade Apache Cassandra to version 2.2.8, you must upgrade Apache Cassandra to version 2.2.8 after you upgrade to API Gateway 7.5.3. For more information on upgrading Apache Cassandra, see Upgrade Apache Cassandra.

Upgrade API Gateway projects

Each API Gateway group has a configuration that is typically deployed as a .fed file. When you upgrade from an earlier version of API Gateway, configuration for all API Gateway groups is automatically upgraded during sysupgrade. However, you might have configuration files that were originally created in Policy Studio in a development environment that also need to be upgraded. You can upgrade the configuration in your development environment in one of the following ways:

  • In Policy Studio:
    • Choose the From an API Gateway instance option to create a new project from the configuration in an already upgraded API Gateway.
    • Choose the From existing configuration option to create a new project from an old configuration. The configuration is upgraded to version 7.5.3 automatically.
  • For more information on creating projects in Policy Studio, see the API Gateway Policy Developer Guide.
  • If you upgraded from version 7.5.1 or later and you have several projects to upgrade (these projects might be independent of one another, or could include shared projects and their dependencies), you can use the projupgrade tool. This tool upgrades several projects at once. For more information, see Upgrade an API Gateway project in the API Gateway DevOps Deployment Guide.

Upgrade services

If you were running the API Gateway and Node Manager processes as services in your old installation, you must update the service scripts manually after the upgrade completes. Follow the steps in Upgrade services.

Migrate the QuickStart tutorial

sysupgrade does not migrate the Quickstart tutorial from your old installation. To migrate it, copy the /apigateway/webapps/quickstart directory from your old installation (for example, /opt/Axway/7.4.1/apigateway/webapps/quickstart) to the same location in the new 7.5.3 installation (for example, /opt/Axway/7.5.3/apigateway/webapps/quickstart).

Related Links