vania-janet/multiturn-rag-retrieval-data huggingface dataset:
This documented configuration uses the “all-in-one”, internet-connected VUM deployment model that uses the IBM Cloud public network to provide internet access to download upgrades and patches.

Clients requiring the use of alternative internet connections must investigate the VMware vSphere Update Manager Download Service (UMDS), which is beyond the scope of this publication.

While VUM can be configured to import updates from a shared repository or import patches and extensions manually from a compressed file, these details aren't discussed in this document.

In vSphere 6.7 and later, it's no longer supported to register VUM to a VCSA during installation of the VUM server on a separate Windows system you can't deploy VUM in a VM within the vCenter Server environment.

This information is organized into the following sections:



* [VMware Update Manager overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vum-overview) - Describes the VUM process and introduces key terms that are needed to understand the operations and UI of the tool.
* Installation, Configuration, and Usage - Describes the steps that are required to get VUM working in a vCenter Server instance:



* [Initial configuration](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vum-init-config) - A one-time task to complete the following processes:



* Configure NSX networking to allow the proxy server access to the internet.
* Install and configure a proxy server to provide internet access for VUM.
* The initial setup of VUM to use the proxy server.



* [Collecting the metadata](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vum-metadata) - VUM downloads metadata about the upgrades, patches, or extensions through a predefined automatic process that you can modify. At regular configurable intervals, VUM contacts VMware, or third-party sources, to gather the most recent metadata about available upgrades, patches, or extensions.
oc patch secret --dry-run -o yaml -n default default-de-icr-io -p '{"metadata": {"namespace": "sdh", "name": "sdh-de-icr-io"}}' | oc -n sdh create -f -
2. Link the secret sdh-de-icr-io to the default service account’s pods.

oc secrets link -n sdh --for=pull default sdh-de-icr-io
3. Deploy the SAP Data Hub Observer in the sdh namespace.

