- Edge for Private Cloud release notes

You're viewing Apigee Edge documentation.
Go to the Apigee X documentation.

On Wednesday, October 26, 2016, we released a new version of Apigee Edge for Private Cloud.

Update procedure

To update your installation, perform the following procedure:

  1. On all Edge nodes, clean Yum repos:
    > sudo yum clean all

  2. On all Edge nodes, update apigee-setup:
    > /opt/apigee/apigee-service/bin/apigee-service apigee-setup update

  3. On all Edge nodes, update edge-gateway:
    >/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile

    where configFile specifies the config file you used to install Edge.

  4. On all Edge UI nodes, update edge-ui:
    >/opt/apigee/apigee-setup/bin/update.sh -c ui -f configFile

    This update includes the fix for EdgeUI-675. After you perform this update, you can configure the Edge UI to allow OpenAPI specs to define requests to private IP addresses as described below.

  5. If you have installed Edge Monetization services only, apply the patch for DEVRT-3098:
    > /opt/apigee/apigee-service/bin/apigee-service edge-mint-management-server add-missing-notification-templates -f configFile

    where configFile specifies the config file you used to install Edge.

Bugs fixed

The following bugs are fixed in this release.

Issue ID Description Build number

XML to JSON policy enhancements

The XML to JSON policy has been enhanced with the following capabilities. You can configure the policy to:

  • Treat some XML elements as arrays during conversion, which puts the values in square brackets '[ ]' in the JSON document.
  • Strip or eliminate levels of the XML document hierarchy in the final JSON document.

For more information, see XML to JSON policy


Error uploading Node.js payloads over 25KB

You can now upload Node.js payloads larger than 25KB.


Error encountered when setting up Monetization notification templates using the UI

An error is raised when setting up Monetization notification templates using the UI, as described in Set up notifications using notification templates.


Allow OpenAPI specs to access private IP Addresses

By default, Edge prevents OpenAPI specs from referencing private IP addresses. You can now enable access to private IP addresses:

  1. Open the ui.properties file in an editor. If the file does not exist, create it.
    > vi /<inst_root>/apigee/customer/application/ui.properties
  2. Set the following property to true:
  3. Save your changes to ui.properties.
  4. Restart the Edge UI:
    > /<inst_root>/apigee/apigee-service/bin/apigee-service edge-ui restart

Known issues

This release has the following known issues.

Issue ID Description

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

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':


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.