vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Also used to manage ESG configuration for add-on services that require public network access for licensing, activation, or usage reporting. 
 Privileged user admin Created for customer use only. 







 ESXi host user IDs 



Table 3. ESXi host user IDs

 User User ID Description 

 Privileged user ic4vroot Used post deployment to add more NFS storage, configure routes for that storage, and to run all server validation code. 
 Privileged user root Created for customer use only. 







 Active Directory user IDs 



Table 4. Active Directory user IDs

 User User ID Description 

 IBM automation automation Used to add a host or a VM for service, and to set up Microsoft® Active Directory and DNS entries. 
 Privileged user Administrator Default Windows® user 
 Privileged user cloudadmin Default user for customer to access vCenter Server 
 Privileged user cloudreadonly Read-only account for customer 







 Microsoft Active Directory groups 



Table 5. Microsoft Active Directory groups

 User User ID Description 

 Privileged user IC4v-vCenter vCenter Administration Group 







 Service user IDs 



Table 6. Service user IDs

 User ID Description 

 prod-BigIP-dynamicID-@domainName Used for installation and configuration of the F5 service. 
 prod-Caveonix-dynamicID-@domainName Used for installation and configuration of the Caveonix RiskForesight service. 
 prod-Fortigate-dynamicID-@domainName Used for installation and configuration of the FortiGate Security Appliance service. 
 prod-FortigateVM-dynamicID-@domainName Used for installation and configuration of the FortiGate Virtual Appliance service. 
 prod-KMIPAdapter-dynamicID-@domainName Used for installation and configuration of the KMIP for VMware service. 
 prod-SPPlus-dynamicID-@domainName Deprecated - Used for installation and configuration of the IBM Spectrum Protect Plus service. 
 prod-Veeam-dynamicID-@domainName Used for installation and configuration of the Veeam service. 
 prod-HCX-dynamicID-@domainName Used for installation and configuration of the VMware HCX™ service. 



where:
For more information about this architecture, see [Automating SAP HANA stand-alone virtual server instance on IBM Cloud® VPC by using Terraform and Ansible](https://cloud.ibm.com/docs/sap?topic=sap-automate-terraform-sap-hana-vsi).





 Script files 

The configuration and script files are provided in GitHub. There are two repositories for each SAP solution:



* Using the bastion server CLI to run the Terraform scripts - [GitHub repository](https://github.com/IBM-Cloud/sap-bw4hana/tree/main/cli)
* Using Schematics user interface on IBM Cloud - [GitHub repository](https://github.com/ibm-cloud/sap-bw4hana/tree/main/schematics)







 Terraform scripts 

For SAP BW/4HANA virtual server instance on IBM Cloud VPC, you modify the:



* terraform.tfvars file to add your IBM Cloud API key
* input.auto.tfvars file to customize the resources for your solution. You specify zones, resource names, SSH keys, and SAP variables.



All of the other configuration files are provided and do not need to be modified.

The IBM Cloud Provider Plug-in for Terraform on IBM Cloud uses these configuration files to provision a VPC in your IBM Cloud account.





 Single-host SAP HANA system 

A single-host system is the simplest system installation type that runs an SAP HANA system entirely on one host. You can scale the system up as needed. The single-host system has these components:

Zoom

![Figure 1. SAP NetWeaver 7.x SAP HANA single-host installation with AAS](https://cloud.ibm.com/docs-content/v1/content/f89cc64b006ca59b35404693959c83d5747fee3e/sap/images/sap-hana-vpc-std-pas-aas.svg)

Figure 1. SAP NetWeaver 7.x SAP HANA single-host installation with AAS
1. Open the root folder of your SWPM-DVD or of your installation DVD as Administrator, and run sapinst. The Welcome to SAP Installation page is displayed.
2. Select SAP NetWeaver 7.5 > IBM DB2 for Linux, Unix, and Windows > SAP Systems > Application Server ABAP.
3. Open Distributed System and run ASCS Instance and Database Instance on the database server.
4. Verify that sapinst successfully shared folders \usrsaptrans and \sapmnt after the ASCS Instance is installed for the next step to work.
5. Run Primary Application Server Instance on the application server. Be sure to use the private addresses for the ASCS and the database hostnames during installation of the application server. Using private addresses ensures that network traffic between the application server and ASCS, or database, path through the private network and not through the public network.



You can now run your SAP installation according to the SAP installation instructions.
[SAP on IBM Power Systems running Linux](https://wiki.scn.sap.com/wiki/display/ATopics/SAP+on+IBM+Power+Systems+running+Linux) Useful information about running Linux on Power 
 [936887 - End of maintenance for Linux distributions](https://launchpad.support.sap.com//notes/936887) Maintenance calendar and product maturity 
 [2679703 - Linux on IBM Power Systems - SAP monitoring recommendations](https://launchpad.support.sap.com//notes/2679703) SAP monitoring recommendations 
 [187864 - Linux: Locale Support on Linux](https://launchpad.support.sap.com//notes/187864) Locale support for Linux 
 [SAP on IBM Power Systems running Linux](https://wiki.scn.sap.com/wiki/display/ATopics/SAP+on+IBM+Power+Systems+running+Linux) SAP on IBM Power Systems library 
 [2382421 - Optimizing the Network Configuration on HANA- and OS-Level](https://launchpad.support.sap.com//notes/2382421) Increasing efficiency on network for operating systems and SAP HANA 
 [401162 - Linux: Avoiding TCP/IP port conflicts and start problems](https://launchpad.support.sap.com//notes/401162) Avoiding network-related start issues 







 Operating systems – SUSE Linux 

For more information about SAP on SUSE Linux, see the following table.



Table 2. Operating systems – SUSE Linux®

 Link Description 

 [2205917 - SAP HANA DB: Recommended OS settings for SLES 12 / SLES for SAP Applications 12](https://launchpad.support.sap.com//notes/2205917) SLES 12 recommended operating system settings 
 [1984787 - SUSE LINUX Enterprise Server 12: Installation notes](https://launchpad.support.sap.com//notes/1984787) SLES 12 installation note
[Shield Sync ID from Application](https://cloud.ibm.com/docs-content/v1/content/57ab3ec034294d8a6de510b97bec3035d4654761/security-broker/images/shield_syncid.svg)

Shield Sync ID from Application
10. Provide the Shield Sync ID and Shield name under Set the Input Variables section.

Shield Name is mandatory if you are installing multiple Shields.
11. Click Install in the Summary pane on the right to complete the installation process.
12. You will be navigated to the IBM Schematicss Workspaces to track the installation progress. Once the installation is successful, a message Workspace creation successfull is displayed as shown below:

Zoom

![Installation of Data Security Broker Shield](https://cloud.ibm.com/docs-content/v1/content/57ab3ec034294d8a6de510b97bec3035d4654761/security-broker/images/install_success.svg)

Installation of Data Security Broker Shield



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



 Next steps 

Once you have successfully installed Data Security Broker Shield, you can refer to the [Data Protection Services](https://cloud.ibm.com/docs/security-broker?topic=security-broker-sb_encrypt_postgress) section to encrypt data.
For more information about the IBM Cloud Provider plug-in for Terraform supported versions, see [Installing the Terraform CLI](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-setup_cli).

For example, you can download terraform_0.15.5_darwin_amd64.zip for a MacOS.
3. Extract the Terraform zip file and copy the files to your terraform directory.
4. Set the environment PATH variable to your Terraform files.

export PATH=$PATH:<terraform-directory>/terraform
5. Verify that the installation is successful by using a terraform command.

./terraform



For more information, see [Installing the Terraform CLI](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-setup_clitf_installation).





 Step 2. Set up the IBM Cloud Provider plug-in 

After the Terraform CLI installation is complete, you must set up the IBM Cloud Provider plug-in for Terraform so that you can start working with resources and services in IBM Cloud. For a list of supported versions, see the [IBM Cloud Provider plug-in releases](https://github.com/IBM-Cloud/terraform-provider-ibm/releases).

The setup of the IBM Cloud Provider plug-in varies depending on the Terraform CLI version that you want to use. To run your Terraform configuration files with Terraform version 0.13.x or higher, installation of the IBM Cloud Provider plug-in for Terraform is not required. For more information, see [Terraform v0.13.x and higher](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-setup_cliinstall-provider-v13).

For example, to run your Terraform configuration files with Terraform version 0.13.x or higher, complete the following steps:



1.
Mount the disk image by double-clicking the macos_dsdriver.dmg file.



A new Finder window opens with the contents of the disk image.

If the Finder window does not open, double-click the macos_dsdriver icon on your desktop. 2. In the Finder window, double-click the installDSDriver.sh file.

The driver package is installed in the default location: /Applications/dsdriver.
* For updates to your existing driver package installation



1. Back up current configuration files:



a. Go the Applications/dsdriver/cfg folder.

b. Copy the following files to a different folder:

db2cli.ini

db2dsdriver.cfg



2. Remove the currently installed driver package by right-clicking the dsdriver folder and selecting Move to Trash.
3. Install the new driver package as described in the preceding For a new installation section:



a. Mount the disk image by double-clicking the macos_dsdriver.dmg file. b. In the Finder window, double-click the installDSDriver.sh file. 4. Restore the configuration files:

Copy the db2cli.ini and db2dsdriver.cfg files that you saved from Step 1 to the /Applications/dsdriver/cfg folder.







 What's next? 

To be able to connect your local applications or client tools to your Db2 on Cloud database, [configure your local environment](https://cloud.ibm.com/docs/Db2onCloud?topic=Db2onCloud-drvr_pkgcfg_loc_env).







 Installing the driver package on Windows 

You can install the Db2 on Cloud driver package on Windows by using the installer.



 Prerequisites 

Before attempting to connect to your Db2 on Cloud database, verify that you have the [prerequisites](https://cloud.ibm.com/docs/Db2onCloud/connecting?topic=Db2onCloud-connect_ovprereqs).
IBM automation@root_domain <br>(Active Directory user) Used post deployment to manage NSX VTEP IP addresses, manage host and cluster configuration when you add and remove hosts and clusters. Also used to manage ESG configuration for services that require public network access for licensing, activation, or usage reporting. 
 Customer admin Created for customer use only. 







 ESXi host user IDs 



Table 3. ESXi host user IDs

 User User ID Description 

 IBM ic4vroot Used post deployment to add more NFS storage, configure routes for that storage, and run all server validation code. 
 Customer root Created for customer use only. 







 Microsoft Active Directory user IDs 



Table 4. Microsoft® Active Directory user IDs

 User User ID Description 

 IBM automation Used to add a host, add a VM for service, and set up Active Directory™ and DNS entries. 
 Customer administrator Created for customer use only. 







 Service user IDs 



Table 5. Service user IDs

 User ID Description 

 prod-BigIP-dynamicID-@domainName Used for installation and configuration of the F5® service. 
 prod-Caveonix-dynamicID-@domainName Used for installation and configuration of the Caveonix RiskForesight™ service. 
 prod-Fortigate-dynamicID-@domainName Used for installation and configuration of the FortiGate® Security Appliance service. This service is deprecated. 
 prod-FortigateVM-dynamicID-@domainName Used for installation and configuration of the FortiGate Virtual Appliance service. 
 prod-HyTrustCC-shortID-@domainName Used for installation and configuration of the Entrust CloudControl™ service. 
 prod-HyTrustDC-shortID-@domainName Used for configuration of the Entrust DataControl® service. 
 prod-HyTrustKC-shortID-@domainName Used for installation and configuration of the Entrust KeyControl™ service. 
 prod-KMIPAdapter-dynamicID-@domainName Used for installation and configuration of the KMIP™ for VMware service.
Decompress the compressed driver package file that you downloaded earlier.

Example:

gunzip file_name.tar.gz

tar -xvf file_name.tar

A dsdriver subdirectory is created in the directory where you ran the decompression commands.
2. Extract the Java and ODBC/CLI drivers.

a. In the dsdriver subdirectory, run the installDSDriver command.

The installDSDriver command creates the db2profile and db2cshrc script files in the dsdriver directory.

b. Run one of the following script files based on your shell environment:



* Bash or Korn shell: source db2profile
* C shell: source db2cshrc









 What's next? 

To be able to connect your local applications or client tools to your Db2 on Cloud database, [configure your local environment](https://cloud.ibm.com/docs/Db2onCloud?topic=Db2onCloud-drvr_pkgcfg_loc_env).







 Installing the driver package on Mac OS X 

You can install the Db2 on Cloud driver package on Mac OS X by using the installDSDriver.sh script.



 Prerequisites 

Before attempting to connect to your Db2 on Cloud database, verify that you have the [prerequisites](https://cloud.ibm.com/docs/Db2onCloud/connecting?topic=Db2onCloud-connect_ovprereqs).





 Procedure 



* For a new installation



1. Mount the disk image by double-clicking the macos_dsdriver.dmg file.



A new Finder window opens with the contents of the disk image.

If the Finder window does not open, double-click the macos_dsdriver icon on your desktop. 2. In the Finder window, double-click the installDSDriver.sh file.

The driver package is installed in the default location: /Applications/dsdriver.
* For updates to your existing driver package installation
Decompress the compressed driver package file that you downloaded earlier.

Example:

gunzip file_name.tar.gz

tar -xvf file_name.tar

A dsdriver subdirectory is created in the directory where you ran the decompression commands.
2. Extract the Java and ODBC/CLI drivers.

a. In the dsdriver subdirectory, run the installDSDriver command.

The installDSDriver command creates the db2profile and db2cshrc script files in the dsdriver directory.

b. Run one of the following script files based on your shell environment:



* Bash or Korn shell: source db2profile
* C shell: source db2cshrc









 What's next? 

To be able to connect your local applications or client tools to your Db2 on Cloud database, [configure your local environment](https://cloud.ibm.com/docs/Db2onCloud/connecting?topic=Db2onCloud-drvr_pkgcfg_loc_env).







 Installing the driver package on Mac OS X 

You can install the Db2 on Cloud driver package on Mac OS X by using the installDSDriver.sh script.



 Prerequisites 

Before attempting to connect to your Db2 on Cloud database, verify that you have the [prerequisites](https://cloud.ibm.com/docs/Db2onCloud/connecting?topic=Db2onCloud-connect_ovprereqs).





 Procedure 



* For a new installation



1. Mount the disk image by double-clicking the macos_dsdriver.dmg file.



A new Finder window opens with the contents of the disk image.

If the Finder window does not open, double-click the macos_dsdriver icon on your desktop. 2. In the Finder window, double-click the installDSDriver.sh file.

The driver package is installed in the default location: /Applications/dsdriver.
* For updates to your existing driver package installation
Decompress the compressed driver package file that you downloaded earlier.

Example:

gunzip file_name.tar.gz

tar -xvf file_name.tar

A dsdriver subdirectory is created in the directory where you ran the decompression commands.
2. Extract the Java and ODBC/CLI drivers.

a. In the dsdriver subdirectory, run the installDSDriver command.

The installDSDriver command creates the db2profile and db2cshrc script files in the dsdriver directory.

b. Run one of the following script files based on your shell environment:



* Bash or Korn shell: source db2profile
* C shell: source db2cshrc









 What's next? 

To be able to connect your local applications or client tools to your Db2 Warehouse on Cloud database, [configure your local environment](https://cloud.ibm.com/docs/Db2whc/connecting?topic=Db2whc-dr_pkgcfg_loc_env).







 Installing the driver package on Mac OS X 

You can install the Db2 Warehouse on Cloud driver package on Mac OS X by using the installDSDriver.sh script.



 Prerequisites 

Before attempting to connect to your Db2 Warehouse on Cloud database, verify that you have the [prerequisites](https://cloud.ibm.com/docs/Db2whc/connecting?topic=Db2whc-connect_ovprereqs).





 Procedure 



* For a new installation



1. Mount the disk image by double-clicking the macos_dsdriver.dmg file.



A new Finder window opens with the contents of the disk image.

If the Finder window does not open, double-click the macos_dsdriver icon on your desktop. 2. In the Finder window, double-click the installDSDriver.sh file.

The driver package is installed in the default location: /Applications/dsdriver.
* For updates to your existing driver package installation
Select Devices > Device List from the main menu to see the list of available server devices.
3. Find the device for which you purchased the IBM Cloud Backup for Classic service, and make a note of its public IP address.



* This IP address is to be used when you log in to the device from the command line. In the command that is shown in Step 5, replace <publicIpAddress> with the actual public IP address.



4. Click Passwords to display the Password manager, and see the usernames and the passwords that are associated with the account.
5. Log in to the target device by entering the following command from the command line.

ssh <user name>@<publicIpAddress>

If you didn't log in to this server with this username before, you are presented a message about the authenticity of the host. You are also asked whether you want to continue. Reply with yes to continue.
6. You are prompted to enter the password unless you set up ssh keys for accessing this server before.







 Updating the OS to prepare for the installation (RHEL only) 

This step is required for RHEL, but optional for other distributions.



* Run the following command at the server prompt.

yum update

If you're prompted, confirm that the download size is okay. The update proceeds and displays a "Complete" message when it finishes.







 Getting the installation script 



* Run the following command at the server prompt.

wget -N http://downloads.service.softlayer.com/evault/evault_manual.sh







 Running the installation Script 



1. Run the following command at the server prompt.

sh ./evault_manual.sh
2. Enter your Cloud Backup Portal username and password.

For more information about viewing the username or changing the backup password, see [Managing username and password for the Cloud Backup service](https://cloud.ibm.com/docs/Backup?topic=Backup-changePassword).
3. After the username and password, no further input is required.
Download and install the IBM Cloud CLI from [https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases/latest](https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases/latest).
2. Verify the installation with:

ibmcloud version

You may need to restart your machine after the installation.







 Docker 



1. Docker Desktop on Windows is one option to run container images on Windows. Make sure to review the terms of the [license agreement](https://docs.docker.com/subscription/docker-desktop-license-agreement) before proceeding with the installation.
2. If you don't have one, sign up for a free account at [https://hub.docker.com/signup](https://hub.docker.com/signup).
3. Download and install Docker Desktop on Windows from [https://docs.docker.com/docker-for-windows/install/](https://docs.docker.com/docker-for-windows/install/).
4. Verify the installation with:

docker --version
docker run hello-world

You may need to log out and wait for the Docker daemon to be started.







 kubectl 



1. Download kubectl from

[https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-kubectl-on-windows](https://kubernetes.io/docs/tasks/tools/install-kubectl/install-kubectl-on-windows).
2. Move kubectl.exe binary to your PATH.
3. Verify the installation with:

kubectl version --client=true







 oc 



1.
Decompress the compressed driver package file that you downloaded earlier.

Example:

gunzip file_name.tar.gz

tar -xvf file_name.tar

A dsdriver subdirectory is created in the directory where you ran the decompression commands.
2. Extract the Java and ODBC/CLI drivers.

a. In the dsdriver subdirectory, run the installDSDriver command.

The installDSDriver command creates the db2profile and db2cshrc script files in the dsdriver directory.

b. Run one of the following script files based on your shell environment:



* Bash or Korn shell: source db2profile
* C shell: source db2cshrc









 What's next? 

To be able to connect your local applications or client tools to your Db2 Warehouse on Cloud database, [configure your local environment](https://cloud.ibm.com/docs/Db2whc?topic=Db2whc-dr_pkgcfg_loc_env).







 Installing the driver package on Mac OS X 

You can install the Db2 Warehouse on Cloud driver package on Mac OS X by using the installDSDriver.sh script.



 Prerequisites 

Before attempting to connect to your Db2 Warehouse on Cloud database, verify that you have the [prerequisites](https://cloud.ibm.com/docs/Db2whc/connecting?topic=Db2whc-connect_ovprereqs).





 Procedure 



* For a new installation



1. Mount the disk image by double-clicking the macos_dsdriver.dmg file.



A new Finder window opens with the contents of the disk image.

If the Finder window does not open, double-click the macos_dsdriver icon on your desktop. 2. In the Finder window, double-click the installDSDriver.sh file.

The driver package is installed in the default location: /Applications/dsdriver.
* For updates to your existing driver package installation



1.