vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [List all disks on a dedicated host](https://cloud.ibm.com/apidocs/vpclist-dedicated-host-disks) (GET /dedicated_hosts/{dedicated_host_id}/disks)
* [Retrieve a dedicated host disk](https://cloud.ibm.com/apidocs/vpcget-dedicated-host-disk) (GET /dedicated_hosts/{dedicated_host_id}/disks/{id})
* [Update a dedicated host disk](https://cloud.ibm.com/apidocs/vpcupdate-dedicated-host-disk) (PATCH /dedicated_hosts/{dedicated_host_id}/disks/{id})



API methods that return instance and dedicated host profiles now include a disks property with information about the storage capability (where present) of resources provisioned with those profiles.

API methods that return instances and dedicated hosts now include a disks property with information about the disks configured for those resources.

For more information, see [About instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage).

Virtual server instance console. You can now access your instances by connecting to a VNC or serial console. Learn about [Accessing virtual server instances by using VNC or serial consoles](https://cloud.ibm.com/docs/vpc?topic=vpc-vsi_is_connecting_console), and explore the new instance console API methods:



* [Create a console access token for an instance](https://cloud.ibm.com/apidocs/vpccreate-instance-console-access-token) (POST /instances/{instance_id}/console_access_token)
* [Retrieve the console WebSocket for an instance](https://cloud.ibm.com/apidocs/vpcget-instance-console) (GET /instances/{instance_id}/console)



Instance resize.
Stand-alone apps such as WAR or EAR files can be deployed to Liberty in IBM Cloud.

To deploy a stand-alone app, run the ibmcloud cf push command with the -p option that points to your WAR or EAR file. For example:

ibmcloud cf push <yourappname> -p myapp.war

When a stand-alone app is deployed, a default Liberty configuration is provided for the app. The default configuration enables the following Liberty features:



* beanValidation-1.1
* [cdi-1.2](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-options_for_pushingcdi12)
* ejbLite-3.2
* el-3.0
* jaxrs-2.0
* jdbc-4.1
* jndi-1.0
* jpa-2.1
* jsf-2.2
* jsonp-1.0
* jsp-2.3
* managedBeans-1.0
* servlet-3.1
* websocket-1.1
* icap:managementConnector-1.0
* appstate-2.0



These features correspond to the Java EE 7 Web Profile features. You can specify a different set of Liberty features by setting the JBP_CONFIG_LIBERTY environment variable. For example, to enable only the jsp-2.3 and websocket-1.1 features, run the command and restage the app:

ibmcloud cf set-env myapp JBP_CONFIG_LIBERTY "app_archive: {features: [jsp-2.3, websocket-1.1]}"
: The buildpack provides a development mode for apps. The development mode is a special mode that allows developers to conduct many activities for an app instance that were not possible before. By using this feature, this version of the IBM® Eclipse Tools for IBM Cloud® can now support remote debugging with incremental file updates against a Liberty app that is running in IBM Cloud. This makes it convenient for a developer that uses Eclipse to debug an app in the cloud and apply changes to that app instantly.



* The buildpack also contains an updated version of the Liberty profile based on the [December beta](https://developer.ibm.com/wasdev/blog/2014/12/10/announcing-liberty-beta-december/).
* In addition, the following four Liberty features that were previously available as beta features, are now production-ready:



* concurrent-1.0
* jsonp-1.0
* servlet-3.1
* websocket-1.0



* The buildpack provides integration with the New Relic service. Once an app is bound to the New Relic service, the buildpack automatically downloads and configures the runtime with the New Relic agent.
* The buildpack has the following known limitations:



* When in development mode, a SessionCache service cannot be bound.
* When in development mode, a thread dump cannot be created.
* When using the servlet-3.1 or websocket-v1.0 feature, the Monitoring & Analytics service cannot be bound.









 5 December 2014 

Updated Liberty buildpack v1.9-20141202-0947
: The buildpack provides an enhanced JVM option support. The JVM options can now be applied with a restart operation. Restaging of the app is not necessary. Also, the default JVM options are optimized for fast failure and pre-configured with a common location that makes it easy to find the generated dumps.
GET /v1/{crn}/zones/{domain_id}/setting/websocket internet-svcs.zones.read internet-svcs.websockets-setting.read 
 Update websocket settings. PUT /v1/{crn}/zones/{domain_id}/setting/websocket internet-svcs.zones.update internet-svcs.websockets-setting.update 
 Get response buffering settings. GET /v1/{crn}/zones/{domain_id}/setting/response_buffering internet-svcs.performance.read internet-svcs.response-buffering-setting.read 
 Update response buffering settings. PUT /v1/{crn}/zones/{domain_id}/setting/response_buffering internet-svcs.performance.update internet-svcs.response-buffering-setting.update 
 Get hotlink protection settings. GET /v1/{crn}/zones/{domain_id}/setting/hotlink_protection internet-svcs.performance.read internet-svcs.hotlink-protection-setting.read 
 Update hotlink protection settings. PUT /v1/{crn}/zones/{domain_id}/setting/hotlink_protection internet-svcs.performance.update internet-svcs.hotlink-protection-setting.update 
 Get maximum upload size settings. GET /v1/{crn}/zones/{domain_id}/setting/max_upload internet-svcs.performance.read internet-svcs.max-upload-setting.read 
 Update maximum upload size settings. PUT /v1/{crn}/zones/{domain_id}/setting/max_upload internet-svcs.performance.update internet-svcs.max-upload-setting.update 
 Get TLS client authentication settings. GET /v1/{crn}/zones/{domain_id}/setting/tls_client_auth internet-svcs.security.read internet-svcs.tls-client-auth-setting.read 
 Update TLS client authentication settings.
If you deployed a WAR file, the web app is accessible under the context root as set in the embedded ibm-web-ext.xml file. If the ibm-web-ext.xml file does not exist, or does not specify the context root, the app is accessible under the root context. For example,

http://<yourappname>.mybluemix.net/

If you deployed an EAR file, the embedded web app is accessible under the context root as defined in the EAR deployment descriptor. For example,

http://<yourappname>.mybluemix.net/acme/

The entire default Liberty server.xml configuration file is as follows:

<server>
<featureManager>
<feature>beanValidation-1.1</feature>
<feature>cdi-1.2</feature>
<feature>ejbLite-3.2</feature>
<feature>el-3.0</feature>
<feature>jaxrs-2.0</feature>
<feature>jdbc-4.1</feature>
<feature>jndi-1.0</feature>
<feature>jpa-2.1</feature>
<feature>jsf-2.2</feature>
<feature>jsonp-1.0</feature>
<feature>jsp-2.3</feature>
<feature>managedBeans-1.0</feature>
<feature>servlet-3.1</feature>
<feature>websocket-1.1</feature>
<feature>icap:managementConnector-1.0</feature>
<feature>appstate-2.0</feature>
</featureManager>

<application name='myapp' location='myapp.war' type='war' context-root='/'/>
<httpEndpoint id='defaultHttpEndpoint' host='' httpPort='${port}'/>
: See [Troubleshooting tips for subscriptions](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-subscriptions).

Added an FAQ for WebSocket support.
: See [Do Code Engine apps support WebSockets](https://cloud.ibm.com/docs/codeengine?topic=codeengine-faqsapp-websockets)?

Updated application limits.
: See [Application limits](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limitslimits_application).





 9 February 2021 

Review the release notes for 9 February 2021.

CLI version 0.5.16 released.
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).

Added information about potentially reaching Docker rate limits.
: See [Accessing container registries](https://cloud.ibm.com/docs/codeengine?topic=codeengine-add-registry) and [Planning your build](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).





 3 February 2021 

Review the release notes for 3 February 2021.

Added planning for Code Engine information.
: See [Planning for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-codeengine).

Added information about working with configmaps and secrets as mounted files.
: See [Referencing secrets and configmaps as mounted files](https://cloud.ibm.com/docs/codeengine?topic=codeengine-secretcm-reference-mountedfiles).

Updated FAQ to add information about differences between Code Engine builds and Docker builds.
Deploying and scaling applications 

With this tutorial, deploy an application with the Code Engine CLI. The application scales to zero when not in use.

An application, or app, runs your code to serve HTTP requests. In addition to traditional HTTP requests, IBM Cloud® Code Engine also supports applications that use WebSockets as their communications protocol. The number of running instances of an app are automatically scaled up or down (to zero) based on incoming requests and your configuration settings. An app contains one or more revisions. A revision represents an immutable version of the configuration properties of the app. Each update of an app configuration property creates a new revision of the app.

Before you begin



* [Set up your Code Engine CLI environment](https://cloud.ibm.com/docs/codeengine?topic=codeengine-install-cli).
* [Create and work with a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-project).



All Code Engine users are required to have a Pay-as-you-Go account. Tutorials might incur costs. Use the Cost Estimator to generate a cost estimate based on your projected usage. For more information, see [Code Engine pricing](https://cloud.ibm.com/docs/codeengine?topic=codeengine-pricing).



 Step 1: Select an image file 

This tutorial uses a sample image, icr.io/codeengine/hello, which is a simple Hello World program. The program includes an environment variable TARGET, and prints Hello ${TARGET}. If the environment variable is empty, Hello World is returned. For more information about the code that is used for this example, see [hello](https://github.com/IBM/CodeEngine/tree/main/hello).

If you have a container image that you want to use, you can replace the image reference in the next step with your own Docker repository, image name, and version.





 Step 2: Creating and deploying an application 



1.
: The default Liberty runtime version 17.0.0.1 was updated to include [PI77770](https://www.ibm.com/support/pages/node/589019), [PI77605](https://www.ibm.com/support/pages/apar/PI77605), [PI79275](https://www.ibm.com/support/pages/apar/PI79275), and PI77438 fixes.



* The monthly Liberty runtime version was updated to the [2017.3.0.0](https://developer.ibm.com/wasdev/blog/2017/03/14/beta-websphere-liberty-tools-march-2017/) release.
* Memory Calculation was moved from staging to the start process, allowing for easier heap memory changes with the restart of an app.
* The buildpack also provides updated versions of the agent for the Auto-Scaling service, and the Extreme Scale Client.







 29 March 2017 

Updated ASP.NET Core buildpack v1.0.13-20170330-1023
: This release includes the following updates:



* Add support for .NET Core runtime 1.0.4
* Add support for .NET Core runtime 1.1.1
* Add support for .NET Core SDK 1.0.1
* Update Node version to 6.10.0
* Remove support for .NET Core SDK 1.0.0-preview2-003131
* Remove support for .NET Core SDK 1.0.0-preview3-004056







 14 March 2017 

Updated Liberty buildpack v3.8-20170308-1507
: The default Liberty runtime version was updated to the 17.0.0.1 release.



* The default Liberty runtime also includes the PI75512 WebSockets interim fix.
* The monthly Liberty runtime version was updated to the [2017.2.0.0](https://developer.ibm.com/wasdev/blog/2017/02/17/beta-websphere-liberty-tools-february-2017/) release.
: See [Choosing a build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).

CLI version 0.5.19 released.
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).

Added notices file.
: See [Code Engine notices](https://cloud.ibm.com/docs/codeengine?topic=codeengine-notices).





 23 February 2021 

Review the release notes for 23 February 2021.

CLI version 0.5.18 released.
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).





 16 February 2021 

Review the release notes for 16 February 2021.

CLI version 0.5.17 released.
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).





 12 February 2021 

Review the release notes for 12 February 2021.

Added an Object Storage subscription tutorial.
: See [Tutorial: Subscribing to Object Storage events](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cos-tutorial).

Added troubleshooting information for subscriptions.
: See [Troubleshooting tips for subscriptions](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-subscriptions).

Added an FAQ for WebSocket support.
: See [Do Code Engine apps support WebSockets](https://cloud.ibm.com/docs/codeengine?topic=codeengine-faqsapp-websockets)?

Updated application limits.
--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.





 Example 

The following command updates a Git access secret that is called github to use a new host.

ibmcloud ce repo update -n github --host NEW_HOST





 Example output 

Getting Git access secret 'github'...
Updating Git access secret 'github'...
OK









 Revision commands 

An application, or app, runs your code to serve HTTP requests. In addition to traditional HTTP requests, IBM Cloud® Code Engine also supports applications that use WebSockets as their communications protocol. An app contains one or more revisions. A revision represents an immutable version of the configuration properties of the app. Each update of an app configuration property creates a new revision of the app.

Use revision commands to manage application revisions.

You must be within the context of a [project](https://cloud.ibm.com/docs/cli?topic=cli-clicli-project) before you use revision commands.

For more information about working with revisions for apps, see [Deploying applications](https://cloud.ibm.com/docs/codeengine?topic=codeengine-application-workloads).

You can use either revision or rev in your revision commands. To see CLI help for the revision commands, run ibmcloud ce revision -h.



 ibmcloud ce revision delete 

Delete an application revision.

ibmcloud ce revision delete --name REVISION_NAME [--force] [--ignore-not-found] [--quiet]



 Command Options 

--name, -n
: The name of the application revision. This value is required.

--force, -f
: Force deletion without confirmation. This value is optional. The default value is false.

--ignore-not-found, --inf
: If not found, do not fail. This value is optional. The default value is false.
If you choose to create your own token, make sure that it is between 8 and 36 characters long and consists only of alphanumeric characters and the following characters: _, ., !, &, @, ?, *, +, (, ), and -.

The token must not contain repeated character sequences, dictionary words, user names, or other predefined sequences.
8. Verify the summary information is correct and then click Add to add the connection.
9. In the device information page, copy and save the following details:



* Organization ID
* Device type
* Device ID
* Authentication method
* Authentication token



You'll need the organization ID, device type, device ID, and authentication token to configure your device to connect to Watson IoT Platform.







 Step 2: Connect your device to Watson IoT Platform 

After you register a device with Watson IoT Platform, you can use the registration information to connect the device and start receiving device data.

Tip: Connection recipes are available for some commonly used devices at [Device connection recipes ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://developer.ibm.com/recipes/tutorials/category/internet-of-things-iot/) on IBM.com.

To connect a device to Watson IoT Platform:



1. Set up your device for MQTT messaging and authenticate by using the organization ID, device type, device ID, and authentication token.
2. Send device messages to your Watson IoT Platform organization by using the MQTT protocol.

The following information is required when connecting your device:



* URL: org_id.messaging.internetofthings.ibmcloud.com

Where org_id is the ID of your Watson IoT Platform organization.
* Port:



* 1883 (disabled by default)
* 8883 (encrypted)
* 443 (websockets)



* Device ID: org_id:device_type:device_id
* User name: use-token-auth
* Password: Authentication token
You can adjust the IOPS by using an API call to the SOAP web service. The following sample API calls can be called from the scripting language of your choice.

For more information about the SLAPI, see the [SLDN](http://sldn.softlayer.com/reference/softlayerapi).



* Adjust IOPS on Performance storage volume.

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://api.service.softlayer.com/soap/v3.1/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Header>
<ns1:authenticate>
</ns1:authenticate>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<ns1:placeOrder>
<orderData xsi:type="ns1:SoftLayer_Container_Product_Order_Network_Storage_AsAService_Upgrade">
<volume xsi:type="ns1:SoftLayer_Network_Storage">
<id xsi:type="xsd:int">XXXXXXXXX</id>
</volume>
<iops xsi:type="xsd:int">2007</iops> 
<packageId xsi:type="xsd:int">759</packageId>
PUT /v1/{crn}/zones/{domain_id}/setting/mobile_redirect internet-svcs.performance.update internet-svcs.mobile-redirect-setting.update 
 Get prefetch / preload settings. GET /v1/{crn}/zones/{domain_id}/setting/prefetch_preload internet-svcs.performance.read internet-svcs.prefetch-preload-setting.read 
 Update prefetch / preload settings. PUT /v1/{crn}/zones/{domain_id}/setting/prefetch_preload internet-svcs.performance.update internet-svcs.prefetch-preload-setting.update 
 Get HTTP2 settings. GET /v1/{crn}/zones/{domain_id}/setting/http2 internet-svcs.security.read internet-svcs.http2-setting.read 
 Update HTTP2 settings. PUT /v1/{crn}/zones/{domain_id}/setting/http2 internet-svcs.security.update internet-svcs.http2-setting.update 
 Get IPv6 settings. GET /v1/{crn}/zones/{domain_id}/setting/ipv6 internet-svcs.zones.read internet-svcs.ipv6-setting.read 
 Update IPv6 settings. PUT /v1/{crn}/zones/{domain_id}/setting/ipv6 internet-svcs.zones.update internet-svcs.ipv6-setting.update 
 Get websocket settings. GET /v1/{crn}/zones/{domain_id}/setting/websocket internet-svcs.zones.read internet-svcs.websockets-setting.read 
 Update websocket settings. PUT /v1/{crn}/zones/{domain_id}/setting/websocket internet-svcs.zones.update internet-svcs.websockets-setting.update 
 Get response buffering settings.
: The buildpack contains security fixes for the [Apache HttpComponents and Java overlay feature vulnerabilities](https://www.ibm.com/blogs/psirt/ibm-security-bulletin-multiple-vulnerabilities-fixed-in-liberty-for-java-for-ibm-bluemix-cve-2012-6153-cve-2014-3577-cve-2015-0178/).



* The buildpack contains an updated version of the Liberty profile based on the [February beta](https://developer.ibm.com/wasdev/blog/2015/02/13/announcing-liberty-beta-tools-february-2015/). The updated version of the Liberty profile provides an updated version of the WebSocket GA feature websocket-1.1. It also makes the following Java EE 7 beta features available in IBM Cloud: cdi-1.2, el-3.0, jsp-2.3, jca-1.7, jacc-1.5, and jaspic-1.1.
* The buildpack provides integration with the [JRebel tool](https://www.jrebel.com/products/jrebel). The integration makes it easy to use JRebel with IBM Cloud apps and perform instant app updates without redeploying or restaging the app. Only stand-alone web apps are supported.







 6 February 2015 

Updated Liberty buildpack v1.12-20150130-1016
: The buildpack contains an updated version of the Liberty profile based on the [January beta](https://developer.ibm.com/wasdev/blog/2015/01/16/announcing-liberty-beta-tools-january-2015/).



* The buildpack contains a trimmed version of the data collector for the Monitoring and Analytics service.







 23 January 2015 

Updated Liberty buildpack v1.11-20150119-1511
: The buildpack contains an updated IBM JRE version 7.1 SR2 FP1.



* It also contains an updated WebSphere eXtreme Scale Client version 8.6.0.6 and updated agent for the Auto-Scaling service.
Logging activity with a webhook 

You can log activity by making a call to an external service or application every time a customer submits input to log the conversation.

A webhook is a mechanism that allows you to call out to an external program based on events in your program.

Add a log webhook to your assistant if you want to use an external service to log Watson Assistant activity. You can log two kinds of activity:



* Messages and responses: The log webhook is triggered each time the assistant responds to user input. You can use this option as an alternative to the built-in analytics feature to handle logging yourself. (For more information about the built-in analytics support, see [Metrics overview](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-logs-overview).)

The log webhook is not supported for API clients that use the v1 /message method.



The log webhook does not return anything to your assistant.

For environments where private endpoints are in use, keep in mind that a webhook sends traffic over the internet. For more information, see [Private network endpoints](https://cloud.ibm.com/docs/assistant?topic=assistant-securitysecurity-private-endpoints).



 Defining the webhook 

You can define one webhook URL to use for logging every incoming message.

The programmatic call to the external service must meet these requirements:



* The call must be a POST HTTP request.



To add the webhook details, complete the following steps:



1. From your assistant, click the ![Overflow menu](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/kebab.png) icon, and then choose Settings.
2. Click Webhooks > Log webhook.
3. Set the Log webhook switch to Enabled.

If you cannot enable the webhook, you might need to upgrade your service plan.