Document version: 17 October 2014
This Readme applies to Axway API Gateway 7.3.0 SP1 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_SP1_Core_win-x86-32_BN201410131.zip
for Windows.
Size: The file size differs for each platform. The MD5 checksum is provided for each file.
This service pack fixes the following problems:
Case ID | Internal ID | Description |
---|---|---|
727339 | 131987 | No entries found for certain LDAP search criteria
Previously, LDAP search was not escaping the search criteria, and as a result no entries were found for certain search criteria. Now, LDAP searches are escaped and search results are returned as expected. |
729740 | 126219 | Auto-environmentalization of CA certificate fields results in incorrect metadata
Previously, the auto-environmentalization of CA Certificate fields (during .pol
export) resulted in env fields being laid down with incorrect metadata, causing
it not to work.
Now, auto-environmentalization of CA certificates works correctly. |
730624 | 126380 | Encrypt Web Service filter does not support nodes.to.encypt message attribute
Previously, the Encrypt Web Service filter did not support the nodes.to.encypt
message attribute.
Now, the Encrypt Web Service filter supports nodes.to.encypt message attribute.
|
739921 | 130622 | Unable to configure FTPS passive ports and issues with max connections
Previously, you could not configure passive ports for FTPS, and there were issues with reaching maximum connections. Now, you can configure passive ports for FTPS connections and control the number of connections that can be opened. |
740531 | 131150 | upgradeconfig gives UnsupportedEncodingException when mismatch between ISO-18859-1 and UTF-8
Previously, in some cases, upgradeconfig gave an UnsupportedEncodingException
when there was an ISO-18859-1 and UTF-8 mismatch between the request and the XML file being upgraded.
Now, upgradeconfig handles XML encoding in the correct manner. |
746093 | 133433 | Adding MIME type to Threatening Content filter fails with exception
Previously, adding a MIME type to a Threatening Content filter failed with an exception. Now, an exception no longer occurs when adding a MIME type to a Threatening Content filter. |
746421 | 133806 | Intermittent crashes viewing transaction logs in API Gateway Manager
Previously, there were intermittent crashes when viewing transaction logs on the Traffic tab of API Gateway Manager. Now, you can now view transaction logs in API Gateway Manager without any crashes. |
746981 | 133850 | Stability issues with traffic monitoring data
Previously, there were stability issues with traffic monitoring data storage and retrieval. Now, you can now view transaction logs in API Gateway Manager without any crashes. |
749194 | 123959 | Errors starting up server if environment properties requiring map are not specified
Previously, there were errors on starting up the server if there were environment properties that required a map, and they were not specified first in the properties file. Now, errors no longer occur on startup of the server regardless of what order the properties are specified in. |
— | 130331 | Validate Timestamp filter restricts drift time to 5 seconds
Previously, the Validate Timestamp filter restricted drift time to 5 seconds or less. Now, you can specify a drift time of more than 5 seconds in the Validate Timestamp filter. |
— | 131864 | Unable to configure a Directory Scanner when using sort settings
Previously, you were unable to configure a Directory Scanner when using the Sort Files options (for example, sort by date last modified). Now, when Sort Files options are used, you can configure a Directory Scanner. |
This section includes the prerequisites and installation instructions for this service pack.
In addition to the prerequisites specified for the main product release:
INSTALL_DIR/system/lib/modules
directory.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.
To install the service pack on your existing API Gateway 7.3.0 Core Server installation, perform the following steps:
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.
apigateway
directory in your
existing installation directory. For example:
tar -xzvf APIGateway_7.3.0_SP1_Core_linux-x86-64_BN201410131.tar.gz -C
/opt/Axway-7.3.0/apigateway/
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.3.0 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.3.0 installation directory. For example:
tar -xzvf APIGateway_7.3.0_SP1_Analytics_linux-x86-64_BN201410131.tar.gz -C
/opt/Axway-7.3.0/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
).
To install the service pack on your existing Configuration Studio installation, perform the following steps:
INSTALL_DIR\configurationstudio
).
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"/>
<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"/>
setcap 'cap_net_bind_service=+ep'
INSTALL_DIR/platform/bin/vshell
to to allow the API gateway to listen on privileged ports.
Note
Axway API Gateway is accompanied by a complete set of documentation, covering all aspects of using the product. These documents include the following:
All Axway documentation is available from Axway Sphere at https://support.axway.com.
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 2014
All rights reserved