Chapter 4. Upgrading an SAP NetWeaver system

Follow the Upgrading from RHEL 8 to RHEL 9 guide to upgrade your SAP NetWeaver non-cloud or BYOS cloud RHEL 8.* system to RHEL 9.*.

At the end of chapter Chapter 6. Verifying the post-upgrade state, verify that only the normal, eus, or e4s repositories are enabled and the RHEL release lock is set to 9.X, where X is a desired minor release.

The upgrade of SAP NetWeaver or other SAP application systems hosted on cloud provider PAYG instances is very similar to the upgrade of SAP HANA systems hosted on cloud provider PAYG instances. All non-HANA specific steps listed earlier in the SAP HANA systems upgrade on cloud provider PAYG instances procedure should be applied to complete the upgrade of SAP NetWeaver or other SAP application systems hosted on cloud provider PAYG instances.

The only difference is the repo channel for standalone SAP NetWeaver hosts on Microsoft Azure PAYG instances.

When upgrading standalone NetWeaver or other SAP applications hosts on Microsoft Azure PAYG instances which correspond to RHEL for SAP Applications SKU, use --channel eus instead of --channel e4s. In other cases, --channel e4s is always used. After the upgrade with --channel eus, the system will have the following Red Hat repositories:

# yum repolist
rhel-9-for-x86_64-appstream-eus-rhui-rpms
rhel-9-for-x86_64-baseos-eus-rhui-rpms
rhel-9-for-x86_64-sap-netweaver-eus-rhui-rpms

The repolist may contain other non-Red Hat repositories, namely custom repositories of cloud providers for RHUI configuration.

As always, run all the upgrade steps, including the preparation and pre-upgrade steps, on a test system first until you have verified that the upgrade can be performed successfully in your production environment.