vania-janet/multiturn-rag-retrieval-data huggingface dataset:
2. Review the change log and verify support for your [cluster version and architecture](https://cloud.ibm.com/docs/containers?topic=containers-cos_plugin_changelog).
3. [Follow the instructions](https://cloud.ibm.com/docs/containers?topic=containers-helminstall_v3) to install the version 3 Helm client on your local machine.

If you enabled [VRF](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf) and [service endpoints](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointservice-endpoint) in your IBM Cloud account, you can use the private IBM Cloud Helm repository to keep your image pull traffic on the private network. If you can't enable VRF or service endpoints in your account, use the public Helm repository.
4. Add the IBM Cloud Helm repo to your cluster.

helm repo add ibm-helm https://raw.githubusercontent.com/IBM/charts/master/repo/ibm-helm
5. Update the Helm repos to retrieve the most recent version of all Helm charts in this repo.

helm repo update
6. If you installed the IBM Cloud Object Storage Helm plug-in earlier, remove the ibmc plug-in.

helm plugin uninstall ibmc
7. Download the Helm charts and unpack the charts in your current directory.

helm fetch --untar ibm-helm/ibm-object-storage-plugin

If the output shows Error: failed to untar: a file or directory with the name ibm-object-storage-plugin already exists, delete your ibm-object-storage-plugin directory and rerun the helm fetch command.
8. If you use OS X or a Linux distribution, install the IBM Cloud Object Storage Helm plug-in ibmc. The plug-in automatically retrieves your cluster location and to set the API endpoint for your IBM Cloud Object Storage buckets in your storage classes.
Review the change log and verify support for your [cluster version and architecture](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_plugin_changelog).
3. [Follow the instructions](https://cloud.ibm.com/docs/openshift?topic=openshift-helminstall_v3) to install the version 3 Helm client on your local machine.

If you enabled [VRF](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf) and [service endpoints](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointservice-endpoint) in your IBM Cloud account, you can use the private IBM Cloud Helm repository to keep your image pull traffic on the private network. If you can't enable VRF or service endpoints in your account, use the public Helm repository.
4. Add the IBM Cloud Helm repo to your cluster.

helm repo add ibm-helm https://raw.githubusercontent.com/IBM/charts/master/repo/ibm-helm
5. Update the Helm repos to retrieve the most recent version of all Helm charts in this repo.

helm repo update
6. If you installed the IBM Cloud Object Storage Helm plug-in earlier, remove the ibmc plug-in.

helm plugin uninstall ibmc
7. Download the Helm charts and unpack the charts in your current directory.

helm fetch --untar ibm-helm/ibm-object-storage-plugin

If the output shows Error: failed to untar: a file or directory with the name ibm-object-storage-plugin already exists, delete your ibm-object-storage-plugin directory and rerun the helm fetch command.
8. If you use OS X or a Linux distribution, install the IBM Cloud Object Storage Helm plug-in ibmc. The plug-in automatically retrieves your cluster location and to set the API endpoint for your IBM Cloud Object Storage buckets in your storage classes.
Version: %Z% %I% %W% %E% %U% [%H% %T%]

Licensed Materials - Property of IBM

5724-H72

Copyright IBM Corp. 2012, 2017 All Rights Reserved.

US Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with
IBM Corp.
@end_non_restricted_prolog@
-->
<?xml version="1.0" encoding="UTF-8"?>
<tns:mqmftCredentials xmlns:tns="http://wmqfte.ibm.com/MQMFTCredentials" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://wmqfte.ibm.com/MQMFTCredentials MQMFTCredentials.xsd">
<tns:qmgr name="<QUEUE_MANAGER_NAME>" mqUserId="<ADMIN_MQ_USER>" mqPassword="<ADMIN_API_KEY>" useMQCSPAuthentication="true" />
</tns:mqmftCredentials>

- <ADMIN_MQ_USER> - this is 'mqUsername' in the file platformApiKey.json of your queue manager.
- <QUEUE_MANAGER_NAME> - this is 'queueManagerName' in the file connection_info.json of your queue manager.
Show more



* <ADMIN_API_KEY> = 'apiKey' in the file platformApiKey.json of your queue manager.



For a detailed information on MQMFTCredentials.xml file, refer to [MFT credentials file format](https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.wmqfte.doc/mqm_credentials_format.htm) in IBM Knowledge Center.
[NLB-DNS commands](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clinlb-dns) Create and manage host names for network load balancer (NLB) IP addresses in a cluster and health check monitors for host names. 
 [Webhook-create commands](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_webhook_create) Register a webhook in a cluster. 
 [API-key commands](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-cliapi_key-commands) View information about the API key for a cluster or reset it to a new key. 
 [Credential commands](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clicredential) Set and unset credentials that allow you to access the IBM Cloud classic infrastructure portfolio through your IBM Cloud account. 
 [Infra-permissions commands](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-cliinfra-commands) Check classic IBM Cloud infrastructure permissions that are used in IBM Cloud Kubernetes Service. 
 [KMS commands](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-cliks_kms) Enable a key management service (KMS) provider in your cluster to encrypt the etcd component and Kubernetes secrets with a root key that you control. 
 [Quota commands](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_quota) View the quota and limits for cluster-related resources in your IBM Cloud account.
oc create -n management-infrastructure-management -f imconnectionsecret.yaml
3. Create a yaml file that is named imconnection.yaml based on the following to create the connection CR.

apiVersion: infra.management.ibm.com/v1alpha1
kind: Connection
metadata:
  labels:
    app.kubernetes.io/instance: connection-1
    app.kubernetes.io/managed-by: connections.infra.management.ibm.com
    app.kubernetes.io/name: example-connection
  name: imconnection
  namespace: management-infrastructure-management
spec:
  cfHost: <YOUR_IM_APPLIANCE_HOSTNAME>
  secrets:
    accessToken:
      secretKeyRef:
        key: accesstoken
        name: imconnectionsecret
Show more



* YOUR_IM_APPLIANCE_HOSTNAME Specifies the hostname of the Infrastructure management appliance server.



4. Run the oc command to create the connection.



oc apply -n management-infrastructure-management -f imconnection.yaml





 Using the OpenShift Console to create the connection: 



* IM_ADMIN_LDAP_USER Specifies the Infrastructure management LDAP admin user.
* IM_ADMIN_LDAP_PASS Specifies the Infrastructure management LDAP admin password.
* YOUR_CP4MCM_HOST The hostname of the IBM Cloud Pak for Multicloud Management console.
* YOUR_CLIENT_ID The client ID used for registering Infrastructure management as an OIDC client with IAM.
* YOUR_CLIENT_SECRET The client secret that is used for registering Infrastructure management as an OIDC client with IAM.
Note: The YOUR_CLIENT_ID and YOUR_CLIENT_SECRET values are generated when you register Infrastructure Management as an OIDC client. The IM_ADMIN_LDAP_USER must be a member of the LDAP group with the role EvmRole-super_administrator in Infrastructure management.





1. Browse to Workloads > Secrets
2.
2. IBM MQ Client

To complete this tutorial you will require the IBM MQ command line tool 'runmqsc' as well as the IBM MQ sample applications 'amqsputc' and 'amqsgetc' installed and on your PATH. If you do not have these commands, you can get them by installing the IBM MQ Client. Appendix 4 at the end of this tutorial details how to do this.



* Note. The IBM MQ Client is only available for Windows and Linux









 Setting up your terminal environment 



1. Open 2 terminal windows



* One terminal will be the admin terminal, used to administer your queue manager
* One terminal will be the app terminal, used to represent an application connecting to the queue manager and performing message 'put' and 'get' operations



2. Specify queue manager details in the admin terminal

The runmqsc command that you will use later requires an environment variable be set to identify the remote queue manager it should connect to. In the admin terminal, export MQSERVER variable with the following command:



* export MQSERVER="CLOUD.ADMIN.SVRCONN/TCP/<HOSTNAME>(<PORT>)"



* <HOSTNAME> - this is 'hostname' in the file connection_info.txt
* <PORT> - this is 'listenerPort' in the file connection_info.txt





3. Specify queue manager details in the app terminal

The amqsputc and amqsgetc commands that you will use later also requires the environment variable be set to identify the remote queue manager they should connect to. In the app terminal, export MQSERVER variable with the following command: In the app terminal, export MQSERVER variable with the following command:



* export MQSERVER="CLOUD.APP.SVRCONN/TCP/<HOSTNAME>(<PORT>)"



* <HOSTNAME> - this is 'hostname' in the file connection_info.txt
* <PORT> - this is 'listenerPort' in the file connection_info.txt





4. Specify the app username
for (int i = 0; i <= 1; i++)
{
try
{
if (MyDb2DataReader.IsDBNull(i))
{
Console.Write("NULL");
}
else
{
Console.Write(MyDb2DataReader.GetString(i));
}
}
catch (Exception e)
{
Console.Write(e.ToString());
}
Console.Write("t");

}
Console.WriteLine("");
}
MyDb2DataReader.Close();
MyDB2Command.Dispose();
MyDb2Connection.Close();
}
}
}
Show more







 ODBC or CLI 

