vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Purging by prefix is useful when you want to purge everything within a directory, or increase control over cached objects in a particular path. It can also simplify the number of purge calls made.





 Purge by hostnames (Enterprise only) 

Purging by hostname is similar to purging by prefixes. Use a list of hostnames to purge the cache of any assets associated with those hostnames.





 Purge by tags (Enterprise only) 

Tags let you define buckets of content that you wish to purge. It is an excellent way to combine objects that are commonly changed together. An HTML blog post, for example, and all of its image content could be tagged together. Mobile-only content also could be bundled using cache-tags, so that you can purge everything when you push a new update to your mobile domain.





 Purge by URLs 

With purge by URL, cached resources are immediately removed from the stored assets in your Content Delivery Network (CDN) across all data centers. New requests for the purged asset receive the latest version from your origin web server and add it back to your CDN cache within the specific data center that served the request.





 Use advanced caching features 

Bypass Cache on Cookie: Configured in a page rule, this feature allows you to serve a cached object unless a cookie of a specific name exists. For example, you can serve a cached version of the homepage unless you find a SessionID cookie indicating that the customer is logged in, and therefore should be presented with personalized content.
Tableau offers several options for connecting to your data. To make full use of your Db2 Warehouse on Cloud database, choose the Connect Live option.





Table 1. Fields in Tableau for connection information

 Tableau field Db2 connections information field 

 Step 1: Enter a server name Host name 
 Step 2: Port Port number 
 Step 3: Enter a database on the server Database name 
 Username User ID 
 Password Password 









 Microsoft Excel 

These instructions explain how to connect Microsoft Excel to a Db2 Warehouse on Cloud database.



 Prerequisites 

