vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Guided tours 

You can explore the Discovery interface by taking an interactive tour. Click Guided tours from the header of the My Projects page to select a tour.

The following tours are available:



*  Learn the essentials of Watson Discovery
*  Extract meaning from text
*  Create and apply dictionaries
*  Create a Content Mining project
*  Learn the keys to a successful mining setup
Migrating enrichments from Watson Explorer 

If you have resources from IBM Watson Explorer, some of them can be migrated to IBM Watson® Discovery.



 Types of resources that can be migrated 

The following types of resources can be migrated from Watson Explorer to Discovery:



* From Watson Explorer Analytical Components: [User dictionaries](https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/com.ibm.discovery.es.ad.doc/iiysatauserdict.html)
* From Watson Explorer oneWEX: [Dictionaries](https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/com.ibm.watson.wex.ee.doc/c_ce_adm_dict_ann.html), [character patterns](https://www.ibm.com/support/knowledgecenter/en/SS8NLW_12.0.0/com.ibm.watson.wex.ee.doc/c_ce_adm_char_ann.html), and [facets](https://www.ibm.com/docs/en/watson-explorer/12.0.x?topic=las-creating-custom-pear-files-use-lexical-analysis-streams).



To analyze data with these migrated enrichments, you can use a Content Mining project. The tools in the associated Content Mining application are similar to tools that are available in Watson Explorer.



* For more information about how to create a Content Mining project, see [Creating projects](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-projects).
* For more information about how to apply enrichments to a collection in the Content Mining application, see [Applying the annotator](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-cm-custom-annotatorcm-custom-annotator-deploy).







 Importing dictionaries from Watson Explorer Analytical Components
[2018-05-31 01:49:26 HST] 34B mynewfile12.txt
[2018-08-10 09:49:08 HST] 20MiB newbigfile.pdf
[2018-11-29 09:53:15 HST] 31B testsave.txt





 find - Search for Objects by Name 

A full list of search options is available in the [complete guide](https://docs.min.io/docs/minio-client-complete-guidefind)

mc find cos/testbucket1 --name my

[2018-11-12 08:09:53 HST] 34B mynewfile1.txt
[2018-05-31 01:49:26 HST] 34B mynewfile12.txt





 head - Display few lines of object 

mc head cos/testbucket1/mynewfile1.txt





 cp - Copy objects 

This command copies an object between two locations. These locations can be different hosts (such as different [endpoints](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpointsendpoints) or storage services) or local file system locations (such as /foo/filename.pdf).

mc cp cos/testbucket1/mynewfile1.txt cos/my_test_bucket/cp_from_minio.txt

...1/mynewfile1.txt: 34 B / 34 B ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ 100.00% 27 B/s 1s





 rm - Remove objects 

More removal options are available on the [complete guide](https://docs.min.io/docs/minio-client-complete-guiderm)

mc rm cos/my_test_bucket/cp_from_minio.txt





 pipe - Copies STDIN to an object 

echo -n 'this is a test' | mc pipe cos/my_test_bucket/stdin_pipe_test.txt
Moving the prefix into the subnet of 18 expands the address of 10.10.128.0/18.







 Exporting routes 

For this example, direct link routes learned from any virtual connection would pass through the export_route_filters to determine whether the direct link advertises them to the customer's on-premises network.

Let's first understand the route filters.

Route filter 1
Action: permit
Address 10.10.0.0
Mask length: 18
Minimum matching length (ge): 18
Maximum matching length (le): 18

Consider a direct link with virtual connections with the following routes:



* Route 1 - 10.10.0.0/18
* Route 2 - 10.10.0.0/19



Only Route 1 - 10.10.0.0/18 would be advertised to the customer's on-premises network.



* Route 1 - 10.10.0.0/18 matches on export filter 1.



* Filter 1's action is set to permit, so route 1 will be advertised.



* Route 2 - 10.10.0.0/19 does not match with any export filter.



* The default export filter determines how this route is handled, which is deny.
* In fact, besides route 1, any other route will be not advertised. No other route will match a filter in the export list.











 Advanced matching examples 

Rather than configuring multiple route filters for consecutive subnets, you can configure a filter with a summary route and qualifying maximum and minimum matching lengths that will match with the consecutive subnets.



 No minimum (GE) or maximum (LE) matching length values 

The route filter with prefix 192.168.64.0/18 will only match a single subnet 192.168.64.0/18.





 Equal minimum (GE) and maximum (LE) matching length values 

The route filter with prefix 192.168.0.0/16, GE 18, and LE 18 will match the following subnets:



* 192.168.0.0/18
* 192.168.64.0/18
* 192.168.128.0/18
* 192.168.192.0/18
The route filter with prefix 192.168.64.0/18 will only match a single subnet 192.168.64.0/18.





 Equal minimum (GE) and maximum (LE) matching length values 

The route filter with prefix 192.168.0.0/16, GE 18, and LE 18 will match the following subnets:



* 192.168.0.0/18
* 192.168.64.0/18
* 192.168.128.0/18
* 192.168.192.0/18







 Unequal minimum (GE) and maximum (LE) matching length values 

The route filter with prefix 192.168.0.0/16, GE 18, and LE 19 will match the following subnets:



* 192.168.0.0/18
* 192.168.64.0/18
* 192.168.128.0/18
* 192.168.192.0/18
* 192.168.0.0/19
* 192.168.32.0/19
* 192.168.64.0/19
* 192.168.96.0/19
* 192.168.128.0/19
* 192.168.160.0/19
* 192.168.192.0/19
* 192.168.224.0/19







 Only minimum (GE) matching length specified 

The route filter with prefix 192.168.0.0/30, GE 30 will match the following subnets (maximum matching length is considered 32):



* 192.168.0.0/30
* 192.168.0.0/31
* 192.168.0.2/31
* 192.168.0.0/32
* 192.168.0.1/32
* 192.168.0.2/32
* 192.168.0.3/32







 Only maximum (LE) matching length specified 

The route filter with prefix 192.168.0.0/16 and LE 19 will match the following subnets (minimum matching length is considered 16):



* 192.168.0.0/16
* 192.168.0.0/17
In a redundant GRE or Direct Link situation, this can be fine, but if you have stateful firewalls, this can be an issue in that the return path to a customer site (or virtual router) can shift if the preferred route changes.
* If the prefix lengths of two routes are different (for example, 192.168.0.0/16 and 192.168.0.0/24), the more precise prefix is preferred. In this example, the connection advertising the /24 prefix would be used for all matching IPs.
* If routes have the same prefix length, but different AS Paths, then the shorter AS Path is the preferred route. The prefix length takes precedence over the AS Path.
"key": "{{environment.attributes.current_date_time}}",
"operator": "dateTimeGreaterThanOrEquals",
"value": "2023-01-01T09:00:00+00:00"
},
{
"key": "{{environment.attributes.current_date_time}}",
"operator": "dateTimeLessThanOrEquals",
"value": "2023-01-06T17:59:59+00:00"
}
]
},
"pattern": "time-based-conditions:once",
"subject": {
"attributes": [
{
"key": "iam_id",
"operator": "stringEquals",
"value": "IBMid-00000AV0S0"
}
]
}
}
Show more





 /v1/policies returns a placeholder for /v2/ policies 

When you list policies with /v1/policies the API returns /v1/ and a placeholder policy for each /v2/ policy that's in the account. The placeholders indicate the existence of additional policies in the account while abiding by the /v1/ schema. To see the full content of a /v2/ policy, list policies by using /v2/policies or retrieve the individual policy by using GET: v2/policies/<ID>. For example, see the following placeholder policy:

{
"id": "33b901fa-8ec5-4432-a2e6-24b6a212c20a",
"type": "access",
"description": "This is a unsupported policy version placeholder, to view the full content, please call GET with provided href",
"subjects": [{
"attributes": {
"name": "iam_id",
"value": "unsupported version"
}]
}],
"roles": [{
"text": "{{event.ibmendefaultlong}}",
"type": "TextBlock",
"weight": "Bolder",
"wrap": true
},
{
"actions":
{
"targetElements":
"stacktrace"
],
"title": "Show Data",
"type": "Action.ToggleVisibility"
}
],
"type": "ActionSet"
},
{
"id": "stacktrace",
"isVisible": false,
"items":
{
"fontType": "monospace",
"isSubtle": true,
"size": "Small",
"text": "{{event.data}}",
"type": "TextBlock",
"weight": "Bolder",
"wrap": true
}
],
"type": "Container"
}
],
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
"version": "1.4"
}
}
]
}
Show more

Here -

ibmendefaultshort is the default short payload provided in the incoming payload. ibmendefaultlong is tbe default long payload provided in the incoming payload. data is the data JSON provided in the incoming payload and will be formated as json in the Microsoft Teams notification.





 Microsoft Teams retry policy 

When publishing an Microsoft Teams notification, issues such as network errors and application glitches can cause the requests to fail. A retry is used to provide resiliency to external requests. Attempt to retry the requests in such situations by using the following values:



* Limit = 60 seconds: total time that the service retries.
* Step = 5 seconds: after each failure, the service waits 5 seconds before retrying. This delay prevents bombarding of the external services (webhook).
![assemble-1.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/assemble-1.png) The Operation Switch provides a decision point. Based on the verb and path pair, the appropriate operation must be invoked.
c. Drag the invoke policy from the palette and drop it on the canvas. Drop one in the /get current path and one in the /get today path. d. Select the invoke policy in the /get current path, and update its title to "invoke-current".
e. Update the URL field with: https://myweatherprovider.mybluemix.net/current?zipcode=$(request.parameters.zipcode). f. Select the invoke policy in the /get today path, and update its title to "invoke-today".
g. Update the URL field with: https://myweatherprovider.mybluemix.net/today?zipcode=$(request.parameters.zipcode).



20. Save your API.



--------------------





 Test your API proxy 



1. To test your API proxy endpoints, select Explore.
2. Select the GET /current operation from the palette.
3. Enter a valid US zip code (for example, 90210) in the test box.
4. Click Call operation to see the response.
![screenshot_explore.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/screenshot_explore.png)



--------------------





 Conclusion
For more information, see [MapReduce Views](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-creating-views-mapreduce) for creating views of your data that is ordered by a key of your choice.





* How do I consume the changes feed?

Given a single database orders, I can ask the database for a list of changes, in this case, limiting the result set to five changes with ?limit=5:

GET /orders/_changes?limit=5
{
"results": [
{
"seq": "1-g1AAAAB5eJzLYWBg",
"id": "00002Sc12XI8HD0YIBJ92n9ozC0Z7TaO",
"changes":
{
"rev": "1-3ef45fdbb0a5245634dc31be69db35f7"
}
]
},
....
],
"last_seq": "5-g1AAAAB5eJzLYWBg"
}

The API call returns the following changes:

results
: An array of changes.

last_seq
: A token that can be supplied to the changes endpoint in a subsequent API call to get the next batch of changes.

See how to fetch the next batch of changes in the following example:

GET /orders/_changes?limit=5&since=5-g1AAAAB5eJzLYWBg
{
"results": [ ...],
"last_seq": "10-g1AAAACbeJzLY"
}

The since parameter is used to define where in the changes feed you want to start from:

since=0
: The beginning of the changes feed.

since=now
: The end of the changes feed.

since=<a last seq token>
: From a known place in the changes feed.

At face value, following the changes feed seems as simple as chaining _changes API calls together.
You can list deployed model in the Natural Language Understanding service instance by calling the following API method.

curl --user "apikey:{apikey}" "{url}/v1/models?version=2018-11-16"

Any deployed models will be returned in an array similar to the following one:

{
"models": [
{
"workspace_id": "{workspace_id}",
"version_description": "{version_description}",
"version": "{version}",
"status": "available",
"name": null,
"model_id": "10:7abc4c2f-5846-3334-b8f7-af5a6fad3398",
"language": "en",
"description": null,
"created": "2018-11-28T17:08:00.000000Z"
}
]
}

The {workspace_id}, {version_description}, and {version} will all match the information listed on the Versions page of your Knowledge Studio service instance.

To use the deployed model, you must specify the model ID of your custom model in the entities.model parameter of an analyze call.

You can use the model with the Natural Language Understanding GET /analyze request to extract the following features:



* entities

The following command finds the entities that are present in the sentence that is passed by using the text parameter:

curl --user "apikey":"{apikey}" "{url}/v1/analyze?version=2018-09-21"
--request POST
--header "Content-Type: application/json"
-d '{"text": "Vehicle 1, a 1995 Honda Civic was traveling north on a two lane
undivided roadway, negotiating a curve to the left on an upgrade.",
"features": {
"entities": {
"model": "your-model-id-here"
}
}
}'
"members_memory_allocation_mb": "2048",
"members_disk_allocation_mb": "10240"
}'

For both the CLI and API commands, you must specify both the RAM and disk amounts, keeping in mind the minimum size is 2 GB RAM and 10 GB disk. You can optionally specify whether the read-only replica uses public or private endpoints. You are not able to specify a version for the read-only replica. The version is automatically set to the same major version as the leader deployment.







 The Read-only Replica 

On the Read Replicas tab of a read-only replica, the Replication pane contains its name and region, and the name and region of its leader. It also has buttons to resync the read-only replica and to promote it.

Zoom

![Replication pane of a read-only replica](https://cloud.ibm.com/docs-content/v1/content/3505da55c475bf1edbe3eb3496324ba13941b783/databases-for-postgresql/images/replica-roreplica.png)

Figure 3. Replication pane of a read-only replica



 Checking Replication Status 

You must monitor replication as replication status is not automatically monitored.

You can check the replication status of a read-only replica with psql, but only from its leader. [Connect to the leader deployment with psql](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-connecting-psql) using the [admin credentials](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-user-managementthe-admin-user). Once you are connected run either,



* For PostgreSQL version 10 and above SELECT * from pg_stat_replication;.



Or



* For PostgreSQL version 9.x and below SELECT * FROM get_pg_stat_replication();.
Status: Pending (Processing Resource)
Status: Pending (Processing Resource)
Status: Creating service binding
Status: Creating service binding
Status: Ready
Waiting for application revision to become ready...
Traffic is not yet migrated to the latest revision.
Ingress has not yet been reconciled.
Waiting for load balancer to be ready
OK







 ibmcloud ce application create 

Create an application.

ibmcloud ce application create --name APP_NAME ((--image IMAGE_REF | (--build-source SOURCE [--image IMAGE_REF])) [--argument ARGUMENT] [--build-commit BUILD_COMMIT] [--build-context-dir BUILD_CONTEXT_DIR] [--build-dockerfile BUILD_DOCKERFILE] [--build-git-repo-secret BUILD_GIT_REPO_SECRET] [--build-size BUILD_SIZE] [--build-strategy BUILD_STRATEGY] [--build-timeout BUILD_TIMEOUT] [--cluster-local] [--command COMMAND] [--concurrency CONCURRENCY] [--concurrency-target CONCURRENCY_TARGET] [--cpu CPU] [--env ENV] [--env-from-configmap ENV_FROM_CONFIGMAP] [--env-from-secret ENV_FROM_SECRET] [--ephemeral-storage EPHEMERAL_STORAGE] [--force] [--max-scale MAX_SCALE] [--memory MEMORY] [--min-scale MIN_SCALE] [--mount-configmap MOUNT_CONFIGMAP] [--mount-secret MOUNT_SECRET] [--no-cluster-local] [--no-wait] [--output OUTPUT] [--port PORT] [--quiet] [--registry-secret REGISTRY_SECRET] [--request-timeout REQUEST_TIMEOUT] [--revision-name REVISION_NAME] [--scale-down-delay SCALE_DOWN_DELAY] [--service-account SERVICE_ACCOUNT] [--user USER] [--visibility VISIBILITY] [--wait] [--wait-timeout WAIT_TIMEOUT]



 Command Options
"lifecycle_state": "stable",
"mount_targets": [
{
"href": "https://us-south.iaas.cloud.ibm.com/v1/shares/207721a9-aff9-4b16-9823-fe68096aeac3/mount_targets/ce244454-0919-45e2-b14b-f4285afcd856",
"id": "ce244454-0919-45e2-b14b-f4285afcd856",
"name": "my-share-mount-target",
"resource_type": "share_mount_target",
"vpc": {
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/vpcs/c8b8fa2d-ccf7-4f42-9d38-df6d123c867d",
"id": "c8b8fa2d-ccf7-4f42-9d38-df6d123c867d",
"name": "my-vpc",
"resource_type": "vpc"
}
}
],
"name": "my-share-3",
"profile": {
"family": "defined-performance",
"href": "https://us-south.iaas.cloud.ibm.com/v1/share/profiles/dp2",
"name": "dp2",
"resource_type": "share_profile"
},
"replication_role": "source",
"replication_status": "active",
"replication_status_reasons": [],
"resource_group": {
"crn": "crn:[...]",
* You must obtain any required service licenses for the data source that you want to connect to. For more information about licenses, contact the system administrator of the data source.



For more information about Salesforce, see the [Salesforce developer documentation](https://developer.salesforce.com/docs/).





 Prerequisite step 

To crawl documents in Salesforce, Discovery uses a Web Service Description Language (WSDL) file. The WSDL file defines a Web service to generate an API that manages access.

If you plan to crawl documents from both a Sandbox and Production instance of Salesforce, you must establish a connection to each web service separately. You must download JAR files from each web service and set up separate collections.

For information about downloading the WSDL JAR files, see the following links:



* [Generate or Obtain the Web Service WSDL](https://developer.salesforce.com/docs/atlas.en-us.210.0.api.meta/api/sforce_api_quickstart_steps_generate_wsdl.htm)
* [Import the WSDL File Into Your Development Platform](https://developer.salesforce.com/docs/atlas.en-us.210.0.api.meta/api/sforce_api_quickstart_steps_import_wsdl.htm)
* [Download Apache Commons BeanUtils](https://commons.apache.org/proper/commons-beanutils/download_beanutils.cgi)





1. Download the following JAR files:



* force-partner.jar (from partner WSDL)
* force-metadata.jar (from metadata WSDL)
* force-wsc.jar (from Force.com Web Service Connector (WSC))
* commons-beanutils.jar (from Apache Commons BeanUtils)



2. Compress the JAR files into a compressed file. You will upload the compressed file to Discovery in the next procedure.





 Connecting to a Salesforce data source 

From your Discovery project, complete the following steps:



1. From the navigation pane, choose Manage collections.
* [SAP Help - SAP HANA System Replication - SAP HANA Administration Guide for SAP HANA Platform](https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/latest/en-US/676844172c2442f0bf6c8b080db05ae7.html)
* [SAP Help - SAP HANA System Replicatio Guide](https://help.sap.com/viewer/4e9b18c116aa42fc84c7dbfd02111aba/latest/en-US)
* [Troubleshoot System Replication - SAP HANA Troubleshooting and Performance Analysis Guide](https://help.sap.com/viewer/bed8c14f9f024763b0777aa72b5436f6/latest/en-US/caca75c6f0cf4204af9d38ae0fe2d379.html)
* [SAP Note 1999880 - FAQ: SAP HANA System Replication](https://launchpad.support.sap.com//notes/1999880)
* [SAP Note 2057595 - FAQ: SAP HANA High Availability](https://launchpad.support.sap.com//notes/2057595)



For more information on setting up the HA cluster extensions of the OS, view the Linux vendor documentation below.

SUSE Linux Enterprise Server for SAP:



* [SAP HANA System Replication Scale-Up - Performance Optimized Scenario](https://documentation.suse.com/sbp/all/html/SLES4SAP-hana-sr-guide-PerfOpt-12/index.html)
* [SUSE Linux Enterprise High Availability Extension](https://documentation.suse.com/sle-ha/)



Red Hat Enterprise Linux for SAP:



* [Supported HA Scenarios for SAP HANA, SAP S/4HANA, and SAP NetWeaver](https://access.redhat.com/articles/4079981)
[IBM Developer<br><br>Visit IBM Developer for technical articles, code patterns, tutorials, and more.<br><br>![112-Developer-tools.svg](https://cloud.ibm.com/media/docs/images/homepage/112-Developer-tools.svg)](https://developer.ibm.com/depmodels/cloud/)[Architecture Center<br><br>Discover the architecture references available for this product.<br><br>![190-Application-Platform.svg](https://cloud.ibm.com/media/docs/images/homepage/190-Application-Platform.svg)](https://www.ibm.com/cloud/architecture)[IBM Training<br><br>Build your skills with IBM Cloud training.<br><br>![83-Elements-of-the-cloud.svg](https://cloud.ibm.com/media/docs/images/homepage/83-Elements-of-the-cloud.svg)](https://www.ibm.com/training/cloud)[Community<br><br>Join the IBM Cloud community and collaborate with others.<br><br>![35-Connectivity.svg](https://cloud.ibm.com/media/docs/images/homepage/35-Connectivity.svg)](https://community.ibm.com/community/user/publiccloud/home)

 Latest updates 

[View more](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-cd-relnotes)22 July 2022 | Beta Terraform resources and data sources, Go SDKs, and HTTP APIs

The Beta Terraform resources and data sources, Go SDKs, and HTTP APIs are now available for working with Toolchains and Tekton Pipelines.

20 July 2022 | Git Repos and Issue Tracking

Upgraded to GitLab 15.0.4.

12 July 2022 | Git Repos and Issue Tracking

Upgraded to GitLab 14.10.5.
Security and Compliance Center 



 Resources Data sources 

 <br><br> * [ibm_scc_account_settings](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/scc_account_settings)<br> * [ibm_scc_posture_collector](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/scc_posture_collector)<br> * [ibm_scc_posture_credential](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/scc_posture_credential)<br> * [ibm_scc_posture_profile_import](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/scc_posture_profile_import)<br> * [ibm_scc_posture_scan_initiate_validation](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/scc_posture_scan_initiate_validation)<br> * [ibm_scc_posture_scope](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/scc_posture_scope)<br> * [ibm_scc_rule](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/scc_rule)<br> * [ibm_scc_rule_attachment"](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/scc_rule_attachment)<br> * [ibm_scc_si