Document version: 5 August 2016
This Readme applies to Axway API Gateway 7.5.1 SP 1, for all platforms. The information in this Readme supersedes any corresponding information in the documentation (online or printed) previously supplied for the product.
The main aim of this service pack is to provide fixes for a number of reported defects. This service pack contains updates for:
The service pack contains new binaries only and does not overwrite the existing configuration.
File packages: An installation archive is provided for all platforms (for example,
APIGateway_7.5.1_SP1_Core_win-x86-32_BNYYYYMMDDn.zip
for Windows).
Size: The file size differs for each platform. The MD5 checksum is provided for each file.
This service pack provides the following corrections and enhancements.
Internal ID | Case ID | Description |
---|---|---|
RDAPI-898 | 00838339 | Issue: Delay in outgoing requests from API Gateway while under load. Resolution: Previously, the transaction access logging was doing a reverse DNS lookup with the source IP address to obtain the source host name required to print Now, the transaction access logging uses the message attributes to retrieve the source host name required to print |
RDAPI-3698 | — | Issue: Sysupgrade --clean broken on Windows.Resolution: Previously, after upgrading API Gateway on Windows, running Now, |
RDAPI-3829 | 00825167 |
Issue: Valid JSON Path incorrectly returns no matches. Now, the JSON Path filter handles these filter expressions. The underlying 3rd party library has been updated to fix the problem. Before installing the service pack, you must remove the old JSON path file ( In addition, Policy Studio uses the JSON path file to validate path expressions. Before installing the service pack, you must also remove the file from Policy Studio ( |
RDAPI-3879 | 00843196 00840339 | Issue: The Admin User Rest API documentation is empty. Resolution: Previously, the Admin User Rest API documentation was missing. Now, the Admin User Rest API documentation has been regenerated. It is available at https://support.axway.com/htmldoc/1433379. |
RDAPI-3884 | 751232 |
Issue: Unable to configure SSL options for outgoing connections. Resolution: Previously, you could not configure SSL/TLS protocols for outbound connections in the Connect To URL filter in API Gateway. Now, you can configure default SSL/TLS protocols for outbound connections in the Connect To URL filter using the <ConfigurationFragment> <SystemSettings> <!-- SSL options for outgoing connections --> ... <!-- Do not use the TLSv1.1 protocol --> <!-- <attribute key="ssloptions">notlsv1_1</attribute> --> <!-- Do not use the TLSv1.2 protocol --> <!-- <attribute key="ssloptions">notlsv1_2</attribute> --> </SystemSettings> </ConfigurationFragment> |
RDAPI-3978 | 00846257 00842837 |
Issue: When a JSON Path expression is not matched, neither the failure path nor the fault handler is invoked. Now, when there is no match, the JSON Path filter executes a failure path or fault handler. |
RDAPI-4220 | 00844652 |
Issue: SAML2 Authentication Assertion fails with a Now, a
|
RDAPI-4255 | 00845501 |
Issue: Cannot run nodetool due to missing JRE. Now, setting |
RDAPI-4485 | 00839882 |
Issue: SSL protocols from
Now, the Connect to URL filter always uses the SSL protocols configured in |
The following issues are known and scheduled for correction in a future release.
Internal ID | Case ID | Description |
---|---|---|
RDAPI-4545 | 00847780 | Path parameter data type cannot be changed (the default type is string). |
RDAPI-3953 | 00838718 | API Gateway hangs for 12 seconds when processing a policy. |
This service pack has the following prerequisites in addition to the prerequisites specified for the main product release:
INSTALL_DIR/system/lib/modules
directory.policystudio/plugins/com.vordel.rcp.filterbase_7.5.1._DATE/lib/json-path-<version>.jar
).JAVA_HOME
is set correctly in cassandra.in.sh
and cassandra.in.bat
to ensure Cassandra tools are launched successfully. INSTALL_DIR/apigateway/Win32/jre
INSTALL_DIR/apigateway/Linux.x86_64/jre
If FIPS mode is enabled, you must perform the following steps:
togglefips --disable
to turn FIPS mode off.nodemanager
to move the JARs.nodemanager
.nodemanager
.nodemanager
.togglefips --enable
to turn FIPS on again.nodemanager
.This section describes how to install the service pack on an existing installation of API Gateway.
Note
To install the service pack on your existing API Gateway 7.5.1 Core Server installation, perform the following steps:
INSTALL_DIR/ext/lib
directory (or the 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.
apigateway
directory
in your existing installation directory. For example:
tar -xzvf APIGateway_7.5.1_SP1_Core_linux-x86-64_BNYYYYMMDDn.tar.gz -C
/opt/Axway-7.5.1/apigateway/
# [ -f /etc/vordel/ssl-engines.xml ] && mv /etc/vordel/ssl-engines.xml /etc/vordel/ssl-engines.xml.1
# chown -R admin:admin /opt/gateway/
# grep "java.library.path" /opt/gateway/system/conf/jvm.xml || sed -i.bak -e '/<JVMSettings/a\\n <!-- Set to allow correct library load after setting CAP_NET_BIND_SERVICE on vshell -->\n <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"/>' /opt/gateway/system/conf/jvm.xml
# setcap 'cap_net_bind_service=+ep cap_sys_rawio=+ep' /opt/gateway/platform/bin/vshell
# ldconfig
Note
ls -l INSTALL_DIR/apigateway/posix/bin
command to view the owner of
the binaries.
To install the service pack on your existing API Gateway Analytics 7.5.1 installation, perform the following steps:
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.
analytics
directory within your existing API Gateway 7.5.1 installation directory. For example:
tar -xzvf APIGateway_7.5.1_SP1_Analytics_linux-x86-64_BNYYYYMMDDn.tar.gz -C
/opt/Axway-7.5.1/analytics/
Note
ls -l INSTALL_DIR/analytics/posix/bin
command to view the owner of
the binaries.
To install the service pack on your existing Policy Studio installation, perform the following steps:
INSTALL_DIR/policystudio
directory.policystudio
directory within your existing API Gateway 7.5.1 installation directory. For example:
tar -xzvf APIGateway_7.5.1_SP1_PolicyStudio_linux-x86-64_BNYYYYMMDDn.tar.gz -C
/opt/Axway-7.5.1/policystudio/
Note
policystudio -clean
.To install the service pack on your existing Configuration Studio installation, perform the following steps:
INSTALL_DIR/configurationstudio
directory.configurationstudio
directory within your existing API Gateway 7.5.1 installation directory. For example:
tar -xzvf APIGateway_7.5.1_SP1_ConfigurationStudio_linux-x86-64_BNYYYYMMDDn.tar.gz -C
/opt/Axway-7.5.1/configurationstudio/
Note
configurationstudio -clean
.Note
To allow an unprivileged user to run the API Gateway on a Linux system, perform the following steps:
INSTALL_DIR/system/conf/jvm.xml
file.
<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"/>
setcap 'cap_net_bind_service=+ep'
INSTALL_DIR/platform/bin/vshell
to allow the API Gateway to listen on privileged ports.
Go to Axway Sphere at https://support.axway.com to find all documentation for this product version.
For information about how API Gateway is used in Axway 5 Suite, refer to:
All Axway documentation is available from Axway Sphere at https://support.axway.com.
The Axway Global Support team provides worldwide 24 x 7 support for customers with active support agreements.
Email support@axway.com or visit Axway Sphere at https://support.axway.com.
Copyright © 2016 Axway. All rights reserved