vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* A single-host system - One SAP HANA instance on one host.
* A distributed system (multiple-host system) - Multiple SAP HANA instances distributed over multiple hosts,







 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/refarch-sap-hana-single-host-only.svg)

Figure 2. SAP NetWeaver 7.x SAP HANA single-host installation with AAS

For more information about SAP systems architectures in IBM Cloud VPC, see [reference architectures](https://cloud.ibm.com/docs/sap?topic=sap-sap-refarch-nw-hana) for each supported database type.

Manually deploying a VPC and installing an SAP system can be time-consuming. The automation assures not only a much quicker implementation, but also a standardized and less prone to error deployment. Terraform and Ansible are used for automating the deployment processes.

The solution that is presented in this how-to guide is the automated deployment of a single host with SAP HANA stand-alone VSI on Red Hat Enterprise Linux 7.6 for SAP Applications.

Database instance (DB) - To assist your project's planning phase, more design considerations are provided at SAP AnyDB – SAP HANA database with IBM Cloud for SAP. For more information, see [AnyDB - SAP HANA](https://cloud.ibm.com/docs/sap?topic=sap-anydb-hana-db) and [Infrastructure certified for SAP](https://cloud.ibm.com/docs/sap?topic=sap-iaas-offerings).
: Installation, upgrade, and uninstallation for the Enterprise DB PostgreSQL operator and license have changed:



* Instructions for installing the EDB PostgreSQL operator and license are now included with the IBM Cloud Pak for Data foundational services. The instructions for installing the Speech services have been updated accordingly. For more information, see [Installing Watson Speech to Text](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=text-installing-watson-speech).
* Instructions for upgrading from Speech to Text version 4.0.0 to 4.0.3 include instructions for uninstalling the previous EDB PostgreSQL operator and license and reinstalling them with the IBM Cloud Pak for Data foundational services. For more information, see [Upgrading Watson Speech to Text](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=text-upgrading-watson-speech).
* Instructions for uninstalling the Speech services now include steps for removing the EDB PostgreSQL operator and license that were previously installed with Speech to Text. For more information, see [Uninstalling Watson Speech to Text](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=text-uninstalling-watson-speech).



New guidance for scaling up your installation
: The service now provides updated guidance about scaling up your installation. The information includes specifying the number of pods, the number of CPUs allocated per pod, and the maximum number of concurrent sessions with previous- and next-generation models. For more information, see [Administering Watson Speech to Text](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=text-administering-watson-speech).

Command-line updates to import and export utilities
: The commands that are used with the import and export utilities for the Speech services include new options and arguments.
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 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).





 Procedure 



1. Run the downloaded executable file as an administrator.

The default installation path of the driver package is: Program FilesIBMIBM DATA SERVER DRIVER
2. (Optional): Add the bin subdirectory of the driver package installation directory to your %PATH% environment variable (so you can run the db2cli command without specifying the full path to the command executable.)







 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).









 Configuring your local environment 

To connect local applications and tools to your Db2 on Cloud database, you need to configure your environment.



 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 



1. Add entries to the driver configuration file, db2dsdriver.cfg, for your database.

The configuration steps are different depending on whether you want to connect to your database by using SSL:
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).





 Procedure 



1. Run the downloaded executable file as an administrator.

The default installation path of the driver package is: Program FilesIBMIBM DATA SERVER DRIVER
2. (Optional): Add the bin subdirectory of the driver package installation directory to your %PATH% environment variable (so you can run the db2cli command without specifying the full path to the command executable.)







 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).









 Configuring your local environment 

To connect local applications and tools to your Db2 on Cloud database, you need to configure your environment.



 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 



1. Add entries to the driver configuration file, db2dsdriver.cfg, for your database.

The configuration steps are different depending on whether you want to connect to your database by using SSL:
For more information about checking port availability, see [Troubleshooting](https://cloud.ibm.com/docs/sap?topic=sap-ibm-metrics-collector-for-sap-linuxtroubleshooting-linux).

The commands that are listed in this section were run on a Red Hat virtual server instance. If you have a SUSE virtual server, you can follow the same steps but you will see a slightly different user interface.

Use the following steps to download the IMCS.



1. [Download the IMCS](ftp://public.dhe.ibm.com/cloud/bluemix/sap/linux/).
2. Select the appropriate tar.gz file. In most cases, use the current version. Connect as guest.
3. Save the file to your internal Downloads folder and click OK.
4. Move or copy the IMCS tar.gz file to your VPC virtual server instance.
5. Extract the file and open the extracted folder.

tar -xvf sap-metrics-collector-v1.3.tar.gz
cd sap
6. Run the install-linux.sh file.

./install-linux.sh
. Paste your [API key](api-key) when prompted. If you don't have an API key, see [Getting an IBM Cloud API key](get-api-key).
7. Check to make sure that the IMCS is running after the installation is complete. The service status displays active when it is ready.

sudo systemctl is-active sap-metrics-collector







 Verifying data collection 

After the installation completes and the service is started, it can take time for the IMCS begins collecting metrics. Wait at least 2 minutes after the installation before you expect full and accurate metrics.



1. Run the following curl command for your localhost address to see your metrics:

curl http://localhost:18181/sap/metrics

<metrics>
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 Windows 

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



 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 



1. Run the downloaded executable file as an administrator.

The default installation path of the driver package is: Program FilesIBMIBM DATA SERVER DRIVER
2. (Optional): Add the bin subdirectory of the driver package installation directory to your %PATH% environment variable (so you can run the db2cli command without specifying the full path to the command executable.)







 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).









 Configuring your local environment 

To connect local applications and tools to your Db2 Warehouse on Cloud database, you need to configure your environment.



 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 



1. Add entries to the driver configuration file, db2dsdriver.cfg, for your database.

The configuration steps are different depending on whether you want to connect to your database by using SSL:
Learn about the Exchange plug-in 

The Exchange plug-in is installed with the Windows® Agent on the host. Through the Cloud Backup Portal, you can configure jobs, back up Exchange databases to a secure, remote vault, and restore Exchange databases. The plug-in integrates into the existing architecture.

The plug-in provides the following capabilities:



*  Ability to back up and restore MS Exchange databases.





  Installing the plug-in 

The Exchange plug-in is installed during the Windows® Agent 64-bit installation. The plug-in can be installed at the same time as the Agent or it can be installed later, by rerunning the installation with the Modify selection.

Before you install the plug-in for your MS Windows® server, stop both IBM Cloud Backup for Classic services in services.msc.



1.  Browse to c:installsIBM Cloud Backup for Classic folder and run the .exe file with the higher revision number.
2.  At the language screen, click OK.
3.  At the welcome screen, click Next.
4.  Select the Modify installation, and click Next.
5.  Select the Leave Unchanged, and click Next.
6.  At the custom setup screen, select each plug-in that you purchased.
7.  Select This feature will be installed on ..., then click Next.
8.  Select Keep my current registration, and click Next.
9.  Click Install.
10. When installed, check to ensure that both services are enabled and running.
11. If Cloud Backup Portal is able to access or view the database, then the installation was successful.







  Downloading the user guide 

Connect to the IBM Cloud® network with IBM Cloud® VPN so that you can access and download the user guide from the [Downloadable IBM Cloud Backup for Classic Documentation](http://downloads.service.softlayer.com/evault/Documentation/). The guide describes how to back up and restore MS Exchange databases by using the Exchange plug-in. The guide also describes how to share a DR backup safe-set. With a DR backup safe-set, you can restore specific mailboxes, messages, or other objects to a .pst file by using the Granular Restore for Microsoft® Exchange application.
* 1 VPC where the virtual server instances are provisioned
* 1 security group. The rules for this security group allow:



* Inbound DNS (port 53) and
* Inbound SSH (TCP port 22) connections to your virtual server instance
* All outbound traffic from the virtual server instance



* 1 subnet to enable networking in your VPC
* 2 X virtual server instances with SAP certified storage and network configurations
* 2 floating IP’s address that you use to access your VPC virtual server instance over the public network



During the second phase, the Ansible Playbook is called and the SAP architecture is installed for both dedicated VSIs SAP App VSI machine and dedicated SAP HANA VSI box. The SAP architecture that is deployed is the SAP S/4HANA release on stand-alone dedicated SAP HANA 2.0 box release as a distributed deployment model. 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).





 Single-host SAP HANA system 

A single-host system is the simplest system installation type that runs an SAP HANA db 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/refarch-sap-hana-single-host-only.svg)

Figure 1. SAP NetWeaver 7.x SAP HANA single-host installation with AAS

The scripts are designed to install SAP (SAP S/4HANA release) solution on an existing VPC together with its dedicated DB SAP HANA box in one task flow.





 Terraform deployment
All third-party JDBC drivers shipped with the Data Crawler are located in the connectorFramework/crawler-connector-framework-../lib/java/database directory of your Data Crawler installation, where you can add, remove, and modify them as necessary. You can also use the extra_jars_dir setting in the crawler.conf file to specify another location.

DB2 JDBC Drivers - The Data Crawler does not ship with the JDBC drivers for DB2 due to licensing issues. However, all DB2 installations in which you installed JDBC support include the JAR files that the Data Crawler requires, to crawl a DB2 installation. To crawl a DB2 instance, you must copy these files into the appropriate directory in your Data Crawler installation so that the Database connector can use them. To enable the Data Crawler to crawl a DB2 installation, locate the db2jcc.jar and license (typically, db2jcc_license_cu.jar) JAR files in your DB2 installation, and copy those files to the connectorFramework/crawler-connector-framework-../lib/java/database subdirectory of your Data Crawler installation directory, or you can use the extra_jars_dir setting in the crawler.conf file to specify another location.

MySQL JDBC Drivers - The Data Crawler does not ship with the JDBC drivers for MySQL because of possible license issues if they were delivered as part of the product. However, downloading the JAR file that contains the MySQL JDBC drivers and integrating that JAR file into your Data Crawler installation is quite easy to do:



1. Use a web browser to visit the MySQL download site, and locate the source and binary download link for the archive format that you want to use (typically zip for Microsoft Windows systems or a gzipped tarball for Linux systems). Click that link to initiate the download process. Registration might be required.
2. Use the appropriate unzip archive-file-name or tar zxf archive-file-name command to extract the contents of that archive, based on the type and name of the archive file that you download.
3.
Another option is to run GUI locally and connect it to SWPM on the target machine. For the first option, you must run X11 in your virtual server and install a VNC server and a browser. You can run the browser locally on your desktop, and connect to SWPM in the virtual server. To connect to SWPM, check the port that SWPM is listening on. SWPM displays the port during startup when it lists the access URL. The port, typically 4237, needs to open in the security group of your VPC. You need to add a New Inbound rule for your IP source range (or 0.0.0.0/0) and the port number. Another possibility, and even more secure, is to tunnel the port through ssh.

[root@sap-app-vsi ] ssh -L 4237:localhost:4237 <your virtual server IP>

