You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info
On Wednesday, May 7, 2014, we released a quarterly version of Apigee Edge on-premises.
If you have questions, go to Apigee Customer Support.
For a list of all Apigee Edge release notes, see Apigee Release Notes.
New features and enhancements
Following are the new features and enhancements in this release.
- Java 7 support
Edge supports Java 1.7 in addition to Java 1.6.
- Multi-datacenter analytics
Edge analytics is now supported in deployments that use multiple datacenters. With an active-active configuration, Analytics Services tracks the router and message processor on which an API request was handled. For more information, see the OPDK Install and Configuration Guide.
- Display Monetization billing documents in HTML format
Monetization now displays billing documents to end users in HTML format. If you want to provide billing documents as PDF files, you can integrate monetization with a billing system that provides PDF generation or license a supported third-party PDF library.
See Create billing documents.
- JMS for multi-datacenter deployments
JMS listeners are now deployed to all routers, allowing inbound JMS endpoints to be deployed in multi-datacenter environment.
This release also contains features and bug fixes from the following cloud releases:
|Incorrect password set
|When creating a password with the word "admin" in it, Edge replaced "admin" with the administrator email ID from the UI config file. Edge now no longer replaces "admin" when used in a password.
|In the setenv.sh script, you can now set the min_permsize argument to reduce server startup time.
|get_pid() in etc/init.d/message-processor
|The functionality of etc/init.d/message-processor was broken if Edge is installed in a directory containing "sh" in the path; for example, /home/shark/apigee4. This issue has been resolved.
|backup.sh and backup-ui.sh
|Issues with OPDK_VERSION in backup.sh and backup-ui.sh scripts for Edge on-premises
versions 14.01.x.x have been resolved.
|When API proxy bundles were undeployed or deleted using either the Edge management UI
or the apigeetool script, deployment errors sometimes occurred. This issue has been