- Edge for Private Cloud release notes

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

On Monday, July 31, 2017, we released a new version of Apigee Edge for Private Cloud.

Update procedure

To update your installation, perform the following procedure on the Edge nodes:

  1. On all Edge nodes:

    1. Clean Yum repos:
      > sudo yum clean all
    2. Update the Edge 4.17.01 bootstrap_4.17.01.sh file in /tmp/bootstrap_4.17.01.sh:
      > curl https://software.apigee.com/bootstrap_4.17.01.sh -o /tmp/bootstrap_4.17.01.sh
    3. Install the Edge 4.17.01 apigee-service utility and dependencies:
      > sudo bash /tmp/bootstrap_4.17.01.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.
    4. Update the apigee-setup utility:
      > sudo /opt/apigee/apigee-service/bin/apigee-service apigee-setup update
    5. Source the apigee-service.sh file:
      > source /etc/profile.d/apigee-service.sh
  2. Update all Cassandra nodes:
    >/opt/apigee/apigee-setup/bin/update.sh -c cs -f configFile

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

  3. Update all Router nodes:

    > yum update apigee-nginx
    > /opt/nginx/scripts/apigee-nginx restart
  4. Update all Router and Message Processor nodes:
    >/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile

  5. Update all Edge UI nodes:
    >/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

Edge Router now working on FIPS-enabled server

The Edge Router can now be deployed to a server that supports FIPS (Federal Information Processing Standards).


Cassandra backup script no longer stops/restarts Cassandra

Previously, the Cassandra backup script stopped and then restarted the Cassandra server as part of the backup process. The script no longer performs this stop/restart and leaves the Cassandra server running during the backup process.



Log file rotation for the Edge Router functioning correctly


HTTP access to Edge UI now functioning after you enable HTTPS

Previoulsy, if you enabled HTTPS access on the Edge UI but left HTTP enabled, an HTTP request on the Edge UI port was redirected to HTTPS on the same port. For example, you enabled HTTP access on port 9000 and then enabled HTTPS on port 9443. HTTP requests on port 9000 were then being redirected to HTTPS on port 9000 instead of to port 9443.


Edge UI trace now working correctly in Internet Explorer