Este conteúdo não está disponível no idioma selecionado.
Chapter 3. Post-installation tasks
This section describes how to complete the post-installation tasks.
3.1. Registering your system Copiar o linkLink copiado para a área de transferência!
This section explains how to register your RHEL server to Red Hat Satellite.
Different steps apply if your system is registered to the Red Hat Customer Portal or your Cloud provider.
Prerequisites
- Your system has been installed and rebooted as explained in the previous chapter.
- You must have a valid Red Hat Enterprise Linux for SAP Solutions subscription so your server has access to required packages via a Red Hat Satellite server, the Red Hat Customer Portal, or your Cloud provider.
You must have the following information provided to you by your Satellite administrator:
- An activation key.
- A string representing the name of the organization.
- A URL for the Katello client package.
- You have system administrator access.
Procedure
Download the Katello client rpm package:
# wget https://sat.int.example.com/pub/katello-ca-consumer-latest.noarch.rpmReplace the URL with the URL provided by your Satellite administrator.
Install the Katello client rpm package:
# dnf install -y katello-ca-consumer-latest.noarch.rpmReplace the package name with the name of the package you downloaded.
Register your system:
# subscription-manager register --org="your-organization-name" \ --activationkey="your-activation-key"Replace
your-organization-namewith the string representing the name of the organization and replaceyour-activation-keywith the activation key. Both are provided by your Satellite administrator.
3.2. Applying the RHEL release lock Copiar o linkLink copiado para a área de transferência!
For RHEL systems running the SAP HANA database (after SAP validates SAP HANA for the RHEL minor release), it is essential that you set the RHEL release lock so that the system remains on the correct RHEL minor release even when doing package updates. Otherwise, the system might be updated to a RHEL release that SAP does not support. For RHEL systems not running the SAP HANA database, any RHEL 10 minor release can be used for running the SAP ABAP Platform (after SAP validates it), so applying the RHEL release lock is not necessary in this case.
Prerequisites
- You have system administrator access.
Procedure
Clear the dnf cache:
# rm -rf /var/cache/dnfSet the release lock:
# subscription-manager release --set=10.xReplace 10.x with the supported minor release of RHEL 10 (for example 10.0).
3.3. Enabling required repositories Copiar o linkLink copiado para a área de transferência!
You need to enable certain RHEL repositories to have access to packages required for the SAP HANA installation. For more information on which repositories to enable, see RHEL for SAP Subscriptions and Repositories.
Prerequisites
- You have system administrator access.
Procedure
Disable all repositories and enable the required ones.
- Enable the e4s repos for systems running the SAP HANA database, after ensuring that the RHEL release lock is set properly (example for RHEL 10.0):
# subscription-manager release Release: 10.0 # subscription-manager repos \ --disable=\* \ --enable="rhel-10-for-$(uname -m)-baseos-e4s-rpms" \ --enable="rhel-10-for-$(uname -m)-appstream-e4s-rpms" \ --enable="rhel-10-for-$(uname -m)-sap-solutions-e4s-rpms" \ --enable="rhel-10-for-$(uname -m)-sap-netweaver-e4s-rpms"
-
If you intend to use the system for the SAP HANA database only, you do not have to enable
sap-netweaver-e4s-rpmsrepository. - For systems running the SAP ABAP Platform only, if you do not want to restrict your system to a specific RHEL minor release when updating packages, enable the normal repos. In this case, verify that no RHEL release lock is set.