Download

Axway API Gateway | Readme

Axway API Gateway 7.3.0 SP2 Readme

Document version: 15 April 2015



Axway API Gateway 7.3.0 SP2

This Readme applies to Axway API Gateway 7.3.0 SP2 on all platforms. This Readme supersedes any corresponding information in the documentation previously supplied for the product (online or printed).

This service pack provides fixes for a number of reported defects, and contains updates for the following components:

The service pack contains new binaries only and does not overwrite the existing configuration.

File Packages: Installation archives are provided for all platforms. For example, APIGateway_7.3.0_SP2_Core_win-x86-32_BN201504151.zip for Windows.

Size: The file size differs for each platform. The MD5 checksum is provided for each file.

Fixed problems

This service pack fixes the following problems:

Case ID Internal ID Description
736618 140638 PDF report on Solaris has no content
Previously, API Gateway Analytics could generate a blank report due to the default timeout (30000 ms) in JavaScript waiting for a generated report.
Now, API Gateway Analytics can be configured with a custom JavaScript timeout using the javascriptDelay Java system property in jvm.xml, for example <VMArg name="-DjavascriptDelay=3600000" />. The default timeout is now set to 300000 ms.
758110 139963 File Upload filter always uses FTPS settings and ignores FTP settings for ASCII/binary transfer
Previously, the File Upload filter always used FTPS settings and ignored FTP settings for ASCII/binary transfer.
Now, the File Upload filter uses FTPS, FTP, or SFTP configuration settings respectively.
763046 142036 The Hash Client Password option of the authentication repository is no longer hashing the password
Previously, the HTTP basic filter might not always authenticate the user correctly via a database repository configured to hash a client password.
Now, API Gateway always hashes the client password if configured in the database repository.
764382 143446 Proxy-Authorization header is not correct when a passphrase is used
Previously, when an API Gateway configuration was protected with a passphrase, a user password in the Proxy settings was not decrypted causing the Proxy-Authorization HTTP header to contain an incorrect value.
Now, a user password in the Proxy settings is correctly decrypted when loading from a passphrase-protected API Gateway configuration.
765749 143577 7.3.0 SP1 port of Mantis 121683: Host header issue with proxies
Previously, the Connect to URL filter was setting the proxy hostname in the Host header instead of the destination hostname, when sending request via a proxy.
Now, the Connect to URL filter sets the destination hostname in the Host header when sending request via a proxy.
767991 144473 Port of Mantis 131911: The /metrics call always reports cpuUsed as zero
Previously, the /metrics call always reported cpuUsed as zero.
Now, the /metrics call always shows a positive number in cpuUsed.
770287 145332 Port of Mantis 132530
Previously, Policy Studio incorrectly reported a Recursion Error when parsing some policies.
Now, Policy Studio does not incorrectly report this error.
771112 145797 Port: Access log's time to serve request (%D) is negative
Previously, the Access Log was reporting a negative number when the log format was configured to use %D.
Now, the Access Log reports the correct number when the log format is configured to use %D.
143965 FTP Poller always uses passive mode for FTPS connection type disregarding the configuration
Previously, the FTP Poller always used passive mode for the FTPS connection type, disregarding the configuration.
Now, the FTP Poller uses passive mode for the FTPS connection type based on the configuration.

Known issues

The following issues are known and scheduled for correction in a future release:

Case IDInternal IDDescription
770305 145334 Java Crash - SIGSEGV in com.vordel.circuit.InvocationEngine.recordFilterEnd

Install the service pack

This section includes the prerequisites and installation instructions for this service pack.

Prerequisites

In addition to the prerequisites specified for the main product release:

  1. Shut down any Node Manager or API Gateway instances on your existing installation.
  2. Back up your existing installation. For more information on backing up, see the API Gateway Administrator Guide.
  3. Remove any old third-party libraries. To do this, delete the INSTALL_DIR/system/lib/modules directory.

Installation

This section describes how to install the service pack on an existing installation of API Gateway.

To install a new API Gateway installation from scratch without an existing installation, see the API Gateway Installation and Configuration Guide.

Install the API Gateway Core Server service pack

