This section describes version 4.19.01 of the Edge for Private Cloud Feature Release.
The following table summarizes the changes in this release:
This release includes the following new features:○ General Availability (GA) release of the Edge UI
○ General Availability (GA) release of Monetization in the Edge UI
○ Edge UI has new TLS configuration properties
○ You can now create, edit, and delete virtual hosts in the Edge UI
○ OpenAPI v3 support added
○ RedHat Enterprise Linux (RHEL) and CentOS 7.6 are now supported
○ Oracle Linux 7.5 is now supported
For more information about each of these new features, see New features.
Since the previous Edge for Private Cloud Feature Release, the following releases have occurred and are included in this release:
|Deprecations||Apigee Edge for Private Cloud version 4.17.09 is no longer supported (deprecated).
For more information, see Apigee deprecations, retirements, and CPS changes.
This release includes the following bug fixes:○ Zookeeper was not stopped by backup script (122694069)
○ 'No organizations' landing page added (120993451)
○ Deleting custom reports (120682369)
○ Geomap tab in New Edge experience (120681592)
○ Zookeeper JVM options (120624977)
○ Undefined errors occurred on tooltips (80187407)
○ Creating reverse proxies via OpenAPI (79949124)
○ Resetting passwords not sending links (77515655)
○ Incorrect headers for reset password links (72799769)
○ Using WSDLs to create API Proxies (69550284)
For more information about each of these fixes, see Bug fixes.
This release includes the following known issues:○ Metadata file format for apigee-sso install (135616498)
○ Message Processor backup not backing up the correct set of files (121095148)
○ Session tokens not invalidated (115278838)
○ Cassandra operations not working when JMX auth is enabled (113342838)
○ Hostnames not resolving (79757554)
○ DataAccessExceptions in multi data center configurations (76087166)
○ MessageLogging policy including extra information in the log message (68722102)
○ Resetting system admin password fails (65737520)
For more information about each of these known issues, including workarounds, see Known issues.
The following table shows the upgrade paths for this release:
|From 4.18.05||Directly upgrade from 4.18.05 → 4.19.01|
|From 4.18.01||Directly upgrade from 4.18.01 → 4.19.01|
|From 4.17.09||Directly upgrade from 4.17.09 → 4.19.01|
|From 4.17.05||Upgrade from 4.17.05 → 4.18.01, then upgrade from 4.18.01 → 4.19.01|
|From 4.17.01||Upgrade from 4.17.01 → 4.18.01, then upgrade from 4.18.01 → 4.19.01|
|From 4.16.09||Upgrade from 4.16.09 → 4.18.01, then upgrade from 4.18.01 → 4.19.01|
|From 4.16.05||Upgrade from 4.16.05 → 4.18.01, then upgrade from 4.18.01 → 4.19.01|
|From 4.16.01||Upgrade from 4.16.01 → 4.18.01, then upgrade from 4.18.01 → 4.19.01|
|From 4.15.0x||Upgrade from 4.15.0x → 4.16.01, then upgrade from Upgrade from 4.16.01 → 4.18.01, then upgrade from 4.18.01 → 4.19.01|
This section lists new features in this release. Additionally, this release includes all features in the Edge UI, Edge Management, and Portal releases listed in Included Releases.
In addition to the following enhancements, this release also contains multiple usability, performance, security, and stability enhancements.
General Availability (GA) release of the Edge UI
The Apigee Edge UI is our latest management UI service. Previously, it was in Beta. With Apigee Edge for Private Cloud v4.19.01, the Edge UI is part of the general release.
To use the Edge UI, you must enable SAML and then install the Edge UI on its own node.
For more information, see The Edge UI for Private Cloud.
General Availability (GA) release of Monetization in the Edge UI
The GA release of Monetization in the New Edge experience UI is now available.
You can now manage all monetization tasks for Apigee Edge for Private Cloud in the New Edge experience UI, including the following:
- Manage companies and developers
- Manage reports
- Configure monetization properties for a company or developer
- Make billing adjustments
With this announcement, monetization variance reports have been officially deprecated. See Apigee deprecations.
apigee-monit adds self-healing and monitoring services
Apigee Edge for Private Cloud now includes
apigee-monit, a tool based on the open source
apigee-monit periodically polls Edge
services; if a service is unavailable, then
apigee-monit attempts to restart it.
For information on installing, configuring, and using
Self healing with apigee-monit.
New TLS configuration properties
The Edge UI supports new TLS configuration properties that you can use to set the following:
- Default TLS protocol
- List of supported TLS protocols
- Supported TLS algorithms
- Supported TLS ciphers
For more information, see Setting optional TLS properties.
Create, edit, and delete virtual hosts in the Edge UI
Self service functionality has been expanded so that you can now create, edit, and delete virtual hosts in a browser (Edge UI only).
For more information, see Create a virtual host using a browser.
OpenAPI v3 support added
This release has added support for creating a proxy via OpenAPI version 3 (Edge UI only).
This release includes the following changes to supported software:
|Support Added||No Longer Supported|
This release adds support for the following platforms:
The following platforms are no longer supported with this release:
For a complete list of supported platforms, see Supported software and supported versions.
This section lists the Private Cloud bugs that were fixed in this release. Additionally, this release includes all bug fixes in the Edge UI, Edge Management, and Portal releases shown in Included Releases.
Zookeeper was not stopped by backup scriptThe Zookeeper process was not being stopped by the backup script before this fix.
'No organizations' landing page addedDevelopers who log in with a user that has no associated organizations are no longer sent to a page that doesn't exist. A new landing page has been added for these users.
Deleting custom reportsUsers could not delete custom reports in the New Edge experience.
Geomap tab in New Edge experienceWhen users navigated to the Geomap tab in the New Edge experience, the New Edge experience was throwing an error.
Zookeeper JVM optionsSetting JVM options by using Code with Config for Zookeeper was not working.
Undefined errors occurred on tooltipsWhen a chart had only one time series, the tooltips were throwing undefined errors.
Creating reverse proxies via OpenAPIThe Use OpenAPI button when creating proxies was not working.
Resetting passwords not sending linksUsers were not getting emails when requesting a link to reset their passwords.
Incorrect headers for reset password linksEven after a user set the
Using WSDLs to create API ProxiesAPI Proxy generation was failing when using WSDLs.
The following table lists known issues in this release:
Metadata file format for apigee-sso install
To work around this issue, you can do one of the following:
Message Processor backup not backing up the correct set of files
Run the backup a second time and it should back up the correct set of files.
Session tokens not invalidated
Session tokens are not invalidated on the server when the user clicks on the Apigee Edge Logout button.
Workaround:Use the New Edge experience with SAML.
Cassandra operations not working when JMX auth is enabled
Workaround:Add your username and password whenever you invoke the
HEAD requests to a Node.js target can hang, leaving connections pending.
To work around this issue, define a handler for
Hostnames not resolving
After installing or upgrading Edge for Private Cloud, hostnames might not resolve to their addresses.
To resolve this issue, restart the Edge UI component:
/opt/apigee/apigee-service/bin/apigee-service edge-ui restart
DataAccessException in multiple data center configurations
In multiple data center configurations, if one datastore becomes unavailable, then you might see the following error:
DataAccessException: Error while accessing datastore; Please retry later
The result is that Management Server may not start because it is trying to connect to Cassandra
nodes in both dc-1 and dc-2. The
Note that the expected state is for the Management Server not to connect to datastore components across regions.
The workaround is to deregister the following Cassandra node types in the unavailable data center and then re-register them after the Cassandra nodes are available again:
To deregister and reregister these Cassandra node types:
Note that these operations register and deregister nodes from Zookeeper and do not have any impact on the Cassandra cluster. For more information about these commands, see Update datastore registrations.
MessageLogging policy including extra information in the log message
Resetting system admin password fails
Resetting the system admin password for the Management Server that contain special characters will fail.
Define the password in a data file that you then pass to the
To get started with Edge for Private Cloud 4.19.01, use the following links: