vania-janet/multiturn-rag-retrieval-data huggingface dataset:
(https://cloud.ibm.com/docs/containers?topic=containers-istio-aboutistio_ov_components)
* [Limitations](https://cloud.ibm.com/docs/containers?topic=containers-istio-aboutistio_limitations)



[Setting up Istio](https://cloud.ibm.com/docs/containers?topic=containers-istioistio)



* [Installing the Istio add-on](https://cloud.ibm.com/docs/containers?topic=containers-istioistio_install)



* [Installing the Istio add-on from the console](https://cloud.ibm.com/docs/containers?topic=containers-istioistio_install-console)
* [Installing the Istio add-on with the CLI](https://cloud.ibm.com/docs/containers?topic=containers-istioistio_install-cli)



* [Installing the istioctl CLI](https://cloud.ibm.com/docs/containers?topic=containers-istioistioctl)
* [Customizing the Istio installation](https://cloud.ibm.com/docs/containers?topic=containers-istiocustomize)
* [Updating the Istio add-on](https://cloud.ibm.com/docs/containers?topic=containers-istioistio_update)



* [Updating the minor version of the Istio add-on](https://cloud.ibm.com/docs/containers?topic=containers-istioistio_minor)
* [Updating the istioctl client and sidecars](https://cloud.ibm.com/docs/containers?topic=containers-istioupdate_client_sidecar)



* [Uninstalling Istio](https://cloud.ibm.com/docs/containers?topic=containers-istioistio_uninstall)
* Classic multizone clusters: Ensure that you enable a [Virtual Routing and Forwarding (VRF)](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf) for your IBM Cloud infrastructure account. To enable VRF, see [Enabling VRF](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf). To check whether a VRF is already enabled, use the ibmcloud account show command. If you can't or don't want to enable VRF, enable [VLAN spanning](https://cloud.ibm.com/docs/vlans?topic=vlans-vlan-spanningvlan-spanning). To perform this action, you need the Network > Manage Network VLAN Spanning[infrastructure permission](https://cloud.ibm.com/docs/containers?topic=containers-access-credsinfra_access), or you can request the account owner to enable it. To check whether VLAN spanning is already enabled, use the ibmcloud ks vlan spanning get --region <region>[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_vlan_spanning_get).





 Installing the Istio add-on from the console 



1. In your [cluster dashboard](https://cloud.ibm.com/kubernetes/clusters), click the name of the cluster where you want to install the Istio add-on.
2. Navigate to the Add-ons section.
3. On the Managed Istio card, click Install.
4. Click Install again.
5. On the Managed Istio card, verify that the add-on is listed.







 Installing the Istio add-on with the CLI 

[Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)



2.
x safenet/config/
x safenet/gateway/
x safenet/SAClient_600.tgz
x safenet/SAClient_622.tgz
x safenet/install_client.sh
x safenet/gateway/start_safenet_gw
x safenet/gateway/gw_delay
x safenet/config/safenet_config
x safenet/config/Chrystoki.conf
3. Navigate to the /var/safenet directory and confirm the folders and files were transferred:

extracted
root@IBMADC690867-s6dr cd safenet
root@IBMADC690867-s6dr pwd
/var/safenet

root@IBMADC690867-s6dr ls
SAClient_600.tgz config install_client.sh
SAClient_622.tgz gateway
4. Execute the installation script using version 622:

root@IBMADC690867-s6dr install_client.sh -v 622

Current Version: 622
Installing Version: 622
Starting to extract SAClient_622.tgz file.
Extracted SAClient_622.tgz file.
Removing SAClient_622.tgz file.



Now follow the configuration steps document available online on Citrix edocs.

5. Confirm the creation of the safenet directory:

root@IBMADC690867-s6dr ls
SAClient_600.tgz gateway installation.log
config install_client.sh safenet
6. Navigate to the /var/safenet/config/ directoy and execute the safenet_config script:

root@IBMADC690867-s6dr cd /var/safenet/config/
root@IBMADC690867-s6dr pwd
/var/safenet/config
You must ensure that your cluster has sufficient resources and is configured to use supported storage. You can choose one of the following storage options:



* Single zone VPC Gen2 cluster with storage OpenShift® Data Foundation
* Multi zone VPC Gen2 cluster with storage OpenShift® Data Foundation



You must also ensure that your cluster has sufficient resources and is configured to use supported storage.







 Step 1. Assign the license 

If you don't already have a license, you can:



* Purchase a license through [IBM Passport Advantage](https://www.ibm.com/software/passportadvantage/index.html).
* [Register](https://www.ibm.com/account/reg/us-en/signup?formid=urx-42212) for a 60-day trial license of IBM Cloud Pak for Data.



Important: The trial is for IBM Cloud Pak for Data software only. The trial does not include entitlement to the Red Hat OpenShift Container Platform.

To assign your license, follow these steps:



1. Log in to your [IBM Cloud account](https://cloud.ibm.com).
2. If you don't see any licenses to assign, navigate to Manage > Account and then click Licenses and entitlements in the navigation menu.
3. If there are no licenses to assign on the Licenses and entitlements page, click Check IBM Passport Advantage.
4. Select the appropriate license and click Assign.







 Step 2. Configure your installation environment 

Specify where you want to install IBM Cloud Pak for Data:



1. Select the Red Hat OpenShift on IBM Cloud cluster where you want to deploy IBM Cloud Pak for Data.
2. Enter or select the Red Hat OpenShift on IBM Cloud project where you want to deploy IBM Cloud Pak for Data.







 Step 3. Configure your workspace 

Specify how you will track and manage your installation:



1. Enter or select a name for the installation.
2. Consider changing the default resource group.
3. Specify any tags that you want to use for the installation.
Instantiation updates the ledger with the initial data that is used by the smart contract, and then starts smart contract pods. The peers can then use the smart contract.



* Only one network member needs to instantiate a smart contract.
* If a peer with a smart contract installed joins a channel where the same smart contract version has already been instantiated, the smart contract container starts automatically.



In this tutorial, we go through the steps to use the IBM Blockchain Platform console to manage the deployment of smart contracts on your network:



* [Write and package your smart contract](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v14ibp-console-smart-contracts-write-package).
* [Install smart contracts on your peers](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v14ibp-console-smart-contracts-install).
* [Instantiate them on channels](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v14ibp-console-smart-contracts-instantiate).
* [Specify endorsement policies](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v14ibp-console-smart-contracts-endorse).
* [Upgrade the smart contract policies and code](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v14ibp-console-smart-contracts-upgrade).





 Before you begin 

Before you can install a smart contract, ensure that you have the following things ready.
<swpm>/sapinst SAPINST_USE_HOSTNAME=${ASCS_vh}



* Install ERS instance on NODE2 by using the virtual hostname ${ERS_vh} that is associated with the virtual IP address for ERS:



<swpm>/sapinst SAPINST_USE_HOSTNAME=${ERS_vh}
* Install instances outside the cluster.



* DB instance
* PAS instance
* AAS instances









 Installing and setting up the RHEL HA Add-On cluster 

Install and set up the RHEL HA Add-On cluster according to [Implement RHEL HA Add-On cluster on Power Systems Virtual Server](https://cloud.ibm.com/docs/sap?topic=sap-ha-rhel).

Configure and test fencing as described in [Creating the fencing device](https://cloud.ibm.com/docs/sap?topic=sap-ha-rhelha-rhel-create-fencing-device).





 Preparing ASCS and ERS instances for the cluster integration 

Use the following steps to prepare the SAP instances for the cluster integration.



 Removing the ASCS and ERS entries from the SAP services files 

Adjust the SAP services file /usr/sap/sapservices to prevent automatic start of the sapstartsrv instance agent for both ASCS and ERS instance after a reboot.

On both nodes, edit the SAP services file and remove or comment out the sapstartsrv entries for both ASCS and ERS.

vi /usr/sap/sapservices

Example:

LD_LIBRARY_PATH=/usr/sap/S01/ASCS01/exe:$LD_LIBRARY_PATH;export LD_LIBRARY_PATH;/usr/sap/S01/ASCS01/exe/sapstartsrv pf=/usr/sap/S01/SYS/profile/S01_ASCS01_cl-sap-scs -D -u s01adm





 Creating mount points for the instance file systems on the takeover node 

Create the mount points for the instance file systems and adjust their ownership.
project.config.install Install (deploy) a project config. 
 project.config.uninsall Uninstall (destroy) a project config. 



For a complete list of custom request and response parameters for each event, see the [Project API](https://cloud.ibm.com/apidocs/projects). The update actions don't provide information about the delta, only the new value is provided.





 Viewing events 

Events that are generated by an instance of the IBM Cloud Projects service are automatically forwarded to the IBM Cloud Activity Tracker service instance that is available in the same location.

IBM Cloud Activity Tracker can have only one instance per location. To view events, you must access the web UI of the IBM Cloud Activity Tracker service in the same location where your service instance is available. For more information, see [Launching the UI](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-launch).
Depending on your order, server is available for use within one to four hours after your order is submitted. You can check the Device Details from the IBM Cloud console (Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > Resource List > Devices) for the status of the provisioning steps. Click the Device Name that matches your device's Hostname and Domain to see its status.





 Bring your own license 

If you have your own operating system license, you install it on your Bare Metal Servers based on the vendor's instructions. For more information, see [The no OS option](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-bm-no-osbm-no-os).





 Access your server 

A public IP is used for remote access, so you can connect to your server through an ssh client (for example, PuTTY on Microsoft Windows). Use the public IP address displayed in the Device List (under the Devices menu) for your device. The root password for your server is also displayed. Click Show Password to see it.





 Partitioning and file systems 

For the single-node example, you ordered a server with one logical disk (on RAID 1). The server has one mirrored disk with the operating system (OS) and one large root file system equal to the total size of the disk (with some space used for /boot). The file system layout in this example is just one possible approach. For production use, follow the sizing information for your system as other layouts might better meet your needs or SAP requirements.



1. Create the three directories required for the SAP installation, /sapmnt, /usr/sap, and /db2.



[root@e2e1270 ] mkdir /sapmnt
[root@e2e1270 ] mkdir /usr/sap
[root@e2e1270 ] mkdir /db2

Your IBM Cloud® Bare Metal Servers is now ready for external storage and the installation of your SAP applications and software.
Installing and managing Text to Speech for IBM Cloud Pak for Data 

IBM Cloud Pak for Data

To install IBM Watson® Text to Speech for IBM Cloud Pak® for Data, see [Watson Speech services on IBM Cloud Pak for Data](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-watson-speech). That page provides an overview of the Watson Speech services on IBM Cloud Pak for Data and includes links to all installation and management topics for version 4.6.x of the services:



* [Preparing to install Watson Speech services](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-preparing-install)
* [Installing Watson Speech services](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-installing)
* [Post-installation setup for Watson Speech services](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-post-installation-setup)
* [Upgrading Watson Speech services](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-upgrading)
* [Administering Watson Speech services](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-administering)
* [Uninstalling Watson Speech services](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-uninstalling)





 Installing and managing previous versions 

For information about installing and managing previous versions of the Watson Speech services, see the following pages:
[root@sap-app-vsi ] systemctl enable uuidd
[root@sap-app-vsi ] systemctl start uuidd
3. Install the tcsh package required for C shell support

[root@sap-app-vsi ] yum install tcsh







 Installing the IBM Cloud Metrics Collector for SAP 

SAP requires the installation of the IBM Cloud Metrics Collector for SAP to analyze your infrastructure if a support case is submitted. Install the collector by using the instructions in [IBM Cloud Metrics Collector for SAP](https://cloud.ibm.com/docs/sap?topic=sap-ibm-metrics-collector-for-sap-linux).





 Downloading your SAP software 

Log in to the SAP Service Marketplace ([https://support.sap.com/swdc](https://support.sap.com/swdc)) and download the required digital versatile discs (DVDs) to a local share drive and then transfer the DVDs to your provisioned server. Alternative option, download the SAP Software Download Manager, install it on your target server and directly download the DVD images to the server. For more information about the SAP Software Download Manager, see [http://service.sap.com](http://service.sap.com/).

You need an S-User ID and the Download Software authorization when you download the DVDs from the SAP Service Marketplace. To request an S-USer ID, see the [SAP Support Portal](https://support.sap.com/en/index.html).





 Preparing for SAP’s Software Provisioning Manager (SWPM) 

Depending on your network bandwidth and latency, you might need to run the SAP SWPM GUI remotely in a virtual network computing (VNC) session. 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.
Download the current version of the zypper (for SLES) or yum (for RHEL).
3. Install the ndctl software for your system:



* For SLES:

$ zypper in ndctl

Refreshing service
'SMT-https_susesapsmtamr_service_networklayer_com'.
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following 2 NEW packages are going to be installed:
libndctl6 ndctl
* For RHEL:

$ yum install ndctl

Refreshing service
'SMT-https_susesapsmtamr_service_networklayer_com'.
Loading repository data...
Reading installed packages...
Resolving package dependencies...



4. List the available regions for your system:

$ ndctl list -R -v

[ ! ! ! ! !
Installing and managing Speech to Text for IBM Cloud Pak for Data 

IBM Cloud Pak for Data

To install IBM Watson® Speech to Text for IBM Cloud Pak® for Data, see [Watson Speech services on IBM Cloud Pak for Data](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-watson-speech). That page provides an overview of the Watson Speech services on IBM Cloud Pak for Data and includes links to all installation and management topics for version 4.6.x of the services:



* [Preparing to install Watson Speech services](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-preparing-install)
* [Installing Watson Speech services](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-installing)
* [Post-installation setup for Watson Speech services](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-post-installation-setup)
* [Upgrading Watson Speech services](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-upgrading)
* [Administering Watson Speech services](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-administering)
* [Uninstalling Watson Speech services](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-uninstalling)





 Installing and managing previous versions 

For information about installing and managing previous versions of the Watson Speech services, see the following pages:
wget -O jq https://github.com/stedolan/jq/releases/download/jq-1.6/jq-linux64

chmod +x ./jq

mv jq /usr/bin

For more information, see [Download jq](https://stedolan.github.io/jq/download/).
4. Run the following commands to enable navigation to your Infrastructure management instance:

chmod 755 ./automation-navigation-updates.sh

./automation-navigation-updates.sh -p management-infrastructure-management



* The automation-navigation-updates.sh expects the default namespace management-infrastructure-management. If you use a different namespace to install Infrastructure management, you must pass the namespace as a parameter when you run the command. Example:



./automation-navigation-updates.sh -p <namespace>
5. Verify that the Infrastructure management instance is in the IBM Cloud Pak console navigation menu. From the IBM Cloud Pak for Multicloud Management menu, click Automate infrastructure > Infrastructure management.





 Results 

You successfully installed and configured Infrastructure management and integrated Infrastructure management with IBM Cloud Pak for Multicloud Management in IBM Cloud.
Installing a custom Cloud Pak for Data connector 

After you have compiled and packaged your custom connector, you need to install it to your Discovery instance.

IBM Cloud Pak for Data

IBM Cloud Pak for Data only

This information applies only to installed deployments.

Discovery provides a script named manage_custom_crawler.sh for installing and uninstalling custom connectors. The script is located in the scripts directory of the expanded custom-crawler-docs.zip file as described in [Understanding the custom-crawler-docs.zip file](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-devccs-grok-crawler-zip-file).



 Installing a connector 

You can install your custom connector to your Discovery instance by performing the following steps.



1. Ensure that you have completed all steps to create a custom connector up to and including the steps listed in [Compiling and packaging the example connector](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-assemblecompile-package-connector).
2. Run the following command from the directory on your local machine where you created and compiled your custom connector:

bash scripts/manage_custom_crawler.sh --endpoint {endpoint} --token {access token} deploy -n {crawler name} -f {built_connector_zip_file}

where you specify values for the following variables:



* endpoint: URL for your service instance. You can get this value from the Access information section of the service instance overview page in the IBM Cloud Pak for Data administrative console.
* access token: Bearer token that is required to access the endpoint. You can get this value from the same page as the endpoint.
* crawler name: (Optional) Name that you specified for the crawler.
* {built_connector_zip_file} is the name of the file you created in [Compiling and packaging the example connector](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-assemblecompile-package-connector).



For example:
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 more information about how to create the Bastion server and its corresponding VPC, see [Automate SAP Bastion server – SAP media storage repository](https://cloud.ibm.com/docs/sap?topic=sap-sap-bastion-server).

After bastion VPC deployment is complete, you must download the SAP Kits for the SAP AAS type and DB you want to deploy to the temporary storage assigned to you on the Bastion Server.