You're viewing **Apigee Edge** documentation.  
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs). info

On March 30, 2021, we released a new version of Apigee Edge for Private Cloud.

> [!NOTE]
> **Note:** Apigee Edge for Private Cloud version 19.06 will be supported until May 31, 2021.

> [!NOTE]
> For more information, see the following resources:
>
> - *[Edge for Private Cloud 4.19.06
>   documentation](https://docs.apigee.com/private-cloud/v4.19.06)*
> - *Questions or issues?* Contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support)
> - *Release notifications* : See [Get Apigee Edge release notifications](https://docs.apigee.com/release/get-release-notifications)

## Update procedure

Updating this release will update the components in the following list of
RPMs:

- edge-gateware-4.19.06-0.0.20115.noarch.rpm
- edge-management-server-4.19.06-0.0.20115.noarch.rpm
- edge-message-processor-4.19.06-0.0.20115.noarch.rpm
- edge-postgres-server-4.19.06-0.0.20115.noarch.rpm
- edge-qpid-server-4.19.06-0.0.20115.noarch.rpm
- edge-router-4.19.06-0.0.20115.noarch.rpm
- apigee-cassandra-2.1.22-0.0.2515.noarch.rpm

You can check the RPM versions you currently have installed, to see if they
need to be updated, by entering:

```
apigee-all version
```

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

1. On all Edge nodes:

   1. Clean the Yum repos:

      ```
      sudo yum clean all
      ```
   2. Download the latest Edge 4.19.06 `bootstrap_4.19.06.sh` file to `/tmp/bootstrap_4.19.06.sh`:

      ```
      curl https://software.apigee.com/bootstrap_4.19.06.sh -o /tmp/bootstrap_4.19.06.sh
      ```
   3. Install the Edge 4.19.06 `apigee-service` utility and dependencies:

      ```
      sudo bash /tmp/bootstrap_4.19.06.sh apigeeuser=uName apigeepassword=pWord
      ```

      where <var translate="no">uName:pWord</var> are the username and password you received from Apigee.
      If you omit <var translate="no">pWord</var>, 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. Use the `source` command to execute the `apigee-service.sh` script:

      ```
      source /etc/profile.d/apigee-service.sh
      ```
2. On all Edge nodes, execute the `update.sh` script for the `edge` process. To do this, execute the following command on each node:

   ```
   /opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
   ```
3. Update all Cassandra nodes:

   ```
   /opt/apigee/apigee-setup/bin/update.sh -c cs -f configFile
   ```

   where <var translate="no">configFile</var> specifies the configuration file that you used to install
   Apigee Edge for Private Cloud. For example, `/opt/silent.conf`.

## Changes to
[supported software](https://docs.apigee.com/release/supported-software#apigeeedgeforprivatecloudsupportedversions)

There are no changes to supported software in this release.

## Deprecations and retirements

There are no new deprecations or retirements in this release.

## New Features

This release introduces the following new features:

- Added support for [JMX with SSL for Cassandra authentication](https://docs.apigee.com/private-cloud/v4.19.06/how-monitor#enable-jmx-with-ssl-for-cassandra), which provides additional security and encryption.

## Bugs fixed

The following table lists the bugs fixed in this release:

| Issue ID | Description |
|---|---|
| 141670890 | **Instructions for setting system level TLS settings were not working.** A bug that was preventing TLS settings from taking effect on message processors has been fixed. |
| 123311920 | **`update.sh` script was failing after enabling TLS on management server.** The update script now works correctly even if TLS is enabled on management server. |

## Security issues fixed

There are no security issues in this release.

## Known issues


For a list of known issues with Edge Private Cloud, see
[Known issues with Edge Private Cloud](https://docs.apigee.com/release/known-issues#private-cloud).