You're viewing Apigee Edge documentation.
Go to the
Apigee X documentation. info
On Monday, March 20, 2017, we released a new version of Apigee Edge for Private Cloud.
Update procedure
To update your installation, perform the following procedure:
-
On all Edge Management Server, Message Processor, and UI nodes, clean Yum repos:
> sudo yum clean all -
On all Management Server and Message Processor nodes, run the command:
>/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
where configFile specifies the config file you used to install Edge.
-
On all Edge UI nodes, update
edge-ui:>/opt/apigee/apigee-setup/bin/update.sh -c ui -f configFile
Bugs fixed
The following bugs are fixed in this release.
| Issue ID | Description | Build number |
|---|---|---|
| APIRT-2854 |
Removed Debug code from JavascriptStepExecution |
edge-gateway-4.16.05-0.0.1074 |
| DOS-4039 |
External authentication causes apigee-service commands to fail When external authentication is enabled, most customers use the Active Directory SAM account name field as the username for authentication, instead of an email address which is used by the Edge OpenLDAP server. If you have integrated with an external directory service and want Edge to support an account name, rather than an email address, as the username, then add the following line to your config file when updating Edge to 4.16.05.07: IS_EXTERNAL_AUTH="true" This line configures Edge to support an account name, rather than an email address, as the username. See Version 4.16.05 for more. |
apigee-lib-4.16.05-0.0.946 |
| EDGEUI-664 | Edge UI session is now correctly extended when user performs an action | edge-ui-4.16.09-0.0.3806 |
| MGMT-1430 |
API proxy resources validation When you have API proxy resource files (such as JavaScript or Java JARs) stored at the environment or organization scope, the validation framework no longer requires you to also include those resources at the API proxy level in a proxy bundle for import to pass validation. Resource validation now occurs at deploy time, not at import time. |
edge-gateway-4.16.05-0.0.1074 |
Known issues
This release has the following known issues.
| Issue ID | Description |
|---|---|
| APIRT-2978 |
Router fails to start Nginx or Router fails to start If the Edge Router fails to start Nginx or fails to start at all, as shown in the /opt/apigee/var/log/edge-router/logs/system.log file, then delete all files in the /opt/nginx/conf.d directory, and restart the router: > rm -f /opt/nginx/conf.d/* > /opt/apigee/apigee-service/bin/apigee-service edge-router restart |
| APIRT-3364 |
Message Processor does DNS lookup on IPv4 and IPv6 If you have installed and enabled NSCD (Name Service Cache Daemon) you might notice that Message Processors make two DNS lookups: one for IPv4 and one for IPv6. To disable the DNS lookup on IPv6:
|
| PRC-1118 |
Error when running "apigee-service apigee-postgresql pg-data-purge" command If you run the "apigee-service apigee-postgresql pg-data-purge" command and see an error in the form: ERROR: must be owner of relation Edit /opt/apigee/apigee-postgresql-4.16.05-0.0.894/lib/actions/pg-data-purge and set the following property to 'apigee': POSTGRES_USER=apigee |
| DOC-1687 | Due to a known package dependency conflict, the Katello agent used in Satellite Server 6 will not install properly on Apigee Edge hosts running the Qpid daemon. |