vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Alternatively, if you are using an SDK, [obtain an IAM API key](https://cloud.ibm.com/iam/apikeys) and set the client options by using environment variables.

export CD_TOOLCHAIN_AUTH_TYPE=iam && export CD_TOOLCHAIN_APIKEY={iam_api_key} && export CD_TOOLCHAIN_URL={base_url}
2. [Look up the ID of the toolchain](https://cloud.ibm.com/apidocs/toolchainlist-toolchains) in which you want to create your tool integration.
3. [Look up the tool_type_id value](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-integrationsintegrations) that corresponds to the tool integration that you want to add.
4. Add the tool integration within the targeted toolchain.



* Curl
* Java
* Node
* Python
* Go



curl -X POST --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" --header "Content-Type: application/json" --data '{ "name": "{tool_name}", "tool_type_id": "{tool_type_id}", "parameters": {tool_parameters} }' "{base_url}/toolchains/{toolchain_id}/tools"

import com.ibm.cloud.continuous_delivery.cd_toolchain.v2.CdToolchain;
import com.ibm.cloud.continuous_delivery.cd_toolchain.v2.model.;
...
CdToolchain toolchainService = CdToolchain.newInstance();
CreateToolOptions createToolOptions = new CreateToolOptions.Builder()
.name({tool_name})
.parameters({tool_parameters})
.toolchainId({toolchain_id})
[“Develop a Code Engine app" toolchain](http://cloud.ibm.com/devops/setup/deploy?repository=https%3A%2F%2Fgithub.com%2Fopen-toolchain%2Fcode-engine-toolchain)<br><br>Available in Dallas, Washington, Toronto, Sao Paulo, Frankfurt, Tokyo, Sydney, Osaka, and London With this toolchain, you can develop and deploy an application securely into Code Engine, a shared, multi-tenant Kubernetes service on IBM Cloud. By default, the toolchain uses a sample Node.js "Hello World" app, but you can link to your own GitHub repository instead. This toolchain is preconfigured for continuous integration, continuous delivery with source control, issue tracking, and online editing.<br><br>Try the tutorial: [Develop and deploy an app by using Code Engine](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-tutorial-cd-code-engine) Delivery Pipeline<br><br>Git Repos and Issue Tracking<br><br>IBM Cloud® Code Engine 
 [Build your own toolchain](https://cloud.ibm.com/devops/setup/deploy?repository=https%3A%2F%2Fgithub.com%2Fopen-toolchain%2Fempty-toolchain)<br><br>Available in Dallas, Washington, Toronto, Sao Paulo, Tokyo, Sydney, Osaka, Frankfurt, and London This toolchain has no preconfigured tools. If you are already familiar with toolchains, you can set up your own toolchain. None
* [Deploying your application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-tutorialcftut-build2-application)
* [Clean up](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-tutorialcftut-clean-up)
* [Next steps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-migrate-cf-ce-tutorialcftut-migrate-next)







 Running a function from local source 

[Running a function from local source](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-tutorialfun-tutorial)



* [Set up your environment](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-tutorialfun-tutorial-envirn)
* [Create the source code](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-tutorialfun-tutorial-sourcecode)
* [Create your function](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-tutorialfun-tutorial-create)
* [Invoke your function](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-tutorialfun-tutorial-invoke)
* [Provide parameters for your function](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-tutorialfun-tutorial-parameters)
* [Clean up](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-tutorialfun-tutorial-clean-up)
* [Write secure Java web apps](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-secure_java_web_app)
* [Adding certificates to the Liberty keystore](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-cert_liberty_keystore)
* [Configure logging and tracing](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-logging_tracing)
* [Configure bound services](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-auto_config)
* [Customize the JRE](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-customizing_jre)
* [Use your own JRE](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-using_own_jre)
* [Install Liberty features](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-install-features)
* [Use the monthly runtime](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-using_monthly_runtime)
* [Use the beta features](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-using_beta_features)
* [Use JConsole to monitor Liberty in IBM Cloud](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-jconsole)
* [Use Dynatrace to monitor Liberty in IBM Cloud](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-using_dynatrace)
[Build your own toolchain](https://cloud.ibm.com/devops/setup/deploy?repository=https%3A%2F%2Fgithub.com%2Fopen-toolchain%2Fempty-toolchain)<br><br>Available in Dallas, Washington, Toronto, Sao Paulo, Tokyo, Sydney, Osaka, Frankfurt, and London This toolchain has no preconfigured tools. If you are already familiar with toolchains, you can set up your own toolchain. None 
 Continuous Delivery toolchain<br><br>Available in Dallas, Washington, Tokyo, Sydney, Frankfurt, and London This toolchain is used when you enable continuous delivery for an app.<br><br>Try the tutorials:<br><br>[Add a toolchain to an app](https://www.ibm.com/cloud/architecture/tutorials/add-a-toolchain-to-an-app) Delivery Pipeline<br><br>GitHub and Issues<br><br>IBM Cloud 







 Toolchain Terraform 

You can use Terraform to define, create, and manage toolchains by using an as code approach.

You can start with an IBM Cloud Terraform Provider example, such as [ibm-cd-toolchain-simple-helm](https://github.com/IBM-Cloud/terraform-provider-ibm/tree/master/examples/ibm-cd-toolchain-simple-helm) or [ibm-cd-tekton-pipeline](https://github.com/IBM-Cloud/terraform-provider-ibm/tree/master/examples/ibm-cd-tekton-pipeline), or you can write your own Terraform.

To start working with Terraform, see [Setting up Terraform for Continuous Delivery](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-terraform-setup).
See [Deploying your app with commands and arguments](https://cloud.ibm.com/docs/codeengine?topic=codeengine-application-workloadsdeploy-app-cmd-args).
* Want to define environment variables for your application? Find out how with [Working with environment variables](https://cloud.ibm.com/docs/codeengine?topic=codeengine-envvar).
* Does your application take advantage of configmaps or secrets? Take a look at [Working with secrets](https://cloud.ibm.com/docs/codeengine?topic=codeengine-secret) or [Working with configmaps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-configmap).
* Do you want to deploy your app in a toolchain? See [Integrating Code Engine workloads with Continuous Delivery](https://cloud.ibm.com/docs/codeengine?topic=codeengine-toolchain-ce).
* Do you want to use Terraform to deploy your app? Find out more with [Setting up Terraform for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-terraform-setup-ce).



Ready to deploy?



* [Deploy application workloads from a public repository](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-app).
* [Deploy application workloads from images in Container Registry](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-app-crimage).
* [Deploy application workloads from images in a private repository](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-app-private).
[Twilio All products and services icon](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/twilio-products.png), click Phone numbers.
4. Follow the instructions to get a phone number.

When you get a Twilio phone number, it supports voice, SMS, and MMS automatically. Your new phone number is listed as an active number.



Keep the Twilio web page open in a web browser tab so you can refer to it again later.



 Migrating from Voice Agent with Watson 

If you created an IBM® Voice Agent with Watson service instance in IBM Cloud to enable customers to exchange text messages with an assistant, use the SMS with Twilio integration instead.

The SMS with Twilio integration provides a more seamless integration with your assistant and supports as many Twilio phone numbers as needed. However, the integration currently does not support the following functions:



* Starting an SMS-only interaction with an outgoing text
* Configuring backup locations
* Reviewing the usage summary page. Use IBM Log Analysis instead. For more information, see [Viewing logs](https://cloud.ibm.com/docs/assistant?topic=assistant-deploy-phonedeploy-phone-logs).



To migrate from Voice Agent with Watson to the Watson Assistant SMS with Twilio integration, complete the following step:



1. Do one of the following things:



* If your Voice Agent with Watson service instance uses an SMS service provider other than Twilio, you cannot continue to use it. You must create an SMS account with Twilio first. Complete the [Before you begin](https://cloud.ibm.com/docs/assistant?topic=assistant-deploy-smsdeploy-sms-service-setup) steps to create the account. Next, set up the integration.
* If your Voice Agent with Watson service instance uses Twilio as its SMS provider, you can go directly to setting up the integration.











 Set up the integration
--strategy buildpacks Build your code and deploy the app in a single step.
: ibmcloud ce job create --build-source . --strategy buildpacks Build your code and deploy the job in a single step.

You can perform these tasks from a single web page in the [Code Engine console](https://cloud.ibm.com/codeengine/overview).





 Bind a Service to a workload 

Cloud Foundry
: ibmcloud cf bind-service [AppName] [ServiceInstance]https://cli.cloudfoundry.org/en-US/v6/bind-service.html

Code Engine
: ibmcloud ce app bind --name [AppName] --service-instance [ServiceInstance]
: ibmcloud ce job bind --name [JobName] --service-instance [ServiceInstance]





 Update applications or jobs commands 

Cloud Foundry
: ibmcloud cf scale ...
: ibmcloud cf set-env ...
: ibmcloud cf push ...
: ibmcloud cf delete ...

For example, to scale your application to 2 instances, 1 G of memory, and restart it, run cf scale APP_NAME -i 2 -m 1G -f

Code Engine
: ibmcloud ce app update ...
: ibmcloud ce job update ...

You can also update your applications and jobs from the [Code Engine console](https://cloud.ibm.com/codeengine/overview).

For more information about what you can update with Code Engine, see the following topics.



* [Working with applications](https://cloud.ibm.com/docs/codeengine?topic=codeengine-application-workloads)
* [Updating an app](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-app)
* [Working with jobs and job runs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-plan)
response: status:500 message:"error in simulation: failed to execute transaction 6cbcf9f94bdef3fc68abba5604e46293ae: could not launch chaincode nodecc:1.1: error building chaincode: error building image: external builder failed: external builder failed to build: external builder 'ibp-builder' failed: exit status 3"

 Why it’s happening 

By default, a Fabric v1.4 peer creates a Node v8 runtime, and a Fabric v2.x peer creates a Node v12 runtime. In order for the smart contract to work with Node 12 runtime, the fabric-contract-api and fabric-shim node modules must be at v1.4.5 or greater.

 How to fix it 

If you are using a smart contract that was originally written to work with Fabric 1.4, update the Node modules by running the following command before deploying the smart contract on a Fabric v2.x peer. See [Support and compatibility for fabric-chaincode-node](https://github.com/hyperledger/fabric-chaincode-node/blob/main/COMPATIBILITY.md) for more information.

npm install --save fabric-contract-api@latest-1.4 fabric-shim@latest-1.4





 Why is the smart contract that I installed on the peer not listed in the UI? 

 What’s happening 

A smart contract was installed on a peer but when you click on the Smart contracts tab, it is not listed.

 Why it’s happening 

This issue can occur when another user or application installs the smart contract onto the peer and you do not have the peer admin identity in your browser wallet.

 How to fix it 

In order to view the smart contracts installed on a peer, you need to be a peer admin. Ensure that the peer admin identity exists in your browser wallet. If it does not, you need to import it into your console wallet.





 My nodes, channels, smart contracts, and identities have disappeared from the console. How can I get them back? 

 What’s happening
Developing with Visual Studio 

IBM® Cloud Foundry is deprecated and no longer supported as of 1 June 2023. For more information, see the [deprecation details](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecationdep_details).



1.  If you don't already have Visual Studio, install Visual Studio 2015 or Visual Studio Code by following the [documentation](https://docs.microsoft.com/en-us/visualstudio/install/install-visual-studio-2015).
2.  [Download your starter code](https://cloud.ibm.com/) and extract it into a folder on your hard disk drive.
3.  Open the project in Visual Studio.



*  If you're using Visual Studio 2015, open the .sln file by going to File > Open > Project/Solution.
*  If you're using Visual Studio Code, open the folder that contains the .sln file by going to File > Open.



4.  After you modify your code, you can redeploy it by using the command line interface (CLI). See [Deploying apps with the Cloud Foundry CLI](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-cf-deploy-cli).
* [Exporting, importing, and deleting a smart contract package](https://cloud.ibm.com/docs/blockchain?topic=blockchain-develop-vscodedevelop-vscode-exporting-deleting-smart-contract-package)



* [Step four: Deploy a smart contract to a preconfigured Hyperledger Fabric network](https://cloud.ibm.com/docs/blockchain?topic=blockchain-develop-vscodedevelop-vscode-deploy)



* [Deploying a preconfigured Hyperledger Fabric network](https://cloud.ibm.com/docs/blockchain?topic=blockchain-develop-vscodedevelop-vscode-connecting-and-disconnecting)
* [Deploying your smart contract (channel application capability V2)](https://cloud.ibm.com/docs/blockchain?topic=blockchain-develop-vscodedevelop-vscode-deploy-smart-contract-v2)
* [Deploying your smart contract (channel application capability V1)](https://cloud.ibm.com/docs/blockchain?topic=blockchain-develop-vscodedevelop-vscode-deploy-smart-contract)
* [Interacting with your smart contract](https://cloud.ibm.com/docs/blockchain?topic=blockchain-develop-vscodedevelop-vscode-submitting-transactions)
* [Connecting your applications to the preconfigured network](https://cloud.ibm.com/docs/blockchain?topic=blockchain-develop-vscodedevelop-vscode-exploring-connection-details)



* [Step five: Test a deployed smart contract](https://cloud.ibm.com/docs/blockchain?topic=blockchain-develop-vscodedevelop-vscode-testing-instantiated-smart-contract)
: The Schematics enhances the bastion host configuration as an optional parameter in the [create](https://cloud.ibm.com/apidocs/schematics/schematicscreate-action) and [update](https://cloud.ibm.com/apidocs/schematics/schematicsupdate-action) action APIs if the inventory connection type is set to winrm.

Schematics Actions API enhancement to support bastion host connection with non-root user
: The Schematics Actions API now supports bastion host connection with non-root user and the ssh in the [create](https://cloud.ibm.com/apidocs/schematics/schematicscreate-action) and [update](https://cloud.ibm.com/apidocs/schematics/schematicsupdate-action) action APIs.

IBM Cloud Schematics job queue process
: For more information about job queue process, see [Executing process of the Schematics job queue](https://cloud.ibm.com/docs/schematics?topic=schematics-job-queue-process) and [FAQ](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqjob-queue-faq).

Schematics Actions APIs enhances the credentials parameter
: You can now access the inventory username through the credentials parameter in the [create](https://cloud.ibm.com/apidocs/schematics/schematicscreate-action) and [update](https://cloud.ibm.com/apidocs/schematics/schematicsupdate-action) action APIs.

Schematics introduces compact flag in the workspace create and update API
: You can now download the sub directory from the GIT repositories through Schematics. For more information, see [How can I download sub directory from the GIT repositories through Schematics?](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqcompact-faq).
In each case, the data points on the graph adjust to an appropriate measurement period. For example, when viewing a graph for a day, the data is presented in hourly values, but when viewing a graph for a week, the data is shown by day. A week always runs from Sunday through Saturday.

You can create custom time periods also, such as a week that runs from Thursday to the following Wednesday, or a month that begins on any date other than the first.

The time shown for each conversation is localized to reflect the time zone of your browser. However, API log calls are always shown in UTC time. As a result, if you choose a single day view, for example, the time shown in the visualization might differ from the timestamp specified in the log for the same conversation.

![Time period control](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/oview-time2.png)
* Intents and Entities filters - Use either of these drop-down filters to show data for a specific intent or entity in your skill.

The intent and entities filters are populated by the intents and entities in the skill, and not what is in the data source. If you have [selected a data source](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-logslogs-deploy-id) other than the skill, you might not see an intent or entity from your data source logs as an option in the filters, unless those intents and entities are also in the skill.
* Refresh data: Select Refresh data to refresh the data that is used in the page metrics.

The statistics show traffic from customers who interact with your assistant; they do not include interactions from the Try it out pane.







 Scorecards 

The scorecards give you a quick view of your metrics. Scroll to see full interactive graphs later in the page.

!
Other items, such as Last 90/7/1 days and Custom timeframe are available in the Time frame list.

Zoom

![Custom time overview](https://cloud.ibm.com/docs-content/v1/content/006fd22ab2811b7d19804c763a00568b3da4c03a/CDN/images/metrics-custom-time-overview.png)

Figure 3: Custom time overview

On the Overview page, you can find a graphical representation of the Total Bandwidth, Bandwidth per Region, Total Hits, and Hits By Type metrics.

Zoom

![Metrics graphs](https://cloud.ibm.com/docs-content/v1/content/006fd22ab2811b7d19804c763a00568b3da4c03a/CDN/images/metrics-custom-time-graphs.png)

Figure 4: Custom time graphs

The maximum number of days that you can view metrics reports is 90 days. Start and end time for the historical time range is fixed.





 Most recent metrics report 

Select Most recent from the Time frame list on the Overview page. Here you can see the Total Bandwidth, Total Hits for the selected time period Most recent.

Zoom

![Most recent overview](https://cloud.ibm.com/docs-content/v1/content/006fd22ab2811b7d19804c763a00568b3da4c03a/CDN/images/metrics-most-recent-overview.png)

Figure 5: Most recent overview

You can also find a graphical representation of Total Bandwidth, Total Hits, and Hits By Type.

Zoom

![Most reent graphs](https://cloud.ibm.com/docs-content/v1/content/006fd22ab2811b7d19804c763a00568b3da4c03a/CDN/images/metrics-most-recent-graphs.png)
Troubleshooting for quota dashboard 

If the quota dashboard does not display metrics as expected, the following methods are used for troubleshooting.



 Adjust the time range of the dashboard’s view 

When an event that generates a metric is not visible on the dashboard, first check the time interval set for the dashboard. If the interval is too large, or the event is out of the interval's scope, events are not visible.

To adjust the time interval for the dashboard



1. Select the time bar on the dashboard that displays a timeframe, such as 9:20 AM - 10:20 AM.
2. Adjust the value in the From textbox to change the date and time the interval begins.
3. Adjust the value in the To text boxes to change the date and time the interval ends.
4. Save the values. The dashboard refreshes.







 Generating a metric 



 Create or delete a resource 

Creating or deleting one of the following resources sends metric events for the associated quota resource name.



* vpc



* For more information on creating a VPC, see [Getting started with Virtual Private Cloud (VPC)](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started&interface=uicreate-and-configure-vpc).



* security-group



* For more information, see [About security groups](https://cloud.ibm.com/docs/vpc?topic=vpc-using-security-groups&interface=ui).



* subnet
For example, if the interval is 1 hour, then each data point represents 5 minutes of data. If the interval is 2 weeks, then each data point represents 24 hours of data.







 Enabling metrics monitoring 

To receive monitoring metrics, you must set up IBM Cloud Monitoring with a monitoring instance.

To do so, follow these steps:



1. Navigate to the [metrics monitoring portal](https://cloud.ibm.com/observe/monitoring), then click Create a monitoring instance.
2. Select a region for your monitoring instance.

If you do not have an existing load balancer, see [Creating a network load balancer](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-ui-creating-network-load-balancer) to provision one.

The region should match the location of your existing load balancer.
3. Choose your pricing plan.

Pricing plan details are explained in the selection window. Select the plan that best meets your requirements.
4. Provide a unique service name for your instance.
5. Optionally, select a resource group. A resource group is a way to organize account resources in customizable groupings. Any account resource that is managed by using IBM Cloud Identity and Access Management (IAM) access control belongs to a resource group within your account.

If you do not have any pre-configured resource groups, or no reason to share this resource selectively, use the default selection.

If your account has multiple resource groups, you can choose which one has access to this monitoring instance. This allows you to have metrics available to some resource groups and not to others.
6. Select the Enable Platform Metrics checkbox. You must select this to receive metrics from your load balancer.
7. Click Create. You are taken back to the monitoring metrics home page.



Within a few minutes, your new monitoring instance is displayed with several configurations. You might have to refresh your browser to see it.





 Working with the IBM Cloud Monitoring dashboard 

To view and work with your monitoring metrics, follow these steps:



1.