vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Important: Watson IoT Platform does not currently support the asset twins concept for data ingestion.





 Boards and cards 

Watson IoT Platform does not include APIs for importing and exporting definitions and customizations of boards and cards. You must manually recreate these in the new org.





 Enable any required extensions 

You must recreate any extensions that you have enabled in the Lite platform, such as links to Event Streams and IBM Cloudant in the new org.

Important: The Event Streams and IBM Cloudant extensions feature has been updated to use [Data Store Connectors (DSC)](https://www.ibm.com/support/knowledgecenter/SSQP8H/iot/platform/reference/dsc/index.html). For more information about migrating your service bindings to DSC, see [Migrating your service bindings](https://www.ibm.com/support/knowledgecenter/SSQP8H/iot/platform/reference/dsc/migration.html) in the Watson IoT Platform documentation.





 Migrating applications 

If you have developed applications that call APIs that are offered with the Watson IoT Platform Lite service to for example send or receive data, or to administer the service, you must update these to use your new Watson IoT Platform Production or Non-Production instance. This also applies to any Node-RED flows that you might be using. The migration involves:



* Updating the applications to use a new six character organization id.
* Updating the applications to use the API key and token credentials that you create for your new service instance.



Important: If you have been using a Cloud Foundry binding to pass the organization id and credentials to the application, you must use a different mechanism as the new Watson IoT Platform instance is not provisioned to run in your Cloud Foundry space.



 Generating API connection credentials 

The migration process to follow depends on the nature of your application. Generally for all cases the first step is to acquire an API Key and Authentication Token for your application to use.



1. Log in to the top-level dashboard of your new Watson IoT Platform service.
2. Select the Usage tab.
3. Click View Details link to bring up the Watson IoT Platform service information.
Please form a line: Kafka](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-aboutabout_kafka)
* [7. Invoking the code: Invoker](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-aboutabout_invoker)
* [8. Storing the results: CouchDB again](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-aboutabout_storing)





[Function as a Service architecture](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-faasfaas)



* [Comparison of OpenWhisk architectures](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-faasfaas_architecture)
* [Cost considerations for Cloud Functions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-faasfaas_cost)



* [Limitless capacity](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-faasfaas_capacity)
* [Run actions in any region](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-faasfaas_region)
* [Redundancy by design](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-faasfaas_redundancy)









 Tutorials 

[Calling an action from another action](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-tutorial_actiontutorial_action)



