vania-janet/multiturn-rag-retrieval-data huggingface dataset:
private.au-syd.kms.cloud.ibm.com crn:v1:bluemix:public:kms:au-syd:::endpoint:private.au-syd.kms.cloud.ibm.com 
 private.jp-tok.kms.cloud.ibm.com crn:v1:bluemix:public:kms:jp-tok:::endpoint:private.jp-tok.kms.cloud.ibm.com 
 Washington 
 private.us-south.kms.cloud.ibm.com crn:v1:bluemix:public:kms:us-south:::endpoint:private.us-south.kms.cloud.ibm.com 
 private.us-east.kms.cloud.ibm.com crn:v1:bluemix:public:kms:us-east:::endpoint:private.us-east.kms.cloud.ibm.com 
 private.eu-gb.kms.cloud.ibm.com crn:v1:bluemix:public:kms:eu-gb:::endpoint:private.eu-gb.kms.cloud.ibm.com 
 private.eu-de.kms.cloud.ibm.com crn:v1:bluemix:public:kms:eu-de:::endpoint:private.eu-de.kms.cloud.ibm.com 
 private.au-syd.kms.cloud.ibm.com crn:v1:bluemix:public:kms:au-syd:::endpoint:private.au-syd.kms.cloud.ibm.com 
 private.jp-tok.kms.cloud.ibm.com crn:v1:bluemix:public:kms:jp-tok:::endpoint:private.jp-tok.kms.cloud.ibm.com 
 Sydney 
 private.us-south.kms.cloud.ibm.com crn:v1:bluemix:public:kms:us-south:::endpoint:private.us-south.kms.cloud.ibm.com
: An error that was displayed when you launched Watson Assistant from the IBM Cloud® dashboard has been fixed. Previously, an error message that said, Module 'ui-router' is not available! You either misspelled the module name or forgot to load it would sometimes be displayed.





 12 December 2019 

Support for private network endpoints
: Users of Premium plans can create private network endpoints to connect to Watson Assistant over a private network. Connections to private network endpoints do not require public internet access. For more information, see [Protecting sensitive information](https://cloud.ibm.com/docs/assistant?topic=assistant-security).

Full support for IBM Cloud IAM
: Watson Assistant now supports the full implementation of IBM Cloud Identity and Access Management (IAM). API keys for Watson services are no longer limited to a single service instance. You can create access policies and API keys that apply to more than one service, and you can grant access between services.



* To support this change, the API service endpoints use a different domain and include the service instance ID. The pattern is api.{location}.{offering}.watson.cloud.ibm.com/instances/{instance_id}.

Example URL for an instance hosted in the Dallas location: api.us-south.assistant.watson.cloud.ibm.com/instances/6bbda3b3-d572-45e1-8c54-22d6ed9e52c2

The previous public endpoint domain was watsonplatform.net.

For more information, see the [API reference](https://cloud.ibm.com/apidocs/assistant/assistant-v2service-endpoint).

These URLs do not introduce a breaking change. The new URLs work both for your existing service instances and for new instances. The original URLs continue to work on your existing service instances for at least one year (until December 2020).
* For more information, see [Authenticating to Watson services](https://cloud.ibm.com/docs/watson?topic=watson-iam).







 26 November 2019 

Disambiguation is available to everyone
<-- </ol> --><-- </section "class="ph" id="section-vpe-api-private-endpoint-setup-api" "> --><-- <section "class="ph" id="section-vpe-api-private-endpoint-terraform" "> --> Accessing the VPC API private endpoint with Terraform To access the VPC API private endpoint using Terraform, do one of the following:<-- <ul> --> * Set an environment variable for the region that you want to access. For example, for us-south, enter:
export IBMCLOUD_IS_NG_API_ENDPOINT=https://us-south.private.iaas.cloud.ibm.com/v1
* Declare the provider block. For example:
provider "ibm" {
region = "us-south"
visibility = "private"
}
<-- </ul> --><-- </section "class="ph" id="section-vpe-api-private-endpoint-terraform" "> --><-- <section "id="section-vpe-related-links" "> --> Related links For more information, see the following topics:<-- <ul> --> * About virtual private endpoint gateways]] * Getting started with IBM Cloud Direct Link]] * Getting started with IBM Cloud Transit Gateway]] ! ! ! ! !
Invoke the Function URL with a parameter by adding ?name=Sunshine to the end of the URL and pasting it into a browser window.

https://funhello.13c66hbi3rhz.us-south.codeengine.appdomain.cloud?name=Sunshine

Hello, Sunshine!





 Clean up 

You can delete your function with the following command.

ibmcloud ce fn delete -n funhello

When you delete your function, the associated build files are also deleted.

Lastly, delete the code bundle that the build created from IBM Cloud Container Registry.



1. Navigate to [Registry](https://cloud.ibm.com/registry/start) in the IBM Cloud console.
2. Find the code bundle that are associated with your function by searching for your function name.
3. Select the code bundle and Delete.







 Next steps 

Looking for more code examples? Check out the [Samples for IBM Cloud Code Engine GitHub repo](https://github.com/IBM/CodeEngine).
target_ids = [ibm_atracker_target.atracker_target-us-south.id]
}
}
data "ibm_atracker_endpoints" "atracker_endpoints" {}
Show more





 How to update the V1 Terraform script to migrate to V2 for 1 region 

When you migrate resources from V1 to V2, make sure that you configure the account settings before migrating your account configuration. You should set the permitted-target-regions list with all the regions where you have currently defined targets in your account. You must set the metadata-region-primary and the default-targets target. You must set a current V1 target as a default target in the settings account configuration.

The following code shows how to update the V1 Terraform configuration in 1 region to migrate your resources to a V2 API configuration:

provider "ibm" {
region = "us-south"
}

resource "ibm_atracker_target" "atracker_target-us-south" {
name = var.cos_target_name
target_type = "cloud_object_storage"
cos_endpoint {
endpoint = var.cos_endpoint
target_crn = var.cos_target_crn
bucket = var.cos_bucket_name
api_key = var.cos_api_key
}
}

 This is new in version 2. MUST BE DEFINED before migration
resource "ibm_atracker_settings" "atracker_settings" {
metadata_region_primary = "us-south"
default_targets = [ibm_atracker_target.atracker_target-us-south.id]
permitted_target_regions = ["us-south", "us-east"]
private_api_endpoint_only = false
}

