This section describes version 4.19.06 of the Edge for Private Cloud Feature Release.
The following table summarizes the changes in this release:
This release includes the following new features:○ LDAP support for SSO
○ HTTP deployment support
○ Pluggable analytics
○ Cassandra rack support
○ IPv6 support
○ Simplified New Edge experience installation
For more information about each of these new features, see New features.
The following issues affecting backward compatibility were introduced in this version of Apigee Edge for Private Cloud:
Since the previous Edge for Private Cloud Feature Release, the following releases have occurred and are included in this release:
With the release of 4.19.06, the following are deprecated:
For more information, see Apigee deprecations, retirements, and CPS changes.
This release includes the following bug fixes:○ UseStringDeduplication not set (140270474)
○ MP errors (111445518)
○ Cassandra failures with JMX (113342838)
○ 13-node upgrades (138931337)
○ Proxies with the same name (119802562)
○ Keystores not loading (118851790)
○ Analytics failed (110988191)
○ Backup failures (110785400)
○ apigee-postgres backup/restore (70291825)
○ Resetting sysadmin password (65737520)
For more information about each of these fixes, see Bug fixes.
This release includes the following known issues:○ Mint not rating transactions initially (141628497)
○ Mint rating servers memory leak (137865184)
○ Metadata file format for apigee-sso install (135616498)
○ Message Processor backup not backing up the correct set of files (121095148)
○ DataAccessExceptions in multi data center configurations (76087166)
○ MessageLogging policy including extra information in the log message (68722102)
For more information about each of these known issues, including workarounds, see Known issues.
Note that Apigee Edge for Private Cloud version 4.19.06 is the last release in which Classic UI will be supported. In all future releases, only the New Edge experience will be supported.
The following table shows the upgrade paths for this release:
|From 4.19.01||Directly upgrade from 4.19.01 → 4.19.06|
|From 4.18.05||Directly upgrade from 4.18.05 → 4.19.06|
|From 4.18.01||Directly upgrade from 4.18.01 → 4.19.06|
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.
HTTP deployment support
By default, Edge uses RPC to deploy API proxies. While this mode works very well for most installations, larger topologies with many MPs might experience timeouts when a large number of concurrent calls are made via RPC.
As a result, Apigee recommends that larger deployments use HTTP rather than RPC for deployment. Enabling HTTP deployments are now supported.
For more information, see Enable HTTP deployment.
Cassandra rack support
Apigee now provides general guidance for scaling operations of Cassandra by making Cassandra on Apigee Edge for Private Cloud rack aware.
For more information, see Cassandra rack support.
By default, analytics data collected by the Message Processor is uploaded to Qpid and Postgres for processing. You can then view the analytics data in the Edge UI.
With this Feature Release, you can configure the Message Processor to write analytics data to disk or you can choose to use both options.
For more information, see Writing analytics data to a file.
Simplified New Edge experience installation
Installation of the New Edge experience has been simplified with a new script.
For more information, see Install the New Edge Experience.
LDAP IDP support
Authentication of users with Edge UI and Edge management API calls now supports LDAP in addition to SAML. LDAP support includes both direct binding and indirect binding methods.
For more information, see Overview of external IDP authentication.
By default, all runtime API calls to Apigee Edge for Private Cloud use IPv4. You can add IPv6 support to the Router with a new property.
For more information, see Use IPv6 on the Router.
INVALID_TSC transactions (Monetization)
You can now exclude
INVALID_TSC transactions from being added to the Postgres
database when using Monetization.
For more information, see Monetization server properties.
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.
UseStringDeduplication not set
MP errorsMessage Processors continuously logged the following error message every 5 min:
2019-06-29 00:02:05,775 Apigee-Timer-6 ERROR CMgmt - ConnectorServiceImpl.refreshToken() : Connector Management API auth token generation failed: 0 null
Cassandra failures with JMXCassandra operations were not working when JMX auth was enabled
13-node upgradesUpgrades of 13-node installations from 17.09, 18.01, and 18.05 were failing.
Proxies with the same nameIf two users in the same organization created proxies with the same names, the second one created would overwrite the first. This only occurred when different users could not see the other proxy.
Keystores not loadingWhen there were more than 100 keystores for an organization/environment, the keystore and reference section in Edge UI was not loading. Instead, the UI displayed an
Analytics failedAnalytics failed for an environment when supplied with data from the Microgateway that was set to a date in the future.
Backup failuresZooKeeper, Cassandra, and OpenLDAP intermittently failed to properly back up their data with the following error:
apigee-postgres backup/restoreExecuting an apigee-postgres backup/restore now backs up data for all components.
Resetting sysadmin passwordResetting the system admin password for the Management Server that contained special characters would fail.
The following table lists known issues in this release:
Mint not rating transactions initially
Edge for the Private Cloud does not rate transactions initially when you first enable monetization for an organization. This applies to new and existing organizations.
The monetization enablement API responds with the job ID and, upon completion, the status of the job will indicate success. However, any monetized API calls made initially will not be processed by monetization and will not be rated. These transactions will only show up in regular analytics.
Workaround:Restart any Message Processors (MPs), which can be done with the following:
apigee-service edge-message-processor restart
After monetization has been enabled, restarting the MPs causes Edge to load the configuration from ZooKeeper at startup. This happens on every restart, which means that the issue only applies initially.
Mint rating servers memory leak
When a new Qpid instance is registered in an mxgroup, the queues build without consumers, which results in the queue depth growing until it uses all available resources.
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.
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
To get started with Edge for Private Cloud 4.19.06, use the following links: