vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can add endpoints to the configmap, such as these [default Satellite link endpoints](https://cloud.ibm.com/docs/satellite?topic=satellite-default-link-endpoints).







 Updating the Delivery Pipeline Private Worker installation 

If the private worker is reported as inactive, you must update the installation.

To view the version of your private worker, type one of the following commands:



* IBM Cloud Kubernetes Service: kubectl -n tekton-pipelines describe deploy private-worker-agent | grep Image
* Red Hat® OpenShift® on IBM Cloud®: kubectl -n openshift-operators describe deploy private-worker-agent-controller-manager | grep Image



To update your private worker installation, complete the following steps:



1. Run the [installation command](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-install-private-workers&interface=cliinstall_pw) again.
2. [Register the private worker](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-install-private-workers&interface=cliregister_pw) on your Kubernetes cluster again.



You can reuse the apikey that you used for the existing private worker.

For more information about Delivery Pipeline Private Workers, see [Troubleshooting for Delivery Pipeline Private Workers](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-troubleshoot-pipeline-private-workerstroubleshoot-pw-images) and [FAQs for Pipeline Private Workers](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-faq_pipeline_private_workers&interface=ui).
You can add endpoints to the configmap, such as these [default Satellite link endpoints](https://cloud.ibm.com/docs/satellite?topic=satellite-default-link-endpoints).







 Updating the Delivery Pipeline Private Worker installation 

If the private worker is reported as inactive, you must update the installation.

To view the version of your private worker, type one of the following commands:



* IBM Cloud Kubernetes Service: kubectl -n tekton-pipelines describe deploy private-worker-agent | grep Image
* Red Hat® OpenShift® on IBM Cloud®: kubectl -n openshift-operators describe deploy private-worker-agent-controller-manager | grep Image



To update your private worker installation, complete the following steps:



1. Run the [installation command](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-install-private-workers&interface=uiinstall_pw) again.
2. [Register the private worker](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-install-private-workers&interface=uiregister_pw) on your Kubernetes cluster again.



You can reuse the apikey that you used for the existing private worker.

For more information about Delivery Pipeline Private Workers, see [Troubleshooting for Delivery Pipeline Private Workers](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-troubleshoot-pipeline-private-workerstroubleshoot-pw-images) and [FAQs for Pipeline Private Workers](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-faq_pipeline_private_workers&interface=ui).
The scripts include Ansible scripts for:



* OS requirements installation and configuration for SAP applications
* Cluster components installation
* Ansible scripts for SAP application cluster configuration and SAP HANA cluster configuration
* HANA installation
* HANA DB backup
* HANA system replica configuration
* ASCS and ERS instances installation
* DB load
* Primary and extra application servers installation



Ansible is started by Terraform and must be available on the same host.





 SAP Solution implemented 

SAP S/4HANA is an ERP system from SAP's ERP software product line. The software is based on the innovative SAP HANA database technology and was started as the fourth product generation in 2015. Users can choose between the SAP S/4HANA Cloud and On-Premise solution.

An ERP system is used for demand-oriented business resource planning. It is used to control processes and to link departments and functional areas in a meaningful way. Individual modules include applications for accounting, sales, production, and marketing. More complex tasks in customer or supply chain management can also be done by ERP software. As the successor to the core product SAP ECC, SAP S/4HANA was presented as the intelligent ERP system of the new generation. Thanks to modern technologies, the Software as Service (SaaS) version is designed to help companies standardize processes and make the leap to digitalization.

While previous SAP ERP solutions support the most common databases, SAP S/4HANA uses exclusively the SAP HANA in-memory database developed by SAP. This in-memory database offers users the greatest technical benefit and they benefit from increased performance. The "S" in S/4HANA stands for "simple", while the "4" refers to the generation sequence. Compared to the SAP core product SAP ECC, which is still used in most companies, SAP S/4HANA offers many innovative functions that revolutionize the system landscape from the ground up. As SAP plans to discontinue the mainstream maintenance of its existing ERP solutions by 2027, many SAP ECC users are already considering a migration to SAP HA SZ S/4HANA





 What is created 

The scripts work in two phases.
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 
 [2578899 - SUSE Linux Enterprise Server 15: Installation Note](https://launchpad.support.sap.com//notes/2578899) SLES 15 installation note 
 [2684254 - SAP HANA DB: Recommended OS settings for SLES 15 / SLES for SAP Applications 15](https://launchpad.support.sap.com//notes/2684254) SLES 15 recommended operating system settings 
 [2790462 - HANA Server connection is not available or timed out after you upgrade to SUSE 15 from SUSE 12](https://launchpad.support.sap.com//notes/2790462) Known issue when you upgrade from 12 to 15 
 [1275776 - Linux: Preparing SLES for SAP environments](https://launchpad.support.sap.com//notes/1275776) Preparing SLES for SAP environments 
 [SUSE Best Practices Library](https://documentation.suse.com/sbp/all/?context=sles-sap) A useful collection of SUSE documentation 
 [SUSE Enterprise Server for IBM POWER](https://www.suse.com/products/power/) IBM and SUSE 







 Operating systems – Red Hat Linux® (RHEL) 

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



Table 3. Operating systems – Red Hat Linux

 Link Description 

 [SAP Note 2772999 RHEL 8.x: Installation and Configuration](https://launchpad.support.sap.com//notes/2772999) <br><br> * <br><br><br>
The gateway ID is defined when you create a Secure Gateway service. If the client fails to connect, you can change your selection by editing the .conf file.

Security token If the gateway ID is enabled to check for a security token, you must provide it now. If the gateway ID does not require a security token, leave this blank.

Logging level The default setting is INFO. Other valid values are TRACE, DEBUG, and ERROR.

Access Control List Enter the absolute path of the file name containing the access control list on what has access to your on-premises resources. For more information, see the README.md file in /opt/ibm/securegateway or Access control list.

Client UI Choose if you want to use client UI. If yes, user can change the port for the UI. Default value is 9003.

NPM installation proxy Enter the proxy info if you want to install the npm module with the proxy. If NPM installation proxy is not required, leave this blank.

Note: Other than the NPM installation proxy info, you do not have to answer any of the prompts, all will take the defined default or be left blank in the sgenvironment.conf file. This allows the installation process to start up Secure Gateway client without user interaction.

Note: The sgenvironment.conf is read every time that you start or restart the client using the system's upstart process. You can edit the /etc/ibm/sgenvironment.conf file at any time to make changes to your configuration and restart the client to pick up those changes. However, UI password in config file could only be set up during installation.

Note: The language of the Secure Gateway client service logs can be changed by changing the LANGUAGE parameter in the /etc/ibm/sgenvironment.conf file. The service logs will change to selected language after service restart.
3. If you restarted the client, to make sure that the client is running properly, issue the following command:

cat /var/log/securegateway/client_console.log
4. If you want to edit the configuration file, to make sure that the configuration file is updated correctly, issue the following command:
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/).



* Envoy proxies inbound and outbound traffic for all services in the mesh. Envoy is deployed as a sidecar container in the same pod as your app container.
* istiod unifies functionality that Pilot, Galley, Citadel, and the sidecar injector previously performed into a single control plane package.
* The istio-ingressgateway and istio-egressgateway control incoming traffic to and outgoing traffic from your Istio-managed apps.
* The Istio operator (addon-istio-operator in Istio version 1.10 or later, or managed-istio-operator in Istio version 1.9 or earlier) in the ibm-operators namespace validates and reconciles any custom Istio operator (IOP) changes that you make.







 Limitations 

Review the following limitations for the managed Istio add-on.



* When you enable the managed Istio add-on, you can't use IstioOperator (IOP) resources to customize the Istio control plane installation. Only the IstioOperator resources that are managed by IBM for the Istio control plane are supported. If you create an IstioOperator resource for custom gateways in your Istio data plane, you are responsible for managing those resources.
* You can't modify any Istio resources that are created for you in the istio-system namespace. If you need to customize the Istio installation, you can [edit the managed-istio-custom configmap resource](https://cloud.ibm.com/docs/containers?topic=containers-istiocustomize).
* The following features are not supported in the managed Istio add-on:
Complete the steps in [Installing the agent](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-wfs-cp4dconnector-wfs-cp4d-prereq1-task) to install the latest version of the agent.
6. Replace the new version of the C:Program FilesIBMesdistributedesadminconfigesfsexport.txt file with the file that you copied in Step 1.

This step adds the configuration of the shared directories that you set up for the previous version of the agent to the new installation. When you reuse the file share, you can skip the step of configuring the shared directories.
7. Run the following command to verify that the directory is shared with the agent service:

C:UsersAdministrator> esagent --lsshare







 Installing the agent 

To install the IBM Watson Discovery Agent for Windows File Systems for the first time, complete the following steps:



1. From the navigation pane, choose Manage collections.
2. Click New collection.
3. Click Windows File System, and then click Next.
4. Scroll to the Download & install Windows Agent section, and then click Download Windows Agent Installer.

A ZIP file is downloaded.
5. Decompress the WindowsAgentServer.zip file.
6. You can choose one of the following methods to run the installation program:



* Double-click the install.exe file to launch the installation wizard.
* To run the installation program in text mode from a console, complete the following steps:



* Change to the agent directory.
* Enter the following command:

install.exe -i console

The screens are rendered in text and prompt you for the same information as the graphical installation.

After you enter the command, a process runs in the background for several seconds before the console installation program is displayed.



* To install the agent server silently, complete the following steps:



* Change to the Agent/responseFiles directory.
* Edit the DistributedFileSystemCrawler.properties template response file to provide information about your environment.
The Terraform scripts solution provides the automated deployment of a single host with SAP NetWeaver with ASE SYB on the Red Hat Enterprise Linux 8 and SUSE 15 for SAP Applications.

The SAP installation media that are used for this deployment are the default media for SAP NetWeaver 7.5 with ASE SYB XXXX.XXX. The media are available at the SAP Support Portal under INSTALLATION AND UPGRADE area. You provide the installation media as an input parameter for Terraform.





 Ansible for SAP installation 

Ansible is an automation tool for the deployment of several IT tasks. Ansible is used for automating the installation of an SAP NetWeaver with ASE SYB. For more information about Ansible, see the [Ansible Documentation](https://docs.ansible.com/ansible/latest/index.html).

The deployment is done by using the Ansible core, which provides CLI tools for automation. More information about Ansible core can be found on the [Ansible core page](https://docs.ansible.com/ansible-core/devel/index.html).

The Ansible playbook is called directly by the Terraform script. The script starts with Terraform specific steps for creating the VPC, and continues automatically with the Ansible specific steps to install the SAP system.





 Where to run the scripts 

The recommended way to run the scripts is from your Deployment Server because the Deployment Server has Terraform and Ansible already installed. If you want to run the scripts from your local workstation, you need to install Terraform and Ansible locally.

For both the Deployment Server and local workstation, you must download the SAP Kits to the temporary storage assigned to you on the Deployment Server. Ansible installs the kits for you. You specify the location of the Kits in the configuration files.





 Prerequisite, create a Bastion server to run the scripts 

Before you deploy any of the SAP automated solutions on IBM Cloud VPC, you create a Bastion server VPC in your chosen region. The Bastion server is used for downloading and storing specific SAP solution media that are needed for later automation deployment. The Bastion server is used for both CLI deployment scenarios, as well for Schematics UI deployments.
For example, If you have an existing workspace: wks-0120 with tag=dev, and you want the workspace to run on Agent-1. Create an agent-selection-policy with the rule to pick Agent-1 when the tag == dev. Subsequently, the workspace job such as plan, apply, update, and so on will be dynamically routed to Agent-1.
* What IAM permissions needed to deploy an agent?

For information about identity and permissions, see [agent permission](https://cloud.ibm.com/docs/schematics?topic=schematics-accessagent-permissions).
* Can I use Terraform custom providers or use a proxy registry to download Terraform provider plug-ins?

Agents supports the use of custom Terraform providers sourced from a private Terraform registry with Schematics Terraform jobs. The support to use custom providers is not available in the shared multi-tenant Schematics service. It is only available with Agents. Agents does not include a local or private provider registry. The registry must be provided and configured by the user on the users private network accessible to the agents.

By default, Schematics jobs running the Terraform CLI will download Terraform provider plug-ins or Terraform modules from the public Terraform registry via the Internet or public network. When an Agent is deployed on a private network, security policies may dictate that a proxy or mirror site must be used for downloading and caching provider plug-ins. Additionally it may be desired to use custom developed Terraform providers to configure environment specific resources using Terraform.

For these usecases, Terraform allows configuration of provider download from alternate provider registries via the use of a provider_installation block in the Terraform CLI configuration. This allows customization of the Terraform default installation behavior. Review the Terraform documentation for [provider installation](https://developer.hashicorp.com/terraform/cli/config/config-fileprovider-installation) for more detail on configuring provider download.
Why can't I install a Helm chart with updated configuration values? 

Virtual Private Cloud

Classic infrastructure

  What’s happening 

When you try to install an updated Helm chart by running helm install <release_name> <helm_repo>/<chart_name> -f config.yaml, you get the following error message.

Error: failed to download "<helm_repo>/<chart_name>"

  Why it’s happening 

You might need to update your Helm installation because of the following reasons:



*  The URL to the IBM Cloud Helm repository that is configured on your local machine might be incorrect.
*  The name of your local Helm repository might not match the Helm repository name or URL of the installation command that you copied from the Helm chart instructions.
*  The Helm chart that you want to install does not support the version of Helm that you installed on your local machine.



  How to fix it 

To troubleshoot your Helm chart:



1.  List the IBM Cloud Helm repositories currently available in your Helm instance.

helm repo list
2.  Remove the IBM Cloud Helm repositories.

helm repo remove <helm_repo>
3.  Reinstall the Helm version that matches a supported version of the Helm chart that you want to install. As part of the installation, add and update the IBM Cloud Helm repositories. For more information, see [Installing Helm v3 in your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-helminstall_v3).



Now, you can follow the instructions in the Helm chart README to install the Helm chart in your cluster.
FAQs for Power Virtual Server for SAP HANA deployable architecture 

FAQs for the Power Virtual Server for SAP HANA deployable architecture. To find all FAQs for IBM Cloud®, see our [FAQ library](https://cloud.ibm.com/docs/faqs).



  What does it mean for a deployable architecture to be SAP-certified? 

SAP-certified designates that the deployable architecture creates services that are certified by SAP to run SAP HANA based systems for production. For more information, see [IBM Cloud documentation for SAP](https://cloud.ibm.com/docs/sap).





  How long does the deployment take? 

Duration for the deployment depends on the daily IBM Cloud data center utilization and on the size and number of PowerVS instances. You can assume that a deployment of one SAP system as 'SAP ready PowerVS' takes about 1 to 2 hours. SAP software installation is additional time.





  Why certain IBM Cloud data centers might not be available? 

This deployable architecture ensures certain level of quality. Every data center is verified by our quality and assurance framework before we make it available. We extend the list of supported data centers regularly after all SAP-related verifications are completed.
In this example, the virtio-win package is being installed on Red Hat Enterprise Linux version 8. Your returned output is similar to the following example:

Installed:
virtio-win-1.9.15-0.el8.noarch
2. Access the virtio-win ISO in the /usr/share/virtio-win directory.

cd /usr/share/virtio-win/
3. Use SCP to copy the virtio-win ISO file, for example virtio-win-1.9.15.iso, to use for your Windows custom image.



4. Use VirtualBox to create a virtual machine with the VHD image that you created in step 2. For more information, see [Oracle VM VirtualBox User Manual](https://www.virtualbox.org/manual/).



If you choose to use a method other than VirtualBox to create the custom image, such as VMware, you must remove all drivers that are specific to that hypervisor from the custom image.





 Customizing the virtual machine 

Complete the following steps to customize the virtual machine.



1. In Storage settings, add the Windows installation ISO and the virtio-win driver ISO as optical drives. For example, Windows-2012-install.iso and virtio-win-1.9.15.iso.
2. Start the virtual machine and begin the Windows installation. When you see the page Where do you want to install Windows? you must load all of the virtio-win drivers. You might need to clear "Hide drivers that aren't compatible with this computer's hardware" to access all of the required drivers. Then, you can select Drive 0 and continue with the installation. When the installation is complete, shut down the virtual machine and remove the optical drives that you added: Windows installation ISO and virtio-win driver ISO. You can ignore any warnings about removing an optical drive.
3. Use the default Windows updater to download and install Windows updates. Repeat the process of downloading and installing updates until no updates are available.
4.
* If you are upgrading to Speech services 4.0.6 from a previous refresh of Cloud Pak for Data version 4.0, continue to use ocs-storagecluster-cephfs. You cannot change the storage that is used in an existing deployment.



The value is specified with the storageClass property in the Speech services custom resource:


 Storage class

storageClass: "ocs-storagecluster-ceph-rbd"

The Speech services work with either version of OpenShift Container Storage. The newly recommended version has more restrictive access permissions. For more information, see



* [Installing Watson Text to Speech](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=speech-installing-watson-text)
* [Upgrading Watson Text to Speech](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=speech-upgrading-watson-text)







 31 January 2022 (Version 4.0.5) 

Version 4.0.5 has been updated
: Text to Speech for IBM Cloud Pak for Data version 4.0.5 has been updated to address installation issues. The case package version is now 4.0.6. Use this package instead of the version 4.0.5 package. For more information about installing and managing the service, see [Installing Watson Text to Speech](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=speech-installing-watson-text).

Important: Extra steps for mirrored installation are no longer necessary
: Important: The [26 January 2022 release notes](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-release-notes-datatext-to-speech-data-26january2022) included important notes for the following steps:



* Additional step for performing a mirrored installation of Minio datastore
* Additional steps for performing a mirrored installation of new next-generation models



These additional steps are no longer needed.