vania-janet/multiturn-rag-retrieval-data huggingface dataset:
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 

For steps on how to connect from SAS to a Db2 Warehouse on Cloud database, see the SAS documentation:



* [SAS/ACCESS Interface to DB2 under UNIX and PC Hosts](https://documentation.sas.com/?docsetId=acreldb&docsetTarget=p1dzq4zjg1iycgn16l4xj9nnvibt.htm&docsetVersion=9.4&locale=en)









 R development environment 

Instead of using the RStudio® environment that is integrated within IBM Watson Studio, you might prefer to use your own, locally installed R development environment. For example, you might have your own RStudio installation, or you might prefer to use some other development tool such as Rcmdr or Rattle. These instructions explain how to connect an R development environment 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 



1. In your local R environment, install the ibmdbR package by entering the following command:

install.packages("ibmdbR")

Your local R environment accesses the Comprehensive R Archive Network (CRAN) and automatically downloads and installs the ibmdbR package and any prerequisite packages that are not already installed.
2. Create an ODBC driver connection between your R development environment and your Db2 Warehouse on Cloud database:

a.
7. Type the user ID and password that you use to log in to Db2 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 results 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. For more information about how to generate charts and reports and how to run SQL queries on your data from the web console, see:



* [Tutorial: Generating charts and reports by using Excel](https://www.ibm.com/support/knowledgecenter/SSFMBX/com.ibm.swg.im.dashdb.analytics.doc/doc/explore_excel_reports.html)
* [Analyzing with Excel](https://www.ibm.com/support/knowledgecenter/SSFMBX/com.ibm.swg.im.dashdb.analytics.doc/doc/exploreexcel.html)











 Data science 



 SAS 

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



 Prerequisites 

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





 Procedure 

For steps on how to connect from SAS to a Db2 on Cloud database, see the SAS documentation:



* [SAS/ACCESS Interface to DB2 under UNIX and PC Hosts](https://documentation.sas.com/?docsetId=acreldb&docsetTarget=p1dzq4zjg1iycgn16l4xj9nnvibt.htm&docsetVersion=9.4&locale=en)
So as a much simpler, business-oriented example, consider a city-wide fire, such as the one that burned down much of Chicago in the late 1800s. Fires on that scale are unusual, but not unique. As a business, should you spend time and money making sure that your computer systems could survive such a fire? The answer depends on various factors, but if for instance, your entire customer base is in Chicago, worrying about events that will wipe out the whole city is likely not useful. So it is worth thinking about what sorts of things might fail, how likely they are to happen, and how damaging they would be, before deciding what level of redundancy is appropriate.



 Geographic redundancy 

Levels of redundancy have both a technical and a geographic component. If you have two houses, are you more likely to become homeless if the houses are next door to each other or if they are in different countries? Similar considerations drive computer system redundancy, and are behind IBM®’s use of local, regional, and global redundancy. Local redundancy duplicates some or all of a computer system in the same data center. This protects against many kinds of outages, but not all. Regional redundancy, as implemented by IBM, provides at least three copies of the system in three different data centers, so a single local event, like a large fire, is unlikely to take down all the systems. Global redundancy is available for customers that want to avoid outages that are caused by large regional events such as severe hurricanes and typhoons.

Zoom

![Geographic levels of redundancy.](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/overview/images/geographic-redundancy.svg)

Figure 2. Local, regional, and global geographic redundancy





 Technical redundancy 

Most public clouds have standardized geographic redundancy, although the various vendors do it in slightly different ways. But technical redundancy is not provided by the cloud vendors. Instead, they provide the tools for customers to build their own technical redundancy.
You can achieve HA with multiple client connections to the same gateway ID as allowed by your [Secure Gateway Service Plan](https://cloud.ibm.com/docs/SecureGateway?topic=SecureGateway-secure-gateway-service-plans). For additional information, see [High Availability](https://cloud.ibm.com/docs/SecureGateway?topic=SecureGateway-about-sgabout-ha).
* What should I do when the security token is expired?

The security token could be regenerated in the edit board of the gateway panel, you can click the link Regenerate Token which next to Token Expiration to regenerate the token. The Save button cannot be used to regenerate the token. For additional information, see [Regenerate security token](https://cloud.ibm.com/docs/SecureGateway?topic=SecureGateway-add-sg-gwregen-sectoken)



Logging and monitoring Activity Tracker Event Routing



* What are the different ways to manage auditing events?

Activity Tracker Event Routing offers 2 different ways to manage auditing events in an IBM Cloud account. You can use Activity Tracker, an IAM enabled service, to manage auditing events through instances that you provision in each IBM Cloud region where you operate. Alternatively, you can use Activity Tracker Event Routing, a platform service, to manage auditing events at the account-level by configuring targets and routes that define where auditing data is routed. Activity Tracker Event Routing can only route events that are generated in [supported regions](https://cloud.ibm.com/docs/atracker?topic=atracker-regionsregions-atracker). Other regions, where Activity Tracker Event Routing is not available, continue to manage events by using Activity Tracker Event Routing hosted event search.

Activity Tracker routes location-based auditing events to an Activity Tracker instance in the region where they are generated and routes global auditing events to the Activity Tracker instance that is provisioned in Frankfurt.

Activity Tracker Event Routing routes events based on the location that is specified in the logSourceCRN field included in the event.
[Using Terraform workspaces](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution26-plan-create-update-deployments/terraform-workspaces.png)

Using Terraform workspaces





 Global Configuration 

Under the [terraform/global](https://github.com/IBM-Cloud/multiple-environments-as-code/tree/master/terraform/global) directory, you find the Terraform scripts to provision common resources. It could be an instance of IBM Cloud Activity Tracker Event Routing (this tutorial won't create such instance). To illustrate what could be done, the file [main.tf](https://github.com/IBM-Cloud/multiple-environments-as-code/blob/master/terraform/global/main.tf) contains the readout of the account ID:

data "ibm_iam_account_settings" "iam_account_settings" {
}

To fully deploy the environments, you will use a mix of Terraform and the IBM Cloud CLI. Shell scripts written with the CLI may need to reference the account ID or region. The global directory also includes [outputs.tf](https://github.com/IBM-Cloud/multiple-environments-as-code/blob/master/terraform/global/outputs.tf) which will produce a file containing this information as keys/values suitable to be reused in scripting:

 generate a property file suitable for shell scripts with useful variables relating to the environment
resource "local_file" "output" {
content = <<EOF
ACCOUNT_ID=${data.ibm_iam_account_settings.iam_account_settings.account_id}
REGION=${var.region}
EOF
filename = "../outputs/global.env"
}





 Individual Environments 

There are different approaches to manage multiple environments with Terraform.
A solution that handles more data, from more sources to deliver the solutions that increase an organization’s success in the next generation of business.

SAP BW/4HANA, combined with SAP S/4HANA and the SAP HANA platform, combines traditional data warehousing, such as operational reporting and historical analysis, with the future - logical data warehouse, Internet of Things, and data lakes.

SAP BW/4HANA combines with SAP S/4HANA to meet your operational and historical analytics needs by using the same data as your applications, so you are always using fresh data.

With a logical data warehouse approach that uses intelligent data integration, SAP BW/4HANA eliminates duplication and expensive data movement to connect the data silos in your organization. All data sources can be connected, including SAP and non-SAP data sources.





 Ansible for SAP installation 

Ansible is an automation tool for the deployment of several IT tasks. For more information about Ansible, see the [Ansible Documentation](https://docs.ansible.com/ansible/latest/index.html).

The deployment is done by using the Ansible core, which provides CLI tools for automation. More information about Ansible core can be found on the [Ansible core page](https://docs.ansible.com/ansible-core/devel/index.html).

The Ansible playbook is called directly by the Terraform script. The script starts with Terraform specific steps for creating the VPC, and continues automatically with the Ansible-specific steps to install the SAP system.





 Where to run the scripts 

The recommended way to run the scripts is from your deployment (bastion) server because the deployment (bastion) server has Terraform and Ansible already installed. If you want to run the scripts from your local workstation, you need to install Terraform and Ansible locally.

For both the deployment (bastion) server and local workstation, you must download the SAP kits to the temporary storage assigned to you on the deployment (bastion) server. Ansible installs the kits for you. You specify the location of the kits in the configuration files.





 Prerequisite, where to run the scripts
* [Global events](https://cloud.ibm.com/docs/atracker?topic=atracker-event_typesevent_types_global)
* [Location-based events](https://cloud.ibm.com/docs/atracker?topic=atracker-event_typesevent_types_location)



When you configure a route in a region, you must specify the type of event. When you set receive_global_events to true or false, you are indicating the type of events that are collected in the region:



* When you set receive_global_events to true, you are indicating that you want global events and location-based events to go to the target that is configured in the rule that is defined in the route.
* When you set receive_global_events to false, you are indicating that you want location-based events to go to the target that is configured in the rule that is defined in the route.



If you operate in different regions, you must define 1 route for each region. In addition, you must choose the region where you want to collect global events, and configure that region to collect both types of events.

The following table outlines different scenarios that explain where auditing events are collected in your account:



Table 1. Auditing events collection scenarios

 Event Type Scenario Outcome 

 Location-based events No routes defined Events are routed to IBM Cloud Activity Tracker. 
 Location-based events 1 route is defined for 1 region with receive_global_events = false Events, that are generated in the region where the route is defined, are sent to the bucket that is configured. Auditing events that are generated in other regions, where there is no route defined, are routed to IBM Cloud Activity Tracker. 
 Location-based events Routes defined for multiple regions with receive_global_events = false Events, that are generated in the regions where routes are defined, are sent to the bucket that is configured per region. Auditing events that are generated in other regions, where there is no route defined, are routed to IBM Cloud Activity Tracker. 
 Global events No route in the account is defined with receive_global_events = true Global events are sent to IBM Cloud Activity Tracker.
tags: department:finance,region:us-south
...
4. Save the changes.



Changes are applied automatically.

For the sample provided, you would get the tags agent.tag.department and agent.tag.region. You could use them to define alerts, customize scopes and more.





 Collecting a set of Kubernetes events 

Monitoring supports event integrations with Kubernetes. {site.data.keyword.mon_short}} agents automatically discover these services and collect event data from them. You can edit the agent config file to change its default behavior, and include or exclude event data.

By default, only a limited set of events is collected. For more information about the events that are collected by default, see [Kubernetes events](https://docs.sysdig.com/en/event-types.html).

To add or remove events, you must customize the sysdig-agent-configmap.yaml file and specify what events to include and which ones to filter out. Note: An entry in a section in sysdig-agent-configmap.yaml overrides the entire section in the default configuration.

To filter events from Kubernetes pods, complete the following steps:



1. Set up the cluster environment. Run the following commands:

First, get the command to set the environment variable and download the Kubernetes configuration files.

ibmcloud ks cluster config --cluster <cluster_name_or_ID>
2. Edit the sysdig-agent-configmap.yaml file.

Run the following command:

kubectl edit configmap sysdig-agent -n ibm-observe
3. Make changes. Add the events section or update the section.

Note: Refer to vi editor instructions to learn how to make changes.

For example, you might want to collect Kubernetes pod pulling events and filter out other pod events that are collected by default. You still want to collect default Kubernetes events for nodes and replicationControllers.

events:
Configuring an Event Streams target 

You can define an Event Streams topic as a IBM Cloud Activity Tracker Event Routing target to send auditing events to other corporate tools such as Security Information and Event Management (SIEM) tools.

This tutorial uses the IBM Cloud Activity Tracker Event Routing v2 API.



 Scenarios 

You can define an Event Streams topic as a IBM Cloud Activity Tracker Event Routing target to send auditing events to other corporate tools such as Security Information and Event Management (SIEM) tools. When you route data to data lakes, other analysis tools, or other SIEM tools, you can add additional capabilities to the ones provided by Activity Tracker Event Routing:



* You can gain visibility into enterprise data across on-premises and cloud-based environments.
* You can identify and prioritize security threats that might affect your organization.
* You can detect vulnerabilities by using Artificial Intelligence (AI) to investigate threats and incidents.







 Prerequisites 



* Learn about Activity Tracker Event Routing. For more information, see [About](https://cloud.ibm.com/docs/atracker?topic=atracker-atracker-resources).
* Install the IBM Cloud CLI. For more information, see [Installing the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli).
* Install the latest Activity Tracker Event Routing CLI V2 plugin in your local system. See [Installing the Activity Tracker Event Routing CLI](https://cloud.ibm.com/docs/atracker?topic=atracker-atracker-cli-config&interface=cli).
* You need a user ID that is a member, or an owner of, an IBM Cloud account. To get an IBM Cloud user ID, go to: [Create an account](https://cloud.ibm.com/login).
* Every user that manages the Activity Tracker Event Routing configuration in your account must be assigned an access policy. The policy determines what actions the user can perform.
Review '<provider>' infrastructure user permissions.

The worker node instance can't be found. Review '<provider>' infrastructure user permissions.

The worker node instance can't be identified. Review '<provider>' infrastructure user permissions.

The IAM token exchange request failed with the message: <message>
IAM token exchange request failed: <message>

The cluster could not be configured with the registry. Make sure that you have the Administrator role for Container Registry.

 Why it’s happening 

The infrastructure credentials that are set for the region and resource group are missing the appropriate [infrastructure permissions](https://cloud.ibm.com/docs/openshift?topic=openshift-classic-roles).

The user's infrastructure permissions are most commonly stored as an [API key](https://cloud.ibm.com/docs/openshift?topic=openshift-access-creds) for the region and resource group. More rarely, if you use a [different IBM Cloud account type](https://cloud.ibm.com/docs/openshift?topic=openshift-access-credsunderstand_infra), you might have [set infrastructure credentials manually](https://cloud.ibm.com/docs/openshift?topic=openshift-access-credscredentials).

 How to fix it 

The account owner must set up the infrastructure account credentials properly. The credentials depend on what type of infrastructure account you are using.

Before you begin, [Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster).



1. Identify what user credentials are used for the region and resource group's infrastructure permissions.



1. Check the API key for a region and resource group of the cluster.

ibmcloud oc api-key info --cluster <cluster_name_or_ID>

Example output
Analyzing your data with the Content Mining application 

Use the Discovery Content Mining application to analyze your data. The application shows subsets of your information in visualizations that can help you to find patterns, trends, and anomalies.

Only users of installed deployments (IBM Cloud Pak for Data) or Enterprise and Premium plan managed deployments can use the Content Mining application.



 Overview video 



* Video transcript

Watson Discovery Content Mining Project presented by Stuart Strolin. (Music intro) The purpose of this video is to familiarize you with the content mining project in Watson Discovery.

Content mining is one of the primary use cases for Watson Discovery and is used for analyzing and exploring both structured and unstructured data to find insights and extract hidden meaning. It is used by both the citizen analyst and the data scientist.

The content mining project can be used for all types of analysis because the user interface is not specific to a particular industry or set of data.

In this scenario, you are an analyst for a fictitious automobile company. Operational reports have alerted the company to an unusual accident rate for one of their cars. Your job is to find out why.

Using the content mining project, you begin your analysis by looking at the unstructured data from the national motor vehicle incident reports. You are presented with an interface that allows you to select the car model and begin your analysis (on the Collections page). In this case, you are interested in the Hill Walker. You could type that information into the search section at the start of the page. But it's easier just to click on the item. You can add as many search terms and conditions as you like. But in reality, you want to let the application guide your analysis.

What you see now is the navigation view (in Guided mode). It keeps track of your analysis and provides options for next steps. It also provides a count of the number of documents that match your current state of analysis. In this small collection, the number of documents relating to the Hill Walker is only 51. In a production data set, the number would usually be much larger. Analyzing trends and anomalies is often a good way to start as it allows you to see if anything seems out of the ordinary.
It’s also more performant at index time because the index loads the document once and generates multiple indexes from it.

Design documents themselves are read and written by using the same read/write endpoints as any other document. With these endpoints, you can create, inspect, modify, and delete design documents from within your application. However, even small changes to design documents can have significant effects on your database. When you update a design document, all views in it become unavailable until indexing is complete. This lag can be problematic in production. To avoid it, you have to do a crazy design document-swapping dance (see [couchmigrate](https://github.com/glynnbird/couchmigrate)).

In most cases, this process is probably not what you want to have to deal with. As you start out, it is most likely more convenient to have a one-view-per-design document policy.

Also, in case it isn’t obvious, views are code. Views must be subject to the same processes you use in terms of source code version management for the rest of your application code. How to achieve this standard might not be immediately obvious. You could increase the version number for the JavaScript snippets. Then, you could cut and paste the code into the IBM Cloudant Dashboard to deploy whenever a change occurs. Yes, we all resort to this practice from time to time.

Better ways to do this exist, and we have one reason to use some of the tools that surround the [couchapp](https://docs.couchdb.org/en/stable/ddocs/) concept. A couchapp is a self-contained CouchDB web application that nowadays doesn’t see much use. Several couchapp tools exist that are there to make the deployment of a couchapp, including its views, crucially, easier.

Using a couchapp tool means that you can automate deployment of views as needed, even when not using the couchapp concept itself.