—Rate this article—
 

14.04.16 - Apigee Edge cloud release notes

On Tuesday, April 29, 2014, we released a new cloud version of Apigee Edge.

If you have questions, go to Apigee Customer Support.

For a list of all Apigee Edge release notes, see Apigee Edge Release Notes.

New features and enhancements

Following are the new features and enhancements in this release.

  • Analytics dashboards
    Edge now provides new Endpoint Performance, API Proxy Performance, and Cache Performance Analytics reports to help you monitor performance.
    See "The Operations dashboards" at Use the built-in charts.
  • Custom metrics aggregation for performance
    A new custom aggregation feature improves analytics performance by letting you define custom metrics that Edge collects and stores as API calls are made. When you view reports, Edge accesses the already-available aggregated metrics rather than fetching them on the fly.
    See Use custom aggregations.
  • Preconfigured OAuth 2.0 in API proxies
    When creating an API proxy, a new "Secure with OAuth v2.0 Access Tokens" option automatically configures the API proxy with policies that support OAuth.
    See OAuth.
  • Data masking in trace
    The /maskconfigs API resource lets you mask sensitive data such as credit card information in API proxy trace sessions, helping ensure user data security during API development.
    Case:810723
    See Data masking.
  • Basic Authentication policy
    The Basic Authentication policy lets you add lightweight Basic Authentication to an API proxy, providing automatic Base64 encoding of user credentials and population of the HTTP Authorization: Basic header.
    See Basic Authentication policy.
  • PostClientFlow
    The PostClientFlow allows you to add MessageLogging policies that execute after the response is sent. This reduces API proxy latency and makes information available for logging that is not calculated until after the response is sent, such as the client.send.start.time and client.send.end.time.
    Case: 814059

Bugs fixed

The following bugs are fixed in this release.

Custom roles is a beta feature.
 
Topic Description
Custom report name validation Edge now validates the names of custom reports to disallow the use of special characters.
Report issues with developer_app drilldown Incorrect developer apps were being returned in custom reports that used the developer_app drilldown. This issue has been fixed.
Time Period not working on custom reports In custom reports that contained filters with multiple parenthetical expressions—for example, (request_verb eq 'POST') or (request_verb eq 'GET')—changing the report's time period had no effect on results. This issue has been fixed.
Case: 810753
Charts not appearing in custom reports An issue with charts not appearing in custom reports has been fixed.
Case: 814623
WSDL import
  • Importing a WSDL with SOAP headers resulted in an incorrect configuration. Support for SOAP headers has been added to address the issue.
  • Importing a WSDL with an external schema resulted in an API proxy that didn't post the proper message to the backend. Importing WSDLs that have multi-part complex types now results in a proper SOAP payload in the API proxy.
  • WSDL import now supports the documentation element in a SOAP operation. The documentation appears in the Description column of the WSDL import UI.
Concurrent Rate Limit policy configuration The Target Endpoint selector is now available only when adding a Concurrent Rate Limit policy to an API proxy. Target Endpoint does not apply to other policies.
Company support for developers For organizations that have companies enabled, you can now specify a company when creating or editing a developer.
Case: 515246
Export of developers, apps, and products You can now export developers, apps, and products to a CSV file from the Developers page in the Edge management UI. This feature is currently unavailable to organizations that have monetization enabled.
Case: 747159
Developer Apps window hanging After a developer deleted an app in the Edge Developer Portal, clicking that developer app in the Edge management UI would cause the window to hang. This issue has been fixed.
Comments in an API proxy configuration Comments in an API proxy configuration are now visible in the API proxy editor code view and Property Inspector.
API proxies created with invalid names The Edge management UI previously allowed the creation of API proxies whose names contained unsupported special characters, resulting in invalid API proxies that couldn't be deleted. API proxy names are now validated at creation time. Only alphanumeric, "-", and "_" characters are allowed.
Case: 550390
Case sensitivity in API proxy naming Edge was creating API proxies with lowercase names, regardless of the case entered. Edge now respects the case of the name entered for the API proxy.
Warning on API proxy save When you save an API proxy in the API proxy editor, Edge deploys the API proxy to all environments where the revision is currently deployed, including production environments. The Edge management UI now provides a warning before saving the proxy.
Custom role with no permissions saving to production environment When a deployed API revision is updated, it triggers an internal undeploy and deploy on deployed environments. A custom role without proper deployment permissions was able to deploy by saving an API proxy. This issue has been addressed by enforcing deployment permissions.
Case: 813084
Duplicate target server When creating a duplicate target server, instead of an HTTP 409 error, Edge overwrote the existing target server and returned a 201 status. This issue has been addressed by throwing a 409 error and not overwrite the existing target server.
Unable to create trace sessions for API proxies Trace sessions were not being created for environments with message processors that were unreachable. This issue has been resolved by attaching trace sessions only to the reachable and available message processors
Case: 812192
JMSReplyTo updated behavior By default, Edge sends the response to the queue specified in the JMSReplyTo header. However, if you want the backend service to handle sending the response to the JMSReplyTo queue rather than Edge, add the X-Apigee-Ignore-JMSResponse header to the API proxy response in any flow and set it to true:
<Header name="X-Apigee-Ignore-JMSResponse">true</Header>
See JMS integration.
High CLOSE_WAIT and 502 bad gateway errors An issue that caused high CLOSE_WAIT metrics and 502 bad gateway errors has been fixed.
Cases: 814656, 814664, 814670
Node.js temp directory When a Node.js script is deployed to Edge, it runs inside a sandbox that restricts file system access to a certain directory. However, os.tmpdir returns a directory name like /tmp or /var/tmp, which didn't exist in the Edge Node.js sandbox, causing some scripts to break. The Edge Node.js sandbox now includes a /tmp directory for os.tmpdir to use.
Null pointer exceptions on API calls In the Assign Message policy, a null response status threw a null pointer exception as Edge tried to capture the response code for metrics. This issue has been fixed.
Case: 815595

 

 

Help or comments?

  • Something's not working: See Apigee Support
  • Something's wrong with the docs: Click Send Feedback in the lower right.
    (Incorrect? Unclear? Broken link? Typo?)