Define a connection between a Microsoft Windows ODBC or CLI application and a Db2 Warehouse on Cloud database.



 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. In a command shell on Linux operating systems, at the Windows command prompt, or in the Db2 command window on Windows operating systems, enter the following commands:

Note: These commands create new entries in the driver configuration file (db2dsdriver.cfg) on your computer and set the connection attributes. You need to do this step only one time.



* For a connection with SSL:

db2cli writecfg add -database BLUDB -host <hostname> -port 50001 -parameter "SecurityTransportMode=SSL"

db2cli writecfg add -dsn <alias> -database BLUDB -host <hostname> -port 50001
* For a connection without SSL:

db2cli writecfg add -database BLUDB -host <hostname> -port 50000
![Queue manager details view in MQ on Cloud with connection information button hightlighted](https://cloud.ibm.com/docs-content/v1/content/3a120b16db5fdc3e70d071af8a63ce5515c1b096/mqcloud/images/mqoc_connect_app_qm_details.png)

![Queue manager connection information dialog open with JSON CCDT highlighted](https://cloud.ibm.com/docs-content/v1/content/3a120b16db5fdc3e70d071af8a63ce5515c1b096/mqcloud/images/mqoc_connect_app_qm_connection_info)
4. In the dialog click "JSON CCDT" to download the JSON CCDT description of your queue manager and save it in a suitable location:



* If you wish to confirm the contents of the channel definitions, it should be a similar format to the example below:



{
"channel": [
{
"name": "CLOUD.ADMIN.SVRCONN",
"clientConnection": {
"connection":
{
"host": "myqueuemanager.qm.us-south.mq.appdomain.cloud",
"port": 31500
}
],
"queueManager": "qm1"
},
"transmissionSecurity": {
"cipherSpecification": "ANY_TLS12_OR_HIGHER",
},
"type": "clientConnection"
},
...
]
}
Show more
5. Create a Keystore file
You need to modify parameters inside the Chrystoki2 and LunaSA Client sections as follows:

Chrystoki2 settings



* LibUnix: Name of the Chrystoki2 library on x86 Linux/UNIX operating systems. The actual name of the library depends on the type of HSM you are using.
* LibUNIX64: Name of the Chrystoki2 library on 64-bit Linux/UNIX operating systems. The actual name of the library depends on the type of HSM you are using.



LunaSA Client settings Typically no changes would be required here unless you have explicitly modified the names of these files.



* ClientPrivKeyFile: Name of the HSM client private key.
* ClientCertFile: Name of the HSM client certificate.
* ServerCAFile: Name of the HSM server certificate.



The following example shows what the file would look like if you were using IBM Cloud HSM. It provides the path to the HSM shared object, certificate and keys. Note that the naming of these files depends on the HSM library that is being used.

Chrystoki2 = {
LibUNIX = /hsm/libCryptoki2.so;
LibUNIX64 = /hsm/libCryptoki2_64.so;
}
...
LunaSA Client = {
...
ClientPrivKeyFile = /hsm/key.pem;
ClientCertFile = /hsm/cert.pem;
ServerCAFile = /hsm/cafile.pem;
...
}





 Step two: Build the HSM client image 

The HSM client image can be built with a Docker file similar to the following:



* The following Docker file is for IBM Cloud HSM. If you are not using IBM Cloud HSM, you need to build your own Docker file.
* You should be aware that this Docker file automatically accepts the Gemalto client license.
* Note that the 64 folder inside the Docker file is required for installing the HSM client.
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/checkmark-icon.svg) 
 [HashiCorp Vault HTTP API compatibility](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-vault-api) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/checkmark-icon.svg) !
