8 minute read
Operating systems and hardware
This section describes the operating system requirements for API Gateway.
API Gateway supports the following software versions:
- CentOS 6.x, 7.x, 8.x (CentOS 8.x is supported from 7.7.20200530 update onward.)
- Oracle Linux 6.x, 7.x
- Red Hat Enterprise Linux 6.x, 7.x, 8.x (Red Hat Enterprise Linux 8.x is supported from 7.7.20200530 update and later updates only.)
- SUSE Linux Enterprise Server 11.x, 12.x
API Gateway supports the following hardware:
- 64-bit Linux running on 64-bit hardware
- Intel Core or AMD Opteron at 2Ghz with Dual Core or faster
NoteWhen new Linux kernels and distributions are released, Axway modifies and tests its products for stability and reliability on these platforms. Axway makes every effort to add support for new kernels and distributions in a timely manner. However, until a kernel or distribution is added to this list, its use with API Gateway is not supported. Axway endeavors to support any generally popular Linux distribution on a release that the vendor still supports.
Your Linux system must have the
LANG environment variable set. If this variable is not configured correctly, your system might have issues handling Unicode characters in file names. A full installation of Linux should configure this for you automatically. If you are running the API Gateway in a Docker image that you have built, set this variable in your Dockerfile as follows:
This variable is automatically set for you in EMT mode.
In CentOS 8.x and Red Hat Enterprise Linux 8.x, the GNU C Library (glibc) no longer includes
glibc-langpack-en libraries. However, those were included in previous releases and are required by the API Gateway. To install the missing libraries, run the following command:
sudo yum install libnsl glibc-langpack-en
Windows is supported only for a limited set of developer tools, see Install developer tools on Windows. API Gateway and API Manager do not support Windows.
This section addresses Policy Studio, Configuration Studio, and Package and Deployment tools only.
Developer tools supports the following software versions:
- Windows 10
- Windows 8.1
Developer tools supports the following hardware:
- 32-bit Windows on both 32-bit hardware and 64-bit hardware
- Intel Core or AMD Opteron at 2Ghz with Dual Core or faster
Disk space and RAM requirements
The disk space and RAM requirements for Linux platforms are:
- Disk space: minimum 4 GB, 50 GB recommended
- Physical memory (RAM): minimum 8 GB
The disk space and RAM requirements for the developer tools on Windows platforms are:
- Disk space: minimum 2 GB
- Physical memory (RAM): minimum 4 GB
There are also specific requirements for the
- Minimum 500 MB available in the
/tmpdirectory and writable permissions on the
noexecmust not be set on
noexecis set, you must remount
noexecdisabled or follow the additional steps detailed in /tmp directory mounted with noexec.
This section describes the supported database versions.
API Gateway and API Manager support the following relational databases to store metrics data:
- MySQL Server 5.7, 8.0
- MariaDB 10.2, 10.5
- Microsoft SQL Server 2016, 2017, and 2019
- Oracle 12.2, 18c, and 19c
- IBM DB2 10.5
For more details, see Install and configure a metrics database.
API Gateway and API Manager support Apache Cassandra version 2.2.12 for internal data storage. For more details, see Install an Apache Cassandra database.
API Gateway Manager and other browser-based client components support the following browsers:
- Internet Explorer 11
- Firefox 13.0 or higher
- Safari 5.1.7 or higher
- Google Chrome 19 or higher
- Microsoft Edge (on Windows 10 only)
Thick client platforms
Policy Studio has the following additional requirements on Linux:
- X-Windows environment
- GTK+ 2
API Gateway and API Manager support elastic topology in Docker deployments. For details of Docker support, see Set up Docker environment.
NoteIf you are using API Manager monitoring, you also require a shared file system between your API Gateway instances and Admin Node Manager. This is required for processing of transaction event logs and writing API metrics to a database.
Specific component requirements
This section describes requirements for specific API Gateway components.
- Policy Studio is a thick client and supports the platforms described in Thick client platforms.
- API Gateway Manager is a web-based client and supports the web browsers listed in Web browsers.
- API Gateway Analytics is a server component that has the same operating system and hardware requirements as API Gateway. See Operating systems and hardware. API Gateway Analytics requires a database. For database requirements, see Databases. The browser-based client component supports the same browsers as API Gateway Manager. See Web browsers.
- API Manager is a browser-based client and supports the same browsers as API Gateway Manager. See Web browsers.
This section describes the default ports used by API Gateway components.
The default ports used by API Gateway are as follows:
- Traffic port:
8080(between clients and API Gateway)
- Management port:
8085(between API Gateway and Admin Node Manager)
Admin Node Manager
The default port used by the Admin Node Manager for monitoring and management of API Gateway instances is
The default URL address used by the Policy Studio tool to connect to the Admin Node Manager is as follows:
API Gateway Manager
The default URL address used by the API Gateway Manager web console to connect to the Admin Node Manager is as follows:
The default URL address used by the API Manager web console for API management is as follows:
API Gateway Analytics
The default port used by API Gateway Analytics for reporting, monitoring, and management is
8040 . The default URL address used by the API Gateway Analytics web console is as follows:
Software and license keys
Axway products are delivered electronically from Axway Support. A welcome email notifies you that your products are ready for download.
When you are ready, perform the following tasks:
- Check your authorization.
- Check the hardware and system requirements.
- Obtain license keys.
- Download the installation setup file from Axway Support.
- Install products.
Check your authorization
Verify that you can log in to Axway Support. If you do not have an account, follow the instructions in your welcome email.
Log in to download or access:
- The product installation package
- Your product license key
- Product documentation
- Product updates, including patches and service packs
- Product announcements
- The support case center, to open a new case or to track opened cases
You can also access other resources, such as articles in the Knowledge Base, the Axway User Forum, and documentation for all Axway products.
API Gateway requires the following license keys.
Axway license file:
You must have a valid Axway license file to install the following API Gateway components:
- API Gateway Server
- API Gateway Analytics
- API Manager
You can obtain an evaluation trial license to enable you to evaluate the API Gateway features. However, you must have a full license to enable all API Gateway features for use in a non-evaluation environment (for example, development, testing, or production). To obtain an evaluation trial license or a full license, contact your Axway Account Manager.
You can install an Admin Node Manager in isolation without an API Gateway license. For more information, see Install the Admin Node Manager.
McAfee license file:
You must have a valid McAfee license file to use the McAfee Anti-Virus filter.
FIPS-compliant mode license file:
You must have a valid Axway FIPS-compliant mode license file to run API Gateway in FIPS-compliant mode.
API Gateway requires a minimum of two installations for high availability (HA). Make sure that you obtain license keys for all of the API Gateway instances that you are installing.
This section lists additional prerequisites for installing API Gateway.
On Linux, you must ensure that the installation executable has the appropriate permissions in your environment. For example, you can use the
chmod command to update the file permissions.
/tmp directory mounted with noexec
If your Linux system has the
/tmp directory mounted with
noexec, you must complete some additional steps before installing or running API Gateway.
When installing API Gateway, do not install the QuickStart tutorial:
- When running the installer in GUI mode, you must select the Custom setup type and deselect the QuickStart tutorial component. For more information, see Installation options.
- When running the installer in unattended mode, you must use the
--setup_type advancedoption and specify
--disable-componentsoption. For more information, see Unattended installation.
NoteDo not install the QuickStart tutorial as this option starts Apache Cassandra, the API Gateway server and the Node Manager when installation completes, and in a system with
noexecyou must make some changes before starting these components.
After completing the installation and before starting the services:
Create a new temporary directory that has
execprivileges (for example,
If you installed Cassandra during API Gateway installation, edit the file
CASSANDRA_INSTALL_DIR/conf/cassandra-env.shand add the following line:
Create or edit the file
VDISTDIR/apigateway/conf/jvm.xml, and add the following:
<ConfigurationFragment> <VMArg name="-Djava.io.tmpdir=<TheNewTmpDir> </ConfigurationFragment>
Service packs for API Gateway are available from Axway Support. If any service packs are available for API Gateway 7.7, download and apply them when the installation completes.
For more information on applying a service pack, see Update API Gateway.
API Gateway uses Secure Sockets Layer (SSL) for communications between all processes in a domain (for example, internal management traffic between the Admin Node Manager and API Gateway instances).
Certificates are not required during installation; however, certificates will be required after installation to secure API Gateway domains. For more information on configuring and securing API Gateway domains, see the API Gateway Administrator Guide.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.