After you upgrade from 7.3.x or 7.4.x

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

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.6.2 automatically.
  • For more information on creating projects in Policy Studio, see the API Gateway Policy Developer Guide.
  • If you upgraded from version 7.4.1 or earlier, you can use the upgradeconfig script that is available in your API Gateway installation directory (for example, /opt/Axway-7.6.2/apigateway/Win32/bin). For more information on running the upgradeconfig script, enter upgradeconfig --help at the command prompt.
Caution   If your .fed file contains API Manager configuration, you cannot upgrade it using upgradeconfig or Policy Studio. You must use sysupgrade.

Update Salesforce connector license

If you upgraded from API Gateway 7.4.1, the API Gateway trace log might show a deployment error indicating that the Salesforce connector does not have a valid license.

The Salesforce connector was added in API Gateway 7.4.1 and was installed together with API Manager. It can be used to import back-end APIs from Salesforce. In 7.6.2, the Salesforce connector is a licensed feature.

You have two options to resolve this issue:

  1. If you intend to use the Salesforce connector in the new API Gateway installation, you must acquire a valid license from Axway Support.
  2. If you do not intend to use the Salesforce connector in the new API Gateway installation, you can remove it using Policy Studio. This will eliminate the deployment error.
  3. For more information on what to remove in Policy Studio, see the Salesforce API connectors section of the API Manager User Guide. After removing the connector, you must deploy the updated configuration to all groups in the topology.

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. Service scripts are not updated by sysupgrade.

Note   If you have set up Cassandra to run as a service on the same machine as the API Gateway services, you must ensure that the Cassandra service starts up before the API Gateway services.

Upgrade services on UNIX/Linux

Complete the following steps after running sysupgrade apply:

  1. Switch user to root to enable you to modify files in /etc/init.d. Typically, Axway services file names start with vshell-.
  2. Edit the Node Manager script and update the VDISTDIR variable to point to the apigateway folder in the new installation.
  3. For example, on a machine called XUbuntu02, edit the file /etc/init.d/vshell-Node-Manager-on-XUbuntu02.
    • Update the VDISTDIR variable (for example, change VDISTDIR="/opt/Axway-7.2.2/apigateway to VDISTDIR="/opt/Axway-7.6.2/apigateway).
  4. Edit each of the relevant API Gateway scripts, and update the VDISTDIR and the VINSTDIR variables to point to the apigateway folder in the new installation.
  5. For example, on a machine called XUbuntu02 with one API Gateway called Gateway1 that is a member of a group called Default Group, edit the file /etc/init.d/vshell-Default-Group-Gateway1.
    • Update the VDISTDIR variable (for example, change VDISTDIR="/opt/Axway-7.2.2/apigateway to VDISTDIR="/opt/Axway-7.6.2/apigateway).
    • Update the VINSTDIR variable (for example, change VINSTDIR="/opt/Axway-7.2.2/apigateway/groups/group-2/instance-1 to VINSTDIR="/opt/Axway-7.6.2/apigateway/groups/group-2/instance-1).
  6. Save the changes to the files and restart the machine. When the machine restarts the new services are started.
Tip   Alternatively, your UNIX/Linux administrator can remove the old services using the preferred UNIX/Linux utility and delete the old init.d service files, and you can use managedomain to recreate the services after running sysupgrade.

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.6.2 installation (for example, /opt/Axway/7.6.2/apigateway/webapps/quickstart).

Add nodes to an Apache Cassandra database cluster for HA

Before you upgraded, you configured an Apache Cassandra cluster with one Cassandra server as detailed in Configure an Apache Cassandra database cluster in the new installation. You can now add more nodes to this cluster to provide high availability (HA), and configure TLS security.

For more information, see Install an Apache Cassandra database in the API Gateway Installation Guide.

Upgrade metrics database with versions earlier than 7.4.0

If you are using an API Gateway version earlier than 7.4.0, you can upgrade your metrics database after you run the sysupgrade command. For example, the metrics database is used for monitoring with API Gateway Analytics, API Manager, or third-party tools. For more information, see Upgrade your metrics database for API Manager.

Related Links