[KEYCLOAK-6962] Added ways to (minor) upgrade rpm distribution

upgrading/topics/install_new_version.adoc

@@ -24,6 +24,42 @@ Files in the bin directory should not be overwritten by the files from previous
 . Copy any custom modules that have been added to the modules directory.
 . Run the applicable upgrade script below.
 
+ifeval::[{project_product}==true]
+To upgrade {project_name} server RPM distribution, complete the following steps:
+
+. Prior to applying the upgrade, handle any open transactions and delete the /var/opt/rh/rh-sso7/lib/keycloak/standalone/data/tx-object-store/ transaction directory.
+. Make sure you have subscribed to proper repositories containing JBOSS EAP and {project_name}.
+
+ subscription-manager repos --enable=jb-eap-7.1-for-rhel-7-server-rpms
+ subscription-manager repos --enable=rh-sso-7.2-for-rhel-7-server-rpms
++
+[NOTE]
+====
+To disable older product repositories for both JBOSS EAP and {project_name} use:
+
+ subscription-manager repos --disable=<OLDER_PRODUCT_REPO>
+
+To check the repositories use:
+
+ yum repolist
+====
+. The RPM upgrade process will not replace any of your modified configuration files, and will instead create .rpmnew files for the default configuration of the new {project_name} version.
++
+To activate any new features in the new release, such as new subsystems, you must manually merge each .rpmnew file into your existing configuration files
++
+. Copy any custom modules that have been added to the modules directory.
+. Run the applicable upgrade script as described below.
++
+[NOTE]
+====
+{project_name} RPM server distribution is using
+
+`{project_dirref}=/opt/rh/rh-sso7/root/usr/share/keycloak`
+
+Use it when calling migration scripts below.
+====
+endif::[]
+
 === Running the Standalone Mode Upgrade Script
 To run the upgrade script for standalone mode, complete the following steps: