vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Segment ID pool for subsequent secondary instance or instances Previous end range in the multisite configuration + 1 to the previous end range in the multisite configuration + 2000 
 Port group SDDC-DPortGroup-vSAN (if applicable) Active uplinks set to uplink2 and Standby uplinks set to uplink1 
 Port group SDDC-DPortGroup-Mgmt Port binding set to Static binding and Load balancing set to Route based on physical NIC load 
 Port group SDDC-DPortGroup-External Port binding set to Static binding 



Security policies for promiscuous mode, MAC address changes, and forged transmits are accepted on distributed port groups.





 Network MTU configuration settings 

The vSphere cluster uses two vSphere Distributed Switches (vDS), one for public network connectivity and the other one for private network connectivity.

The private network connections are configured to use Jumbo Frames MTU (Maximum Transmission Unit) with the size of 9000, which improves performance for large data transfers such as storage and VMware vMotion. This value is the maximum MTU allowed within VMware and by IBM Cloud.

The public network connections use a standard Ethernet MTU of 1500, which must be maintained. Any changes might cause packet fragmentation over the internet.

Review the following table for an overview of the Network MTU configuration settings that are applied to the public and private Distributed Virtual Switch (DVS).



Table 6. MTU configuration settings for vCenter Server instances and clusters

 Configuration setting Value 

 Public switch 1500 (default) 
 Private switch 9000 (Jumbo Frames) 





 Updating the public switch MTU setting 

To update the MTU setting for the public switch, complete the following steps in the VMware vSphere Web Client:



1. Right-click the vDS and click Edit Settings.
2. On the Properties tab, select the Advanced option.
3. Ensure that the Maximum MTU value is set to 1500.

When the MTU size in a vDS is changed, the attached uplinks (physical NICs) are brought down and up again. As a result, a brief outage occurs for the VMs that are using the uplink.
: The SDK for Node.js buildpack v3.25 provides IBM SDK for Node.js versions 4.8.5, 4.8.7 and Node.js community versions 6.14.4, 6.15.0, 8.11.4, 8.14.0, 10.10.0 and 10.14.0. The default is latest 6.x, so it is currently 6.15.0. The buildpack also fixes a minor bug in the Dynatrace hook.





 14 December 2018 

Updated Liberty buildpack v3.27-20181130-1702
: The buildpack now includes Java Platform, Enterprise Edition 8.0. Java EE 8 no longer needs to be installed when an app is pushed.



* The default Liberty runtime version was updated to the [18.0.0.4](https://openliberty.io/blog/2018/12/14/microprofile21-18004.html) release.
* The monthly Liberty runtime version was updated to the 2018.11.0.0 release.
* The IBM JRE version was updated to 8 SR5 FP26.







 12 December 2018 

Updated ASP.NET Core buildpack v2.1-20181205-1536
: This release includes version 2.2.0 of the dotnet-core Cloud Foundry buildpack.



* Add support for .NET ASP.NET Core 2.1.2
* Add support for .NET ASP.NET Core 2.1.4
* Add support for .NET ASP.NET Core 2.1.5
* Add support for .NET Runtime 1.0.11
* Add support for .NET Runtime 1.0.12
* Add support for .NET Runtime 1.1.9
* Add support for .NET Runtime 1.1.10
* Add support for .NET Runtime 2.0.7
* Add support for .NET Runtime 2.0.9
* Add support for .NET Runtime 2.1.2
* Add support for .NET Runtime 2.1.5
* Add support for .NET SDK 1.0.4
persistentVolumeClaim:
claimName: my-cos-pvc







 Review 

In this tutorial, you installed the Object Storage plug-in in your cluster and enabled quotas for any PVCs created with the plug-in. Then, you created a PVC which dynamically created a bucket with a quota limit in your Object Storage instance. After that, you deployed a simple app that prints the contents of a file in your bucket.





 Next steps 



* Set up the [Object Storage CLI](https://cloud.ibm.com/docs/cloud-object-storage-cli-plugin?topic=cloud-object-storage-cli-plugin-ic-cos-cli) to point to your bucket.
* Use the Object Storage SDKs to [add storage to your apps](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-sdk-gs).
Launch the [IBM Cloud Monitoring web UI](https://cloud.ibm.com/docs/monitoring?topic=monitoring-launch) from the Observability page.
2. Click DASHBOARDS.
3. In the Default Dashboards section, expand IBM.
4. Choose the App Configuration dashboard from the list.

Access your deployment's monitoring dashboard from IBM Cloud Monitoring, it's in the sidebar, under IBM.

Next, change the scope or make a copy of the default dashboard to monitor an App Configuration service instance.

Zoom

![IBM Monitoring UI](https://cloud.ibm.com/docs-content/v1/content/f3dada89f147af3b88388a2218ddbf64b3c41e5f/app-configuration/images/ac-monitoring-dash.png)

Figure 2. IBM Cloud Monitoring dashboard







 Metrics available by Service Plan 

App Configuration supports three metrics that you can use to configure in your dashboard for monitoring. The table provides the details about the metrics.



Table 2. List of App Configuration server, client, and admin SDKs

 Metric Name Enterprise Standard Lite 

 [IBM Appconfig Instance API request](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-monitoringibm_apprapp_instance_api) Yes Yes Yes 
 [IBM Appconfig Evaluation Count](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-monitoringibm_apprapp_instance_eval) Yes Yes Yes 
 [IBM Appconfig Instance Unauth Request](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-monitoringibm_apprapp_instance_unauth) Yes Yes Yes 





 IBM Appconfig Instance API request 

API request count per instance: Count of config API requests made from the SDK.



Table 3. API request metadata

 Metadata Description 

 Metric Name ibm_apprapp_instance_api_request
You can use the [Node](mailto:https://github.com/IBM/event-notifications-node-admin-sdk) or [Go](https://github.com/IBM/event-notifications-go-admin-sdksend-notifications) admin SDK instead of calling the API directly.

Zoom

![Send notifications](https://cloud.ibm.com/docs-content/v1/content/4c9a07fe500838e5e55e71e73131ef20b44a6c66/event-notifications/images/en-send-notifications.png)

Figure 6. Send notifications

Zoom

![Receive notifications](https://cloud.ibm.com/docs-content/v1/content/4c9a07fe500838e5e55e71e73131ef20b44a6c66/event-notifications/images/en-receive-push.png)

Figure 7. Receive notifications





 Migrating FCM legacy HTTP API to HTTP v1 API 

Apps using the FCM legacy HTTP API should consider migrating to the HTTP v1 API using the instructions in this section. The HTTP v1 API has advantages such as secure access tokens, efficient customizations, and future proof as well as more extendable client platform versions.

In Event Notifications, you can create an android destination by following FCM norms. For legacy HTTP API we have been providing support via two required parameters server_key and sender_id. For the v1 HTTP API, FCM introduced three new parameters: project_id, client_email, and private_key. The important point to observe here is both legacy and v1 HTTP APIs are mutually exclusive and we have taken care of that in Event Notifications.

Here's how you can migrate from an old configuration to a new one.



1. Under your existing FCM Android destination configuration you will find server_key and sender_id provided.
* Click [here](https://docs.microsoft.com/en-us/windows-server/failover-clustering/manage-cluster-quorum) for more information on configuring and managing quorum servers for Windows Server 2012 and Windows Server 2012 R2.



IBM Cloud Block Storage has built-in HA capabilities, so a single shared iSCSI LUN does not introduce a Single Point Of Failure (SPOF) because your network layout is redundant. However, the specifics of your cluster product might require multiple quorum devices.





 HA and network considerations 

An IBM Cloud Classic Infrastructure environment-based installation comes with one of the following network configurations:



* Private network
* Public network
* Public and private networks
* Two private networks (on special request, dependent on the server type and physical hardware components configuration)



Like on-premises installations, extra network adapters can be ordered depending on the physical restrictions of the hardware. The restriction is the same for on-premises installations, how many NIC cards can fit into the Bare Metal.

Ordering redundant network adapters during hardware deployments helps prevent single point of failures (SPOF) across your network topology.

Redundant adapters for Bare Metals are set up in a failover configuration with Link Aggregation Control Protocol (LACP). For Linux, the setup uses bonding interfaces, and teaming adapters are used for Microsoft Windows. Doing so will create a logical interface for redundancy and increased bandwidth.

When using IBM Cloud for VMware Solutions, redundant adapters for VMware are set up by the VMware vSphere Distributed Switch (VDS) using either [VDS on NSX-V](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-nsx-v-designnsx-v-design-distr-switch) or [VDS on NSX-T](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-nsx-t-designnsx-t-design-distr-switch), in accordance with current VMware best practices for SDDC.
* Context-based restrictions protect only the actions associated with the [VPC Infrastructure Services APIs](https://cloud.ibm.com/apidocs/vpc) or the is plugin, through the IBM CLI. The SDK and Terraform options are also supported. Actions associated with the following platform APIs are not protected by context-based restrictions:



* [Resource Instance List APIs](https://cloud.ibm.com/apidocs/resource-controller/resource-controllerlist-resource-instances)
* [Resource Instance Delete resource API](https://cloud.ibm.com/apidocs/resource-controller/resource-controllerdelete-resource-instance)
* [Global Search APIs](https://cloud.ibm.com/apidocs/search)
* Global Tagging [Attach](https://cloud.ibm.com/apidocs/taggingattach-tag) and [Detach](https://cloud.ibm.com/apidocs/taggingdetach-tag) APIs



* When you create a rule, it might take up to 10 minutes to become enforced.
* Due to a limitation that is currently being addressed, context-based restrictions must not be in place for [Secrets Manager APIs](https://cloud.ibm.com/apidocs/secrets-manager) if you are using the [Load balancer for VPC service](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-vs-elb), as it results in failing to attach the certificates to the listener associated with the load balancer
Set up and configure the Virtual Server Instance for the toolchain to deploy the app to the Virtual Server Instance. You can use an existing Virtual Server Instance or set up a new one that conforms to the following requirements:



1. [Set up the Virtual Server Instance on IBM Cloud](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers).
2. [Reserve a floating IP address](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-the-ibm-cloud-consolereserving-a-floating-ip-address) to make the Virtual Server Instance accessible over the public internet. Alternatively, you can use the available DNS entry. This tutorial uses a floating IP address.
3. Create the user (preferably non-privileged) and [SSH keys](https://cloud.ibm.com/docs/vpc-on-classic-vsi?topic=vpc-on-classic-vsi-ssh-keysssh-keys) for the Virtual Server Instance.
4. Configure [Security Groups](https://cloud.ibm.com/docs/security-groups?topic=security-groups-getting-started) for the Virtual Server Instance. Enable the toolchain to perform health checks on the deployed app by adding an inbound rule for TCP to allow port 8080 so that it can access the app endpoint. For more information about adding an inbound rule, see [Managing security groups](https://cloud.ibm.com/docs/security-groups?topic=security-groups-managing-sg).
5. Ensure that Java™ SDK is installed on your VM or use the following command to install it: yum install -y tar java.
6. Optional. If you need to store secrets in Key Protect, perform base64 encoding of the value.
git clone https://github.com/watson-developer-cloud/openwhisk-sdk
2. Deploy the package.

ibmcloud fn deploy -m openwhisk-sdk/packages/discovery-v1/manifest.yaml
3. Verify that the package is added to your package list.

ibmcloud fn package list

Example output

packages
/myOrg_mySpace/discovery-v1 private
4. Bind the credentials from the Discovery instance you created to the package.

ibmcloud fn service bind discovery discovery-v1

Example output

Credentials 'Credentials-1' from 'discovery' service instance 'Watson Discovery' bound to 'discovery-v1'.
5. Verify that the package is configured with your Discovery service instance credentials.

ibmcloud fn package get discovery-v1 parameters

Example output

ok: got package discovery-v1, displaying field parameters
[
{
"key": "__bx_creds",
"value": {
"discovery": {
"credentials": "Credentials-1",
"instance": "Watson Discovery",
"password": "AAAA0AAAAAAA",
"url": "https://gateway.watsonplatform.net/discovery/api",
"username": "00a0aa00-0a0a-12aa-1234-a1a2a3a456a7"
}
}
}
]







 Installing from the Cloud Functions console 

You can install your package from the Cloud Functions console.



1. In the Cloud Functions console, go to the [Create page](https://cloud.ibm.com/functions/create).
2. Select the namespace that you want to install the package into.
3. Click Install Packages.
4. Click the Watson package group.
5. Click the Discovery package.
6. Click Install.
7.
[update-training-example](https://cloud.ibm.com/apidocs/discoveryupdate-training-example) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, environment_id, collection_id, query_id, example_id, cross_reference, relevance Change a label or cross reference for an example. 
 [delete-user-data](https://cloud.ibm.com/apidocs/discoverydelete-user-data) Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, customer_id Delete labeled data. 





 Creating a Discovery service instance 

Before you install the package, you must create a Discovery service instance and service credentials.



1. [Create a Discovery service instance](https://cloud.ibm.com/catalog/services/discovery).
2. When the service instance is created, service credentials are automatically created for you.







 Installing the Discovery package 

After you have a Discovery service instance, install the Discovery package into your namespace.



 Installing from the Cloud Functions CLI 

Install the Discovery package from the CLI. Be sure to [install the Cloud Functions plug-in for the IBM Cloud CLI](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-cli_install) first.

To install the Discovery package, run the following commands:



1. Clone the Discovery package repo.

git clone https://github.com/watson-developer-cloud/openwhisk-sdk
2. Deploy the package.

ibmcloud fn deploy -m openwhisk-sdk/packages/discovery-v1/manifest.yaml
3. Verify that the package is added to your package list.

ibmcloud fn package list

Example output

packages
/myOrg_mySpace/discovery-v1 private
Instantiation of Observer's Template](https://access.redhat.com/articles/5100521sdi-observer-instantiate) in the RHA to confirm the deployment instructions and the source URL are valid.
3. Download the installation script

curl -O https://raw.githubusercontent.com/redhat-sap/sap-data-intelligence/master/observer/run-observer-template.sh
4. Edit the downloaded script file in your favorite editor; especially, mind the following parameters:

FLAVOUR=ubi-build
REDHAT_REGISTRY_SECRET_PATH="$HOME/sap/install/rht-registry-secret.yaml"
NAMESPACE=sdi-observer
SDI_NAMESPACE=sdi
SLCB_NAMESPACE=sap-slcbridge
SDI_NODE_SELECTOR="node-role.kubernetes.io/sdi="
5. Save the script.
6. Deploy the SAP Data Intelligence Observer in the sdi namespace - i.e. run the script using bash.

bash ./run-observer-template.sh

In chapter [4.3 Managing SDI Observer](https://access.redhat.com/articles/5100521sdi-observer-manage) of the RHA you will learn how you can review and update SDI Observer's current configuration.
7. Get information about Red Hat's SDI node-configurator



The worker nodes need be configured to grant proper execution of SAP Data Intelligence - see also the documentation at [Red Hat's SDI Node Configurator](https://github.com/redhat-sap/sap-data-intelligence/tree/master/node-configurator) on GitHub.



1. First set security context constraints to the sdi-node-configurator service account:

oc adm policy add-scc-to-user -n sdi-observer privileged -z sdi-node-configurator
2. Copy the template from GitHub:
BMSClient.sharedInstance.initialize(bluemixRegion: BMSClient.Region.usSouth) // Make sure that you point to your region

You must initialize the BMSClient with the bluemixRegion parameter. In the initializer, the bluemixRegion value specifies which IBM Cloud deployment you're using, for example, BMSClient.Region.usSouth, BMSClient.Region.unitedKingdom, or BMSClient.Region.sydney.







 Initializing your Cordova app 



1. Add the Cordova plugin by running the following command from your Cordova app root directory:

cordova plugin add bms-core
2. Initialize the BMSClient class in your Cordova app by adding the initialization code in the main JavaScript file, or in a location that works best for your project.

BMSClient.initialize(BMSClient.REGION_US_SOUTH);

You must initialize the BMSClient with the bluemixRegion parameter. In the initializer, the bluemixRegion value specifies which IBM Cloud deployment you're using, for example, BMSClient.REGION_US_SOUTH, BMSClient.REGION_UK, or BMSClient.REGION_SYDNEY.







 Related Links 



* [BMSCore Android SDK](https://github.com/ibm-bluemix-mobile-services/bms-clientsdk-android-core)
* [BMSCore iOS SDK](https://github.com/ibm-bluemix-mobile-services/bms-clientsdk-swift-core)
* [BMSCore Cordova Plugin](https://github.com/ibm-bluemix-mobile-services/bms-clientsdk-cordova-plugin-core)
(https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/tut-sdu-manage-fields-tab.png)

Figure 22. The Manage fields tab
2. From the list of fields to index, set the switcher to No for all fields except these ones:



* footnote
* html
* subtitle
* table
* text



Zoom

![Shows the fields to index list](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/tut-sdu-fields-to-index.png)

Figure 23. Fields in the index list
3. Click Apply changes and reprocess.

A notification is displayed to indicate that the collection was updated. You remain on the Manage fields page, but the Apply changes and reprocess button is disabled.



You successfully configured the index to control the content that is available to searches! You excluded fields that might contain popular search terms, but do not also include meaningful content.

For more information about managing fields, see [Excluding content from query results](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-hide-data).





 Step 7: Split the document 

Now that Discovery knows more about the structure of the document, we can split the single 99-page document into more documents. Remember, only one passage was returned for each query that you submitted before. If we split the document into multiple segments, Discovery can return the best passages from across all of the document segments.

When you split a document, you turn one document into many documents. Be aware of the document limits for your plan type. Each document segment that is generated by splitting a document counts toward the plan's document limit.
: The following features are generally available from managed IBM Cloud deployments at the time of this release, but not from installed deployments:



* Answer finding
* Manage data page







 4.6.1 release, December 2022 

IBM Watson® Discovery Cartridge for IBM Cloud Pak® for Data was not refreshed as part of 4.6.1. However, the product documentation was updated with fixes and enhancements.





 4.6 release, 30 November 2022 

IBM Watson® Discovery Cartridge for IBM Cloud Pak® for Data 4.6 is available.

For a list of new features and bug fixes, see [What's new and changed in Watson Discovery](https://www.ibm.com/docs/SSQNUZ_4.6.x/fixlist/discovery-fixlist.html)

Features that are not available in this release
: The following features are generally available from managed IBM Cloud deployments at the time of this release, but not from installed deployments:



* Answer finding
* Manage data page







 4.5.3 release, 13 October 2022 

IBM Watson® Discovery Cartridge for IBM Cloud Pak® for Data 4.5.3 is available.

There are no new features in this release. For a list of bug fixes, see [What's new and changed in Watson Discovery](https://www.ibm.com/docs/SSQNUZ_4.5.x/fixlist/discovery-fixlist.html)

Features that are not available in this release
: The following features are generally available from managed IBM Cloud deployments at the time of this release, but not from installed deployments:



* Answer finding
* Manage data page
* Advanced document view for search results
* The similar parameter of the Query method
* The smart_document_understanding field in the Get collection method response







 15 August 2022 

SDKs were updated to reflect the latest API changes.
: The following [Discovery v2 API](https://cloud.ibm.com/apidocs/discovery-data) changes are now reflected in the SDKs:



* Use the new document classifier API to get, add, update, or delete a document classifier.
curl -u "apikey:f5sAznhrKQyvBFFaZbtF60m5tzLbqWhyALQawBg5TjRI" "{url}/v1/{method}"



For testing and development, you can pass in an API key directly. However, for production use, unless you use the Watson SDKs, use an IAM token. When you pass an API key, the service looks up the API key details, so it might affect performance. For more information, see [Invoking IBM Cloud service APIs](https://cloud.ibm.com/docs/account?topic=account-iamapikeysforservices).

The Watson SDKs support both methods. For more information, see the Authentication section of the [API reference](https://cloud.ibm.com/docs?tab=api-docs&category=ai) for your service and SDK.

Some service plans support IBM® Key Protect for IBM Cloud® to control access to data. For more information, see [Protecting sensitive information in your Watson service](https://cloud.ibm.com/docs/watson?topic=watson-keyservice).





 Authenticating to IBM Cloud Pak for Data 

IBM Cloud Pak for Data

You authenticate to the service by passing an access token with each request. You pass a bearer token in an Authorization header to authenticate. Several methods exist to generate the token, including by using an API key or by username. For more information, see [Generating an authorization token or API key](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=resources-generating-authorization-token-api-key).

For more information about authentication methods that are supported by the Watson SDKs for services installed on IBM Cloud Pak for Data, see the Authentication section of the [API reference](https://cloud.ibm.com/docs?tab=api-docs&category=ai) for your service and SDK.







 About API keys 

Three types of API keys are supported by Watson services:



* Service-specific API keys