Skip to content
CA API Gateway - 9.0
Documentation powered by DocOps

New Features and Enhancements

Last update December 21, 2017
Description Notes
Solution Kits

The CA API Gateway now supports Solution Kits—new functionality that can be purchased and installed at any time, independent of the Gateway releases. Solution kits can be installed two different ways:

  • Using the Policy Manager: The Manage Solution Kits task provides a graphical interface to install, upgrade, or uninstall Solution Kits.
  • Using the REST Management API: This "headless" method can install and manage Solution Kits without a graphical interface, as a resource in the REST Management API.
    Tip: The relative URL of this resource is "/solutionKitManagers"; for example:
    https://<GatewayHostName>:<port>/restman/1.0/solutionKitManagers
    Refer to the REST Management API documentation for more information about this resource.
OAuth Toolkit installation

The CA API Management OAuth Toolkit has been redesigned to take advantage of the new Solution Kit architecture.

The Policy Manager task "Install OAuth Toolkit as OAuth" has been removed. It is replaced with an OAuth Toolkit solution kit file installed and managed by the Manage Solution Kits task.

For more information about the OAuth Toolkit and how to install it, see docops.ca.com/otk.

Swagger support
The CA API Gateway can now validate requests against the API from a Swagger document. For more information, see Validate Against Swagger Document Assertion.
Scheduled Tasks New Manage Scheduled Task lets you schedule a policy fragment to run at a specific time or interval.
Enroll with Portal
New Enroll with Portal task makes it easy to connect an on-premise CA API Gateway to serve as the API Proxy for a CA API Developer Portal SaaS installation.
Policy Manager "offline" help By default, the Policy Manager online help retrieves content for your Gateway version from http://docops.ca.com. This ensures that you always have access to the latest documentation. If web access is not available due to restrictions at your organization, you can redirect the Policy Manager to open an "offline" version of the help installed at your site instead. For more information, see Install Offline Help.
Updates to appliance settings

A number of changes were made to the default configuration settings to improve the Gateway appliance performance with production traffic.

Added one new cluster property and changed defaults for existing properties:

Changed defaults for the following system properties:

  • com.l7tech.message.httpParamsMaxFormPost: 512000 to 5242880
  • com.l7tech.http.maxParameterLength: 600000 to 1000000
  • com.l7tech.common.http.prov.apache.CommonsHttpClient.maxConnectionsPerHost: 200 to 1500
  • com.l7tech.common.http.prov.apache.CommonsHttpClient.maxTotalConnections: 2000 to 3000

In node.properties:

  • c3p0DataSource.maxPoolSize default increased from 260 to 600

In appliancedefs.sh:

  • Removed "usebigmemory" logic that caps Gateway heap size to 2GB or 4GB. The CA API Gateway now uses half the total system memory.

Miscellaneous:

  • Cookie values are no longer truncated at the first equal sign ('=').
Enhancements to Server Module Files

Several enhancements have been made to the Server Module Files functionality:

  • No longer need to manually enable this feature by changing the serverModuleFile.upload.enable cluster property.
  • No longer need to manually enable write permissions to internal Gateway folders.
  • Only digitally signed modules can be uploaded now.
  • Manage Server Module Files "headlessly" without a graphical interface, as a resource in the REST Management API. Use the relative URL: "/serverModuleFiles". For example:
    https://<GatewayHostName>:<port>/restman/1.0/serverModuleFiles
Gateway AMI documentation

Full documentation for setting up and using the CA API Gateway AMI appliance is now included in this wiki. This replaces the previous CA API Gateway AMI Getting Started v8.2 PDF.

For more information, see Using the Gateway AMI Appliance.

Gateway Azure VM

The CA API Gateway is now available for deployment in the Azure VM Depot environment. For more information, see Run CA API Gateway in Microsoft Azure Cloud.

XML VPN Client help

The online help for the XML VPN Client is now in the same wiki format as the CA API Gateway. This simplifies the cross referencing of topics between the two products. 

Gateway Management Interfaces document The previous CA API Gateway Management Interfaces manual is now incorporated into this wiki documentation set and the PDF manual has been removed. For details, see WS Management API.

Internationalization

The product supports various encoding, including single and multibyte characters. However, certain industry standards may have specific encoding requirements (for example, the HTTP specifications require that HTML headers and values be restricted to the ISO-8859-1 character set). Field lengths that are specified in this documentation apply equally to single and multibyte character sets. For example, a field with a maximum length of 32 characters can accept 32 English or Korean characters.

Was this helpful?

Please log in to post comments.