-L option for local tunnels and connecting your browser to that localhost port, instead of the remote IP. Remember to add the ports that are required by your SAP application (example: ports 3200-3299, depending on your SAP NetWeaver instance number) to the security group. For more information about ports, see [SAP ports](https://help.sap.com/viewer/ports) for details.

Zoom

![Figure 14. All security groups for VPC](https://cloud.ibm.com/docs-content/v1/content/f89cc64b006ca59b35404693959c83d5747fee3e/sap//images/quickstudy-intel-vs-gen2-image5.png)

Figure 14. All security groups for VPC





 Installing SAP software 

After you download the installation media, follow the standard SAP installation procedure that is documented in the [SAP installation guides](https://help.sap.com/viewer/index) for your SAP version and components. Also, review the corresponding SAP notes.
Source Subnet, IP range Target Subnet, IP range Port Protocol Purpose Service 

 OCP New subnet ordered in private VLAN Windows Active Directory Private primary subnet <br>Infrastructure VMs 53 UDP Use Windows DNS service DNS 
 OCP New subnet ordered in private VLAN vCenter Server Infrastructure VMs 443 TCP Use vCenter Server REST service HTTPS 
 OCP New subnet ordered in private VLAN IBM Cloud infrastructure NTP service IBM Cloud infrastructure services network 123 UDP Use IBM Cloud infrastructure NTP service NTP 
 OCP New subnet ordered in private VLAN OCP cluster network OCP internal IP range 10.128.0.0/14 5443/8443 TCP OCP cluster management WEBREST API 
 OCP edge public IP addresses New subnet ordered in public VLAN Public websites required for Red Hat OpenShift installation<br><br>[1] 80/123/443 TCP and UDP Time service, Red Hat OpenShift installation content, and images NTP/HTTP/HTTPS 
 IBM CloudDriver Private primary subnet <br>Infrastructure VMs OCP New subnet ordered in private VLAN 22 TCP Set up and configure OCP SSH 



For more information about OCP networking, see [About the Red Hat OpenShift SDN network provider](https://docs.openshift.com/container-platform/4.13/networking/openshift_sdn/about-openshift-sdn.html).





 Ports for Veeam 

The following table provides information about the Veeam® ports.



Table 8. Veeam ports

 Source Subnet, IP range Target Subnet, IP range Port Protocol Purpose Service 

 Veeam Private primary subnet IBM Cloud infrastructure DNS service IBM Cloud infrastructure services network 53 UDP Use IBM Cloud infrastructure DNS service UDP 
 Veeam Private primary subnet IBM Cloud infrastructure NTP service IBM Cloud infrastructure services network 123 UDP Use IBM Cloud infrastructure NTP service NTP 
 Veeam Private primary subnet IBM Cloud infrastructure service - Provision Windows VSI IBM Cloud infrastructure services network ICMP Use infrastructure services to provision Windows VSI for Veeam Ping
* [Installation of SAP ABAP S/4HANA and BW/4HANA Systems on UNIX: SAP HANA 2.0 Database](https://help.sap.com/viewer/39c32e9783f6439e871410848f61544c/CURRENT_VERSION_SWPM20/en-US/1937febc57ad4d81a213fca9b3e031a5.html)



HANA and SAP NetWeaver on Windows:



* [Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows: SAP HANA Database](https://help.sap.com/viewer/2703bed525eb478c935bc312b3c3b0a6/CURRENT_VERSION/en-US/9420dabb130e4ae1996b3f39e202cc6e.html)
* [Installation of SAP Systems Based on the Application Server Java of SAP NetWeaver 7.5 and SAP Solution Manager 7.2 SR2 Java on Windows: SAP HANA Database](https://help.sap.com/viewer/14ccd8beec6f4651905783bc469bce5d/CURRENT_VERSION/en-US/9420dabb130e4ae1996b3f39e202cc6e.html)
* [Installation of SAP ABAP S/4HANA and BW/4HANA Systems on Windows: SAP HANA 2.0 Database](https://help.sap.com/viewer/3741bfe0345f4892ae190ee7cfc53d4c/CURRENT_VERSION_SWPM20/en-US/1937febc57ad4d81a213fca9b3e031a5.html)







 SAP on SAP HANA using Intel Bare Metal 

See [SAP Note 2414097 - SAP Applications on IBM Cloud: Supported DB/OS and IBM Cloud Bare Metal Server Types](https://launchpad.support.sap.com//notes/2414097) for supported SAP HANA database versions.

A sample configuration is shown in:
Installation overview 

Find information about how to install IBM Watson® Discovery Cartridge for IBM Cloud Pak® for Data.

IBM Cloud Pak for Data

This information applies only to installed deployments.



 Full installation instructions 



* [4.7.x](https://www.ibm.com/docs/SSQNUZ_4.7.x/svc-discovery/discovery-install-overview.html)
* [4.6.x](https://www.ibm.com/docs/SSQNUZ_4.6.x/svc-discovery/discovery-install-overview.html)
* [4.5.x](https://www.ibm.com/docs/SSQNUZ_4.5.x/svc-discovery/discovery-install-overview.html)
* [4.0.x](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=discovery-installing-watson)
* [2.2.0, 2.2.1](https://www.ibm.com/docs/cloud-paks/cp-data/3.5.0?topic=services-watson-discovery)



Federal Information Security Management Act (FISMA) support is available for Discovery for Cloud Pak for Data offerings purchased on or after August 30, 2019. IBM Watson® Discovery is FISMA High Ready.





 Support matrix 

You install IBM Cloud Pak for Data, and then install the Discovery service.



* The 4.6.2 release is the last supported release on Red Hat OpenShift Container Platform 4.8.
* The 4.5.3 release is the last supported release on Red Hat OpenShift Container Platform 4.6.29 or later.





Support matrix

 Discovery version IBM Cloud Pak for Data version Red Hat OpenShift version 

 4.7.0 4.7.0 4.12 
 4.7.0 4.7.0 4.10 
 4.6.5 4.6.6 4.12 
 4.6.5 4.6.6 4.10 
 4.6.5 4.6.5 4.12
* [Installation of SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 : MS SQL Server](https://help.sap.com/viewer/c22d9ecc82ca4ab591a91942fe5c0020/CURRENT_VERSION/en-US/9420dabb130e4ae1996b3f39e202cc6e.html)
* [Installation of SAP Systems Based on the Application Server Java of SAP NetWeaver 7.5 and SAP Solution Manager 7.2 SR2 Java : MS SQL Server](https://help.sap.com/viewer/34ba60e8526d4110921c9c0fd05b4b6d/CURRENT_VERSION/en-US/9420dabb130e4ae1996b3f39e202cc6e.html)



MS SQL Server licensing supported by SAP



* [SAP Note 1491158 - Information About the Microsoft SQL Server License Scope](https://launchpad.support.sap.com//notes/1491158)
* [SAP Note 398136 - Support Policy for Microsoft SQL Server](https://launchpad.support.sap.com//notes/398136)



MS SQL Server release/support information



* [SAP Note 2807743 - Release planning for Microsoft SQL Server 2019](https://launchpad.support.sap.com//notes/2807743)
* [SAP Note 2779625 - Setting up Microsoft SQL Server 2019](https://launchpad.support.sap.com//notes/2779625)
* [SAP Note 2492596 - Release planning for Microsoft SQL Server 2017](https://launchpad.support.sap.com//notes/2492596)
* [SAP Note 2484674 - Setting up Microsoft SQL Server 2017](https://launchpad.support.sap.com//notes/2484674)
* [SAP Note 2201059 - Release planning for Microsoft SQL Server 2016](https://launchpad.support.sap.com//notes/2201059)