vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Prerequisites](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_rh_tutorialvpc_rh_prereqs)
* [Create a cluster in a VPC](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_rh_tutorialvpc_rh_create_vpc_cluster)
* [Deploy an app to your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_rh_tutorialvpc_rh_app)
* [Set up a VPC load balancer to expose your app publicly](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_rh_tutorialvpc_rh_vpc_lb)
* [What's next?](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc_rh_tutorialvpc_rh_next)







 Installing the CLI and API 

[Installing the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-cli-installcli-install)



* [Understanding the CLI tools](https://cloud.ibm.com/docs/openshift?topic=openshift-cli-installcli-understand)
* [Run the installation command](https://cloud.ibm.com/docs/openshift?topic=openshift-cli-installcli-install-include-step1-install-idt)
* [Verify the installation](https://cloud.ibm.com/docs/openshift?topic=openshift-cli-installcli-install-include-step2-verify-idt)
VPC infrastructure contains a number of Infrastructure-as-a-Service (IaaS) offerings, including Virtual Servers for VPC. Use the following information to understand a simple use case for planning, creating, and configuring resources for your VPC, and learn about more VPC overviews and VPC tutorials. For more information about VPC, see [Getting started with Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started).





 SAP on IBM Cloud® 

SAP NetWeaver is the core foundation of the SAP technology stacks and is the platform that is used for ABAP and Java applications. SAP system can be installed and configured in IBM Cloud for various system and database types.

For more information about SAP system architectures on IBM Cloud VPC, see the infrastructure reference architectures for SAP for each supported database type. For example, [SAP NetWeaver 7.x on UNIX with Db2 on IBM Cloud® VPC](https://cloud.ibm.com/docs/sap?topic=sap-sap-refarch-nw-db2) is the dedicated reference architecture for this SAP solution.

Manually deploying a VPC and installing an SAP system can be time-consuming. The Terraform 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 Terraform scripts solution provides the automated deployment of a single host with SAP Netweaver with Db2 on the Red Hat Enterprise Linux® 7.6 for SAP Applications.

The SAP installation media that are used for this deployment are the default media for SAP Netweaver 7.5 with Db2 10.5FP7 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 several IT tasks. Ansible is used for automating the installation of an SAP Netweaver with Db2. For more information about Ansible, see the [Ansible Documentation](https://docs.ansible.com/ansible/latest/index.html).
[Figure 1. Standard installation](https://cloud.ibm.com/docs-content/v1/content/f89cc64b006ca59b35404693959c83d5747fee3e/sap/images/refarch-sap-hana-single-host-all.svg)

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

For example, SAP NetWaver (ABAP or JAVA stack) has a dedicated reference architecture that is running on SAP HANA or AnyDB databases that are published on IBM cloud [SAP NetWeaver on UNIX architecture diagram](https://cloud.ibm.com/docs/sap?topic=sap-sap-refarch-nw-sybasesap-netweaver-arch-diag-syb).

Manually deploying a VPC and installing an SAP system can be time-consuming. The Terraform 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 Terraform scripts solution provides the automated deployment of a single host with SAP Netweaver with ASE SYB on the Red Hat Enterprise Linux® 8.4 and SUSE 15.3 for SAP Applications.

The SAP installation media that are used for this deployment are the default media for SAP AAS of NetWeaver 7.x (ABAP stack) on SUSE/RHEL with ASE SYB 16 as distributed instance available at the SAP Support Portal under INSTALLATION AND UPGRADE area. You provide the installation media as an input parameter for Terraform for your SAP AAS solution chosen on dedicated kits storage from bastion server.





 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.
Make sure that the policy for pulling images in your cluster supports pulling images from icr.io. For example, if you are installing the private worker framework on IBM Cloud Private, add those policies by using the IBM Cloud Private Web console. For more information about managing image security enforcement by using the IBM Cloud Private Web console, see [Enforcing container image security](https://www.ibm.com/support/knowledgecenter/en/SSBS6K_3.1.0/manage_images/image_security.html). For more information about managing image security enforcement by using Porteris, see [Portieris Policies](https://github.com/IBM/portieris/blob/master/POLICIES.md).

The following example shows how to use the IBM Cloud CLI to create the ClusterImagePolicy:

If you use Portieris as an admission controller, you might need to change the apiVersion in the example to portieris.cloud.ibm.com/v1.

cat <<EOF | kubectl apply -f -
apiVersion: securityenforcement.admission.cloud.ibm.com/v1beta1
kind: ClusterImagePolicy
metadata:
name: iks-private-registries
spec:
repositories:
- name: ".icr.io/"
policy:
EOF





 Why is my Delivery Pipeline Private Worker not listed? 

 What’s happening 

My private worker agent is listed on the cluster with a status of inactive, but it is not listed on the private worker integration Overview page.

 Why it’s happening 

The API key that was used to install the worker agent might not be included in the ServiceID that is used by the private worker integration.

 How to fix it 

Remove the misconfigured worker agent from the cluster and install the worker agent again. Make sure that the API key that is included in the installation command also exists in the ServiceId that is used in the same installation command. Use the link for the ServiceId that is available on both the private worker integration page and the Identity and Access Management (IAM) page to generate a valid API key.
Troubleshooting for Pipeline Private Workers 

General problems with using Pipeline Private Workers might include Kubernetes cluster and kubectl version issues. In many cases, you can recover from these problems by following a few easy steps.



 Why is my Delivery Pipeline Private Worker inactive? 

Private workers within a pool of workers can be in one of the following states:



* Active with the current, supported version of private workers
* Inactive with an unsupported version of private workers
* Inactive



 What’s happening 

Your private worker is inactive. Inactive private workers cannot handle incoming run requests. Pipeline stages that use an inactive private worker cannot complete.

 Why it’s happening 

There is an issue with your Kubernetes cluster and the worker cannot be contacted. Or, the version of the private worker that you are running is no longer supported.

 How to fix it 

To activate your Delivery Pipeline private worker, [install](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-install-private-workersinstall_pw) the private worker again. Then, [register](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-install-private-workersregister_pw) the Delivery Pipeline private worker on the Kubernetes cluster again.





 I tried to install support for Delivery Pipeline Private Workers in Kubernetes. Why did the installation fail? 

If there is an issue with the version of kubectl that you are running on the client machine, the Delivery Pipeline Private Worker installation fails.

 What’s happening 

After you try to install support for private workers in Kubernetes, an error message is displayed to indicate that there is a schema mismatch and the installation fails.

SchemaError(io.k8s.apimachinery.pkg.apis.meta.v1.APIGroup): invalid object doesn't have additional properties

 Why it’s happening 

There is a mismatch between the versions of kubectl that you are running on the Kubernetes server and the Kubernetes client.
"host": "qm1-1234.qm.us-south.mq.appdomain.cloud",
"port": 31500
}
],
"queueManager": "QM1"
},
"transmissionSecurity": {
"cipherSpecification": "ANY_TLS12_OR_HIGHER"
},
"type": "clientConnection"
}
]
}
Show more

The cipher specification in the JSON CCDT example above has been specified as ANY_TLS12_OR_HIGHER, which allows the runmqsc client to negotiate a permitted cipher with the queue manager within the family of TLS v1.2 ciphers, based on what ciphers the channel is configured to permit. For maximum flexibility the queue manager channel can also be configured as ANY_TLS12_OR_HIGHER which allows the client and server to negotiate between them.





 Configure the necessary environment variables for the runmqsc environment 

We will configure environment variables to instruct the runmqsc client to use the JSON CCDT to obtain the queue manager connection details, which includes the name of the channel cipher spec that we defined in the previous step.



1. Open a command prompt window and navigate to the MQ bin directory of your installation. The location of this will depend on your operating system, for example;



Table 1. Installation file location for different Operating Systems

 Operating System file location 

 Linux full MQ installation /var/mqm/bin 
 Windows C:Program FilesIBMMQbin 
 Linux/Mac, using the client installation /mytoolkit/IBM-MQ-Toolkit-Mac-x64-9.1.2.0/bin 



2. Set the MQCCDTURL environment variable to instruct the runmqsc client to read the JSON CCDT, the MQCCDTURL variable is a URL pointing to the JSON CCDT file.



* MQCCCDTURL is the full file path from the system root to the ccdt file.

 Linux/MacOS
: Important: Before upgrading to Watson Speech services version 4.6.3 or 4.6.4, you must make a backup of your data. Preserve the backup in a safe location. For more information about backing up your Watson Speech services data, see Backing up and restoring Watson Speech services data in [Administering Watson Speech services](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-administering). That topic also includes information about restoring your data if that becomes necessary.

Defect fix: You can now change the installed models and voices with the advanced installation options
: Defect fix: During installation, you can now specify different models or voices with the advanced installation options of the command-line interface. Previously, the service always installed the default models and voices. The limitation continues to apply for Watson Speech services versions 4.6.0, 4.6.2, and 4.6.3. For information about installing models and voices, see Specifying additional installation options in [Installing Watson Speech services](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-installing).

Setting load balancer timeouts
: Watson Speech services require that you change the load balancer timeout settings for both the server and client to 300 seconds. These settings ensure that long-running speech recognition requests, those with long or difficult audio, have sufficient time to complete. For more information, see Information you need to complete this task in [Installing Watson Speech services](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-installing).

Documentation updates for IBM SPR symbols
: The overview documentation for IBM SPR symbols has been updated to clarify the use of multi-character symbols. For more information, see [Speech sound symbols](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-symbolsintro-SPRs-symbols).

Security vulnerabilities addressed
: The following security vulnerabilities have been fixed:
The Terraform scripts solution provides the automated deployment of a single host with SAP NetWeaver with Db2 3-tier on the Red Hat Enterprise Linux® and SUSE for SAP Applications (releases specified in [README file](https://github.com/IBM-Cloud/sap-netweaver-abap-db2-distributed/blob/main/README.md).

The SAP installation media that are used for this deployment are the default media for SAP NetWeaver 7.5 with Db2 (releases specified in [README file](https://github.com/IBM-Cloud/sap-netweaver-abap-db2-distributed/blob/main/README.md) available at the SAP Support Portal in the 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 Db2 3-tier. 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 (bastion) server because the deployment (bastion) 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 (bastion) server and local workstation, you must download the SAP kits to the temporary storage assigned to you on the deployment (bastion) server. Ansible installs the kits for you.
Why does installing the IBM Cloud Object Storage plug-in fail? 

Virtual Private Cloud

Classic infrastructure

 What’s happening 

When you install the ibm-object-storage-plugin, the installation fails with an error similar to the following:

Error: rendered manifest contains a resource that already exists. Unable to continue with install. Existing resource conflict: namespace: , name: ibmc-s3fs-flex-cross-region, existing_kind: storageClass, new_kind: storage.k8s.io/v1, Kind=StorageClass
Error: plugin "ibmc" exited with error

 Why it’s happening 

During the installation, many different tasks are executed by the IBM Cloud Object Storage plug-in such as creating storage classes and cluster role bindings.

Some resources might already exist in your cluster from previous IBM Cloud Object Storage plug-in installations and were not properly removed when you removed or upgraded the plug-in.

 How to fix it 

Delete the resource that is display in the error message and retry the installation.



1. Delete the resource that is displayed in the error message.

kubectl delete <resource_kind> <resource_name>

Example for deleting a storage class resource:

kubectl delete storageclass <storage_class_name>
2. [Retry the installation](https://cloud.ibm.com/docs/containers?topic=containers-storage_cos_install).
3. If you continue to see the same error, get a list of the resources that are installed when the plug-in is installed. Get a list of storage classes that are created by the ibmcloud-object-storage-plugin.

kubectl get StorageClass --all-namespaces -l app=ibmcloud-object-storage-plugin -o jsonpath='{range .items[]}{.metadata.name}{"n"}{end}'
4. Get a list of cluster role bindings that are created by the ibmcloud-object-storage-plugin.
SAP Commerce 

SAP Commerce (formerly SAP Hybris Commerce) is part of the Customer Experience (CX) portfolio under the SAP C/4HANA suite.

Due to the design and business purpose and the nature of SAP Commerce, the installation, deployment, and additional development code is much more suited to a DevOps way of working. Project teams often use agile SDLC/PM methodologies (such as Scrum or SAFe). As an example of the flexibility, SAP Commerce runs across multiple different Operating Systems that are supported by SapMachine, a downstream OpenJDK release that is maintained and supported by SAP.

Therefore, deployments of SAP Commerce are available in different variants; we detail the following to assist understanding what IBM Cloud® for SAP can provide:



* SAP Commerce "on-premises edition" variants:



* SAP Commerce "on-premises edition" with on-premises data center
* SAP Commerce "on-premises edition" on Cloud IaaS



* SAP Commerce Cloud (PaaS solution) variants:



* SAP Commerce Cloud hosted on SAP Infrastructure (also known as CCv1 using VMs)
* SAP Commerce Cloud in the Public Cloud (also known as CCv2 using Kubernetes)





Within the IBM Cloud® for SAP portfolio, infrastructure is supported for SAP Commerce "on-premises edition" on Cloud IaaS.

This solution involves an installation of the SAP Commerce software onto Cloud IaaS, according to SAP installation and best practice guidance:



* [SAP Commerce (on-premises) Installation and Upgrades](https://help.sap.com/viewer/a74589c3a81a4a95bf51d87258c0ab15/2005/en-US/8bf5a611866910149242e1a3a41eb9af.html)
* [SAP Commerce (on-premises) Architecture options are Single Node, Cluster Node, and Multi-Tenant Node](https://help.sap.com/viewer/b490bb4e85bc42a7aa09d513d0bcb18e/1905/en-US/8b5588d8866910149d4eb5f99c75b6b4.html)
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-workersinstall_pw) again.
2. [Register the private worker](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-install-private-workersregister_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 SAP installation media that are used for this deployment are the default media for SAP Netweaver 7.5 with Db2 10.5FP7 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 several IT tasks. Ansible is used for automating the installation of an SAP Netweaver with Db2. 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, where 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.
To cancel the license charge, you must delete the license separately.

For more information, see [Managing Veeam licenses](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam_managing_licenses).
* Order a new Veeam stand-alone license

An order is placed with the number of VMs to license. A license key is not displayed because no unique keys are generated.

For more information, see [Managing Veeam licenses](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam_managing_licenses).
* Delete a Veeam stand-alone license

When you delete a Veeam stand-alone license, the license charge is canceled. Deleting the license has no effect on the Veeam installation.

When you want to increase your usage, delete your old stand-alone instance after you order a new instance to avoid unnecessary charges.

For more information, see [Managing Veeam licenses](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam_managing_licenses).







 Considerations for installing and deleting Veeam licenses 

The following information about licenses applies to both Veeam and Veeam 9.5u4b.

For Veeam 10 and Veeam, Veeam licenses are installed and deleted in a different way than previous Veeam versions.

After you place an order for Veeam, a Veeam stand-alone license is automatically deployed. The Veeam service installation begins only after the stand-alone license order completed successfully. After that, depending on what you ordered, Veeam is installed on the bare metal server, VM, or VSI.

When you uninstall Veeam, the stand-alone license instance is not deleted. You must delete it separately to avoid being charged for the stand-alone license.

Consider the following when you plan to upgrade your Veeam usage.