On May 1, 2020, we released a new version of Apigee Edge for Private Cloud.
To update your installation, perform the following procedure on the Edge nodes:
On all Edge nodes:
- Clean the Yum repos:
sudo yum clean all
- Download the latest Edge 4.19.06
curl https://software.apigee.com/bootstrap_4.19.06.sh -o /tmp/bootstrap_4.19.06.sh
- Install the Edge 4.19.06
apigee-serviceutility and dependencies:
sudo bash /tmp/bootstrap_4.19.06.sh apigeeuser=uName apigeepassword=pWord
Where uName:pWord are the username and password you received from Apigee. If you omit pWord, you will be prompted to enter it.
- Update the
sudo /opt/apigee/apigee-service/bin/apigee-service apigee-setup update
- Use the
sourcecommand to execute the
- Clean the Yum repos:
- Run the
update.shscript on all nodes. On each node, execute the following command:
/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
Where configFile specifies the configuration file that you used to install Apigee Edge for Private Cloud.
- If you use Apigee Developer Services portal (or simply, the portal), upgrade PHP, Drupal, and SmartDocs. For more information, see Upgrade the portal.
This release upgrades the following software used by Apigee Developer Services portal (or simply, the portal):
- PHP to 7.3 (RHEL 7/CentOS 7) or latest PHP in distribution (Amazon Linux AMI)
- Drupal core to 7.69
- Drush to 8.3.2
For more information, see Upgrade the portal.
Deprecations and retirements
The following table lists the bugs fixed in this release:
XSS Vulnerability in SmartDocs
This release fixes a security vulnerability in SmartDocs. Sites using SmartDocs are urged to upgrade immediately.
Policy execution order
In some cases, the order of execution for policies was not as expected.
Qpid server logging
The Qpid server process was logging messages about the
Requests with unavailable targets could result in multiple responses
When faults occurred during the processing of a request without a target, Edge for the Private Cloud sometimes sent multiple responses.
Shared flows in PostClientFlow
The Message Processor was going into an infinite loop when a proxy referenced a shared flow that was not deployed in the environment.
The following table describes the known issues for this release:
Do not use the following builds of OpenJDK 1.8.0:
If you are running one of these versions, Apigee recommends that you downgrade to a previous version. For more information, see How to download and install prebuilt OpenJDK packages.
KVMs in multi-data center environment
If an organization spans multiple datacenters (for example, dc-1, dc-2), the Management Server should connect only to the Cassandra nodes in the local data center for key management and Key Value Map (KVM) operations. However, the Management Server randomly connects to any of the datacenters.