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

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

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

## 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. Download the latest Edge 4.18.05 `bootstrap_4.18.05.sh` file to `/tmp/bootstrap_4.18.05.sh`:

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

      ```
      sudo bash /tmp/bootstrap_4.18.05.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. Update all Message Processor, Router, and Management Server nodes. On each node, execute the following command:

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

   Where <var translate="no">configFile</var> specifies the configuration file that you used to install
   Edge.

## Deprecations and retirements

### Removal of jmxri and jmxtools Java libraries

The following Java libraries were removed from Edge:

- jmxri
- jmxtools

Apigee Edge no longer uses these libraries.

If you have a [JavaCallout policy](https://docs.apigee.com/api-platform/reference/policies/java-callout-policy.md.txt) that uses one of these libraries, Apigee recommends
that you do one of the following:

- Download your own version of the JAR file and add them as [API proxy resources](https://docs.apigee.com/api-platform/develop/resource-files.md.txt)

  **OR**
- Refactor your Java code to not use these libraries

Note that access to these libraries has been neither documented nor supported, so this
internal refactoring does not fall under the [Apigee deprecation policy](https://docs.apigee.com/release/deprecation.md.txt). (APIRT-3564, APIRT-3550)

## Bugs fixed

The following table lists the bugs fixed in this release:

| Issue ID | Description | Build Number^\*^ |
|---|---|---|
| 117912012 | **Shared Flow deployment issues** | `edge-gateway-4.18.05-0.0.20004-noarch.rpm` |

### ^\*^About the build numbers

> [!NOTE]
> The **Build Number** column in the table specifies the earliest version of the component that contains the fix. Use that build number to determine if you already have the fix installed, or if you need to perform an update.
>
> To find out the build number of a currently installed component, use the
> `apigee-service` utility with the following syntax:
>
> ```
> /opt/apigee/apigee-service/bin/apigee-service component version
> ```
>
> Where <var translate="no">component</var> is the name of the component without the build number extension.
> For example:
>
> ```
> /opt/apigee/apigee-service/bin/apigee-service apigee-setup version
> ```
>
> You can get the build number of *all components* with the `apigee-all`
> utility:
>
> ```
> /opt/apigee/apigee-service/bin/apigee-all version
> ```