16.08.17 - Apigee Edge for Public Cloud release notes

You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info

On Tuesday, August 30, 2016, we released a new version of Apigee Edge for Public Cloud.

New features and updates

Following are the new features and updates in this release.

JSON payloads in Assign Message and Raise Fault

With this enhancement, no workarounds are needed to ensure proper JSON message formatting, and variables can be specified using curly braces without creating invalid JSON. For example, the following inserts the value of message.content in the JSON message:

<Payload contentType="application/json">{"message" : "{message.content}"}</Payload>

If you used a workaround, your code will continue to work as is. You can also use variablePrefix and variableSuffix instead of curly braces to indicate variables.

See the <Set><Payload> element in the Assign Message policy and Raise Fault policy reference docs. (APIRT-1160)

XML to JSON policy enhancements

The XML to JSON policy has been enhanced with the following capabilities. You can configure the policy to:

• Treat some XML elements as arrays during conversion, which puts the values in square brackets '[ ]' in the JSON document.
• Strip or eliminate levels of the XML document hierarchy in the final JSON document.

For more information, see XML to JSON policy. (APIRT-1144)

Multiple wildcards in API Product resource paths

When defining resource paths in API Product, you can include wildcards in multiple places in a resource path. For example, /team/*/invoices/** allows API calls with any one value after /team and any resource paths after invoices/. An allowed URI on an API call would be proxyBasePath/team/finance/invoices/company/a.

If after this release your existing API Product resource paths stop working as expected, set the following property on your organization to revert to the previous behavior: features.enableStandardWildCardMatchForAPIProductResources = true

(MGMT-3273)

Crypto functions in JavaScript

A new set of high-performance JavaScript crypto functions is available for creating, getting, and updating the following has objects: MD5, SHA-1, SHA256, SHA512. The crypto object also lets you get the date in various formats. For more information, see JavaScript object model. (APIRT-2886)

Java Callout JAR version checking

When uploading a Java JAR resource to an API proxy, an HTTP 400 status code is returned (instead of a 500) if the version of the Java resource is incompatible with the Edge supported version of Java, listed in Supported software and supported versions. (MGMT-3420)

API proxy resources validation

When you have API proxy resource files (such as JavaScript or Java JARs) stored at the environment or organization scope, the validation framework no longer requires you to also include those resources at the API proxy level in a proxy bundle for import to pass validation. Resource validation now occurs at deploy time, not at import time. (MGMT-1430)

Configure the timeout for individual API proxies

You can configure API proxies to time out after a specified time (with a 504 gateway timeout status). The primary use case is for Private Cloud customers who have API proxies that take longer to execute. For example, say you need specific proxies to time out at 3 minutes. You can use a new api.timeout property in the configuration for an API proxy. Here's how you'd do it with the 3-minute example:

1. First, be sure to configure the load balancer, router, and message processor to time out after 3 minutes.
2. Then configure the relevant proxies to time out at 3 minutes. Specify the value in milliseconds. For example:

   <ProxyEndpoint name="default">
     <HTTPProxyConnection>
       <BasePath>/v1/weather</BasePath> 
       <Properties> 
         <!-- api.timeout is in milliseconeds -->
         <Property name="api.timeout">180000</Property>
       </Properties>
       ...

3. Note, however, that raising the system timeouts could result in performance issues, because all proxies without an api.timeout setting use the new, higher load balancer, router, and message processor timeouts. So configure other API proxies that don't require longer timeouts to use lower timeouts. For example, the following sets an API proxy to time out after 1 minute:
   <Property name="api.timeout">60000</Property>

Cloud customers, who can't modify the Edge timeouts, can also configure an API proxy timeout, as long as the timeout is shorter than the standard Edge message processor timeout of 57 seconds.

You cannot populate the value with a variable. This property is covered in the Endpoint properties reference. (APIRT-1778)

TLS/SSL for Message logging Policy

<KeyStore> and <TrustStore> can be set in the SSLInfo configuration on the Message Logging policy, allowing one- and two-way TLS/SSL with a logging service. You configure SSLInfo on the Message Logging policy the same way you would on a proxy TargetEndpoint. However, Message Logging TLS/SSL supports only the TCP protocol. (APIRT-1858)

Bugs fixed

The following bugs are fixed in this release. This list is primarily for users checking to see if their support tickets have been fixed. It's not designed to provide detailed information for all users.