vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can exclude the image field from the index later. 







 Reusing SDU models 

After you define a model with the SDU tool, you can save it and reuse it in other collections by exporting it from one collection and importing it to another.

To reuse a model, complete the following steps:



1. Export the model that you want to reuse. From the SDU toolbar menu, select Export model.

Zoom

![Import and export menu](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/sdu-import-export.png)

Figure 1. Import and export menu
2. Create the collection where you want to reuse the model. Add only one document to the collection at first.
3. Import the model from the SDU toolbar. The exported model has a file extension of .sdumodel.
4. Add the rest of the documents to the collection. Open the Activity tab of the Manage collections page, and then click Upload data to add more files to the collection.



Use the imported model as-is. Do not make any more annotations. If you make annotations after you import the .sdumodel file, the imported model will be overwritten.







 Smart Document Understanding limits 

The number of custom fields that you can create per Smart Document Understanding model depends on your Discovery plan type.



Custom field limits

 Plan Custom fields per SDU model 

 Cloud Pak for Data Unlimited 
 Premium 100 
 Enterprise 100 
 Plus (includes Trial) 40 



The maximum number of documents that you can annotate to train an SDU model per collection depends on your Discovery plan type.



Training set limits

 Plan Documents per collection 

 Cloud Pak for Data 40 
 Premium 40 
 Enterprise 40 
 Plus (includes Trial) 40 







 Managing fields 

The Manage fields tab contains several options:

Identify fields to index
Add the IP range 198.51.100.0 to 198.51.100.255 to the current allowlist for the "MyPSQL" deployment

ibmcloud cdb deployment-whitelist-add MyPSQL 198.51.100.0/24 "Testing range is now open"







 ibmcloud cdb deployment-allowlist-delete 

Short version - wl-del

Removes an IP address or range from the current allowlist for a deployment. An IP address is an IPv4 or IPv6 address while a range is a masked IPv4 address, for example, 1.2.3.0/24.

ibmcloud cdb deployment-allowlist-delete <deployment name or CRN> <allowlist address or range> [--nowait] [--json]



 Command options 



* --nowait or -n Do not wait for the allowlist delete task to complete. Display the allowlist delete task details and exit.
* --json or -j Display results as JSON.







 Examples 

Remove the IP address 198.51.100.1 from the current allowlist for the "MyPSQL" deployment

ibmcloud cdb deployment-whitelist-delete MyPSQL 198.51.100.1 "allowlisted for testing"

Remove the IP range 198.51.100.0 to 198.51.100.255 from the current allowlist for the "MyPSQL" deployment

ibmcloud cdb deployment-whitelist-delete MyPSQL 198.51.100.0/24 "Testing range is now open"









 Tasks 

Tasks are created whenever you perform an action on your deployment. Tasks include things like taking a backup, group scaling, and changing a user password. Most cdb commands poll the running task and exit when it completes. You can change this behavior with the --nowait flag, which returns task information and exits. Records of successful tasks are shown for 24 - 48 hours, and unsuccessful tasks are shown for 7 - 8 days.
Add the IP range 198.51.100.0 to 198.51.100.255 to the current allowlist for the "MyPSQL" deployment

ibmcloud cdb deployment-whitelist-add MyPSQL 198.51.100.0/24 "Testing range is now open"







 ibmcloud cdb deployment-whitelist-delete 

Short version - wl-del

Removes an IP address or range from the current allowlist for a deployment. An IP address is an IPv4 or IPv6 address while a range is a masked IPv4 address, for example, 1.2.3.0/24.

ibmcloud cdb deployment-whitelist-delete <deployment name or CRN> <allowlist address or range> [--nowait] [--json]



 Command options 



* --nowait or -n Do not wait for the allowlist delete task to complete. Display the allowlist delete task details and exit.
* --json or -j Display results as JSON.







 Examples 

Remove the IP address 198.51.100.1 from the current allowlist for the "MyPSQL" deployment

