Install 4.54.00.x patch updates

This page lists the changed RPM packages and update procedures for Apigee Edge for Private Cloud 4.54.00.x patch releases. If you are updating from a version earlier than the previous patch release, see Applying multiple patch versions.

Standing prerequisite steps

Before running the component-specific update steps for a patch release, run the following steps on each Edge for Private Cloud node that hosts a component updated by the patch release:

Check the currently installed component versions:

/opt/apigee/apigee-service/bin/apigee-all version

If apigee-monit is running on the node, stop monitoring and stop the service so that it doesn't restart components during the update:

/opt/apigee/apigee-service/bin/apigee-service apigee-monit unmonitor -c all
/opt/apigee/apigee-service/bin/apigee-service apigee-monit stop

Clean the package manager cache:
```
sudo dnf clean all
```

Download the latest 4.54.00 bootstrap script to /tmp/bootstrap_4.54.00.sh:

curl https://software.apigee.com/bootstrap_4.54.00.sh -o /tmp/bootstrap_4.54.00.sh

Install the 4.54.00 apigee-service utility and repository configuration:
```
sudo bash /tmp/bootstrap_4.54.00.sh apigeeuser=uName apigeepassword=pWord
```
Replace uName and pWord with the credentials you received from Apigee. If you omit pWord, the script prompts you to enter it.
Load the updated environment profile:
```
source /etc/profile.d/apigee-service.sh
```

Update the apigee-setup utility:

/opt/apigee/apigee-service/bin/apigee-service apigee-setup update

4.54.00.01

Installing Edge for Private Cloud 4.54.00.01 updates the following RPM packages:

edge-gateway-4.54.00-0.0.60414.noarch.rpm
edge-management-server-4.54.00-0.0.60414.noarch.rpm
edge-message-processor-4.54.00-0.0.60414.noarch.rpm
edge-postgres-server-4.54.00-0.0.60414.noarch.rpm
edge-qpid-server-4.54.00-0.0.60414.noarch.rpm
edge-router-4.54.00-0.0.60414.noarch.rpm
edge-uapim-4.54.00-0.0.60414.noarch.rpm
edge-uapim-connector-4.54.00-0.0.60414.noarch.rpm
edge-management-ui-4.54.00-0.0.20091.noarch.rpm
edge-management-ui-static-4.54.00-0.0.20107.noarch.rpm
apigee-openldap-2.6.10-0.0.2559.noarch.rpm
apigee-validate-4.54.00-0.0.639.noarch.rpm
apigee-setup-4.54.00-0.0.1166.noarch.rpm
apigee-provision-4.54.00-0.0.634.noarch.rpm
apigee-nginx-1.30.0-1.0.41.el8.x86_64.rpm
apigee-nginx-1.30.0-1.0.41.el9.x86_64.rpm
apigee-mtls-4.54.00-0.0.20265.noarch.rpm
apigee-mtls-consul-4.54.00-0.0.20175.noarch.rpm
apigee-monit-5.33-0.0.627.noarch.rpm

Component update steps for 4.54.00.01

After you complete the standing prerequisite steps, update the components in your Edge for Private Cloud deployment:

If apigee-mtls is installed, update apigee-mtls and apigee-mtls-consul on all mesh nodes:
Unlike the rolling update in Step 2, updating apigee-mtls requires stopping all Edge for Private Cloud components on every mesh node at the same time, which causes downtime until the mesh and components are restarted in Steps 1b and 1c.
1. On each node in the mTLS mesh, stop all Edge for Private Cloud components, uninstall the existing apigee-mtls package (which also uninstalls apigee-mtls-consul), and install and configure the updated package (which installs the updated apigee-mtls-consul package as a dependency; see Upgrade Apigee mTLS):
```
/opt/apigee/apigee-service/bin/apigee-all stop
/opt/apigee/apigee-service/bin/apigee-service apigee-mtls uninstall
/opt/apigee/apigee-service/bin/apigee-service apigee-mtls install
/opt/apigee/apigee-service/bin/apigee-service apigee-mtls setup -f configFile
```
  If you use a custom mTLS certificate, re-integrate your SHA-256-signed certificate on each node as described in Step 5: Integrate the custom certificate.
2. After apigee-mtls setup (and custom certificate re-integration, if applicable) completes on all mesh nodes, start apigee-mtls on each node:
```
/opt/apigee/apigee-service/bin/apigee-service apigee-mtls start
```
3. Verify that apigee-mtls is running on every node, then start the remaining Edge for Private Cloud components in the standard startup order:
```
/opt/apigee/apigee-service/bin/apigee-service apigee-mtls status
```
Update the Edge runtime, OpenLDAP, and New Edge UI components in rolling order across your topology:
If you run a 1-node all-in-one (AIO) topology, update apigee-provision and apigee-validate (if installed) first, and then run /opt/apigee/apigee-setup/bin/update.sh -c all -f configFile. For multi-node topologies, update nodes in the following sequence:
1. On each Router and Message Processor node (one node at a time across data centers), update edge-router, edge-message-processor, edge-gateway, and apigee-nginx:
```
/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
```
2. On each Management Server node (one node at a time across data centers), update edge-management-server and edge-gateway (and apigee-provision and apigee-validate, if installed):
```
/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
/opt/apigee/apigee-service/bin/apigee-service apigee-provision update
/opt/apigee/apigee-service/bin/apigee-service apigee-validate update
```
3. On each OpenLDAP node, update apigee-openldap (including the integrated OIDC identity broker):
```
/opt/apigee/apigee-setup/bin/update.sh -c ldap -f configFile
```
4. On each New Edge UI node, update edge-management-ui and edge-management-ui-static:
```
/opt/apigee/apigee-setup/bin/update.sh -c ue -f configFile
```
5. On each Qpid Server and Postgres Server analytics node (one node at a time across data centers), update edge-qpid-server, edge-postgres-server, and edge-gateway:
```
/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
```

If the API Hub for Private Cloud connector is installed, on its dedicated connector node, update, reconfigure, and restart edge-uapim-connector (which also updates edge-uapim):

/opt/apigee/apigee-service/bin/apigee-service edge-uapim-connector update
/opt/apigee/apigee-service/bin/apigee-service edge-uapim-connector configure
/opt/apigee/apigee-service/bin/apigee-service edge-uapim-connector restart
/opt/apigee/apigee-service/bin/apigee-service edge-uapim-connector wait_for_ready

If apigee-monit is installed on a node, update, reconfigure, and start it:

/opt/apigee/apigee-service/bin/apigee-service apigee-monit update
/opt/apigee/apigee-service/bin/apigee-service apigee-monit configure
/opt/apigee/apigee-service/bin/apigee-service apigee-monit start
/opt/apigee/apigee-service/bin/apigee-service apigee-monit wait_for_ready

Verify the update:
1. On every node, confirm that all services are running and updated to their 4.54.00.01 versions:
```
/opt/apigee/apigee-service/bin/apigee-all status
/opt/apigee/apigee-service/bin/apigee-all version
```
2. On the Management Server node, run the apigee-validate utility to verify runtime API proxy traffic, as described in Test the install.

Applying multiple patch versions

This section explains how to apply multiple patch versions when updating from a version of Edge for Private Cloud earlier than the previous patch release.

Each patch release updates specific components of Edge for Private Cloud, such as edge-management-server. To apply multiple patch versions, update each component included in any patch release later than your currently installed version. Check the per-patch RPM lists on this page (starting at 4.54.00.01) to identify every component that changed after your installed version.