If OpenShift Container Platform CLI tools are not installed on the system, you need to download, decompress, and install the OpenShift Container Platform CLI tools oc from [OpenShift Container Platform client binary files](https://mirror.openshift.com/pub/openshift-v4/clients/).







 Step 1. Generate client ID and client secret 

Create unique strings to use for client ID and client secret. You can generate base64-encoded 32 character strings. Examples:

echo There is a huge white elephant in LA zoo | base64 > client_id.txt

echo 12345678901234567890123456789012345 | base64 > client_secret.txt

Retain these values as you need them for subsequent steps. You can use the examples and the values are available in the files client_id.txt and client_secret.txt for later reference.

Note: These values in subsequent steps are referenced as <YOUR_CLIENT_ID> and <YOUR_CLIENT_SECRET>.





 Step 2. Determine IBM Cloud Pak for Multicloud Management Route 

Determine the main console URL for IBM Cloud Pak for Multicloud Management by using the cp-console route. Run the following command:

oc -n ibm-common-services get route cp-console --template '{{.spec.host}}'

Example command output: cp-console.apps.mycluster.os.fyre.ibm.com

Note: This value in subsequent steps is referenced as <YOUR_CP4MCM_ROUTE>.





 Step 3. Determine Infrastructure management Route 

Determine the main URL (HTTPd route) of the Infrastructure management installation. Since Infrastructure management is not yet installed, the route is an assumed route as the eventual route doesn't exist yet.

This can be derived by appending the Infrastructure management installation name (default: inframgmtinstall) to the cluster domain.

Example: inframgmtinstall.apps.mycluster.os.fyre.ibm.com

Note: This value in subsequent steps is referenced as <YOUR_IM_HTTPD_ROUTE>.
* [Administering a queue manager using runmqsc from an IBM MQ client](https://cloud.ibm.com/docs/services/mqcloud?topic=mqcloud-mqoc_admin_mqcliexp)







 Tasks on the MQ on Cloud queue manager 

As mentioned earlier, enabling security on an MQ channel requires configuring a cipher spec, and exchanging public certificates between the queue manager and the client (and for Mutual TLS, also between the client and the queue manager). The configuration of the cipher spec may be done using any of the three standard MQ administration tools. The method for each is described below, so pick your preferred tool and follow the instructions. For access to the user credentials and certificate, the MQ on Cloud service console is required.



 Using the MQ on Cloud service console to gather credentials and certificates 



1. Open the MQ on Cloud service console and locate your queue manager.
2. Gather the admin user's credentials When you first select the Administration tab for your queue manager, your user will be given permissions as the administrator. You should note the user name, and follow the steps to download the API key (which is the password you will use to connect later).
3. Create an application user for the JMS and C applications Select the Application credentials tab for your queue manager, and follow the process to add a new application credentials. Save the generated API key, which is the password for applications to connect with.
4. Download the JSON CCDT description of your queue manager Click the Connection Info button, and follow the instructions to download the CCDT form of the connection info. You might also want to download the text version, which is easier to read, and a useful source of the queue manager name and url.

The CCDT file downloaded should look like this:

{
"channel": [
{
"name": "CLOUD.ADMIN.SVRCONN",
"clientConnection": {
"connection":
{
"host": "myhost.cloud.ibm.com",
"port": 31605
}
],
: (Optional) Select the client that you want to log in. Valid values are docker and podman. If this option is not used and Docker is installed, the default is docker; if Docker is not installed, the default is podman.





 Example 

To log in to the registry with Podman, run the following command.

ibmcloud cr login --client podman







 ibmcloud cr manifest-inspect 

View the contents of the [manifest](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_manifest) for an image. You can reference the image that you want to inspect either by digest or by tag.

ibmcloud cr manifest-inspect [--quiet | -q ] IMAGE



 Prerequisites 

To find out about the required permissions, see [Access roles for using Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iamaccess_roles_using).





 Command options 

IMAGE
: The name of the image for which you want to inspect the manifest. You can identify images by using either the digest <dns>/<namespace>/<repo>@<digest> or by tag <dns>/<namespace>/<repo>:<tag>. Where <dns> is the domain name, <namespace> is the namespace, <repo> is the repository, <digest> is the digest, and <tag> is the tag.

To find the names of your images, run one of the following commands:



* To identify your image by digest, run the ibmcloud cr image-digests command. Combine the content of the Repository column (repository) and the Digest column (digest) separated by an at (@) symbol to create the image name in the format repository@digest.
* To identify your image by tag, run the ibmcloud cr image-list command. Combine the content of the Repository column (repository) and Tag column (tag) separated by a colon (:) to create the image name in the format repository:tag.



--quiet, -q
Upgrading HCX components 

Upgrading VMware HCX™ is a process that uses the client web UI on the client-side HCX Manager update and the cloud web user interface on the cloud side HCX Manager update.

You must upgrade both sides as any fleet component updates cause both to redeploy the fleet components with the level of code that is installed on HCX Manager.

If VMware® Support asks for the system ID, provide both the client and cloud side. Use SSH into HCX Manager (client or cloud) and run cat /common/location to locate the System ID.



  Related links 



*  [Glossary of HCX components and terms](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcxclient-components)
*  [Preparing the installation environment](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcxclient-planning-prep-install)
*  [HCX Client deployment](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcxclient-vcs-client-deployment)
*  [HCX on-premises Service Mesh](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcxclient-vcs-mesh-deployment)
*  [VMware Hybrid Cloud migrations](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcxclient-migrations)
*  [Monitoring parameters and components](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcxclient-monitoring)
SSH to HCX Manager by using the admin account and the supplied password.
2. Run the su – command and enter the password of the root user (same as admin password) to change to root.
3. Change the directory to /opt/vmware/bin and run the ./ccli command. If this attempt is not successful because the environment is not set up for root, run the ./ccliSetup.pl command.
4. Run the list command within the ccli shell to list the fleet components registered with HCX Manager.
5. Specify the fleet ID for the ccli by typing the ID listed for the fleet component. For example, go 8.
6. Run the debug remoteaccess enable command to connect by using SSH to the wanted fleet component.
7. Exit ccli and connect by using SSH to the IP address of the SSH-enabled fleet component.
8. Continue to troubleshoot.
9. Return to the ccli and disable the ssh service for the component.
10. If necessary, use the hc ccli command to run a health check on the components.









 Destination hardware compatibility issues 

vMotion migration can be an issue when the client source side is of newer hardware version and vSphere release than the cloud. Since replication-based migration copies data to a newly built virtual machine (VM) on the destination side, changing the migration type to “Bulk Migration” allows the migration to succeed in most cases.





 Stretched L2 Concentrator issues 

If the L2C loses connectivity it reconnects automatically after the network connectivity is restored. Use the ccli shell to check health and operation. After SSH is enabled and the L2C is connected, run the ip tunnel and ip link |grep t_ commands to view the status of the tunnels.





 Related links 



* [Glossary of HCX components and terms](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcxclient-components)