Before attempting to connect to your Db2 Warehouse on Cloud database, verify that you have the [prerequisites](https://cloud.ibm.com/docs/Db2whc/connecting?topic=Db2whc-connect_ovprereqs).

You must have the Db2 driver package or the IBM® Data Server Driver Package installed on your local computer.

Restriction: Connections between Excel and Db2 Warehouse on Cloud are supported on only the Windows operating system.





 Procedure 



1. In the web console, go to the Run SQL page.
2. Type one or more SELECT statements in the editor text box.
3. Click one of the Run options.
4. Click Excel ODC File.
5. Download and open the BLUExcel.odc file in Excel. If a security notice is displayed, click Enable.
6. Click Open to connect to the Db2 Warehouse on Cloud database. The Connect To DB2 Database dialog box opens.
7. Type the user ID and password that you use to log in to Db2 Warehouse on Cloud. To obtain the user ID and password, click Connect in the web console or Connect > Connection Information in the web console.
8. Ensure that the connection mode is Share, and then click OK.







 Results 

The query results are displayed in an Excel spreadsheet. These are the same results that are displayed in the Results viewer. Now you can generate charts and reports and analyze your data by using Excel.
* Observer: The observer is the resource that creates and stores a CADF record from information available in a CADF event
* Outcome: The outcome is the status of the action against the target.
* Target: The target is the resource against which the action is performed, attempted to perform, or is pending to complete.







 Target locations 

Control of the storage location is critical to building enterprise-grade solutions on the IBM Cloud.

In IBM Cloud Activity Tracker Event Routing, a target defines where auditing events are collected. For more information, see [Targets](https://cloud.ibm.com/docs/atracker?topic=atracker-atracker-resourcesatracker-resources-targets).

You can configure different types of targets:



Table 1. List of targets

 Target Type When to use 

 IBM Cloud Object Storage (COS) cloud_object_storage To comply with Financial Services regulations. 
 Activity Tracker hosted event search logdna To comply with PCI, SOC2, Privacy Shield and HIPAA, and to view, search, and manage auditing data through the UI. 
 IBM® Event Streams for IBM Cloud® event_streams To send auditing data to data lakes, other analysis tools, and to other corporate tools such as Security Information and Event Management (SIEM) tools. 



In IBM Cloud Activity Tracker Event Routing, a route defines the rules that indicate where auditing events that are generated in an account are routed. For more information, see [Routes](https://cloud.ibm.com/docs/atracker?topic=atracker-atracker-resourcesatracker-resources-routes).





 Features 



* Consolidate auditing events to the region of your primary operations
* Route auditing events to one or multiple locations
* Improve your data residency compliance stature, keeping data at-rest within certain regions
* Feed a data lake for analytics
* Forward your activity event data to IBM Cloud Object Storage (COS) for IBM Cloud for Financial Services compliance
Depending upon how you ingested your documents previously, you can do so by using your own solution or one of the following methods:



* The [API](https://cloud.ibm.com/apidocs/discovery-dataadddocument)
* A [connector](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-sources)





 Restoring training data 

After you restore your projects, you can begin the process of re-creating your relevancy training models. To restore your training data queries and examples, re-create your individual training queries and the examples by using the [create training query](https://cloud.ibm.com/apidocs/discovery-datacreatetrainingquery) API, or you can restore your queries and examples on Discovery. For more information about restoring your training data by using Discovery, see the instructions for accessing the Train page in [Improving result relevance with training](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-train).

For the restore to work properly, note that the document IDs that you use in your training data point to the documents in your current project. Use the same IDs in your new projects to ensure that the correct documents are referenced. If the IDs do not match, your restored relevancy training will not work.





 Restoring connections to external data sources 

In case of an unanticipated loss of data, you might lose your scheduled crawls of external data sources. See [Configuring IBM Cloud data sources](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-sources) for the list of available sources.

To restore your external data, reestablish your connections to these data sources, and then recrawl them.

To find the data source credentials that you stored, follow the instructions for your chosen data source in [Configuring IBM Cloud data sources](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-sources). These instructions explain how you can reconnect to your data sources and get the data imported into Discovery.
Scroll down to the Monitoring and activity tracking section and toggle the radio button to Activity tracking enabled. Select an appropriate plan, and give the new instance a memorable name. As you may likely want to create the Activity Tracker instance in the same region as the bucket (e.g. us-east) you could name the instance something like US East AT so that you can easily find it later.
2. Click to enable Track data events and select both read & write from the drop-down list.



[Monitoring](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-monitoring-cos)

Before you get started, you need:



* An instance of [IBM Cloud™ Monitoring](https://cloud.ibm.com/docs/monitoring?topic=monitoring-getting-started)
* A user ID with [administrator platform permissions](https://cloud.ibm.com/docs/account?topic=account-userroles) and the service access [writer role](https://cloud.ibm.com/docs/account?topic=account-userrolesservice_access_roles).





1. Scroll down to the Monitoring and activity tracking section and toggle the radio button to Monitoring enabled. Select an appropriate plan, and give the new instance a memorable name. For example, if you are creating the instance in the same region as the bucket (e.g. us-east) you could name the instance US East MM so that you can easily find it later.
2. Enable monitoring for both usage and request metrics.









 Step 3: Verify the information is correct 





 Step 4: Click Create bucket to add the new bucket to your instance of Object Storage 

After your bucket is created with Activity Tracker and Monitoring, it may take a few minutes for the rules to take effect.

You are now ready to store data in a secure content store with encryption, monitoring, and audit observability!





 Get started by uploading data 



* See [uploading data](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-upload) for more information.







 Add capabilities
* How often does the problem happen?
* What sequence of events leads up to the time that the problem is reported?
* Does the problem happen after an environment change, such as upgrading or installing software or hardware?



Responding to these types of questions can give you a frame of reference in which to investigate the problem.





 Under which conditions does the problem occur? 

Knowing which systems and applications are running at the time that a problem occurs is an important part of troubleshooting. These questions about your environment can help you to identify the root cause of the problem:



* Does the problem always occur when the same task is being performed?
* Does a certain sequence of events need to happen for the problem to occur?
* Do any other applications fail at the same time?



Answering these types of questions can help you explain the environment in which the problem occurs and correlate any dependencies. Remember that just because multiple problems might have occurred around the same time, the problems are not necessarily related.





 Can the problem be reproduced? 

From a troubleshooting standpoint, the ideal problem is one that can be reproduced. Typically, when a problem can be reproduced you have a larger set of tools or procedures at your disposal to help you investigate. Consequently, problems that you can reproduce are often easier to debug and solve.

However, problems that you can reproduce can have a disadvantage: If the problem is of significant business impact, you do not want it to recur. If possible, re-create the problem in a test or development environment, which typically offers you more flexibility and control during your investigation.



* Can the problem be re-created on a test system?
* Are multiple users or applications encountering the same type of problem?
* Can the problem be re-created by running a single command, a set of commands, or a particular application?









 Cannot access the application 

Find out how to grant users access to Knowledge Studio, and address common access issues.



 Administrator 

Each Knowledge Studio instance has an administrator role associated with it. The person who originally signs up to use the application is given the administrator role automatically. The administrator can invite other people.
Securing your data 

To ensure that you can securely manage your data when you use Activity Tracker Event Routing, it is important to know exactly what data is stored and encrypted, and how you can delete any stored data.



 What data is stored in Activity Tracker Event Routing 

When you use Activity Tracker Event Routing to manage your audit events, you should differentiate between configuration data and audit data.



 Configuration data 

To configure Activity Tracker Event Routing, you must configure account settings, targets, and routes. You can configure Activity Tracker Event Routing via REST API calls, CLI commands, or by using terraform scripts. The definitions of these resources are hosted on the IBM Cloud.



* You can configure the Activity Tracker Event Routing account settings to indicate the primary and backup metadata locations where global definitions are stored such as route definitions and the type of endpoints that are enabled.

You can set the primary metadata location by configuring the account settings. Alternatively, when you define the first target in the account; the location where the target is defined is automatically set as the primary location.

You must configure the account settings to define the backup metadata location. This location is optional.
* You can define [targets](https://cloud.ibm.com/docs/atracker?topic=atracker-atracker-resourcesatracker-resources-targets) in any [supported region](https://cloud.ibm.com/docs/atracker?topic=atracker-regions).

You can control the locations in the account where a target is defined by specifying the allowed locations in the Activity Tracker Event Routing account settings.

Targe definitions are stored in the primary metadata location. If you have a backup metadata location, target definitions are also stored there.
* Route definitions are stored in the primary metadata location. If you have a backup metadata location, route definitions are also stored there.







 Auditing data 

Activity Tracker Event Routing collects management and data events from IBM Cloud services and resources:



* Management Events are generated when an API call changes the state of a Cloud resource. A resource might be an entire service instance or a resource managed by the service.
* Open an [IBM Cloud infrastructure support case](https://cloud.ibm.com/docs/openshift?topic=openshift-get-help).







 Could not obtain network VLAN 

Message:

Could not obtain network VLAN with ID: <vlan-id>

Description and resolution:

Your worker node could not be provisioned because the selected VLAN ID could not be found for one of the following reasons:



* You might have specified the VLAN number instead of the VLAN ID. The VLAN number is 3 or 4 digits long, whereas the VLAN ID is 7 digits long. To retrieve the VLAN ID, run ibmcloud oc vlan ls --zone <zone>.
* The VLAN ID might not be associated with the IBM Cloud infrastructure account that you use. To list available VLAN IDs for your account, run ibmcloud oc vlan ls --zone <zone> . To change the IBM Cloud infrastructure account, see [ibmcloud oc credential set](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_credentials_set).







 Location invalid 

Message:

The location provided for this order is invalid

Description and resolution:

Your IBM Cloud infrastructure is not set up to order compute resources in the selected data center. Contact [IBM Cloud support](https://cloud.ibm.com/docs/openshift?topic=openshift-get-help) to verify that you account is set up correctly.





 Permissions error 

Message:

The user does not have the necessary classic infrastructure permissions to add servers

'Item' must be ordered with permission.

The credentials could not be validated.

'<Provider>' infrastructure request not authorized

Description and resolution:

You might not have the required permissions to perform the action in your IBM Cloud infrastructure portfolio, or you are using the wrong infrastructure credentials.
When you enable a Forwarding URL, all of your other settings are disabled because you are sending all of your traffic to another URL.



 Setting up a forwarding URL 

To enable Forwarding URL, follow these steps:



1. Use the navigation menu to select Page Rules under Performance.
2. Create a page rule with the URL pattern that references your domain.
3. Add the Forwarding URL setting.
4. Select the forwarding type and enter the destination URL.
5. Select Provision Resource.







 Forwarding URL examples 

Imagine that you want to make it easy for anyone coming to reach a URL such as:

www.example.com/+

example.com/+

This pattern matches:

http://example.com/+
http://www.example.com/+
https://www.example.com/+
https://blog.example.com/+
https://www.blog.example.com/+

It does not match:

http://www.example.com/blog/+ [extra directory before the +]
http://www.example.com+ [no trailing slash]

After you've created the pattern that matches what you want, add the Forwarding URL setting and select the forwarding type and enter the destination URL. For example:

https://plus.google.com/yourid

Select Provision Resource. Within a few seconds any requests that match the pattern are forwarded to the new URL with the specified redirect.





 Advanced forwarding options 

If you use a basic redirect, such as forwarding the root domain to www.yourdomain.com, you lose anything else in the URL. For example, you could set up the pattern:

example.com

And have it forward to:

http://www.example.com

But then if someone entered:

example.com/some-particular-page.html

Then they are redirected to:

www.example.com

instead of:
Salesforce 

Crawl documents that are stored in a Salesforce data source.

IBM Cloud

IBM Cloud only

This information applies only to managed deployments. For more information about connecting to Salesforce from an installed deployment, see [Salesforce](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-salesforce-cp4d).



 What documents are crawled 

During the initial crawl of the content, documents from all of the objects that can be accessed from the URL that you specify are crawled and added to your collection. Knowledge Articles are crawled only if their version is published and their languages is en-us.

During subsequent scheduled recrawls, only new and modified documents are crawled and any changes are reflected in your collection. Documents that are deleted from the external data source are not deleted from the collection.

All Discovery data source connectors are read-only. Regardless of the permissions that are granted to the crawl account, Discovery never writes, updates, or deletes any content in the original data source.

Discovery can crawl the following objects:



* Any default and custom objects that you have access to
* Accounts
* Contacts
* Cases
* Contracts
* Knowledge articles
* Attachments







 Data source requirements 

In addition to the [data source requirements](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-sourcespublic-requirements) for all managed deployments, your Salesforce data source must meet the following requirements:



* The instance that you plan to connect to must be part of an Enterprise plan or higher.
* 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.







 What you need before you begin 

You must have the following information ready. If you don't know it, ask your Salesforce administrator to provide the information or consult the [Salesforce developer documentation](https://developer.salesforce.com/docs/).

Username
: The username of an account that has access to the Salesforce site. For example, jdoe@example.com
* Contact your IBM Cloud infrastructure account manager to verify that you don't exceed an account limit, such as a global quota.
* Open an [IBM Cloud infrastructure support case](https://cloud.ibm.com/docs/containers?topic=containers-get-help).







 Could not obtain network VLAN 

Message:

Could not obtain network VLAN with ID: <vlan-id>

Description and resolution:

Your worker node could not be provisioned because the selected VLAN ID could not be found for one of the following reasons:



* You might have specified the VLAN number instead of the VLAN ID. The VLAN number is 3 or 4 digits long, whereas the VLAN ID is 7 digits long. To retrieve the VLAN ID, run ibmcloud ks vlan ls --zone <zone>.
* The VLAN ID might not be associated with the IBM Cloud infrastructure account that you use. To list available VLAN IDs for your account, run ibmcloud ks vlan ls --zone <zone> . To change the IBM Cloud infrastructure account, see [ibmcloud ks credential set](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_credentials_set).







 Location invalid 

Message:

The location provided for this order is invalid

Description and resolution:

Your IBM Cloud infrastructure is not set up to order compute resources in the selected data center. Contact [IBM Cloud support](https://cloud.ibm.com/docs/containers?topic=containers-get-help) to verify that you account is set up correctly.





 Permissions error 

Message:

The user does not have the necessary classic infrastructure permissions to add servers

'Item' must be ordered with permission.

The credentials could not be validated.

'<Provider>' infrastructure request not authorized

Description and resolution:

You might not have the required permissions to perform the action in your IBM Cloud infrastructure portfolio, or you are using the wrong infrastructure credentials.
Determine your ODBC DSN data from the [connection information](https://cloud.ibm.com/docs/Db2whc/connecting?topic=Db2whc-db_details_cxn_credsdb_details_cxn_creds) that you collected beforehand.
2. Create a new connection:

a. In the ArcCatalog Catalog tree, open the Database Connections node and click Add Database Connection.

b. In the Database Connections wizard:



* Select DB2 from the Database Platform drop-down list.
* Enter the following string in the Data source field:

HostName=<hostname>;Port=<port>;Database=<database>;
CLIENTBUFFERSUNBOUNDLOBS=1;LOBCACHESIZE=50000000;
FET_BUF_SIZE=256K

where <hostname>, <port>, and <database> are placeholders that represent the host name, port number, and database name that you noted earlier.
* Select Database authentication as the authentication type.
* Specify your user name and password (the user ID and password that you noted earlier) in the corresponding fields.
* Press OK.

Zoom

![Database Connections wizard](https://cloud.ibm.com/docs-content/v1/content/68e10678b2f8b8694884ecb5442c326c9b60a3fb/Db2whc/connecting/images/2_gs_conn.jpg)

Figure 1. Database Connections wizard









 Results 

The ArcCatalog component of Esri ArcGIS for Desktop is now connected to your Db2 Warehouse on Cloud database.









 Data science 



 SAS 

These instructions explain how to create a connection from SAS to a Db2 Warehouse on Cloud database.



 Prerequisites 

Before attempting to connect to your Db2 Warehouse on Cloud database, verify that you have the [prerequisites](https://cloud.ibm.com/docs/Db2whc/connecting?topic=Db2whc-connect_ovprereqs).





 Procedure
[Datastore Properties - Target](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/connecting/images/IIDR_target_datastore.jpg)

Figure 5. View of target datastore properties

c. If the user (for example, admin) that connects to the Access Server does not exist, create that user:

Zoom

![New User](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/connecting/images/IIDR_management_user.jpg)

Figure 6. View of New User creation tool

d. Click the Access Manager tab.

e. On the Datastore Management tab, assign the user to both the source and target datastores by right-clicking each datastore and then clicking Assign User. Ensure that the credentials for accessing each instance are correct.

Zoom

![IIDR Management Console - Access Manager](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/connecting/images/IIDR_management_assign_user.jpg)

Figure 7. IIDR Management Console - Access Manager







 What to do next 

Define a subscription and perform data replication. For information, see:



* [Loading data from InfoSphere Data Replication](https://www.ibm.com/support/knowledgecenter/SSFMBX/com.ibm.swg.im.dashdb.doc/learn_how/loaddata_iidr.html)









 Data Studio 

These instructions explain how to create a connection from IBM® Data Studio to a Db2 on Cloud database.



 Prerequisites