To install the service pack on your existing API Gateway 7.3.0 Core Server installation, perform the following steps:

  1. Ensure that your existing API Gateway instance and Node Manager have been stopped. For more details, see the API Gateway Administrator Guide.
  2. Remove any previous patches from your INSTALL_DIR/ext/lib directory (or ../ext/lib directory in an API Gateway instance). These patches have already been included in this service pack. You do not need to copy patches from a previous version.
  3. Unzip and extract API Gateway 7.3.0 SP2 Core over the apigateway directory in your existing installation directory. For example:

    tar -xzvf APIGateway_7.3.0_SP2_Core_linux-x86-64_BN201504151.tar.gz -C /opt/Axway-7.3.0/apigateway/

  4. Restart your API Gateway instance and Node Manager. For more details, see the API Gateway Administrator Guide.

Note

Install the API Gateway Analytics service pack

To install the service pack on your existing API Gateway Analytics 7.3.0 installation, perform the following steps:

  1. Ensure that your existing API Gateway Analytics instance and Node Manager have been stopped. For more details, see the API Gateway Administrator Guide.
  2. Remove any previous patches from your INSTALL_DIR/ext/lib directory (or the ext/lib directory in an API Gateway Analytics instance). These patches have already been included in this service pack. You do not need to copy patches from a previous version.
  3. Unzip and extract API Gateway 7.3.0 SP2 Analytics over the analytics directory within your existing API Gateway 7.3.0 installation directory. For example:
  4. tar -xzvf APIGateway_7.3.0_SP2_Analytics_linux-x86-64_BN201504151.tar.gz -C /opt/Axway-7.3.0/analytics/

Note

Install the Policy Studio service pack

To install the service pack on your existing Policy Studio installation, perform the following steps:

  1. Delete your existing Policy Studio installation directory (for example, INSTALL_DIR\policystudio).
  2. Use the API Gateway 7.3.0 installation executable to install Policy Studio into the same directory.

Note

Install the Configuration Studio service pack

To install the service pack on your existing Configuration Studio installation, perform the following steps:

  1. Delete your existing Configuration Studio installation directory (for example, INSTALL_DIR\configurationstudio).
  2. Use the API Gateway 7.3.0 installation executable to install Configuration Studio into the same directory.

After installation

To allow an unprivileged user to run the API Gateway on a Linux system, perform the following steps:

  1. Add the following line to the INSTALL_DIR/system/conf/jvm.xml file.
  2. 64-bit installation

    <VMArg name="-Djava.library.path=$VDISTDIR/$DISTRIBUTION/jre/lib/amd64/server:$VDISTDIR/$DISTRIBUTION/jre/lib/amd64:$VDISTDIR/$DISTRIBUTION/lib/engines:$VDISTDIR/ext/$DISTRIBUTION/lib:$VDISTDIR/ext/lib:$VDISTDIR/$DISTRIBUTION/jre/lib:system/lib:$VDISTDIR/$DISTRIBUTION/lib"/>

  3. 32-bit installation

    <VMArg name="-Djava.library.path=$VDISTDIR/$DISTRIBUTION/jre/lib/i386/server:$VDISTDIR/$DISTRIBUTION/jre/lib/i386:$VDISTDIR/$DISTRIBUTION/lib/engines:$VDISTDIR/ext/$DISTRIBUTION/lib:$VDISTDIR/ext/lib:$VDISTDIR/$DISTRIBUTION/jre/lib:system/lib:$VDISTDIR/$DISTRIBUTION/lib"/>

  1. Run the command setcap 'cap_net_bind_service=+ep' INSTALL_DIR/platform/bin/vshell to to allow the API Gateway to listen on privileged ports.

Note


Related documentation

Axway API Gateway is accompanied by a complete set of documentation, covering all aspects of using the product. These documents include the following:

Axway API Gateway documentation

Axway API Manager documentation

Axway 5 Suite documentation

All Axway documentation is available from Axway Sphere at https://support.axway.com.


Support services

Support services are available from Axway Sphere at https://support.axway.com, including:

The Axway Global Support team also provides worldwide 24 x 7 support, subject to validation of your license agreement. Email support@axway.com or, for your local support telephone number, visit Axway Sphere at https://support.axway.com and click Contact Axway Support.

For details on the information that you should provide when contacting Axway Support, see "Troubleshoot your API Gateway installation" in the API Gateway Administrator Guide.

For information about Axway training services, go to: www.axway.com.


Copyright © Axway Software 2015
All rights reserved