Review the [Required Input Parameters](https://access.redhat.com/articles/3630111deploy-sdh-observer) to confirm the deployment instructions and the source URL are valid.

oc process -f https://raw.githubusercontent.com/redhat-sap/sap-datahub/master/sdh-observer.yaml 
BASE_IMAGE_TAG=v3.11 SDH_NAMESPACE=sdh MAKE_VSYSTEM_IPTABLES_PODS_PRIVILEGED=true NAMESPACE=sdh 
REGISTRY=de.icr.io/sdh_cr_os | oc create -f -







 Preparing IBM Cloud IBM Cloud Object Storage for SAP Vora Checkpoint 

For production environments, storage for the SAP Vora Checkpoint must be set up. Follow these instructions to set up IBM Cloud IBM Cloud Object Storage and to define the parameters that will be handed over to the installation dialog.

For test and evaluation environments, you may skip this topic and go directly to the [Manual Installation using an installation script (manual)](https://access.redhat.com/articles/3630111manual) instructions, and the instructions for [running the installation script](https://cloud.ibm.com/docs/sap?topic=sap-rhos-datahub) for the IBM Cloud specific parameters.



 Before you begin 

Review [Getting started with IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage) for general information on IBM Cloud Object Storage.





 Provisioning Object Storage
The Istio version in the managed add-on is tested by IBM Cloud and approved for the use in IBM Cloud Kubernetes Service. Additionally, the Istio add-on simplifies the maintenance of your Istio control plane so you can focus on managing your microservices. IBM Cloud keeps all your Istio components up-to-date by automatically rolling out patch updates to the most recent version of Istio that is supported by IBM Cloud Kubernetes Service. To update your Istio components to the most recent minor version of Istio that is supported by IBM Cloud Kubernetes Service, such as from Istio version 1.6 to 1.7, you can follow the steps in [Updating the minor version of the Istio add-on](https://cloud.ibm.com/docs/containers?topic=containers-istioistio_minor).

Whenever the managed Istio add-on is updated, make sure that you [update your istioctl client and the Istio sidecars for your app](https://cloud.ibm.com/docs/containers?topic=containers-istioupdate_client_sidecar) to match the Istio version of the add-on. You can check whether the versions of your istioctl client and the Istio add-on control plane match by running istioctl version.

If you need to use the latest version of Istio or customize your Istio installation, you can install the open source version of Istio by following the steps in the [Quick Start with IBM Cloud tutorial](https://istio.io/latest/docs/setup/platform-setup/ibm/). However, note that you can't run community Istio concurrently with the managed Istio add-on in your cluster.







 What comes with the Istio add-on? 

In Kubernetes clusters, you can install the generally available managed Istio add-on, which runs Istio version 1.18.0.

The Istio add-on installs the core components of Istio. For more information about any of the following control plane components, see the [Istio documentation](https://istio.io/latest/about/service-mesh/).
cp /opt/ocpinstall/auth/kubeconfig /.kube/config
oc patch configs.imageregistry.operator.openshift.io cluster --type merge --patch '{"spec":{"storage":{"emptyDir":{}}}}'

After the installation is complete, change the image-registry to a suitable location.
4. Run the following command to monitor the installation:

openshift-install --dir=. wait-for install-complete
5. Wait until you see the following message. The system provides the URL and credentials to log in to the Red Hat OpenShift Console after the installation is complete. Your URL and password is different:

INFO Install complete!
INFO To access the cluster as the system:admin user when using 'oc', run 'export KUBECONFIG=/root/go/src/github.com/openshift/installer/bin/auth/kubeconfig'
INFO Access the OpenShift web-console here: https://console-openshift-console.opc.dallas.ibm.local
INFO Login to the console with user: kubeadmin, password: my-kube-password

The password for the user that was created during installation can also be found in the auth subdirectory in the install-dir. You can log in through oc login and have access to the web console. The URL for the console is https://console-openshift-console.<cluster>.<base_domain>.
6. Run the following command from the /opt/ocpinstall directory:

watch -n5 oc get clusteroperators
7. Monitor for cluster completion. An output is provided in the following example. Replace 4.x.5 with the current Red Hat OpenShift version, for example, 4.7.5.

Every 5.0s: oc get clusteroperators

NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE
authentication 4.x.5 True False False 20m
* Terraform







 Deploying Additional Application Server (AAS) to SAP HANA and AnyDB on an existing IBM Cloud VPC with automation 

You can use Terraform scripts to create a single-tier VPC and create the AAS to HANA and AnyDB infrastructure on the VPC. The Terraform scripts use the VPC information that you provide and then call the Ansible playbook to create the SAP architecture on the specified VPC. Terraform on IBM Cloud® enables predictable and consistent provisioning of IBM Cloud Virtual Private Cloud (VPC) infrastructure resources so that you can rapidly build complex, cloud environments. IBM Cloud VPC infrastructure consists of SAP certified hardware that uses Intel Xeon CPUs and additional Intel technologies.



 What is created 

The scripts use the information that you provide for an existing VPC and deploy AAS to SAP HANA or AnyDB on different host than CI (SAP Central Instance) VSI host. For more information about this architecture, see [SAP NetWeaver 7.x on UNIX with HANA or AnyDB on IBM Cloud VPC on IBM Cloud VPC](https://cloud.ibm.com/docs/sap?topic=sap-sap-refarch-nw-sybase). You specify the information for the VPC to use in the input.auto.tfvars file.

The scripts call the Ansible Playbook to install the SAP architecture.





 Script files 

The configuration and script files are provided on GitHub. Each supported interface for the SAP solution installation has its own folder in the GitHub repository:



* [Github repository for Terraform - AAS SYB](https://github.com/IBM-Cloud/sap-aas-abap-ase-syb/tree/main/cli).
* [Github repository for Terraform – AAS HANA](https://github.com/IBM-Cloud/sap-abap-hana-aas)







 Terraform interface 

To run the Terraform scripts, you modify:



* The input.auto.tfvars file to specify the existing VPC resources for your solution. You specify the variables for the existing VPC:



* VPC name
* Security group
* Subnet
* Install SAP HANA on RHEL:



* [SAP Note 2772999 - Red Hat Enterprise Linux 8.x: Installation and Configuration](https://me.sap.com/notes/2772999)
* [SAP Note 2777782 - SAP HANA DB: Recommended OS Settings for RHEL 8](https://me.sap.com/notes/2777782)



* SAP HANA Server Installation:



* [SAP HANA Server Installation and Update Guide](https://help.sap.com/docs/SAP_HANA_PLATFORM/2c1988d620e04368aa4103bf26f17727/7eb0167eb35e4e2885415205b8383584.html)



* SAP HANA System Replication:



* [SAP HANA System Replication Guide](https://help.sap.com/docs/SAP_HANA_PLATFORM/4e9b18c116aa42fc84c7dbfd02111aba/afac7100bc6d47729ae8eae32da5fdec.html)



* Configure SAP HANA System Replication:



* [Automating SAP HANA Scale-Up System Replication by using the RHEL HA Add-On - 2. SAP HANA System Replication](https://access.redhat.com/articles/3004101sap-hana-system-replication)





* A valid RHEL for SAP Applications or RHEL for SAP Solutions subscription is required to enable the repositories that you need to install SAP HANA and the resource agents for HA configurations. The [RHEL for SAP Subscriptions and Repositories](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_for_sap_solutions/8/html/rhel_for_sap_subscriptions_and_repositories/asmb_enable_repo_rhel-for-sap-subscriptions-and-repositories-8con_hana_rhel-for-sap-subscriptions-and-repositories-8) documenation describes how to enable the required repositories.
SAP NetWeaver deployment to Bare Metal on Classic Infrastructure, using RHEL 

A Quick Study, someone who is able to learn new things quickly.

These Quick Study Tutorials provide a single sample configuration with less detailed instructions to provide an introduction for customers who prefer hands-on tasks to increase their pace of learning.

The following information provides an introduction for customers who are new to the Classic Infrastructure environment. Two sample configurations are provided to help you through the ordering process to the start of the SAP installation.

The first configuration sample is a simple, single node 32 GB RAM server with Red Hat Enterprise Linux® (RHEL). The second is an advanced two node configuration that adds a second virtual server of 192 GB RAM with Red Hat Enterprise Linux (RHEL) to the landscape.

An example of how to set up external storage, which can be applied to either sample configuration, is also provided.

The sample layouts might not be your preferred layout. The purpose of this guidance is to show two possibilities. Your installation should follow your business requirements and SAP installation documentation.



 Step 1: Provisioning a 32 GB server for a single-host environment 



1. Log in to the [IBM Cloud console](https://cloud.ibm.com) with your unique credentials.
2. Click Create > Compute > Infrastructure > Bare Metal Server.
3. Click Continue. If you can't click Continue, you don't have the correct permissions to create a server. Check with your system administrator about your permissions.
4. Leave 1 in the Quantity field.
5. Enter e2e1270 in the Hostname field. Hostname is a permanent or temporary name for your servers. Click Information for formatting specifics.
6. Enter mycloud.com in the Domain field. Domain is the identification string that defines administrative control within the internet. Click Information for formatting specifics.
7. Billing defaults to Monthly. Currently, 1-year contract and 3-year contract are not available for SAP-certified servers.
8. The data centers displayed under Location depend on product availability within a particular data center. Select NA East TOR01-Toronto.
9.
[Installation of Data Security Broker Manager](https://cloud.ibm.com/docs-content/v1/content/57ab3ec034294d8a6de510b97bec3035d4654761/security-broker/images/install_success.svg)

Installation of Data Security Broker Manager

If you get an error message saying, Workspace creation failed, refer to the Logs available in the Terraform output.







 Next Steps 

After installing Data Security Broker Manager, follow the steps listed below in the flow diagram to configure and setup the Data Security Broker Manager:

Zoom

![Encryption flow in Data Security Broker](https://cloud.ibm.com/docs-content/v1/content/57ab3ec034294d8a6de510b97bec3035d4654761/security-broker/images/sb_userflow.svg)

Figure 1. Encyrption flow in Data Security Broker Manager
For more information, see the [Approving the CSRs for your machines](https://docs.openshift.com/container-platform/4.2/machine_management/more-rhel-compute.htmlinstallation-approve-csrs_more-rhel-compute) topic in the OpenShift documentation.







 Step 4. Set the deployment values 

Override the default values by configuring the required deployment values for the OpenShift cluster that you have installed:



Table 1. Deployment values

 Parameter Description Default 

 defaultAdminUser Configure default admin user name. admin 
 defaultAdminPassword Configure default admin user password. Password must be at least 32 characters by default, and can include only number, letter, and hyphens.<br><br>Note: The password that you set during installation might be available as plain text in some pods and logs. You must change the default_admin_password after you successfully install IBM Cloud Pak for Multicloud Management. For more information about changing the password after IBM Cloud Pak for Multicloud Management installation, see [Changing the cluster administrator password](https://www.ibm.com/support/knowledgecenter/SSFC4F_1.3.0/iam/3.4.0/change_admin_passwd.html). 
 storageClass Configure storage class. ibmc-block-bronze 







 Step 5. Install the IBM Cloud Pak for Multicloud Management 



1. Ensure that you have assigned a license for the IBM Cloud Pak for Multicloud Management to the deployment.
2. Confirm that you have read and agree to the license agreements.
3. Click Install.







 Post-installation 

To interact with the IBM Cloud Pak for Multicloud Management by using the management console from your local machine, perform the following steps:



1. Run kubectl cluster-info to get the Kubernetes API server address and port. Example output:

kubectl cluster-info
kind: Subscription
metadata:
name: ibm-cloud-databases-redis-operator
spec:
name: ibm-cloud-databases-redis-operator
source: ibm-cloud-databases-redis-operator-catalog
sourceNamespace: openshift-marketplace
EOF
4. Validate that the operator was successfully created.

a) Run the following command to confirm that the subscription was applied:

oc get sub -n $OPERATOR_NS ibm-cloud-databases-redis-operator -o jsonpath='{.status.installedCSV} {"n"}'

b) Run the following command to confirm that the operator is installed:

oc get pod -n $OPERATOR_NS -l app.kubernetes.io/name=ibm-cloud-databases-redis-operator 
-o jsonpath='{.items[0].status.phase} {"n"}'











 4.0.4 



 Integrations image problem on air-gapped installations 

If your Watson Assistant 4.0.4 installation is air-gapped, your integrations image fails to properly start.

If the installation uses the IBM Entitled Registry to pull images, complete the steps in the IBM Entitled Registry section. If the installation uses a private Docker registry to pull images, complete the steps in the Private Docker registry section.



 IBM Entitled Registry 

If your installation uses the IBM Entitled Registry to pull images, complete the following steps to add an override entry to the Watson Assistant CR:



1. Get the name of your Watson Assistant by running the following command:

oc get wa
2. Edit and save the CR.

a) Run the following command to edit the CR. In the command, replace INSTANCE_NAME with the name of the Watson Assistant instance:

oc edit wa INSTANCE_NAME

b) Edit the CR by adding the following lines:

appConfigOverrides:
container_images:
integrations:
image: cp.icr.io/cp/watson-assistant/servicedesk-integration
Finally, the address of the Container Image Repository here is de.icr.io/sap_di_cr.
5. Run the SLCB installation process:

./slcb init



During installation of the SLCB, you're prompted to enter following parameters:



 Parameter Value 

 Address of the Container Image Repo: de.icr.io/sap_di_cr 
 S-User Name: Sxxxxxxxxxx 
 S-User Password: xxxxxxxx 
 New Technical User - xxxxx-#custnr#: tUser 
 Path to the "kubeconfig" file: /.kube/config 
 Expert mode: 2 
 Kubernetes namespace for the SLC Bridge: sap-slcbridge 
 name of the admin user for the SLCB Base: admin 
 password of the administrator user admin: xxxxxxx IMPORTANT: regard the password constraints below 
 NodePort: 2 
 Proxy Settings: no 
 noFeedback: 3 



Password constraints:



* It must at least consist of 8 characters
* It must contain at least one lower case, one upper case, one numerical and one special character
* The allowed special characters are . @ # $ % * + _ ? ! -



You need to note the hostname and port of the SLCB service by following commands:



* get the fully qualified hostname that you will need later

ibmcloud oc cluster get -c rv-sap-di-cl | grep -i subdomain
* get the port number >PORT> that you will need later

oc get svc -n sap-slcbridge slcbridgebase-service -o jsonpath=$'{.spec.ports[0].nodePort}n'



This URL will be required later to launch the SDI installation - [https://HOSTNAME](https://HOSTNAME):PORT/docs/index.html.







 SAP Data Intelligence installation via running the SAP Maintenance Planner
Ensure that you assigned a license for IBM Cloud Pak for Multicloud Management to the deployment.
2. Confirm that you read and agree to the license agreements.
3. Click Install.









 Next steps 

When the installation completes, you can access your IBM Cloud Pak for Multicloud Management deployment with the provided URL.



1. Log in the IBM Cloud Pak for Multicloud Management management console by using the administrator username and password which were generated when the workspace was created.



* To get the administrator username, run oc get secret platform-auth-idp-credentials -n ibm-common-services -o jsonpath='{.data.admin_username}' | base64 -d; echo ""
* To get the administrator password, run oc get secret platform-auth-idp-credentials -n ibm-common-services -o jsonpath='{.data.admin_password}' | base64 -d; echo ""



2. For more information about changing the password after IBM Cloud Pak for Multicloud Management is installed, see [Changing the cluster administrator password](https://www.ibm.com/support/knowledgecenter/SSFC4F_2.1.0/iam/3.4.0/change_admin_passwd.html).
3. Optional: After installation, you can choose to enable or disable additional operators and services such Infrastructure Management, Operations, Monitoring, and other services. For instructions, refer to [Advanced configuration](https://www.ibm.com/support/knowledgecenter/SSFC4F_2.1.0/install/config_adv.htmledit).









 Uninstall IBM Cloud Pak for Multicloud Management 

To uninstall IBM Cloud Pak for Multicloud Management, you can use the IBM Cloud Pak for Multicloud Management console or the command-line interface (CLI).



 Uninstalling IBM Cloud Pak for Multicloud Management from the IBM Cloud console 



1.
Ensure that you assigned a license for IBM Cloud Pak for Multicloud Management to the deployment.
2. Confirm that you read and agree to the license agreements.
3. Click Install.









 Next steps 

When the installation completes, you can access your IBM Cloud Pak for Multicloud Management deployment with the provided URL.



1. Log in the IBM Cloud Pak for Multicloud Management management console by using the administrator username and password which were generated when the workspace was created.



* To get the administrator username, run oc get secret platform-auth-idp-credentials -n ibm-common-services -o jsonpath='{.data.admin_username}' | base64 -d; echo ""
* To get the administrator password, run oc get secret platform-auth-idp-credentials -n ibm-common-services -o jsonpath='{.data.admin_password}' | base64 -d; echo ""



2. For more information about changing the password after IBM Cloud Pak for Multicloud Management is installed, see [Changing the cluster administrator password](https://www.ibm.com/support/knowledgecenter/SSFC4F_2.0.0/iam/3.4.0/change_admin_passwd.html).
3. Optional: After installation, you can choose to enable or disable additional operators and services such Infrastructure Management, Operations, Monitoring, and other services. For instructions, refer to [Advanced configuration](https://www.ibm.com/support/knowledgecenter/SSFC4F_2.0.0/install/config_adv.htmledit).









 Uninstall IBM Cloud Pak for Multicloud Management 

To uninstall IBM Cloud Pak for Multicloud Management, you can use the IBM Cloud Pak for Multicloud Management console or the command-line interface (CLI).



 Uninstalling IBM Cloud Pak for Multicloud Management from the IBM Cloud console 



1.
Ensure that you assigned a license for IBM Cloud Pak for Multicloud Management to the deployment.
2. Confirm that you read and agree to the license agreements.
3. Click Install.









 Next steps 

When the installation completes, you can access your IBM Cloud Pak for Multicloud Management deployment with the provided URL.



1. Log in the IBM Cloud Pak for Multicloud Management management console by using the administrator username and password which were generated when the workspace was created.



* To get the administrator username, run oc get secret platform-auth-idp-credentials -n ibm-common-services -o jsonpath='{.data.admin_username}' | base64 -d; echo ""
* To get the administrator password, run oc get secret platform-auth-idp-credentials -n ibm-common-services -o jsonpath='{.data.admin_password}' | base64 -d; echo ""



2. For more information about changing the password after IBM Cloud Pak for Multicloud Management is installed, see [Changing the cluster administrator password](https://www.ibm.com/support/knowledgecenter/SSFC4F_2.3.0/iam/3.4.0/change_admin_passwd.html).
3. Optional: After installation, you can choose to enable or disable additional operators and services such Infrastructure Management, Operations, Monitoring, and other services. For instructions, refer to [Advanced configuration](https://www.ibm.com/support/knowledgecenter/SSFC4F_2.3.0/install/config_adv.htmledit).









 Uninstall IBM Cloud Pak for Multicloud Management 

To uninstall IBM Cloud Pak for Multicloud Management, you can use the IBM Cloud Pak for Multicloud Management console or the command-line interface (CLI).



 Uninstalling IBM Cloud Pak for Multicloud Management from the IBM Cloud console 



1.