Apigee Edge Private Cloud 4.16.09 Release Is Out!
We’re pleased to announce the general availability of Apigee Edge Private Cloud version 4.16.09. This release, which brings our customers the latest innovations in Edge, is centered around the themes of developer productivity, DevOps productivity, and performance.
Geo map dashboard
The geo map dashboard is now available in the Edge Private Cloud management UI. It enables you to track and assess important information about traffic patterns, error patterns, and quality of service across geographical locations. The dashboard can be accessed from the GeoMap item in the analytics menu.
Improved SOAP wizard
The new release also includes an improved SOAP wizard for building SOAP pass-through and SOAP-REST mediation services.
With pass-through SOAP, where the proxy simply passes through a SOAP request payload as is. All WSDL operations are now sent to the proxy base path "/" rather than to proxy resources (such as "/cityforecastbyzip"). Operation names are passed through to the target SOAP service. This behavior matches the SOAP specification.
The generated proxy no longer supports JSON in the request—it supports only XML. The proxy ensures SOAP requests have an envelope, body, and a namespace.
With REST to SOAP to REST, the proxy converts an incoming payload, such as JSON, to a SOAP payload and converts the SOAP response back to the format the caller expects. In the latest release, the proxy lets you POST JSON data instead of FormParams. The proxy has better support for CORS (cross-origin resource sharing) and offers better namespace and AbstractType recognition.
The new release also includes enhancements to our monetization features. You can create webhooks, which define an HTTP callback handler that is triggered by an event, and configure them to handle event notifications as an alternative to using the monetization notification templates. This makes it easy to notify any custom endpoint (user-defined) for monetization related events. It can be accessed by selecting “webhooks” in the admin menu.
The new release also contains public and private rate plans:
- Public rate plans are visible to app developers, who can subscribe to them through the developer portal. This option works great for external rate plans.
- Private rate plans are not visible to app developers. You can add app developers to them using the Edge management UI or using monetization APIs. This kind of rate plan can be used for scenarios involving either internal use cases or when a workflow or manual intervention is required before an app developer can subscribe.
A new "adjustable notification with custom attribute" rate plan lets you add to a developer's transaction count using the value of a custom attribute. With the standard adjustable notification rate plan, each successful API call adds one to a developer's transaction count. But with the new rate plan, the value of the custom attribute is added to the developer's transaction count.
For example, if custom attribute "small" has a value of 0.1 in the response, the transaction count is incremented by 0.1; or if custom attribute "addressTotal" has a value of 50, the count is incremented by 50.
With our JSON payload enhancement, no workarounds are needed to ensure proper JSON message formatting, and variables can be specified using curly braces without creating invalid JSON.
Other improvements include:
- The ability to configure a policy to treat some XML elements as arrays during conversion, which puts the values in square brackets '[ ]' in the JSON document.
- The ability to configure a policy to strip or eliminate levels of the XML document hierarchy in the final JSON document.
- The ability to include wildcards in multiple places in a resource path when defining resource paths in API product. 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.
- The ability to 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 than the timeout configured on the load balancer, router, and message processor.
On the DevOps productivity front, we’ve released a beta version of a new monitoring dashboard to provide monitoring for Apigee Edge infrastructure. It helps you understand the health of various components (routers and message processors) as well as HTTP error codes for various orgs and environments in your deployment.
You can also snapshot these details and share them with Apigee to resolve support incidents. This can significantly shorten the time needed to capture important information about your environment during your support case.
Analytics collector utility
We’ve released a beta version of the analytics collector utility as a Node package, which can be deployed on your machines locally. It helps private cloud customers collect useful API traffic metrics and push them into Apigee 360.
Apigee 360 offers one convenient place to open and manage support cases, track traffic and usage metrics, and receive important notifications. It provides customers a 360-degree view of their relationship with Apigee.
This version supports Postgres 9.4.5, which offers tremendous performance improvements: generalized inverted Indexes are now up to 50% smaller and up to 3X faster; materialized views are concurrently updatable for faster, more up-to-date reporting; and parallel writing to the PostgreSQL transaction log is faster.
How to upgrade
We strongly encourage customers to upgrade to this new release as soon as possible. For customers already on 4.16.01 or 4.16.05 it’s easy to upgrade. If you’re on an older release, you will need to migrate to 4.16.01 first and then upgrade to 4.16.09 (check out these upgrade instructions).
Hope you’re as excited as we are about this new release. There’s a lot more to share than what can fit in here; additional details can be found in our official release notes.