resource "ibm_atracker_route" "atracker_route_instance-us-south" {
name = var.route_name
receive_global_events=true
rules {
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).



Ready to deploy?



* [Creating Function workloads with inline code](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-create-inlinecode).
* [Creating Function workloads with repository source code](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-create-repo).
* [Creating Function workloads from local source code](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-create-local).



Want to add more customizations?



* Want to integrate with other IBM Cloud services? See [Integrating IBM Cloud services with service binding](https://cloud.ibm.com/docs/codeengine?topic=codeengine-service-binding).







 Log and monitor your workloads 

Logging can help you troubleshoot your applications, jobs and functions. See [Viewing logs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-view-logs).

You can also [view, manage, and audit](https://cloud.ibm.com/docs/codeengine?topic=codeengine-at_events) user-initiated activities that occur in your Code Engine project.

Finally, analyze performance metrics by collecting information with [IBM Cloud Monitoring](https://cloud.ibm.com/docs/codeengine?topic=codeengine-monitor). You can create [custom dashboards to monitor Code Engine workloads](https://cloud.ibm.com/docs/codeengine?topic=codeengine-monitor-custom).





 Migrate your workloads
* [Webhook](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-destinations-webhook)
* [IBM Cloud Functions](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-destinations-cloud-functions)
* [Code Engine](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-destinations-codeengine)
* [IBM Cloud Object Storage](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-destinations-cloud-object-storage)
London eu-gb.kms.cloud.ibm.com 
 Frankfurt eu-de.kms.cloud.ibm.com 
 Sydney au-syd.kms.cloud.ibm.com 
 Tokyo jp-tok.kms.cloud.ibm.com 
 Osaka jp-osa.kms.cloud.ibm.com 
 Toronto ca-tor.kms.cloud.ibm.com 
 São-Paulo br-sao.kms.cloud.ibm.com 



For more information about authenticating with Key Protect, see [Accessing the API](https://cloud.ibm.com/docs/key-protect?topic=key-protect-set-up-api).
To learn more about VRF, see [Virtual routing and forwarding on IBM Cloud](https://cloud.ibm.com/docs/dl?topic=dl-overview-of-virtual-routing-and-forwarding-vrf-on-ibm-cloud).

To learn how to configure Delivery Pipeline Private Workers to connect to Continuous Delivery by using private endpoints, see [Configuring the Delivery Pipeline Private Worker to use private endpoints](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-install-private-workersinstall_pw_agent_pse).

Review the following table to determine the private API endpoints to use when you connect to the [Continuous Delivery API](https://cloud.ibm.com/docs?tab=api-docs&category=devops&subCategory=ContinuousDelivery).



Table 2. Private endpoints for interacting with Continuous Delivery APIs over IBM Cloud's private network

 Region Private endpoints 

 Dallas private.us-south.devops.cloud.ibm.com 
 Washington DC private.us-east.devops.cloud.ibm.com 
 London private.eu-gb.devops.cloud.ibm.com 
 Frankfurt private.eu-de.devops.cloud.ibm.com
* Updated the Composer topic.
* Added information about adding an IBM Cloud Functions Channel to IBM Cloud Monitoring.
* Added information for versioning your actions.



* [12 March 2021](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-mar1221)



* Added support for au-syd (Sydney) region.





* [January 2021](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-jan21)



* [29 January 2021](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-jan2921)



* Added a sitemap.
* Updated information about packaging Go source files.





* [December 2020](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-dec20)



* [14 December 2020](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-dec1420)



* Added versions to Quick start template docs.
* Updated securing web actions to include information about X-Require-Whisk-Auth.
* Added tips to monitoring topic.
* Updated namespace instances to indicate if the namespace name or the namespace ID is required.





* [October 2020](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-oct20)



* [29 October 2020](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-openwhisk-relnotesopenwhisk-oct2920)



* GO 1.15 is now supported.
For more information, see [New system entities](https://cloud.ibm.com/docs/assistant?topic=assistant-system-entities).





 14 January 2020 

Fixed an error message that was displayed when opening an instance
: An error that was displayed when you launched Watson Assistant from the IBM Cloud® dashboard has been fixed. Previously, an error message that said, Module 'ui-router' is not available! You either misspelled the module name or forgot to load it would sometimes be displayed.





 12 December 2019 

Support for private network endpoints
: Users of Premium plans can create private network endpoints to connect to Watson Assistant over a private network. Connections to private network endpoints do not require public internet access. For more information, see [Protecting sensitive information](https://cloud.ibm.com/docs/assistant?topic=assistant-security).

Full support for IBM Cloud IAM
: Watson Assistant now supports the full implementation of IBM Cloud Identity and Access Management (IAM). API keys for Watson services are no longer limited to a single service instance. You can create access policies and API keys that apply to more than one service, and you can grant access between services.



* To support this change, the API service endpoints use a different domain and include the service instance ID. The pattern is api.{location}.{offering}.watson.cloud.ibm.com/instances/{instance_id}.

Example URL for an instance hosted in the Dallas location: api.us-south.assistant.watson.cloud.ibm.com/instances/6bbda3b3-d572-45e1-8c54-22d6ed9e52c2

The previous public endpoint domain was watsonplatform.net.

For more information, see the [API reference](https://cloud.ibm.com/apidocs/assistant/assistant-v2service-endpoint).

These URLs do not introduce a breaking change. The new URLs work both for your existing service instances and for new instances. The original URLs continue to work on your existing service instances for at least one year (until December 2020).
You also need an instance of [NeuralSeek on IBM Cloud](https://cloud.ibm.com/catalog/services/neuralseek).
2. In NeuralSeek, open the Configure page and enter your information in the Discovery instance details section.
3. On the Integrate page, and click the OpenAPI file link to download the NeuralSeek.json OpenAPI specification file configured for your instance.
4. Also on the Integrate page, copy the API key for NeuralSeek. The API key for NeuralSeek is not the same as the API key for Discovery that you used on the Configure page. The API key for NeuralSeek is only available on the Integrate page.



Simple instructions for setting up NeuralSeek are available on the Integrate page. You can also follow those instructions to get NeuralSeek working with Watson Assistant.





 Create and add extension 



1. In your assistant, on the Integrations page, click Build custom extension and use the OpenAPI specification file to build a custom extension. For general instructions on building any custom extension, see [Building the custom extension](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-build-custom-extensionbuilding-the-custom-extension).
2. After you build the NeuralSeek extension and it appears on your Integrations page, click Add to add it to your assistant. Use your NeuralSeek API key to authenticate. For general instructions on adding any custom extension, see [Adding an extension to your assistant](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-add-custom-extension).







 Add the NeuralSeek starter kit action template 



1. Open the Actions page.
2. If you have no actions, choose Create a new action. If you already have some actions, choose New action.
3. On Create an action, choose Quick start with templates.

Quick start with templates is available in English-language assistants only.
4. On Quick start with templates, add the NeuralSeek search starter kit.







 Edit system actions
For more information about the actions to take, see [Updating endpoint URLs from watsonplatform.net](https://cloud.ibm.com/docs/watson?topic=watson-endpoint-change).



* Verify that the API key in your call matches the URL in the service instance.
* Validate the role that is associated with your credentials. The service access role that is associated with your API key determines which endpoints and methods you can access.

For example, with a Reader role, you might not be able to edit, create, or delete anything, and might not be able to view some details of a resource.



* To manage roles through the IBM Cloud console, go to Manage > Access (IAM), and then select Users, Access groups, or Service IDs to get started.
* For more information about access to Watson Assistant resources, see [Managing access to resources](https://cloud.ibm.com/docs/assistant?topic=assistant-access-control).
* For more information about roles required for other Watson services, see [IAM roles and actions](https://cloud.ibm.com/docs/account?topic=account-iam-service-roles-actions) and search for your service.
* For more information about IAM roles in IBM Cloud, see [Access management](https://cloud.ibm.com/docs/account?topic=account-cloudaccess).
API target urls: apiconnect-3aa7087d-b454-4e13-bbc5-8228ebe00eef.pszetousibmcom-dev.apic.cloud.ibm.com/
API invoke tls-profile: client:Loopback-client



8. Next, you must modify the Product definitions with the values that are returned during the publish time. To do this complete the following steps:



1. In the API Designer UI, click APIs.
2. Select your API.
3. Click Assemble.
4. In the Assembly editor, click the Filter policies icon.
5. Select DataPower Gateway policies.
6. Double-click invoke.
7. Update the following fields with the values you retrieved in step 7.



* Invoke URL: Insert the API target URL. You must specify the secure protocol HTTPS. For example:



https://apiconnect-33e7b062-092b-4227-af97-047499dab2e7.<IBM_Cloud_org>-<IBM_Cloud_space>.apic.<domain_name>$(request.path)

If you did not make a note of this value, you can retrieve by going to the management URL returned in step 7. You can also retrieve it by logging in to IBM Cloud and viewing your app information.



* TLS Profile: Insert the API invoke tls-profile. For example:



client:Loopback-client
8. Click Save to save the API.











 Creating a LoopBack API by using the API Designer 

The following procedure describes how to create a LoopBack API by using the API Designer.



 Prerequisites 

Note: The following instructions assume that you are using the latest version of the developer toolkit. To check the latest version, see the [npm](https://www.npmjs.com/package/apiconnect) package page.

First, you need to create a LoopBack project using the CLI.
[2022-01-07T01:33:13.609] [OPTIMIZED] db.redis.RedisManager - Redis trying to connect. counter 1
[2022-01-07T01:33:13.628] [OPTIMIZED] db.redis.RedisManager - Redis connected
[2022-01-07T01:33:13.629] [OPTIMIZED] db.redis.RedisManager - Redis is ready to serve!
[2022-01-07T01:33:14.614] [OPTIMIZED] Server - Server started at: https://localhost:9449











 4.0.0 



 Install Watson Assistant 4.0.0 with EDB version 1.8 

Complete this task only if you need a fresh installation of Watson Assistant 4.0.0. Do not complete this task on existing clusters with data. Completing this task on an existing cluster with data results in data loss.

If you upgraded to EDB version 1.8 and need a new installation of Watson Assistant 4.0.0, complete the following steps. In the following steps, wa is used as the name of the custom resource. Replace this value with the name of your custom resource:



1. First, apply the following patch:

cat <<EOF | oc apply -f -
apiVersion: assistant.watson.ibm.com/v1
kind: TemporaryPatch
metadata:
name: wa-postgres-180-hotfix
spec:
apiVersion: assistant.watson.ibm.com/v1
kind: WatsonAssistantStore
name: wa Specify the name of your custom resource
patchType: patchStrategicMerge
patch:
postgres:
postgres:
spec:
bootstrap:
initdb:
options:
- "--encoding=UTF8"
- "--locale=en_US.UTF-8"
- "--auth-host=scram-sha-256"
EOF
Show more
2.
Server, or Cloud address. This is most likely your IBMid password, which you use to log in to 
 IBM Cloud. 





2. Select Load Organizations to populate the list of organizations that are associated with your ID and password.
3. Select Organizations to associate the project to one of the organizations that are available.
4. Select Push to APIM, and then select Ok.
5. Select Close to close the window. A new browser tab opens in your default browser and displays your API.



Associate the IBM App Connect API with API Connect.



 Import OpenAPI API definition 

To import the OpenAPI file that is associated with the REST API project in the IBM App Connect into the API Connect service, follow these steps:



1. Log in to your API Connect service.
2. In the API Manager UI title bar, select Navigate to > Drafts.
3. Select APIs in the menu bar.
4. Select your imported API to open the API Designer.
5. Select Assemble in the navigation window. A list of policies is displayed in the navigation window.
6. Select Create assembly.
7. Add the Invoke policy by dragging it to your assembly in the main window.
8. Select the Invoke policy on the main window to modify its configuration settings.
9. Configure the host/basePath to the URL field with the following information:



* hostname: Setting that depends on your cloud instance. For more information about the host name, see [IBM App Connect Professional](https://www.ibm.com/support/knowledgecenter/en/SS3LC4_7.5.2.0/mapfiles/ic_home.html).
* basepath: Path that you specify on the httpReceive Request note in App Connect Professional orchestration.



10. Add and save your IBMid user name and password to the Http Basic authentication details that you use for App Connect Professional.







 Test the API 

To test the API, follow these steps:



1. In the Assemble tab of your API, select !
To access the database service from the Code Engine app later on, it needs the proper authorization. Thus, you create service credentials and label them slackbotkey:

ibmcloud resource service-key-create slackbotkey Manager --instance-name eventDB --output json > slackbotkey.json

The output is stored in the file slackbotkey.json and needed at a later step. Run this command to extract the database connection URL:

cat slackbotkey.json | jq '.credentials.connection.db2 | "ibm_db_sa://" + (.authentication.username + ":" + .authentication.password + "@" + .hosts[0].hostname + ":" + (.hosts[0].port | tostring) + "/" + .database + "?Security=SSL")'

The output should be of the following format: ibm_db_sa://username:password@database-hostname:port/bludb?Security=SSL;.
5. Create an instance of the Watson Assistant service. Use eventAssistant as name and the free Lite plan. Adapt us-south to your location.

ibmcloud resource service-instance-create eventAssistant conversation free us-south
6. Deploy the pre-built container image with the custom extension as Code Engine app. First, create a project:

ibmcloud ce project create --name slackbot

Then select the project as the active one:

ibmcloud ce project select --name slackbot

Then, deploy the app naming it slackbot-backend. Replace the value for the API_TOKEN (MY_SECRET) with your own secret. It is used to secure the calls to the REST API. For DB2_URI replace the parts with the database connection URL from above.
[Shows the search extension with the instance and project selected.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/tut-convo-enviro-2.png)

Figure 29. Search extension configuration
6. The default result content configuration uses the best fields; you don't need to change them.
7. In the Define the text your search will display to the end user section, edit the content to show the following message:

The Federal Reserve Economic Data website has this information:

Verify that the Emphasize the answer switch is set to On. This setting adds the find_answers:true parameter to the query request. As a result, a succinct answer to the query is shown in bold in the response that is returned by the assistant.

Zoom

![Shows the updated Message text and Emphasize the answer turned on.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/tut-convo-enviro-3.png)

Figure 30. Search extension settings configured
8. Click Create.







 Step 6: Preview the assistant 

To preview an assistant that connects to data that is stored in Discovery, you must preview the assistant from the Environments page. When you test it separately, the assistant is not able to retrieve data from Discovery.



1. From the Environments page, click Preview this environment.

Zoom

![Shows the draft environment with search extension enabled](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/tut-convo-test-0a.png)

Figure 31.