ibmcloud cdb deployment-whitelist-delete MyPSQL 198.51.100.1 "allowlisted for testing"

Remove the IP range 198.51.100.0 to 198.51.100.255 from the current allowlist for the "MyPSQL" deployment

ibmcloud cdb deployment-whitelist-delete MyPSQL 198.51.100.0/24 "Testing range is now open"









 Tasks 

Tasks are created whenever you perform an action on your deployment. Tasks include things like taking a backup, group scaling, and changing a user password. Most cdb commands poll the running task and exit when it completes. You can change this behavior with the --nowait flag, which returns task information and exits. Records of successful tasks are shown for 24 - 48 hours, and unsuccessful tasks are shown for 7 - 8 days.
[Shows text from the "Technology - computerworld.com" document with only the text "February 3, 2009" annotated as a mention of the "RuleDate" class.](images/rule-add10.png "Shows text from the "Technology - computerworld.com" document with only the text "February 3, 2009" annotated as a mention of the "RuleDate" class.")

You can search for all occurrences of RuleDate class mentions in the sample documents by clicking the Search annotation in documents icon ![A magnifying glass to represent a search](https://cloud.ibm.com/docs-content/v1/content/50eddb8fd81f33092880335ff107a78ff5cd0f65/watson-knowledge-studio/images/filter_gray.png) next to the RuleDate class from the Class panel. It is a good practice to check that all dates are captured properly to confirm that you defined the pattern correctly.

![Shows the "Find Annotations" page with two documents that contain dates that match the rule pattern you just defined.](images/rule-add11.png "Shows the "Find Annotations" page with two documents that contain dates that match the rule pattern you just defined.")









 Lesson 8: Creating a rule-based model 

In this lesson, you will learn how to create a rule-based model.



 About this task 

For more information about creating a rule-based model, see [Creating the rule-based model](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-knowledge-studio-wks_rule_train).





 Procedure 



1. Select Rule-based Model > Versions and click the Rule-based model type mapping tab.
2. Map the RuleDate class to the DATE entity from the type system.



1. Find the DATE entity, and click Edit.

![Shows the user clicking Edit for the "DATE" entity type in the "Rule-based model type mapping" tab.]
This path will be referenced as <PATH_TO_SAMPLE_BIN_DIR> for the rest of this task.



* For Windows, this will be the bin directory unpacked in the previous step, the location of which will depend upon where you chose to unpack the bundle.
* For Linux, this will be the samp/bin directory unpacked in the previous step, the location of which will depend upon where you chose to unpack the bundle.











 TLS additional setup 

To use a connect via TLS, we will need to specify the channel definitions using a CCDT file.



1. Open a web browser, and navigate to your MQ on Cloud service instance in IBM Cloud.
2. Find your queue manager in the queue manager list and click on it's name to navigate to the queue manager details page.

![Queue manager list view in MQ on Cloud with queue manager name highlighted](https://cloud.ibm.com/docs-content/v1/content/3a120b16db5fdc3e70d071af8a63ce5515c1b096/mqcloud/images/mqoc_connect_app_qm_list.png)
3. Click the "Connection Information" button in the top right of this page.

You may also want to download the text version, which is easier to read, and a useful source of the queue manager name and url.

![Queue manager details view in MQ on Cloud with connection information button hightlighted](https://cloud.ibm.com/docs-content/v1/content/3a120b16db5fdc3e70d071af8a63ce5515c1b096/mqcloud/images/mqoc_connect_app_qm_details.png)

!
Understanding your responsibilities when using projects 

Learn about the management responsibilities and terms and conditions that you have when you use projects. For a high-level view of the service types in IBM Cloud® and the breakdown of responsibilities between the customer and IBM for each type, see [Shared responsibilities for IBM Cloud offerings](https://cloud.ibm.com/docs/overview?topic=overview-shared-responsibilities).

Review the following sections for the specific responsibilities for you and for IBM when you use projects. For the overall terms of use, see [IBM Cloud® Terms and Notices](https://cloud.ibm.com/docs/overview/terms-of-use?topic=overview-terms).



 Incident and operations management 

Incident and operations management includes tasks such as monitoring, event management, high availability, problem determination, recovery, and full state backup and recovery.



Table 1. Responsibilites for incident and operations
The first column describes the task that the customer or IBM might be responsibility for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Task IBM Responsibilities Your Responsibilities 

 Monitor the status of a project IBM provides the ability for customers to monitor their project's lifecycle. Use the [needs attention widget](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-needs-attention-projects) to monitor events that specifically impact the lifecycle of your project. You can also use the IBM Cloud Activity Tracker service to [audit events for a project](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-at_events). 







 Change management 

Change management includes tasks such as deployment, configuration, upgrades, patching, configuration changes, and deletion.



Table 2. Responsibilites for change management
The first column describes the task that the customer or IBM might be responsibility for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Task IBM Responsibilities Your Responsibilities
If you do not specify the --job option, the --name and the --image values are required. This value is optional.

--instances, --is
: Specifies the number of instances that are used for this job run. When you use this option, the system converts to array indices. For example, if you specify instances of 5, the system converts to array-indices of 0 - 4. This option can only be specified if the --array-indices option is not specified. This value is optional. The default value is 1.

--job, -j
: The name of the job configuration. View job configurations with the job list command. If you specify the --job value, you can optionally specify the --name value. If you don't specify the --job value, you must specify the --name and --image values. This value is optional.

--maxexecutiontime, --met
: The maximum execution time in seconds for this job run. This option can only be specified if mode is task. This value is optional. The default value is 7200.

--memory, -m
: The amount of memory to assign to this job run. Use M for megabytes or G for gigabytes. For valid values, see [Supported memory and CPU combinations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-mem-cpu-combo). This value is optional. The default value is 4G.

--mode
: The mode of the job run. Valid values are task and daemon. In task mode, the maxexecutiontime and retrylimit options apply. In daemon mode, since there is no timeout and failed instances are restarted indefinitely, the maxexecutiontime and retrylimit options are not allowed. This value is optional. The default value is task.

--mount-configmap, --mount-cm
[AMT-Sign-On](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-AMT-Request-SSP.png)
6. Save the record.

You have successfully submitted an access request for Self-Service Automation access! You will receive an email notification when your access request is reviewed and granted.





 Supported Requests 

Currently Service Requests are only supported in non-production environments.



 Start Asset Management Application 

This task can be used to start the IBM Maximo Manage application for the target environment.

To execute this task on an environment, follow the instructions for [Submitting a Service Request](https://cloud.ibm.com/docs/mas-ms?topic=mas-ms-sspsubmitting-a-service-request).





 Stop Asset Management Application 

This task can be used to stop the IBM Maximo Manage application for the target environment.

To execute this task on an environment, follow the instructions for [Submitting a Service Request](https://cloud.ibm.com/docs/mas-ms?topic=mas-ms-sspsubmitting-a-service-request).





 Restart Asset Management Application 

This task can be used to restart the IBM Maximo Manage application for the target environment.

To execute this task on an environment, follow the instructions for [Submitting a Service Request](https://cloud.ibm.com/docs/mas-ms?topic=mas-ms-sspsubmitting-a-service-request).





 Run ConfigDB 

This task can be used to apply all pending database configuration changes for the target environment. The task stops the IBM Maximo Manage application, runs the Maximo ConfigDB process, then restarts the IBM Maximo Manage application.
For users with a Pay-As-You-Go or Subscription account, you can create extra resource groups to make managing quota and viewing billing usage for a set of resources easier. You can also group resources to make it easier for you to assign users access to more than one service at a time. To learn more about working with resource groups for your account, see [Managing resource groups](https://cloud.ibm.com/docs/account?topic=account-rgs).

Updates for IBM Cloud IAM
: The introduction of resource groups within your IBM Cloud account provides a new way for you to assign access. Users and service IDs can be assigned access to all services within a resource group, enabling you to quickly assign access to more than one resource at a time. You can also customize access for each user or service ID by assigning access to just some services within a resource group, or you choose to assign access to individual resources down to the service instance level. For more information about the features that you can take advantage of by using IAM, see [What features does IAM provide?](https://cloud.ibm.com/docs/account?topic=account-iamoverviewfeatures)

Customize your dashboard view
: You can view and manage all the resources in your account from your dashboard in the IBM Cloud console. And now, you can set filters to customize your view. For example, you can filter by resource group to view the specific resources in a resource group. You can also filter by region or Cloud Foundry space. For more details, see [Managing resources on the dashboard](https://cloud.ibm.com/docs/overview?topic=overview-uidashboardview).





 02 November 2017 

Support Center
: We now have the new Support Center where you can search for information, post questions to our developer community, and manage tickets. Go to Support > Support Center in the IBM Cloud console menu bar.







 October 2017 



 31 October 2017 

Introducing IBM Cloud
: Bluemix is now IBM Cloud. Besides rolling out our new name, nothing changes. You can still easily build and run your apps and services as always.
In the Ingress controller resource, find the spec.endpointPublishingStrategy.loadBalancer section and define the following providerParameters values.

endpointPublishingStrategy:
loadBalancer:
providerParameters:
type: IBM
ibm:
protocol: TCP
scope: External
type: LoadBalancerService
3. Save and apply the resource.









 Customizing Ingress routing with annotations 

If you want to customize routing rules for your app, you can use [route-specific HAProxy annotations](https://docs.openshift.com/container-platform/4.11/networking/routes/route-configuration.htmlnw-route-specific-annotations_route-configuration) in the Ingress resources that you define.

These supported annotations are in the format haproxy.router.openshift.io/<annotation> or router.openshift.io/<annotation>.IBM Cloud Kubernetes Service annotations (ingress.bluemix.net/<annotation>) and NGINX annotations (nginx.ingress.kubernetes.io/<annotation>) are not supported for the Ingress controller or the Ingress resource in Red Hat OpenShift version 4.
Specify the name and location in which to store the CSV file that is generated, and then click Save.







 Uploading entities 

If you have a large number of entities, you might find it easier to upload them from a comma-separated value (CSV) file than to define them one by one.

Entity annotations are not included in the upload of an entity CSV file. You must upload the entire dialog skill to retain the associated annotations for a contextual entity in that skill. If you download and upload entities only, then any contextual entities that you downloaded are treated as dictionary-based entities after you upload them.



1. Collect the entities into a CSV file, or export them from a spreadsheet to a CSV file. The required format for each line in the file is as follows:

<entity>,<value>,<synonyms>

where <entity> is the name of an entity, <value> is a value for the entity, and <synonyms> is a comma-separated list of synonyms for that value.

weekday,Monday,Mon
weekday,Tuesday,Tue,Tues
weekday,Wednesday,Wed
weekday,Thursday,Thur,Thu,Thurs
weekday,Friday,Fri
weekday,Saturday,Sat
weekday,Sunday,Sun
month,January,Jan
month,February,Feb
month,March,Mar
month,April,Apr
month,May

Uploading a CSV file also supports patterns. Any string wrapped with / will be considered a pattern (as opposed to a synonym).

ContactInfo,localPhone,/(d{3})-(d{4})/
ContactInfo,fullUSphone,/(d{3})-(d{3})-(d{4})/
ContactInfo,internationalPhone,/^((?+?[0-9])?)?[0-9_- ()]$/
ContactInfo,email,/b[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+.
The following sysctl network values can be set on all worker nodes in a cluster by using the daemonset described in the [Modifying worker node kernel settings](https://cloud.ibm.com/docs/openshift?topic=openshift-kernelworker-kernel-ds) section. However, there currently isn't a way to set these sysctl keepalive settings on all pods by default in a cluster. The best way to modify the settings on all pods is to use a privileged initContainer. Review the following example of how to set up an initContainer for a deployment in a test-ns namespace.

Allow privileged initContainers in the test-ns namespace:

 {: pre}
oc adm policy add-scc-to-groupl privileged system:serviceaccounts:test-ns


Deploy the following example initContainer. Remember to change the containers: section to your own application containers. The initContainer then sets the sysctl settings for all the regular containers in the pod because they all share the same network namespace.

 {: pre}
kubectl apply -f - << EOF
apiVersion: apps/v1
kind: Deployment
metadata:
name: test-sysctl
namespace: test-ns
labels:
run: test-sysctl
spec:
replicas: 2
selector:
matchLabels:
run: test-sysctl
template:
metadata:
labels:
run: test-sysctl
spec:
initContainers:
- command:
- sh
- -c
- sysctl -e -w net.ipv4.tcp_keepalive_time=40; sysctl -e -w net.ipv4.tcp_keepalive_intvl=15; sysctl -e -w net.ipv4.tcp_keepalive_probes=6;
image: us.icr.io/armada-master/alpine:latest
Change management 

Change management includes tasks such as deployment, configuration, upgrades, patching, configuration changes, and deletion.



Table 2. Responsibilites for change management
The rows are read from left to right. The first column describes the task that the customer or IBM might be responsibility for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 IBM Responsibilities Your Responsibilities 

 Updates, fixes, and new features IBM provides regular updates and bug fixes, as well as new features following a continuous delivery model in a manner transparent to the customer. 
 Updates, fixes, or the delivery of new profiles Release updates and new profiles in accordance with changing compliance requirements. Notify customers of changes made through release notes and change logs. Review change logs to understand the updates and migrate to the new profile by creating new attachments. 







 Identity and access management 

Identity and access management includes tasks such as authentication, authorization, access control policies, and approving, granting, and revoking access.



Table 3. Responsibilites for identity and access management
The rows are read from left to right. The first column describes the task that the customer or IBM might be responsibility for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 IBM Responsibilities Your Responsibilities 

 Restricting access Provide the ability to control user access based on role. Use Identity and Access Management (IAM) to assign access. 







 Security and regulation compliance 

Security and regulation compliance includes tasks such as security controls implementation and compliance certification.



Table 4. Responsibilites for security and regulation compliance
The rows are read from left to right. The first column describes the task that the customer or IBM might be responsibility for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 IBM Responsibilities Your Responsibilities 

 Meet security and compliance objectives Provide a secure service that complies with key standards.
Table 4. Responsibilities for change management for VMware Solutions offerings (other than VMware Shared)
The rows are read from left to right. The first column describes the task that a customer or IBM might be responsible for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Task IBM responsibilities Your responsibilities 

 Scaling Scale your VMware infrastructure as requested. Choose the capacity for your VMware Solutions instances. 
 Upgrading and patching For VMware vCenter Server, VMware vSphere, VMware Regulated Workloads, and Cyber Recovery, IBM does not have access to components to perform upgrades and patching. You have the responsibility to apply updates to VMware components (VMware vSphere Hypervisor ESXi, vCenter Server, VMware NSX-T, VMware vSAN, Microsoft Active Directory™) and any additional add-on components (VMware Aria, Entrust, Caveonix RiskForesight, Veeam Backup and Replication). You can use [VMware Update Manager](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-opsmgmt-vum) to assist with the updates. The Regulated Workloads section of this documentation also includes a [version compatibility matrix](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrw-apply-updates). 









 Identity and access management 

Identity and access management includes tasks such as authentication, authorization, access control policies, and approving, granting, and revoking access.

The following table describes the responsibilities that are related to identity and access management for all VMware Solutions offerings.



Table 5. Responsibilities for identity and access management
The rows are read from left to right. The first column describes the task that a customer or IBM might be responsible for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Task IBM responsibilities Your responsibilities