CA API Gateway 9.1

9.4 9.1

Software Gateway Specifications

Minimum requirements for a host machine running the Software form factor of the gateway:
gateway94
Minimum requirements for a host machine running the Software form factor of the 
CA API Gateway
:
Requirement
 
Minimum
 
Networking
one IPv4 or IPv6 interface
Processor
Dual core processor, 2 GHz or faster
Memory
4 GB (8 GB or above recommended)
Operating System
Dedicated server running one of:
  • Red Hat Enterprise Linux (RHEL) 5.10, 6.x, 7.x
  • CentOS 6.x, 7.x
  • SuSE Linux Enterprise 10 or 11
  • Solaris 10 (x86 or Sparc)
Support for Cloud Environments:
 CA Technologies has not formally tested Software Gateway deployment in cloud environments. CA Technologies is fully committed to ensuring that the Software form factor runs on all supported operating systems, regardless of where those operating systems are located. Issues that arise between that operating system and the cloud environment should be directed to the operating system vendor or cloud environment owners.
Java
Java SE Development Kit (JDK) 1.8.0 u102
 
AdoptOpenJDK for Gateway Version 9.4 CR3+
Beginning with version 9.4 CR3 of the Gateway, CA Technologies recommends AdoptOpenJDK 8u222+
Java Cryptography Extensions (JCE)
For Versions Older than JDK8 u151
JCE unlimited strength jurisdiction policy files
  2. Extract files.
  3. Copy the 
    jce/*
     files to 
    <JDK directory>
    /jre/lib/security/*
     on Gateway.
For Versions JDK8 u151 to u161
This release introduces a new feature whereby the JCE jurisdiction policy files used by the JDK can be controlled via a new Security property. In older releases, JCE jurisdiction files had to be downloaded and installed separately to allow unlimited cryptography to be used by the JDK. The download and install steps are no longer necessary. To enable unlimited cryptography, one can use the new 
crypto.policy
Security property. If the new Security property (crypto.policy) is set in the 
java.security
 file, or has been set dynamically by using the 
Security.setProperty()
 call before the JCE framework has been initialized, that setting is honored. By default, the property is undefined. If the property is undefined and the legacy JCE jurisdiction files do not exist in the legacy lib/security directory, then the default cryptographic level remains at 'limited'. To configure the JDK to use unlimited cryptography, set the 
crypto.policy
 to a value of 'unlimited'. See the notes in the 
java.security
 file shipping with this release for more information.
For Versions JDK8 u162 and later
If you have JDK8 u162 or a later version installed,
 
none of the steps above apply for JCE enablement. JCE is automatically enabled and
 cryto.policy
 is set to a value of 'unlimited' by default.
Database
MySQL 5.7.x, with root user and password
  • minimum 500 MB for tablespace (1 - 10 GB recommended)
  • INNODB table handler required
Solaris 10 Exception:
 The Solaris 10 software form factor supports only MySQL 5.5. There are no MySQL 5.7 packages for Solaris 10.
Support for non-English characters:
 If non-English characters will be used in the Policy Manager (connected to a Software Gateway), configure the MySQL server to use "character-set-server=utf8" in the MySQL server configuration file.
CA API Management OAuth Toolkit (OTK)
OTK 4.3.00
Optional Software
The following software is recommended:
  • SNMP installed and configured
  • NTP daemon installed and configured, for time synchronization
 The 
CA API Gateway
 offers the option to run with an embedded database that offers slightly reduced functionality, but with advantage of not requiring MySQL to be present.

Content feedback and comments