Upgrading and extending SCC parameters (part 2) (#3504)

* Upgrading and extending SCC parameters (part 2).

* Replacing SCC with an actual parameter.

modules/administration/pages/disconnected-setup.adoc

@@ -23,7 +23,7 @@ For more information on RMT, see {sles-base-os-documentation}/book-rmt.html.
 
 
 [[disconnected-setup-sync-scc]]
-== Synchronize Channels and Repositories from SCC
+== Synchronize Channels and Repositories from {scc}
 
 === Synchronize RMT
 
@@ -50,7 +50,7 @@ For more information on setting up RMT, see {sles-base-os-documentation}/book-rm
 
 
 
-.Procedure: Synchronizing RMT with SCC
+.Procedure: Synchronizing RMT with {scc}
 . On the RMT instance, list all available products and repositories for your organization:
 +
 ----
@@ -102,7 +102,7 @@ For more details on installing and configuring SMT, see https://documentation.su
 
 
 
-.Procedure: Synchronizing SMT with SCC
+.Procedure: Synchronizing SMT with {scc}
 . On the SMT instance, create a database replacement file:
 +
 ----
@@ -209,7 +209,7 @@ mgrctl exec -ti -- mgr-sync add channel channel-label
 [NOTE]
 ====
 Be aware that if [literal]``server.susemanager.fromdir`` is set, {productname} will not be able to check if {scclongform} credentials are valid or not.
-Instead, a warning sign will be displayed and no SCC online check will be performed.
+Instead, a warning sign will be displayed and no {scc} online check will be performed.
 ====
 
 An alternative to disconnected setup may be to copy content between servers using Inter-Server Synchronization (ISS).

modules/administration/pages/mgr-sync.adoc

@@ -24,7 +24,7 @@ mgr-sync [-h] [--version] [-v] [-s] [-d {1,2,3}] {list,add,refresh,delete}
 | list | List channels, organization credentials, or products | ``mgr-sync list channels``
 | add | Add channels, organization credentials, or products | ``mgr-sync add channel <channel_name>``
 | refresh | Refresh the local copy of products, channels, and subscriptions | ``mgr-sync refresh``
-| delete | Delete existing SCC organization credentials from the local system | ``mgr-sync delete credentials``
+| delete | Delete existing {scc} organization credentials from the local system | ``mgr-sync delete credentials``
 | sync | Synchronize specified channel or ask for it when left blank| ``mgr-sync sync channel <channel_name>``
 |===
 

modules/administration/pages/ptfs.adoc

@@ -32,7 +32,7 @@ Other versions or operating systems do not have this feature and the pages are n
 .Procedure: Enabling and synchronizing PTF repositories using the command line
 
 . On the console enter [command]``mgr-sync refresh``.
-. Enter [command]``mgr-sync list channel`` and look for channels starting with your SCC account name and `ptfs` in its name.
+. Enter [command]``mgr-sync list channel`` and look for channels starting with your {scc} account name and `ptfs` in its name.
   For example, `a123456-sles-15.3-ptfs-x86_64`.
 . Enable the PTF channel with [command]``mgr-sync add channel <label>``.
 
@@ -49,7 +49,7 @@ In {productname} {webui} every system with PTFs available for installation has a
 . In the {productname} {webui}, navigate to menu:Admin[Setup Wizard > Products] and look for the product you want to enable the PTF repository for.
 . Click btn:[Show product's channels] next to the products sync status.
 . You should see a popup listing mandatory and optional channels for the product.
-. In the optional channels list look for channels starting with your SCC account name and `ptfs` in its name.
+. In the optional channels list look for channels starting with your {scc} account name and `ptfs` in its name.
   For example `a123456-sles-15.3-ptfs-x86_64`.
 . Select the channel using the checkbox next to its name and click btn:[Confirm] to schedule the sync.
 

modules/administration/pages/subscription-matching.adoc

@@ -1,8 +1,8 @@
 [[subscription-matching]]
 = Subscription Matching
 
-Your {suse} products require subscriptions, which are managed by the {scclongform} (SCC).
-{productname} runs a nightly report checking the subscription status of all your registered clients against your SCC account.
+Your {suse} products require subscriptions, which are managed by the {scclongform} ({scc}).
+{productname} runs a nightly report checking the subscription status of all your registered clients against your {scc} account.
 The report gives you information about which clients consume which subscriptions, how many subscriptions you have remaining and available to use, and which clients do not have a current subscription.
 
 Navigate to menu:Audit[Subscription Matching] to see the report.

modules/administration/pages/task-schedules.adoc

@@ -90,7 +90,7 @@ server.susemanager.forward_registration = 0
 
 [WARNING]
 ====
-Disabling data synchronizing with SCC will lead to reduced visibility of your managed clients between RMT, SMT, {productname} and SCC-directly registered clients.
+Disabling data synchronizing with {scc} will lead to reduced visibility of your managed clients between RMT, SMT, {productname} and {scc}-directly registered clients.
 
 By synchronizing data, you ensure a uniform view of all registered clients.
 

modules/administration/pages/troubleshooting/tshoot-firewalls.adoc

@@ -19,13 +19,13 @@ If more detailed instructions are required, put them in a "Resolving" procedure:
 . Last step
 
 
-Cause: User firewall is set to block outgoing traffic by dropping the packet request. During sync with SCC, SUMA waits for an answer on each URL until it times out, eventually causing the entire refresh of the product list to timeout. Applies only to third party (non-SUSE) products, as sync with SCC needs to access locations other than SCC to verify if the if the download location is valid.
+Cause: User firewall is set to block outgoing traffic by dropping the packet request. During sync with {scc}, SUMA waits for an answer on each URL until it times out, eventually causing the entire refresh of the product list to timeout. Applies only to third party (non-SUSE) products, as sync with {scc} needs to access locations other than {scc} to verify if the if the download location is valid.
 
-Consequence: The sync to SCC fails, and the third party products are not shown in the product list.
+Consequence: The sync to {scc} fails, and the third party products are not shown in the product list.
 
 Fix: Configure the firewall to reject requests from SUMA instead of drop (preferred), or configure a firewall on the server (if no ability to change firewall settings)
 
-Result: Sync to SCC is either able to reach the URLs required, or rejects the request so that the request fails rather than times out.
+Result: Sync to {scc} is either able to reach the URLs required, or rejects the request so that the request fails rather than times out.
 ////
 
 If you are using a firewall that blocks outgoing traffic, it can either ``REJECT`` or ``DROP`` network requests.

modules/client-configuration/pages/client-upgrades.adoc

@@ -3,7 +3,7 @@
 
 Clients use the versioning system of their underlying operating system, and require regular upgrades.
 
-For SCC registered clients using {suse} operating systems, you can perform upgrades within the {productname} {webui}.
+For {scc} registered clients using {suse} operating systems, you can perform upgrades within the {productname} {webui}.
 For supported {sle}{nbsp}15 upgrade paths, see {sles-base-os-documentation}/cha-upgrade-paths.html
 
 To upgrade clients running SLE{nbsp}12 to SLE{nbsp}15, the upgrade is automated, but you need to do some preparation steps before you begin.

modules/installation-and-upgrade/pages/connect-payg.adoc

@@ -19,7 +19,7 @@ Before using the {payg} feature ensure:
 
 * A basic {scclongform} account is required. Enter your valid {scclongform} credentials in menu:Admin[Setup Wizard > Organization Credentials]. This account is required for accessing the {productname} client tools for boostrapping regardless of {payg} instances.
 
-* If you bootstrap the {payg} instance to SUSE Manager, SUSE Manager will disable its {payg} repositories then add repositories from where it mirrored the data from the RMT server. The final result will be {payg} instances acquiring the same repositories from the RMT servers but through the SUSE Manager server itself. Of course repositories can still be setup primarily from SCC.
+* If you bootstrap the {payg} instance to SUSE Manager, SUSE Manager will disable its {payg} repositories then add repositories from where it mirrored the data from the RMT server. The final result will be {payg} instances acquiring the same repositories from the RMT servers but through the SUSE Manager server itself. Of course repositories can still be setup primarily from {scc}.
 
 
 
@@ -93,7 +93,7 @@ To monitor the syncing progress of each channel, check the log files in the [pat
 ====
 If a product is provided by both the {payg} instance and one of the {scclongform} subscriptions, it will appear only once in the products list.
 
-When the channels belonging to that product are synced, the data might still come from the SCC subscription, and not from the Pay-As-You-Go instance.
+When the channels belonging to that product are synced, the data might still come from the {scc} subscription, and not from the Pay-As-You-Go instance.
 ====
 
 

modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc

@@ -296,7 +296,7 @@ Proceed to the next section to add your organization credentials for syncing wit
 
 == Connect {productname} {productnumber} to {scclongform}
 
-This section covers synchronizing with SCC from the {webui} and adding your first client channel.
+This section covers synchronizing with {scc} from the {webui} and adding your first client channel.
 
 [[proc-admin-organization-credentials]]
 .Procedure: Entering Organization Credentials

modules/installation-and-upgrade/pages/general-requirements.adoc

@@ -25,15 +25,15 @@ Create an account with {scclongform} prior to deployment of {productname} {produ
 [[creating.scc.account.mgr]]
 .Procedure: Obtain Your Organization Credentials
 . Navigate to https://scc.suse.com/login in your web browser.
-. Log in to your SCC account, or follow the prompts to create a new account.
+. Log in to your {scc} account, or follow the prompts to create a new account.
 . If you have not yet done so, click btn:[Connect to an Organization] and type or search for your organization.
 . Click btn:[Manage my Organizations] and select your organization from the list by clicking the organization name.
 . Click the btn:[Users] tab, and then select the btn:[Organization Credentials] sub-tab.
 . Record your login information for use during {productname} setup.
 
 Depending on your organization's setup, you might also need to activate your subscription, using the btn:[Activate Subscriptions] menu from the left navigation bar.
 
-For more information about using SCC, see https://scc.suse.com/docs/help.
+For more information about using {scc}, see https://scc.suse.com/docs/help.
 
 
 

modules/installation-and-upgrade/pages/install-proxy.adoc

@@ -46,7 +46,7 @@ Before you begin, you will need to have created an account with {scclongform}, a
 
 . Click btn:[Local install media (ISO image or CDROM)].
 
-. In the [guimenu]``Create a new virtual machine`` dialog, click btn:[Browse] and locate the full SLES image you downloaded from your SCC account.
+. In the [guimenu]``Create a new virtual machine`` dialog, click btn:[Browse] and locate the full SLES image you downloaded from your {scc} account.
 
 . Configure your machine with at least 2 GB RAM and a minimum of 2 CPUs.
 
@@ -89,7 +89,7 @@ rpm -e --nodeps sles-release
 ----
 +
 
-. Register {productname} Proxy with SCC (for example, replace `<productversion>` with `{productnumber}` and `<architecture>` with `x86_64`):
+. Register {productname} Proxy with {scc} (for example, replace `<productversion>` with `{productnumber}` and `<architecture>` with `x86_64`):
 +
 
 ----

modules/installation-and-upgrade/pages/uyuni-server-setup.adoc

@@ -107,18 +107,18 @@ When you have completed the {productname} {webui} setup, you are taken to the me
 
 == Optional: Synchronizing Products from {scclongform}
 
-{scclongform} (SCC) maintains a collection of repositories which contain packages, software and updates for all supported enterprise client systems.
+{scclongform} ({scc}) maintains a collection of repositories which contain packages, software and updates for all supported enterprise client systems.
 These repositories are organized into channels each of which provide software specific to a distribution, release, and architecture.
-After synchronizing with SCC, clients can receive updates, be organized into groups, and assigned to specific product software channels.
+After synchronizing with {scc}, clients can receive updates, be organized into groups, and assigned to specific product software channels.
 
-This section covers synchronizing with SCC from the {webui} and adding your first client channel.
+This section covers synchronizing with {scc} from the {webui} and adding your first client channel.
 
 [NOTE]
 ====
 For Uyuni, synchronizing products from {scclongform} is optional.
 ====
 
-Before you can synchronize software repositories with SCC, you will need to enter organization credentials in {productname}.
+Before you can synchronize software repositories with {scc}, you will need to enter organization credentials in {productname}.
 The organization credentials give you access to the {suse} product downloads.
 You will find your organization credentials in https://scc.suse.com/organizations.
 

modules/quickstart/pages/container-deployment/suma/quickstart-deploy-suma-server.adoc

@@ -161,7 +161,7 @@ In this guide you learned how to deploy {productname} {productnumber} Server as
 
 == Synchronize with SUSE Customer Center 
 
-This section covers synchronizing with SCC from the {webui} and adding your first client channel.
+This section covers synchronizing with {scc} from the {webui} and adding your first client channel.
 
 [[proc-admin-organization-credentials]]
 .Procedure: Entering Organization Credentials

modules/quickstart/pages/container-deployment/uyuni/quickstart-deploy-uyuni-server.adoc

@@ -165,18 +165,18 @@ Administrator's email: [email protected]
 
 == Optional: Synchronizing Products from {scclongform}
 
-{scclongform} (SCC) maintains a collection of repositories which contain packages, software and updates for all supported enterprise client systems.
+{scclongform} ({scc}) maintains a collection of repositories which contain packages, software and updates for all supported enterprise client systems.
 These repositories are organized into channels each of which provide software specific to a distribution, release, and architecture.
-After synchronizing with SCC, clients can receive updates, be organized into groups, and assigned to specific product software channels.
+After synchronizing with {scc}, clients can receive updates, be organized into groups, and assigned to specific product software channels.
 
-This section covers synchronizing with SCC from the {webui} and adding your first client channel.
+This section covers synchronizing with {scc} from the {webui} and adding your first client channel.
 
 [NOTE]
 ====
 For Uyuni, synchronizing products from {scclongform} is optional.
 ====
 
-Before you can synchronize software repositories with SCC, you will need to enter organization credentials in {productname}.
+Before you can synchronize software repositories with {scc}, you will need to enter organization credentials in {productname}.
 The organization credentials give you access to the {suse} product downloads.
 You will find your organization credentials in https://scc.suse.com/organizations.
 

modules/quickstart/pages/legacy-installation/quickstart-install-uyuni-server.adoc

@@ -126,18 +126,18 @@ When you have completed the {productname} {webui} setup, you are taken to the me
 
 == Optional: Synchronizing Products from {scclongform}
 
-{scclongform} (SCC) maintains a collection of repositories which contain packages, software and updates for all supported enterprise client systems.
+{scclongform} ({scc}) maintains a collection of repositories which contain packages, software and updates for all supported enterprise client systems.
 These repositories are organized into channels each of which provide software specific to a distribution, release, and architecture.
-After synchronizing with SCC, clients can receive updates, be organized into groups, and assigned to specific product software channels.
+After synchronizing with {scc}, clients can receive updates, be organized into groups, and assigned to specific product software channels.
 
-This section covers synchronizing with SCC from the {webui} and adding your first client channel.
+This section covers synchronizing with {scc} from the {webui} and adding your first client channel.
 
 [NOTE]
 ====
 For Uyuni, synchronizing products from {scclongform} is optional.
 ====
 
-Before you can synchronize software repositories with SCC, you will need to enter organization credentials in {productname}.
+Before you can synchronize software repositories with {scc}, you will need to enter organization credentials in {productname}.
 The organization credentials give you access to the {suse} product downloads.
 You will find your organization credentials in https://scc.suse.com/organizations.
 

modules/reference/pages/cli-sync.adoc

@@ -12,7 +12,7 @@ For all other clients, use ``spacewalk-repo-sync``.
 
 
 
-== Synchronize SCC Repositories With mgr-sync
+== Synchronize {scc} Repositories With mgr-sync
 
 //This content is the same as the content at modules/administration/pages/mgr-sync.adoc Perhaps we should snippet it? --LKB 2020-10-09
 
@@ -37,7 +37,7 @@ mgr-sync [-h] [--version] [-v] [-s] [-d {1,2,3}] {list,add,refresh,delete}
 | list | List channels, organization credentials, or products | ``mgr-sync list channels``
 | add | Add channels, organization credentials, or products | ``mgr-sync add channel <channel_name>``
 | refresh | Refresh the local copy of products, channels, and subscriptions | ``mgr-sync refresh``
-| delete | Delete existing SCC organization credentials from the local system | ``mgr-sync delete credentials``
+| delete | Delete existing {scc} organization credentials from the local system | ``mgr-sync delete credentials``
 | sync | Synchronize specified channel or ask for it when left blank| ``mgr-sync sync channel <channel_name>``
 |===
 

modules/specialized-guides/pages/public-cloud-guide/faq/faq-billing-products.adoc

@@ -15,7 +15,7 @@ link:https://documentation.suse.com/suma/4.3/en/suse-manager/client-configuratio
 
 It is simple to open a support case with SUSE for {productname} {payg}.
 
-Create a ‘supportconfig’ via {productname} {payg} instance CLI and upload the output to the SUSE Customer Center (SCC) at the following link:
+Create a ‘supportconfig’ via {productname} {payg} instance CLI and upload the output to the SUSE Customer Center ({scc}) at the following link:
 
 https://scc.suse.com/cloudsupport
 
@@ -47,13 +47,13 @@ Billing will occur from the downstream {productname} {payg} Server instance, whe
 
 == Can I manage {byoslongform} - {byos} SLES instances in the cloud with {productname} {payg}?
 
-To manage {byos} instances, SUSE Customer Center (SCC) credentials with entitlement to valid SLES or SLES for SAP subscriptions will be required. These credentials should be added to the {productname} configuration to enable this functionality.
+To manage {byos} instances, SUSE Customer Center ({scc}) credentials with entitlement to valid SLES or SLES for SAP subscriptions will be required. These credentials should be added to the {productname} configuration to enable this functionality.
 
 == I have a hybrid setup; can I manage instances (workloads) outside of the cloud?
 
 Yes, it is possible to manage instances, in the cloud, on premises or both.
 
-To enable management of SUSE workloads in an on-premises data center, SCC credentials with entitlement to valid SLES or SLES for SAP subscriptions will be required.
+To enable management of SUSE workloads in an on-premises data center, {scc} credentials with entitlement to valid SLES or SLES for SAP subscriptions will be required.
 
 These credentials should be added to the {productname} configuration to enable this functionality.
 

modules/specialized-guides/pages/public-cloud-guide/payg/aws/payg-aws-connections-and-bootstrapping.adoc

@@ -7,14 +7,14 @@ Connecting and registering {payg} images is supported and can be done without ad
 
 
 {byos} ({byoslongform}) Images::
-Registering {byos} images requires SCC ({scclongform}) credentials beforehand. 
-If a user attempts to onboard a {byos} image without providing SCC credentials, the operation will fail, as these credentials are required to verify your subscription.
+Registering {byos} images requires {scc} ({scclongform}) credentials beforehand. 
+If a user attempts to onboard a {byos} image without providing {scc} credentials, the operation will fail, as these credentials are required to verify your subscription.
 
 [IMPORTANT]
 ====
 * Always verify the type of image ({payg} or {byos}) prior to initiating the registration process with {productname} to ensure a smooth and error-free connection.
 
-* If you have SCC credentials ensure your SCC credentials are valid and have the necessary permissions for utilizing {byos} images.
+* If you have {scc} credentials ensure your {scc} credentials are valid and have the necessary permissions for utilizing {byos} images.
 
 **Do not** register {payg} instances with the {scclongform}.
 Only {byos} instances should be registered against the {scclongform}.