vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If the gateways used for private network access and public network access are different, use the default gateway to allow for public network access and the on-premises HCX Manager Admin Console to create a static route for private network access.
4. After the HCX Manager deployment is completed, use the HCX Manager Admin Console to activate the on-premises HCX Manager. To obtain an activation key for the on-premises HCX Manager, order an on-premises HCX instance in the IBM Cloud for VMware Solutions console. For more information, see [Ordering on-premises HCX instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-standalone_orderingserviceinstances).
5. If you used a self-signed SSL certificate when you order the HCX service, you must import the certificate into the on-premises HCX Manager by completing the following steps.



1. In the on-premises HCX Manager Admin Console, click the Administration tab.
2. From the left navigation pane, click Trusted CA Certificate, and then click IMPORT on the right.
3. Click URL, and then enter the URL of the certificate you want to apply. The URL is the HCX Cloud IP (https://<cloud-side public IP>), which you can find on the HCX service details page in the IBM Cloud for VMware Solutions console.
4. Click APPLY.





You now completed the basic setup of the on-premises HCX Manager. You can proceed to pair the on-premises HCX site with the cloud-side HCX site.

For more information, see [VMware Hybrid Cloud Extension](https://cloud.vmware.com/vmware-hcx).







 Considerations before you delete on-premises HCX instances 

Review the following considerations before you delete an HCX instance that was ordered for on-premises use:



1. In the VMware vSphere Web Client, go to the HCX user interface and check the following items:



1. Ensure that no HCX migration or disaster recovery operation is running.
2.
ibmcloud cdb deployment-connections example-deployment -u <newusername> --all [--endpoint-type <endpoint type>]

If you don't specify a user, the deployment-connections commands return information for the admin user by default. If you don't specify an endpoint type, the connection string returns the public endpoint by default. If your deployment has only a private endpoint, you must specify --endpoint-type private or the commands return an error. The user and endpoint type is not enforced. You can use any user on your deployment with either endpoint (if both exist on your deployment).

To use the ibmcloud cdb CLI commands, you must [install the Cloud Databases plugin](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=databases-cli-plugin-cdb-referenceinstalling-the-cloud-databases-cli-plug-in).





 Getting Connection Strings through the API 

To retrieve user's connection strings through the API, use the [/users/{userid}/connections](https://cloud.ibm.com/apidocs/cloud-databases-apidiscover-connection-information-for-a-deployment-f-e81026) endpoint. You must specify in the path which user and which type of endpoint (public or private) should be used in the returned connection strings. The user and endpoint type is not enforced. You can use any user on your deployment with either endpoint (if both exist on your deployment).

curl -X GET -H "Authorization: Bearer $APIKEY" 'https://api.{region}.databases.cloud.ibm.com/v4/ibm/deployments/{id}/users/{userid}/connections/{endpoint_type}'





 Additional Users and Connection Strings 

Access to your Databases for EnterpriseDB deployment is not limited to the admin user. You can create users by using the Service Credentials pane, the IBM CLI, or through the IBM Cloud Databases API.

All users on your deployment can use the connection strings, including connection strings for either public or private endpoints.
* Obtain the registered domain name.
* Obtain the signed TLS certificate and the private key.
* Set up your [Code Engine CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-install-cli) environment.
* [Create a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-project).
* [Create an app](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-appdeploy-app-cli).



When your domain name is registered, you have a signed TLS certificate and its matching private key for this domain, and you have an existing Code Engine application, you are ready to add a custom domain mapping to this application. You can use the domainmapping create command in the CLI to create a custom domain mapping with your Code Engine application.



1. Create a TLS secret with the signed TLS certificate and the private key. In this example, the mycert.txt file contains the TLS certificate, including all intermediate certificates, which are associated with your domain. If the certificate is provided to you as separate files, concatenate the content of the files. The myprivatekey.txt file contains the matching private key that corresponds to the certificate chain.

ibmcloud ce secret create --name mytlssecret --format tls --cert-chain-file mycertchain.txt --private-key-file myprivatekey.txt

Example output

Creating tls secret 'mytlssecret'...
OK
2. Create the custom domain mapping between the Code Engine myapp application and the custom domain, www.example.com. Use the TLS secret that you created in the previous step.

ibmcloud ce domainmapping create --domain-name www.example.com --target myapp --tls-secret mytlssecret

Example output

OK
Domain mapping successfully created.



The following table summarizes the options that are used with the domainmapping create command in this example.
You must ssh to the host by using your credentials, or the root credentials that are available from the IBM Cloud Console.

You will require root permissions in order to install the monitoring agent.

For example, you can complete the following steps to get the bare metal information that you need to ssh into the server:



1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login).
2. Click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/icon_hamburger.svg) > Classic Infrastructure > Device List.
3. Identify the bare metal server that you want to monitor. Copy the Public IP.
4. Click the bare metal server device name.
5. Select Passwords. Copy the password for the root user.

Then, from a terminal, run the following command:

ssh <USER_ID>@<IP_ADDRESS>

Where:

<USER_ID> is the user ID that you use to log in to the bare metal server. For example, use root.

<IP_ADDRESS> is the public IP address of the bare metal server.

For example: ssh root@45.123.122.12









 Step 1: Configure a monitoring agent to collect metrics from the bare metal server 

You must install a monitoring agent to collect and forward metrics from a bare metal server to an IBM Cloud Monitoring instance.

Complete the following steps from the command line to install a monitoring agent:



1. Obtain the access key. For more information, see [Getting the access key through the IBM Cloud UI](https://cloud.ibm.com/docs/monitoring?topic=monitoring-access_keyaccess_key_ibm_cloud_ui).
2. Obtain the ingestion URL.
For more information about the PKCS #11 user types, see <br><br>[PKCS #11 Cryptographic Token Interface Usage Guide Version 2.40 - Users](http://docs.oasis-open.org/pkcs11/pkcs11-ug/v2.40/cn02/pkcs11-ug-v2.40-cn02.html_Toc406759984). 
 normal_user_name The name for the normal user type. The PKCS #11 standard defines two types of users for login: the security officer (SO) and the normal user. For more information about the PKCS #11 user types, see <br><br>[PKCS #11 Cryptographic Token Interface Usage Guide Version 2.40 - Users](http://docs.oasis-open.org/pkcs11/pkcs11-ug/v2.40/cn02/pkcs11-ug-v2.40-cn02.html_Toc406759984). 
 private_keystore_spaceid The 128-bit [Universally Unique IDentifier (UUID)](https://www.cryptosys.net/pki/uuid-rfc4122.html) of the private keystore. You can generate the UUID with a third-party tool, such as [UUID generator](https://www.uuidgenerator.net/).<br><br>Hyper Protect Crypto Services provides you with two database-backed EP11 keystores for enhanced security and better user access management: the private keystore that only the normal user type can access and the public keystore that all user types can access. 
 private_keystore_password Authorized sessions can be used by enabling the sessionauth configuration option. If the sessionauth option is enabled, it must be enabled for both keystores. If addition, a text password that is 6-8 characters in length is required for the tokenspaceIDPassword field and the password must be identical for both keystores.
Workload edge cluster hosts workload Tier 0 and Tier 1 Gateways for your workloads. A predefined example overlay network topology with one Tier 1 Gateway is provided by automation. You can customize it for your own needs by changing or deleting example segments or by adding new segments.



The gateway cluster must not be mixed with the NSX-T edge cluster, which consists of VMware NSX-T™ edge transport nodes. The gateway cluster provides compute capacity for hosting Juniper vSRX, Fortinet FortiGate, or other third-party routers or firewalls. The VLAN routing can be controlled by [gateway appliance configuration](https://cloud.ibm.com/docs/gateway-appliance?topic=gateway-appliance-managing-vlans-and-gateway-appliances) though IBM Cloud Classic portal.





 NSX-T topology 

When you deploy a vCenter Server instance in your IBM Cloud Classic Infrastructure, you obtain the default network topology as presented in the following diagram.

Zoom

![NSX-T default network topology](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/arch-pattern-nsx-t-topology.svg)

Figure 3. NSX-T default network topology

The default topology can be summarized as follows:



1. Depending on the network preference selection, your instance is deployed with both public and private connectivity or private connectivity only.
2. The automation deploys an NSX-T Tier 0 (T0) Gateway in the NSX-T workload edge cluster. The T0 gateway is attached to both IBM Cloud private and public networks or IBM Cloud private network only based on the selection.
3. The automation deploys an example NSX-T overlay topology with a Tier 1 (T1) Gateway and a few example overlay segments attached both to the T1 and T0 Gateways. You might customize the topology based on your needs.
4.
Response code: 404





 ST0039 error message 

IBM Cloud Satellite is not available in this region. Choose a supported IBM Cloud region with ibmcloud target -r REGION to manage your Satellite location from, and try again. For supported multizone regions, see http://ibm.biz/satloc-mzr.

Error type: Satellite

Response code: 404





 ST0040 error message 

Format error in template file. TEMPLATE-ERROR

Error type: Bad request

Response code: 400





 ST0041 error message 

Maximum allowed storage requests limit reached. Existing count:EXISTING-COUNT allowed count:ALLOWED-COUNT.

Error type: Bad request

Response code: 400





 ST0042 error message 

A storage request for volume-type:<volumeType> already exists with ID REQUEST-ID.

Error type: Bad request

Response code: 400





 ST0043 error message 

Backend service access denied.

Error type: Services Response code: 403





 ST0044 error message 

Provided total-capacity must be greater than current total-capacity.

Error type: Bad request

Response code: 400





 ST0045 error message 

Total-capacity must be a positive integer and the unit of total-capacity must be in the form of E, T, G, M, K, B.

Error type: Bad request

Response code: 400





 ST0046 error message 

This storage configuration is already up to date with the latest revision. No newer revision available for TEMPLATE-NAME at version TEMPLATE-VERSION. Current revision: CURRENT-VERSION and latest revision.

Error type: Bad request

Response code: 406





 ST0047 error message 

The PARAMETER1 value PARAMETER2 must contain only alphabets, numbers, underscore, and hyphen.

Error type: Bad request

Response code: 400





 ST0048 error message 

Failed to update wanted storage configuration. Assignment creation failed.

Error type: Services

Response code: 500





 ST0049 error message 

Configuration is created in CONFIG-LOCATIOIN location but the cluster is in CLUSTER-LOCATION location.
[hamburger icon](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/icon_hamburger.svg) and select DevOps. On the Toolchains page, click a toolchain to open its Overview page. Alternatively, on your app's Overview page, on the Continuous delivery card, click View toolchain. Then, click Overview.

a. Click Add tool.

b. In the Tool Integrations section, click Delivery Pipeline Private Worker.
2. Type a name for the tool integration. This name identifies a pool of private workers in the Workers tab of the pipeline stage.
3. Type your service ID API key to authenticate access to the work queue where one or more private workers can look for work. If you don't have a service ID API key, click Create to generate one for this private worker.
4. Click Create Integration.
5. From your toolchain's Overview page, on the Delivery pipelines card, click Delivery Pipeline Private Worker. A list of all of the workers that are registered by using an API key that is associated with this service ID is displayed.



The list of workers is empty until you use Delivery Pipeline private workers for the first time.

For more information about the Delivery Pipeline Private Worker tool integration, see [Configuring Delivery Pipeline Private Worker](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-privateworker).





 Configuring the Delivery Pipeline Private Worker tool integration with the API 



1. [Obtain an IAM bearer token](https://cloud.ibm.com/apidocs/resource-controllerauthentication).
2.
The claims are set for each token separately and are sequentially applied as shown in the following example.

{
"accessTokenClaims": [
{
"source": "saml",
"sourceClaim": "moderator"
},
{
"source": "saml",
"sourceClaim": "viewer",
"destinationClaim": "reader"
}
],
"idTokenClaims": [
{
"source": "saml",
"sourceClaim": "attributes.uid"
},
{
"source": "saml",
"sourceClaim": "Name",
"destinationClaim": "firstName"
},
{
"source": "saml",
"sourceClaim": "Country"
}
]
}



Table 1. Claims mapping variables explained

 Object Description 

 source Defines the source of the claim. Options include: saml, cloud_directory, facebook, google, appid_custom, and attributes. 
 sourceClaim Defines the claim as provided by the source. It can refer to the identity provider's user information or the user's App ID custom attributes. 
 destinationClaim Optional: Defines the custom attribute that can override the current claim in token. 









 Configuring tokens 

With the API, you can customize the information that is returned in your App ID tokens.

If you want to configure the lifespan of your token, you can quickly make the changes through the service dashboard. For more information, see [Managing authentication](https://cloud.ibm.com/docs/appid?topic=appid-managing-idpidp-token-lifetime).



1. In terminal, run the following command to obtain an API key.

ibmcloud iam api-key-create NAME [-d DESCRIPTION] [-f, --file FILE]



Table 2. Understanding the creating an API key command options

 Option Description 

 NAME The name that you want to give your key.
For example, see the following condition on log entries in the vnkernel component: 2 | vmkernel | bad CDB .* scsi_op=0x9e || 0 | vmkernel | 0x1a. H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x2[04] 0x0
6. Restart the ESXi host to reload the syslog daemon and activate the log filters.









 Step 3. Verify logs in Log Analysis 

Complete the following steps:



1. [Launch the UI](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-launch).
2. In the search bar, run queries to verify the data.



For example, you can run any of the following queries:



* vCenter Application management logs excluding audit events: host:<VCENTER-HOSTNAME> app:applmgmt -app:applmgmt-audit
* Logs from NSX nodes and components: app:nsx
* ESXi hostd logs: app:Hostd
* ESXi vmkernel logs: app:vmkernel



You can check if you have connectivity problems connecting to connect to Vcenter Server via vSphere client. When vSphere vCenter Server is inaccessible through vSphere client, you can search for the following error "503 Service Unavailable" app:wcpsvc.

You can look at user's log in logs by running the following query: app:vpxd Event -app:vpxd-main -app:vpxd-profiler "logged in".





 Appendix 1. Check current logging configuration in your vCenter deployment 

You can configure the amount of detail that vCenter Server collects in log files.



 Check the Log Level in your vCenter deployment 

Complete the following steps to find the log level that is configured for the vCenter deployment across all hosts and components:



1. Launch the vSphere Client.
2. Select the vCenter Server instance. Then, select Configure.
3.
set the region (-r) and resource group (-g)
$ ibmcloud target -r us-south -g Default

 set the ACCESS_TOKEN environment variable (with Bearer)
$ export ACCESS_TOKEN=ibmcloud iam oauth-tokens | grep IAM | cut -d : -f 2 | sed 's/^ //'

 show the access token
$ echo $ACCESS_TOKEN

Bearer eyJraWQiOiIyMDIwMDcyNDE4MzEiLCJh...<redacted>...o4qlcKjl9sVqLa8Q

 set the ACCESS_TOKEN environment variable (without Bearer)
$ export ACCESS_TOKEN=ibmcloud iam oauth-tokens | grep IAM | cut -d ' ' -f 5 | sed 's/^ //'

eyJraWQiOiIyMDIwMDcyNDE4MzEiLCJh...<redacted>...o4qlcKjl9sVqLa8Q
Show more







 4 - Invalid body data was passed... 



 Message 

Invalid body data was passed: Please ensure the data passed had valid formatting with no invalid characters

Reason code: BAD_BODY_ERR





 HTTP status code 

400 - Bad Request

The HTTP 400 Bad Request response status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

The client should not repeat this request without modification.





 Context 

Some examples of this error are:



* Create an instance policy



* Only one of each policy can be created
* No resources section was provided
* Extraneous fields in the resources section (see example 1)



* Create a key



* One resource is required (see example 2)
* Metadata is empty (see example 3)
* Key has zero value or it's empty







 Example 1 

The create instance policy request fails because the resource contains an extra field (extra_field).
You can [view a list of all access keys](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-access_keyaccess_key_view) to obtain the access key values.
* GUID is the GUID of the instance that is associated with the access key.









 Hide the access key 

To hide the Access Key page for non-admin users in an Workload Protection instance through the IBM Cloud UI, complete the following steps:



1. [Log in to the IBM Cloud console](https://cloud.ibm.com/login).
2. Go to the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > Resource list.
3. Select Security. You can see the list of instances that are available on IBM Cloud.
4. Identify the instance. Select Open dashboard.
5. From the Selector button in the navigation bar, choose Settings > User Profile > Admin Priviledges.
6. Enable the option Hide Agent Install to hide the access key for non-admin users.
Type the user ID and password that you use to log in to Db2 Warehouse on Cloud. To obtain the user ID and password, click Connect in the web console or Connect > Connection Information in the web console.
8. Ensure that the connection mode is Share, and then click OK.







 Results 

The query results are displayed in an Excel spreadsheet. These are the same results that are displayed in the Results viewer. Now you can generate charts and reports and analyze your data by using Excel. For more information about how to do this and how to run SQL queries on your data from the web console, see:



* [Tutorial: Generating charts and reports by using Excel](https://www.ibm.com/support/knowledgecenter/SS6NHC/com.ibm.swg.im.dashdb.analytics.doc/doc/explore_excel_reports.html)
* [Analyzing with Excel](https://www.ibm.com/support/knowledgecenter/SS6NHC/com.ibm.swg.im.dashdb.analytics.doc/doc/exploreexcel.html)









 Esri ArcGIS for Desktop 

You can connect Esri ArcGIS for Desktop to a Db2 Warehouse on Cloud database and then use it to analyze and visualize geospatial data.



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

You must have the Db2 driver package or the IBM® Data Server Driver Package installed on your computer.





 Procedure 



1. Determine your ODBC DSN data from the [connection information](https://cloud.ibm.com/docs/Db2whc/connecting?topic=Db2whc-db_details_cxn_credsdb_details_cxn_creds) that you collected beforehand.
2. Create a new connection:

a. In the ArcCatalog Catalog tree, open the Database Connections node and click Add Database Connection.
Why do Schematics Workspaces create using the API/UI/CLI fails? 

 What’s happening 

The Schematics create workspace fails when you attempt to create using the API by using following CURL command.

curl --request POST --url https://cloud.ibm.com/schematics/workspaces -H "Authorization: Bearer scfQ" -d '{"name":"test_api","type": ["terraform_v0.12"],"location": "eu-de","description": "via api","resource_group": "5e1f06f5b2b24a319f6cd5be86f531dd","tags": [],"template_repo": {"url": "https://github.ibm.com/Rise-with-SAP/iac-hec-sap"},"template_data": [{"folder": ".","type": "terraform_v0.12","variablestore": ]}]}'

 Why it’s happening 

When Schematics runs the CURL command, an error state Schematics cannot find the complete information in the payload. And the workspace create is marked with Bad request message.

{
"requestid": "3b57ed5d-8610-4a86-9864-8d8197b80336",
"timestamp": "2021-09-22T14:49:04.565693526Z",
"messageid": "M1008",
"message": "Bad request. Check that the information you entered in the payload is complete and formatted correctly in JSON.",
"statuscode": 400
}

 How to fix it 

Verify your CURL or the payload contains that the location and the url are pointing to the same region where you want to create or update the workspace.

For example