* [Create the cos-access action](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-tutorial_actiontutorial_action_cos-action)
* For more information on how to connect specific device types to Watson IoT Platform, see [developerWorks 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/).
* Check out the [client libraries ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.ibm.com/support/knowledgecenter/SSQP8H/iot/platform/iot_platform_client_lib.html) for tools to build code for integrating and connecting your devices and apps.
* Explore the [Watson IoT Platform API Documentation](https://cloud.ibm.com/docs/services/IoT?topic=IoT-api_overviewapi_overview).
* [Connect an IBM® Cloudant® for IBM Cloud® service ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.ibm.com/support/knowledgecenter/SSQP8H/iot/platform/cloudant_connector.html) to your Watson IoT Platform to store historical device data.
* To take advantage of the full [Watson IoT Platform feature set ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.ibm.com/support/knowledgecenter/SSQP8H/iot/overview/overview.html), you can purchase one of the Connection and Analytics Service plans and then migrate your existing environment.



To migrate plans, contact your IBM® representative or raise a support ticket.
[@sendgrid/mail](https://www.npmjs.com/package/@sendgrid/mail) Provides email support via the SendGrid API. 
 [@wiotp/sdk](https://www.npmjs.com/package/@wiotp/sdk) IBM Watson IoT Platform JavaScript SDK. 
 [amqplib](https://www.npmjs.com/package/amqplib) A library for making AMQP 0-9-1 clients for Node.js. 
 [apn](https://www.npmjs.com/package/apn) A Node.js module for interfacing with the Apple Push Notification service. 
 [async](https://www.npmjs.com/package/async) Provides functions for working with asynchronous functions. 
 [axios](https://www.npmjs.com/package/axios) Promise-based HTTP client for the browser and Node.js. 
 [bent](https://www.npmjs.com/package/bent) Functional HTTP client for Node.js with async/await. 
 [bodyparser](https://www.npmjs.com/package/body-parser) Parse incoming request bodies in a middleware before your handlers, available under the req.body property. 
 [btoa](https://www.npmjs.com/package/btoa) A port of the browser's btoa function. 
 [bufferutil](https://www.npmjs.com/package/bufferutil) bufferutil is what makes ws fast. 
 [canvas](https://www.npmjs.com/package/canvas) A Cairo-backed Canvas implementation for Node.js. 
 [cassandra-driver](https://www.npmjs.com/package/cassandra-driver) DataStax Node.js Driver for Apache Cassandra.
Testing the trigger and action](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_obstoragepkg_obstorage_ev_test)
* [Next steps for Object Storage and Cloud Functions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_obstoragepkg_obstorage_next)
* [Reference for Object Storage and Cloud Functions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_obstoragepkg_obstorage_ev_ch_ref)



* [Configuring the IBM Cloud Object Storage package](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_obstoragepkg_obstorage_configure)



* [1. Installing the IBM Cloud Object Storage package](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_obstoragepkg_obstorage_install)
* [2. Setting an IAM access policy for your Cloud Functions namespace](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_obstoragepkg_obstorage_rw_auth)
* [Setting default parameters for a package or action](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_obstoragepkg_obstorage_param_bind)



* [Writing an object to a bucket](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_obstoragepkg_obstorage_write)
And now what I'll do is ibmcloud ce project create —name amazing product production app. So this create our nice, little… Target first. I’ll get my default resource group and then I'll go ahead and create the project. There we go. Should only take a moment - perfect. Now you can change your name to whatever you like. This is just a catch-all for your project, which is useful. Then I will take the next command, which is ibmcloud ce app create —name pythonbackend — build-source . —strategy build packs

Now because I already have a requirements.txt, this will be, this application is smart enough to figure out, “hey it's a python application! So let's go ahead and build it!", which is nice. So as you can see, it's taking step one here. It's running the build, which is good. It creates a nice, private image for us too, which is useful. It takes a couple moments. There we go and now we see that if we wanted to do this with no wait, which is the -nw, we can actually put this into the background and wait for it to come up and then we can check it via this build run get the actual name. Being that we're going to be looking at this live, we'll go ahead and do this here.

Perfect! So now I go ahead and open up the this URL here and it came over here and as you can see

“hello moving from Heroku to Code Engine”

And that's it. I took the exact same code I did from Heroku. I created a new project and then I created an application and I just pushed it and it just worked so imagine what you can do with that for yourself. This shows the power that is Code Engine and on a free tier it is truly free - just like Heroku was or will be or was will won't be in the future. Code Engine is free forever, which is great and hopefully, it'll make your life a little easier.
Combining library sets 

You can install a Python packages via pip or conda, as well as download a file as part of the library set by combining these options when you create the library set and prepare the JSON file tp pass in the REST API call.

You can use the combination option as shown in the following example:

{
"application_details": {
"application": "/opt/ibm/customization-scripts/customize_instance_app.py",
"arguments": ["{"library_set":{"action":"add","name":"multi_library","libraries":{"pip":{"python":{"packages":"numpy"]}}},"script":{"source":"py_files","params":"script_params"]}}}"],
"py-files": "cos://<bucket>.dev-cos/jar/customization_script.py",
"conf": {
"spark.hadoop.fs.cos.dev-cos.endpoint":"https://s3.direct.us-south.cloud-object-storage.appdomain.cloud",
"spark.hadoop.fs.cos.dev-cos.access.key":"<cos_access_key>",
"spark.hadoop.fs.cos.dev-cos.secret.key":"<cos_secret_key>"
}
}
}

To increase readability, the unescaped JSON for the arguments would look as follows:

{
"library_set": {
"action": "add",
"name": "multi_library",
"libraries": {
"pip": {
"python": {
"packages": [
"numpy"
]
}
}
},
"script": {
"source": "py_files",
"params": [
"script_params"
]
}
}
}
{: codeblock}
Show more
For more information, see [Track where your code is deployed with toolchains](https://www.ibm.com/cloud/blog/announcements/track-code-deployed-toolchains/).
10. Click Create Integration.
11. From your toolchain's Overview page, on the Repositories card, click the Git repo that you want to work with. Your project overview page opens.



If you don't have Master or Owner privileges for the repo that you are linking to, your integration is limited because you can't use a webhook. Webhooks are required to automatically run a pipeline when a commit is pushed to the repo. Without a webhook, you must start your pipelines manually.



 Configuring Git Repos and Issue Tracking by using the API 

The Git Repos and Issue Tracking tool integration supports the following configuration parameters that you can use with the [Toolchain HTTP API and SDKs](https://cloud.ibm.com/apidocs/toolchain) when you [create](https://cloud.ibm.com/apidocs/toolchaincreate-tool), [read](https://cloud.ibm.com/apidocs/toolchainget-tool-by-id), and [update](https://cloud.ibm.com/apidocs/toolchainupdate-tool) tool integrations.

You must specify the tool_type_id property in the request body with the hostedgit value.



Table 1. Git Repos and Issue Tracking tool integration parameters

 Parameter Usage Type Terraform argument Description 

 api_root_url optional, updatable String api_root_url The URL of the Git Repos and Issue Tracking API. 
 api_token optional, updatable Password api_token The Personal Access Token (PAT). This parameter is required only if the auth_type is set to pat, otherwise it is ignored. 
 auth_type optional, updatable, Default: oauth String auth_type Set the authentication method to use to access the Git provider.
Install mobile SDK from source code 



1. Download the [source code](https://github.com/apache/openwhisk-client-swift).
2. Open the project by using the OpenWhisk.xcodeproj with Xcode. The project contains two schemes: "OpenWhisk" (targeted for iOS) and "OpenWhiskWatch" (targeted for watchOS 2).
3. Build the project for the targets that you need and add the resulting frameworks to your app (usually in /Library/Developer/Xcode/DerivedData/your-app-name).









 Install the starter app example for mobile SDK 

You can use the Cloud Functions CLI to download example code that embeds the Cloud Functions SDK framework.

To install the starter app example, enter the following command:

ibmcloud fn sdk install iOS

This command downloads a compressed file that contains the starter app. The project directory contains a Podfile.

To install the SDK, enter the following command:

pod install





 Getting started with mobile SDK 

To get up and running quickly, create a WhiskCredentials object with your Cloud Functions API credentials and create a Cloud Functions instance from the object.

For example, use the following example code to create a credentials object:

let credentialsConfiguration = WhiskCredentials(accessKey: "myKey", accessToken: "myToken")
let whisk = Whisk(credentials: credentialsConfiguration!)

In previous example, you pass in the myKey and myToken that you get from Cloud Functions. You can retrieve the key and token with the following CLI command:

ibmcloud fn property get --auth

Example output

whisk auth kkkkkkkk-kkkk-kkkk-kkkk-kkkkkkkkkkkk:tttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttt

The string before the colon is your key, and the string after the colon is your token.
* Body: Search result description. Use an abstract, summary, or highlight field from the collection as the search result body.

You must select something for the body or no search result response is displayed in the Facebook and Slack integrations.
* URL: This field can be populated with any footer content that you want to include at the end of the search result.

For example, you might want to include a hypertext link to the original data object in its native data source. Most online data sources provide self-referencing public URLs for objects in the store to support direct access. If you add a URL, it must be valid and reachable. If it is not, the Slack integration will not include the URL in its response and the Facebook integration will not return any response.

The Facebook and Slack integrations can successfully display the search result response when the URL field is empty.



You must use a field for at least one of the search results.

If no options are available from the drop-down fields, give Discovery more time to finish creating the collection. After waiting, if the collection is not created, then your collection might not contain any documents or might have ingestion errors that you need to address first.

![Shows that the Title, Shortdesc, and url fields are selected and the preview search card is populated with information from those fields](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/search-skill-configure-fields.png)

As you add field mappings, a preview of the search result is displayed with information from the corresponding fields of your data collection. This preview shows you what gets included in the search result response that is returned to users.

To get help with configuring the search, see [Troubleshooting](https://cloud.ibm.com/docs/assistant?topic=assistant-skill-search-addskill-search-add-troubleshoot).
3.
[Node SDK](https://github.com/IBM/appconfiguration-node-sdk) <br>[Documentation](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-integrate-sdks) <br>[Python SDK](https://github.com/IBM/appconfiguration-python-sdk) <br>[Documentation](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-python) <br>[Go SDK](https://github.com/IBM/appconfiguration-go-sdk) <br>[Documentation](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-golang) <br>[Java SDK](https://github.com/IBM/appconfiguration-java-sdk) <br>[Documentation](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-java) 
 Client side These SDKs are designed for web and mobile applications. [Android SDK](https://github.com/IBM/appconfiguration-android-client-sdk) <br>[Documentation](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-integrate-sdks-android) <br>[JavaScript SDK](https://github.com/IBM/appconfiguration-js-client-sdk) <br>[Documentation](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-javascript) <br>[React SDK](https://github.com/IBM/appconfiguration-react-client-sdk) <br>[Documentation](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-react)
* Body: Search result description. Use an abstract, summary, or highlight field from the collection as the search result body.

You must select something for the body or no search result response is displayed in the Facebook and Slack integrations.
* URL: This field can be populated with any footer content that you want to include at the end of the search result.

For example, you might want to include a hypertext link to the original data object in its native data source. Most online data sources provide self-referencing public URLs for objects in the store to support direct access. If you add a URL, it must be valid and reachable. If it is not, the Slack integration will not include the URL in its response and the Facebook integration will not return any response.

The Facebook and Slack integrations can successfully display the search result response when the URL field is empty.



You must use a field for at least one of the search results.

If no options are available from the drop-down fields, give Discovery more time to finish creating the collection. After waiting, if the collection is not created, then your collection might not contain any documents or might have ingestion errors that you need to address first.

![Shows that the Title, Shortdesc, and url fields are selected and the preview search card is populated with information from those fields](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/search-skill-configure-fields.png)

As you add field mappings, a preview of the search result is displayed with information from the corresponding fields of your data collection. This preview shows you what gets included in the search result response that is returned to users.

To get help with configuring the search, see [Troubleshooting](https://cloud.ibm.com/docs/services/assistant?topic=assistant-skill-search-addskill-search-add-troubleshoot).
3.
* [UploadPartRequest](https://ibm.github.io/ibm-cos-sdk-java/com/ibm/cloud/objectstorage/services/s3/model/UploadPartRequest.html)
* [UploadPartResult](https://ibm.github.io/ibm-cos-sdk-java/com/ibm/cloud/objectstorage/services/s3/model/UploadPartResult.html)



* Methods



* [abortMultipartUpload](https://ibm.github.io/ibm-cos-sdk-java/com/ibm/cloud/objectstorage/services/s3/AmazonS3.htmlabortMultipartUpload-com.ibm.cloud.objectstorage.services.s3.model.AbortMultipartUploadRequest-)
* [completeMultipartUpload](https://ibm.github.io/ibm-cos-sdk-java/com/ibm/cloud/objectstorage/services/s3/AmazonS3.htmlcompleteMultipartUpload-com.ibm.cloud.objectstorage.services.s3.model.CompleteMultipartUploadRequest-)
* [initiateMultipartUpload](https://ibm.github.io/ibm-cos-sdk-java/com/ibm/cloud/objectstorage/services/s3/AmazonS3.htmlinitiateMultipartUpload-com.ibm.cloud.objectstorage.services.s3.model.InitiateMultipartUploadRequest-)
* [uploadPart](https://ibm.github.io/ibm-cos-sdk-java/com/ibm/cloud/objectstorage/services/s3/AmazonS3.htmluploadPart-com.ibm.cloud.objectstorage.services.s3.model.UploadPartRequest-)











 Upload larger objects using a Transfer Manager
* Text to Speech Example
* Natural Language Understanding Example
* Personality Insights Example
* Language Translator Example



Each of these example code snippets is included in the Git repository under the #Usage section of the documentation:



[#Usage section with sample code for the ABAP SDK for IBM Watson, using SAP NetWeaver](https://github.com/watson-developer-cloud/abap-sdk-nwasusage)

[#Usage section with sample code for the ABAP SDK for IBM Watson, using SAP Cloud Platform ABAP Environment](https://github.com/watson-developer-cloud/abap-sdk-scpusage)







 API Reference 

The API Reference is built into the open source Git repository, and is therefore hosted by GitHub Pages:



* [ABAP Client Library for Watson API Reference](https://watson-developer-cloud.github.io/abap-sdk-nwas/).









 Release and Support 

As the ABAP SDK is a community release, it is not updated with the same schedule as IBM-supported SDKs. It is the choice and responsibility of application developers how this Community SDK is used.

The ABAP SDK is a Community SDK for IBM Watson, created by the IBM Watson development community and SAP's ABAP development community - written by ABAPers from IBM Cloud, IBM Services, and IBM Systems.

Therefore, as a community release it is not updated with the same schedule as IBM-supported SDKs, and does not include support by IBM. For more information about IBM-supported SDKs and the update policy, see [Watson SDKs Reference information](https://cloud.ibm.com/docs/watson?topic=watson-using-sdks).

If you have questions about the IBM Watson services or are having difficulties with using the APIs, ask a question on [Stack Overflow under tag ibm-watson-cognitive](http://stackoverflow.com/questions/ask?tags=ibm-watson-cognitive).
Functions to read and write data 

pyst supports most of the common geospatial formats, including geoJSON and WKT.



 GeoJSON format 

To work with files in geoJSON format in a Python notebook, first create a geoJSON reader and writer:

geojson_reader = stc.geojson_reader()
geojson_writer = stc.geojson_writer()

The following code snippets show reading live location data in geoJSON format available in Mapbox:



* Read the contents of a GeoJSON file copied to your local machine from Mapbox and display the first three lines of the file:

! wget -q https://www.mapbox.com/help/data/stations.geojson
df = geojson_reader.read('stations.geojson')
df.head(3)
* Read content in GeoJSON format from a Python dictionary:

data = json.load(open('stations.geojson'))
df = geojson_reader.read(data)
df.head(3)
* Read data directly from Mapbox by using a URL and display the first three lines of the file:

df = geojson_reader.read(‘https://www.mapbox.com/help/data/stations.geojson’) df.head(3)
* Read binary data (useful when reading streaming bytes from IBM Cloud Object Storage for example):

 Assume station.geojson is in IBM Cloud Object Storage in the bucket "test"
client = ibm_boto3.client('s3')
streaming_body_2 = client.get_object(Bucket='test', Key='station.geojson')['Body']
df = shapefile_reader.read(streaming_body_2.read())
df.head(3)
* Write the contents in a pandas DataFrame to a Python dictionary:

geojson_writer.write(df)
* Write the contents of a pandas DataFrame to a GeoJSON file: