vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Back in the IBM Cloud console in the bucket Configuration panel scroll down to the Static website hosting endpoints section and copy the Public URL into a browser tab. Since you configured this earlier to redirect to index.html the web application will be displayed and content will be delivered through the CDN. For me the URL was fredflinstone-mywebsite.s3-web.us-south.cloud-object-storage.appdomain.cloud notice the s3-web.





 Access the static website through custom subdomain 

Accessing the website at the URL provided by the COS bucket is great, but access via a custom domain, like web.example.com, is even better. Follow the instructions at [Domain Routing for IBM Cloud Object Storage static web hosting](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-routing-rules-cos). Paste web.example.com into the browser which will default to https:// which will display the page correctly, but the CDN content will only be rendered if it also accessed via an https:// URL. You can explicitly specify [http://example.com](http://example.com) or better yet ensure that HTTPS was selected when creating the CDN and https:// URL references to the CDN content were pasted into the index.html file in the previous step.







 Step 5: Remove resources 

To clean up resource, perform the following steps:



* Delete the [IBM® Content Delivery Network service](https://cloud.ibm.com/cdn).
* Delete the [IBM Cloud Object Storage bucket and / or service](https://cloud.ibm.com/resources).



Depending on the resource it might not be deleted immediately, but retained (by default for 7 days). You can reclaim the resource by deleting it permanently or restore it within the retention period. See this document on how to [use resource reclamation](https://cloud.ibm.com/docs/account?topic=account-resource-reclamation).





 Related content
WebP conversion does not change the image URL. The Content-Type HTTP header tells the browser the original format of an image.





 Common Cf-Polished statuses 

Cf-Polished statuses

The following table lists common Cf-Polished statuses and how to troubleshoot them. If no Cf-Polished header is returned, try using single-file cache purge to purge the image.



Table 1. Common Cf-Polished statuses

 Status Definition Recommendation 

 input_too_large The input image is too large or complex to process and needs a lower resolution. Use .png or .jpeg images that are less than 1,000px and 10MB. 
 not_compressed or not_needed The image was fully optimized at the origin server and no compression was applied. 
 webp_bigger Polish attempted to convert to WebP, but the image was optimized at the origin server and/or was created using a low quality setting. Because the WebP version doesn’t exist, the status is set on the JPEG/PNG version of the response. 
 cannot_optimize or internal_error The input image is corrupted or incomplete at the origin server. Upload a new version of the image to the origin server. 
 format_not_supported The input image format is not supported (for example, BMP, TIFF) and/or the origin server is using additional optimization software that is not compatible with Polish. Try converting the input image to a web-compatible format (for example, PNG, JPEG) and/or disabling additional optimization software at the origin server. 
 vary_header_present The origin web server has sent a Vary header with a value other than accept-encoding. If the origin web server is attempting to support WebP, disable WebP at the origin web server and let Polish perform the WebP conversion. 



Image size optimization still works when the accept-encoding is not the only header listed within the Vary header.
For more information on how to handle notification responses from apps, see [here](https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/handling_notification_responses_from_apns).
* Chrome or Firefox devices:



* NotFound - the subscription is expired and can’t be used.
* Gone - the subscription is no longer valid.



For more information, see [web push protocol](https://web.dev/push-notifications-web-push-protocol/).



* What is the difference between Event Notifications Topic Subscriptions and Event Notifications Tag Subsciptions to push devices?



* Event Notifications Topic subscriptions:

For the topic subscriptions, start by creating a Topic and write conditions on that topic. This topic is responsible for routing the incoming notification that satisfies the topic conditions.

You can subscribe to multiple Event Notifications destinations like email, SMS, webhooks, slack, and Microsoft teams. Also, you can subscribe push type destinations like android, iOS, Firefox, chrome, and safari.

If the incoming notifications satisfy the condition written for Topic (T), it routes the notification to all the destinations subscribed or connected to Topic (T) irrespective of the type of destinations.

For example, ACME Bank wants to route maintenance event notifications to customers by using android and iOS devices. Acme Bank is following these steps:



1. Create a topic named ACME-Maintenance.
2. Write Advance condition $.notification-type == 'maintenance'.
3. Subscribe push android and push iOS destinations to the above topic.
4. Next, send an event notification with payload containing attribute "notification-type":"maintenance"and "ibmenpushto": "{"platforms":["push_android","push_ios"]]}", notification-type attribute is added so that it matches against the topic condition and ibmenpushto for targeting customers with android and iOS devices.
5.
FAQS: General 



  Why isn't my server listed in the Virtual Servers list? 

If you have XenServer, Hyper-V or Virtuozzo on your server, but it is not listed in the [Virtual Servers ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://cloud.ibm.com/classic/devices) list, then you need to open a [support case ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://cloud.ibm.com/unifiedsupport/cases/add).

This request is filled during normal United States CST business hours.





  If clients are a service provider, can they use their own VSPP licensing for hosts that they rent in IBM Cloud? 

No. You can either use IBM Cloud® VSPP or BYOL for socket-based licensing. You cannot use your own VSPP agreement.





  Can I use the secondary IP block that came with the server for virtual machines? 

No. The secondary IP that is provided with your server is routed to work on the physical server and not on a virtual machine. You need to have Portable IP blocks to connect your virtual machine to the network.
* Check to make sure you are not using the ESR version of Firefox. If you are, switch to another browser such as Chrome and retry.
* If you have a multi-zone region (MZR) cluster you need to enable [VLAN spanning](https://cloud.ibm.com/docs/vlans?topic=vlans-vlan-spanningmanage-vlan-spanning).



If your cluster is available, select it and click Next. It might take a few minutes for the console to finish being linked to your cluster. When the linking process has finished, click Launch the IBM Blockchain Platform console to open the console. You are now ready to start exploring the console.





 Blockchain component deployment 

![version 2.x](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/2-x_Pill.png) The following illustration shows how the IBM Blockchain Platform components are deployed to the Kubernetes cluster assuming Hyperledger Fabric v2.x images are used by the peer.

Zoom

![IBM Blockchain Platform and the Kubernetes Service](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/IBP-IKS-Diagram-20.svg)

Figure 2: Deploying the IBM Blockchain Platform to a Kubernetes cluster on IBM Cloud.



* Pod: When each Certificate Authority, peer, ordering service, or smart contract is deployed, a new Pod is created in a worker node in your cluster. Every time you deploy a smart contract, a new pod is launched for the smart contract.
* App containers: Containers are created inside the pods for each node that is deployed.
* Persistent Storage: Storage for each node is dynamically provisioned from the Kubernetes cluster default storage class every time a node is deployed.



!
Edit cdn.html and replace the occurrences of CDN with your CNAME, http://static.example.com, in the example above. If you open the file in the vim editor the command :%sCDNhttp://static.yourwebsite.com will do the trick.

Upload cdn.html by replacing the file index.html:

ibmcloud cos upload --bucket $BUCKET_NAME --key index.html --file cdn.html

Back in the IBM Cloud console in the bucket Configuration panel scroll down to the Static website hosting endpoints section and copy the Public URL into a browser tab. Since you configured this earlier to redirect to index.html the web application will be displayed and content will be delivered through the CDN. For me the URL was fredflinstone-mywebsite.s3-web.us-south.cloud-object-storage.appdomain.cloud notice the s3-web.





 Access the static website through custom subdomain 

Accessing the website at the URL provided by the COS bucket is great, but access via a custom domain, like web.example.com, is even better. Follow the instructions at [Domain Routing for IBM Cloud Object Storage static web hosting](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-routing-rules-cos). Paste web.example.com into the browser which will default to https:// which will display the page correctly, but the CDN content will only be rendered if it also accessed via an https:// URL. You can explicitly specify [http://example.com](http://example.com) or better yet ensure that HTTPS was selected when creating the CDN and https:// URL references to the CDN content were pasted into the index.html file in the previous step.







 Step 5: Remove resources 

To clean up resource, perform the following steps:



* Delete the [IBM® Content Delivery Network service](https://cloud.ibm.com/cdn).
* If you use the Accept request header, you specify the format and any additional parameters as shown in the following example. The example specifies the audio/l16 format and a sampling rate of 16,000 Hz.

audio/l16;rate=16000
* If you use the accept query parameter, you must URL-encode the format and any additional parameters as shown in the following example. The example specifies the same format and sampling rate as the previous example.

audio%2Fl16%3Brate%3D16000



To receive audio in the default format, omit both the header and the query parameter. For more information, see [Synthesizing text to audio](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-usingHTTPsynthesize).
* With the WebSocket /v1/synthesize method, you must specify a format by using the required accept parameter of the text message that you pass to initiate synthesis. To receive audio in the default format, specify the value / for the parameter. For more information, see [Send input text](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-usingWebSocketWSsend).







 Playing an audio file 

To play an audio file that the service generates, use one of the following tools:



* A web browser such as Google Chrome™, Firefox®, or Microsoft® Internet Explorer®
* An audio player such as Audacity® ([audacityteam.org](https://www.audacityteam.org/)) or FFmpeg ([ffmpeg.org](https://www.ffmpeg.org))
If you pass both custom language and custom acoustic models with a request, the service applies the following guidelines when deciding on the base model version to use with the request:



* If both custom models are based on the older base model, the service uses the old base model for recognition.
* If both custom models are based on the newer base model, the service uses the new base model for recognition.
* If only one of the two custom models is upgraded to the newer base model, the service uses the old base model for recognition. The old base model is the version that the two custom models have in common.



Both custom models must be owned by the credentials that are passed with the request, both must be based on the same base model (for example, en-US_BroadbandModel), and both must be in the available state. For more information about using both types of custom models with a recognition request, see [Using custom language and custom acoustic models for speech recognition](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-useBothuseBothRecognize).





 Example of using an upgraded custom model 

The earlier example listed the following available versions for a custom language model:

"versions": [
"en-US_BroadbandModel.v2018-07-31",
"en-US_BroadbandModel.v2020-01-16"
],

The following synchronous HTTP request specifies that the older version of the base model is to be used. Thus, the older version of the specified custom language model is also used.

IBM Cloud

curl -X POST -u "apikey:{apikey}" --header "Content-Type: audio/flac" --data-binary @{path}audio-file.flac "{url}/v1/recognize?model=en-US_BroadbandModel&base_model_version=en-US_BroadbandModel.v2018-07-31&language_customization_id={customization_id}"

IBM Cloud Pak for Data
Message: A service cannot be published with "ibm_created" or "3rd_party" tags. These tags can be set only by an administrator.





 BXNUI2060E 

Message: The usage information could not be processed.

If you see this message again, go to the [IBM Cloud status page](https://cloud.ibm.com/status?selected=status) to check whether a service or component has an issue. Also make sure you have [appropriate access](https://cloud.ibm.com/docs/account?topic=account-iamfaqiam-access). If the error occurs again, follow the [troubleshooting steps for console pages that don’t load](https://cloud.ibm.com/docs/account?topic=account-ts_err). If the problem continues, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2061E 

Message: The pricing catalog information cannot be parsed.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2062E 

Message: The account information could not be processed.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2063E 

Message: No starter is associated with this app.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2064E 

Message: The web identity unique ID cannot be retrieved.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2065E 

Message: The template ID is invalid because it contains HTML.

The template ID cannot include HTML tags < and >.

Remove those tags and try again.





 BXNUI2066E 

Message: No JazzHub repository is associated with this app.
6. The browser consumes the redirect instruction and navigates to IAM to allow IBM Cloud to finish the login sequence. This browser redirect is necessary to set necessary single-sign-on cookies on the user's browser that prevents the user from entering the login credentials again.
7. IAM then finishes its authentication flow with the console by sending an OAuth2 compliant redirect with an authorization code to the browser.
8. The browser provides the authorization code to the console, which in turn is used to retrieve the required tokens from IAM.
9. When the console receives the tokens, the login sequence ends. The console can now invoke IBM Cloud APIs and identify the user.
10. The console displays the dashboard with user-specific content.







 Login sequence for federated users with an IBMid 

IBMid allows enterprise customers to federate their user authentication and authorization system with IBMid. This way, users don't need to manage an extra user ID. Instead, they are able to log in into IBM Cloud using their well-known customer-managed user ID. The login sequence for federated users in IBM Cloud works according to the following sequence:

Zoom

![Login process for federated users with an IBMid](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/account/images/login-fed-id.svg)

Figure 2. Login process for federated users with an IBMid



1. The user starts by visiting the URL [https://cloud.ibm.com](https://cloud.ibm.com) with a browser. The IBM Cloud console sends back a login page to the browser.
2. On the login page, the user enters their username.
3. After clicking to continue, the IBM Cloud console redirects the user's browser to IBM Cloud's IAM component.
Enabling automatic subscription makes testing of your APIs easier because a test application is used, with a pre-supplied client ID and client secret, which is automatically subscribed to all the Plans in the Catalog, so you don't have to specify a plan or application when testing.

Automatic subscription is available only for a development Catalog.
3. If the Catalog is the default staging Catalog, select Default. Calls to APIs that are published to the Catalog can use a shorter URL that does not include the Catalog name .

You can only select Default for one Catalog.
4. Optional: Click Endpoints, and populate the following fields:



* Custom Gateway URL: In the Custom Gateway URL text field, enter a URL. You use the Custom Gateway URL if you want to achieve custom branding of URLs for APIs that are deployed to API Connect, rather than using the default URL that API Manager generates. By default, the API Connect gateway URL has the following format:

https://gateway_cluster_hostname/organization_name/Catalog_name

You can override the default by specifying a URL that is more appropriate for your enterprise; for example, https://api.mycompany.com. Any API endpoints that are displayed in the Developer Portal reflect the specified URL.

Notes:



* You must configure a DNS entry that maps your custom host name and domain to the default gateway URL.
* For the endpoints of an API to reflect your custom gateway URL, you must configure the API to be enforced by the API Connect gateway. For more information, see [Specifying an alternative host for an API](https://www.ibm.com/support/knowledgecenter/en/SSFS6T/com.ibm.apic.toolkit.doc/task_apionprem_creating_apis.htmltask_tq2_11r_xt__enforce_step).



* Ensure that the same custom gateway URL is not applied to multiple Catalogs as the behavior in that scenario is undefined.
Message: The web identity unique ID cannot be retrieved.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2065E 

Message: The template ID is invalid because it contains HTML.

The template ID cannot include HTML tags < and >.

Remove those tags and try again.





 BXNUI2066E 

Message: No JazzHub repository is associated with this app.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2067E 

Message: A service broker with the ID of "{1}" wasn't created or updated because an invalid URL, "{0}", was detected.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2068E 

Message: A remote URL for the service ID, "{0}", wasn't loaded because a null URL value was detected.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2069E 

Message: The URL, "{0}", for the service ID, "{2}", wasn't loaded because of an error: "{1}".

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2070E 

Message: The {0} organization doesn't own {1}.

[IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2071E 

Message: Only managers can modify certificates.

[IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter){: external.





 BXNUI2072E 

Message: The certificate wasn't uploaded.
* Severity: select severity from the severity dropdown list.
* Advanced conditions: write your own custom conditions, which must follow [jsonpath specifications](https://jsonpath.com/).







 Step 6: Create an Event Notifications subscription 

Click Subscriptions in the Event Notifications console. Enter the following subscription details:



* Click Create to display subscription wizard.
* Complete the following subscription details:



* Subscription name: name of the subscription.
* Subscription description: add an optional description.



* Under the Subscribe to a topic section, select a topic from the drop-down list and select a destination from the destination drop-down list.
* Destination type: select type under Destination and click Add.







 Step 7: Set up Event Notifications Chrome web SDK 

The Chrome web SDK enables Chrome websites to receive push notifications. Complete the following steps to install Event Notifications Chrome web SDK, initialize the SDK, and register for notifications for your website.



* To include the SDK in your project, add the ENPushSDK.js,ENPushServiceWorker.js, and manifest_Website.json files to your project root folder.
* Edit the manifest_Website.json file.

{
"name": "YOUR_WEBSITE_NAME"
}
* Change the manifest_Website.json file name to manifest.json.
* Include the manifest.json in <head> tag of your html file.

<link rel="manifest" href="manifest.json">
* Include IBM Cloud web push SDK to the script.

<script src="ENPushSDK.js" async></script>
* Complete the following steps to enable website to initialize the SDK.

var enPush = new ENPush()

function callback(response) {
alert(response.response)
}

var initParams = {
"instanceGUID": "<instance_guid>",
"apikey": "<instance_apikey>",
"region": "<region>",
MotionPro stand-alone clients for Mac OS X 



 If you start from the Web browser and use the automatically downloaded MotionPro client 

If you have ever [logged on to SSL VPN](https://cloud.ibm.com/docs/iaas-vpn?topic=iaas-vpn-getting-startedlogin-to-the-vpn) using a Web browser, the compatible version of MotionPro client is downloaded for you to install.



1. Next time you click on the wanted VPN endpoint from the [VPN endpoint page](https://www.ibm.com/cloud/vpn-access) and log in, the client is automatically launched.
2. A profile for the selected endpoint is automatically loaded in your Web-launched MotionPro client. You do not have to create a new profile.
3. Click Connect.



The automatically downloaded MotionPro client does not work on MacOS Monterey (Version 12.x).





 If you are using the manually installed MotionPro clients 

If you have downloaded and installed the MotionPro client manually from the following pages, complete these steps to configure a connection.



* Mac OS MotionPro client on the [Array Networks Clients and Tools page](https://support.arraynetworks.net/prx/001/http/supportportal.arraynetworks.net/downloads/downloads.html)
* Mac OS MotionPro client (Web-Launched MP Client) on the [Array Networks Clients and Tools](https://support.arraynetworks.net/prx/001/http/supportportal.arraynetworks.net/downloads/downloads.html) website.



The MotionPro Plus clients, located in the [Apple Store](https://apps.apple.com/us/app/motionpro-plus/id1218085720?mt=12), are not supported.



1. Open the Mac MotionPro or MotionPro Plus application.
2. Click Profile, then Create. The Create Profile window shows.
3. Enter the following information:



* Profile Name
* Virtual Site Host
* Virtual Site Port
* User Name
* Password