vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Create or retrieve an IBM Cloud API key](https://cloud.ibm.com/docs/account?topic=account-userapikeycreate_user_key). The API key is used to authenticate with the IBM Cloud platform and to determine your permissions for IBM Cloud services.
* [Create or retrieve your SSH key ID](https://cloud.ibm.com/docs/ssh-keys?topic=ssh-keys-getting-started-tutorial). You need the 40-digit UUID for the SSH key, not the SSH key name.
* Terraform should already be installed on the bastion server that you deployed. For more information, see Bastion server for SAP deployment.







 Creating the infrastructure with the Schematics user interface 

Use these steps to configure the SAP NetWeaver 7.X with ASE SYB on your existing VPC by using the Schematics user interface. The scripts can take 1 - 2 hours to complete.



1. From the IBM Cloud menu, select [Schematics](https://cloud.ibm.com/schematics/overview).
2. Click Create workspace.
3. On the Specify template page:



* Enter the URL of Schematics folder.
* Select the Terraform version that is listed in the readme file.
* Click Next.



4. On the Workspace details page:



* Enter a name for the workspace.
* Select a Resource group.
* Select a Location for your workspace. The workspace location does not have to match the resource location.
* Select Next.



5. Select Create to create your workspace.
6. On the workspace Settings page, in the Input variables section, review the default input variables and provide values that match your solution:



* Your API key
* Your private SSH key from your local machine
* The ID for the SSH key that you created and uploaded to IBM Cloud.
You must create a service ID for your IBM Cloud Object Storage instance. This service ID is used by the IBM Cloud Activity Tracker instance to authenticate with your IBM Cloud Object Storage instance.

You must assign specific access policies to the service ID that restrict permissions for using specific services, or even combine permissions for accessing different services.

Complete the following steps to create a service ID with writing permissions for the IBM Cloud Object Storage instance:



1. From the Dashboard, select the IBM Cloud Object Storage instance where you plan to create the bucket.
2. Select Service credentials. Then, select New credential.
3. Enter a name that it is easy to recognize. For example, you can name the service ID activity-tracker-cos-serviceID.
4. Select the Reader role.
5. Click Add.

A new service ID is created and added to the list.

Note: The service ID that is created in the IBM Cloud and listed through the IAM UI has a generic name. The name of the service ID in the IAM UI maps to the value of the field iam_apikey_name that you created in this step through the COS service ID UI.
6. [Optional] To lock the service ID to prevent deletion, from the menu bar, click Manage > Access (IAM). Search for the service ID. Then, select the action Lock.



For the service ID that you just created, click View credentials. You can see information that is related to the service ID.



* Copy the API key. This is the value set for the field apikey.

When the service credential is rotated, make sure the [API Key is updated with the new API Key.](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-archivingarchiving_step8) Archiving will stop if the API Key is not updated.
* Copy the resource instance ID. This is the value set for the field resource_instance_id.
* Copy the value of the iam_apikey_name field.







 Step 5.
[Navigate to COS](https://cloud.ibm.com/docs-content/v1/content/63322f2f3a72050206eb05ba7f590fdcb741105c/cloud-object-storage/images/kp-tut-4.png)
2. Choose a region that corresponds with the bucket, give it a memorable name, and click Create and continue. ![Navigate to COS](https://cloud.ibm.com/docs-content/v1/content/63322f2f3a72050206eb05ba7f590fdcb741105c/cloud-object-storage/images/kp-tut-5.png)
3. Give the root key a name and click Create and continue. ![Navigate to COS](https://cloud.ibm.com/docs-content/v1/content/63322f2f3a72050206eb05ba7f590fdcb741105c/cloud-object-storage/images/kp-tut-6.png)
4. Verify the information is correct.
5. Click Create bucket.



If bucket creation fails with a 400 Bad Request error with the message The Key CRN could not be found, ensure that the CRN is correct and that the service to service authorization policy exists.

In the Buckets listing, the bucket has a View link under Attributes where you can verify that the bucket has a Key Protect key enabled.





 Step 3: Verify that it works 



1. When viewing the bucket, click the Configuration tab to verify that the bucket has Key Protect enabled.
2. Scroll down to Advanced configurations and locate Associated key management service .
3. Verify the information is correct.ß
* Create services from IBM Cloud catalog.
* Create and modify IBM Cloud VPC services, virtual server instances, networks, network prefixes, storage volumes, SSH keys, and security groups of this VPC.
* Create and modify Power® Systems Virtual Server services, virtual server instances, networks, storage volumes, ssh keys of this Power® Systems Virtual Server.
* Create and modify IBM Cloud direct links and IBM Cloud Transit Gateway.
* Access existing Object Storage services.



For information about configuring permissions, contact your IBM Cloud account administrator.





 Access for IBM Cloud projects 

You can use IBM Cloud projects as a deployment option. Projects are designed with infrastructure as code and compliance in mind to help ensure that your projects are managed, secure, and always compliant. For more information, see [Learn about IaC deployments with projects](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-understanding-projects).

You need the following access to create a project and create project tooling resources within the account. Make sure that you have the following access:



* The Editor role on the Projects service
* The Editor and Manager role on the Schematics service
* The Viewer role on the resource group for the project



For more information, see [Assigning users access to projects](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-access-project).







 Create an SSH key 

Make sure that you have an SSH key that you can use for authentication. This key is used to log in to all virtual server instances that you create. For more information about creating SSH keys, see [SSH keys](https://cloud.ibm.com/docs/vpc?topic=vpc-ssh-keys).





 Choose an operating system 

Choose a Linux operating system for your deployments. We recommend that you use the same OS release for all the hosts in the environment. When you use the same operating system version and release, it simplifies the operations management of the whole landscape. You might choose between Red Hat Enterprise Linux and Suse Linux Enterprise Server.





 Private networks
Creating a configuration in the API 



1. Generate an API key, then request a refresh token. For more information, see [Generating an IBM Cloud IAM token by using an API key](https://cloud.ibm.com/docs/account?topic=account-iamtoken_from_apikey).
2. Copy one of the following example requests and replace the variables that you want to use.

Example request to create a version 4.8 configuration.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ "config-name": "string", "controller": "string", "storage-class-parameters": [ { "additionalProp1": "string", "additionalProp2": "string", "additionalProp3": "string" } ], "storage-template-name": "local-volume-file", "storage-template-version": "4.8", "update-assignments": true, "user-config-parameters": { "entry.name": "LABEL-KEY", { "entry.name": "LABEL-VALUE", { "entry.name": "DEVICEPATH", { "entry.name": "FSTYPE","user-secret-parameters": }

Example request to create a version 4.9 configuration.
(Optional) Specify any [tags](https://cloud.ibm.com/docs/account?topic=account-tag) you want to use.
11. Select whether of not the service instance receives platform metrics for all service instances in the region.
12. To provision the IBM Cloud Monitoring service in the IBM Cloud resource group where you are logged in, click Create.



After you provision an instance, the Monitoring dashboard opens.

Note: To provision an instance through the CLI, see [Provisioning an instance through the IBM Cloud CLI](https://cloud.ibm.com/docs/monitoring?topic=monitoring-provisionprovision_cli).





 Step 3: Configure your Ubuntu server to send metrics to your instance 

To configure your Ubuntu server to send metrics to your IBM Cloud Monitoring instance, you must install a monitoring agent.

Complete the following steps from a command line:



1. Open a terminal. Then, log in to the IBM Cloud. Run the following command and follow the prompts:

ibmcloud login -a cloud.ibm.com

Select the account and region where the IBM Cloud Monitoring instance is available.
2. [Access your Ubuntu server](https://cloud.ibm.com/docs/vpc?topic=vpc-vsi_is_connecting_linux).
3. Obtain the access key. For more information, see [Getting the access key through the IBM Cloud UI](https://cloud.ibm.com/docs/monitoring?topic=monitoring-access_keyaccess_key_ibm_cloud_ui).
4. Obtain the ingestion URL. For more information, see [collector endpoints](https://cloud.ibm.com/docs/monitoring?topic=monitoring-endpointsendpoints_ingestion).
5. Deploy the monitoring agent. Run the following command:
Generate an API key, then request a refresh token. For more information, see [Generating an IBM Cloud IAM token by using an API key](https://cloud.ibm.com/docs/account?topic=account-iamtoken_from_apikey).
2. Copy one of the following example requests and replace the variables that you want to use.

Example request to create a version 21.04 configuration.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ "config-name": "string", "controller": "string", "storage-class-parameters": [ { "additionalProp1": "string", "additionalProp2": "string", "additionalProp3": "string" } ], "storage-template-name": "netapp-ontap-san", "storage-template-version": "21.04", "update-assignments": true, "user-config-parameters": { "entry.name": "MANAGEMENTLIF", { "entry.name": "DATALIF", { "entry.name": "SVM", { "entry.name": "LIMITVOLUMESIZE", { "entry.name": "LIMITAGGREGATEUSAGE","user-secret-parameters": { "entry.name": "USERNAME",{ "entry.name": "PASSWORD",}

Example request to create a version 22.04 configuration.
If you need to create more than one auditing service key, use the [UI](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-service_keysservice_keys_ui) or use the [API]](service_keys_api_create).

To create an auditing service key for a auditing instance through the command line, complete the following steps:



1. [Pre-requisite] [Install the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli).
2. Log in to the region in the IBM Cloud where the auditing instance is running. Run the following command: [ibmcloud login](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cliibmcloud_login)
3. Set the resource group where the auditing instance is running. Run the following command: [ibmcloud target](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cliibmcloud_target)

By default, the default resource group is set.
4. Get the instance name. Run the following command: [ibmcloud resource service-instances](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_service_instances)

ibmcloud resource service-instances
5. Create the IBM Cloud resource service key. Run the [ibmcloud resource service-key-create](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_service_key_create) command:

ibmcloud resource service-key-create <NAME> --instance-name <SERVICE_INSTANCE>

Where NAME is the desired name of the service key and SERVICE_INSTANCE is the name of the service instance from the previous step.
You need to set up a [30-day free trial](https://www.tableau.com/products/trial).







 Step-by-step instructions 



 Step 1: Obtain an API key to deploy infrastructure to your account 

Follow the steps [here](https://cloud.ibm.com/docs/account?topic=account-userapikey&interface=uicreate_user_key) to create an API key. This key is used in Step 2.





 Step 2: Clone the repo and change directories into the Terraform directory 

Use the following command to clone the appropriate repo and change directories into the Terraform directory:

git clone https://github.com/IBM-Cloud/mongo-bi-tools-tutorial.git
cd mongo-bi-tools-tutorial/terraform





 Step 3: Create your terraform.tfvars document 

Using the following command, create a document that is named terraform.tfvars:

ibmcloud_api_key = "<your_api_key_from_step_1>"
region = "eu-gb" Choose a suitable region for your deployment instance.
admin_password = "<create_10_character_password>"

The terraform.tfvars document contains variables that you might [want to keep secret](https://docs.github.com/en/get-started/getting-started-with-git/ignoring-files).





 Step 4: Create your infrastructure 

Using the following command, run the Terraform script:

terraform init 
terraform apply --auto-approve
terraform output -json > ../import-covid-data/output.json

The Terraform folder contains a number of simple scripts:



* main.tf tells Terraform to use IBM Cloud.
* variables.tf contains the variable definitions whose values are populated from the terraform.tfvars file.
* mongo.tf creates a Databases for MongoDB EE instance with the Analytics Add-On with the following options:



* 6 CPU cores
* 14 GB RAM
Use the following steps to create a new SSH key. You can create only RSH SSH key types. To use an Ed25519 SSH key, that SSH key must be imported. For more information, see [Importing an SSH key by using the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-ssh-keysimporting-ssh-keys-ui).



1. In [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > SSH keys.
2. Click Create and enter the information that is in Table 1.



Table 1. Creating an SSH key for VPC selections

 Field Value 

 Location Locations are composed of regions (specific geographic areas) and zones (fault-tolerant data centers within a region). Select the location where you want to create your SSH key. 
 Name A name is required for your SSH key. 
 Resource group Select a resource group for the SSH key. 
 Tags You can assign a user tag to the SSH key so that you can easily filter a list of SSH keys. For more information, see [Working with tags](https://cloud.ibm.com/docs/account?topic=account-tag&interface=ui). 
 Access management tags Access management tags help you apply flexible access policies on specific resources. For more information, see the [Controlling access to resources by using tags](https://cloud.ibm.com/docs/account?topic=account-access-tags-tutorial) UI tutorial. 
 SSH key type The default value is rsa. 



3. Select Generate a key pair for me.
4. Click Save private key.
5. Click Save public key.
6.
[Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/icon_hamburger.svg) > Partner Center > Sell > Get started.
2. Enter the name of your company as you want it to be displayed in the catalog, and click Save. For the purpose of this tutorial, enter Example Corp as the company name.







 Step 2: Create your test environment 

You, or a member of your team, uses the test environment to onboard the virtual server image and validate that it can be deployed to your VPC. Your test environment includes a private catalog in which you import the virtual server image from an external repository.



1. Click Create in the Create your test environment section.
2. Enter Example Corp Catalog as the name of the private catalog, and click Create.







 Step 3: Set up access for your team 

You can enlist team members to help with the onboarding process by assigning them specific levels of IBM Cloud Identity and Access Management (IAM) access. To streamline the process of assigning access, complete the following steps to create your access group:



1. Click Assign in the Assign access section.
2. Enter Example Corp Virtual Server Image as the name of the access group, and click Assign. The following roles are assigned to the access group by default:



* Administrator on the Catalog Management service
* Editor on the Partner Center - Sell service
* Editor on the User Management service
* Editor on the IAM Access Groups service
* Viewer on all account management services



For more information about the actions associated with each role, see [Actions and roles for account management services](https://cloud.ibm.com/docs/account?topic=account-account-servicesaccount-management-actions-roles).







 Step 4: Invite team members to your account 

After you create the Example Corp Virtual Server Image access group, you're ready to invite team members to your account and add them to your access group. Team members are granted the following editor permissions by default:
For more information, see [Assigning user access for working with support center](https://cloud.ibm.com/docs/get-support?topic=get-support-access&interface=ui).



 Asking a question 

The Stack Overflow forum provides a wide variety of searchable answers for your IBM Cloud questions. If you don't find an existing answer, ask a new question. Go to [Stack Overflow](https://stackoverflow.com/questions/tagged/ibm-cloud) to ask technical questions about developing apps with the IBM Cloud platform and services.

IBM Cloud development and support teams actively monitor Stack Overflow and follow the questions that are tagged with ibm-cloud. When you create a question, add the ibm-cloud tag to your question to ensure that it's seen by the IBM Cloud development and support teams.







 Getting support for IBM Cloud Dedicated or Bluemix Local 

If your account is either IBM Cloud Dedicated or Bluemix Local, support is provided by the IBM Cloud support team.



* Open a new case by using the [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter) page and click Create a case. Mention that your account is either IBM Cloud Dedicated or Bluemix Local in the Subject and Description of the support case.
* If you don't have an IBMid, contact someone in your organization that does, or work with your IBM representative.







 Requesting support for resources in the European Union 

European Union (EU) support is available to customers who choose to enable the EU supported setting. EU Support is provided 24 hours a day and 7 days a week by engineers that are located in Europe. Global teams provide support at the discretion of the EU support team. Global teams might be contacted, for example, when issues are not resolved by the Advanced Customer Support (ACS) team in the EU, and more expertise is needed.

You can specify that you want EU support for your account if the following criteria are true:



* The EU Supported setting is enabled for your account by the master user or account owner.
If you do not specify a region with the -r flag, you must also select a region.

ibmcloud login

If your credentials are rejected, you might be using a federated ID. To log in with a federated ID, use the --sso flag. See [Logging in with a federated ID](https://cloud.ibm.com/docs/account?topic=account-federated_id) for more details.

If it's the first time you're using the IBM Cloud CLI, check out the [getting started tutorial](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).
2. Create an access policy and assign it to a user or a service ID by using the command [ibmcloud iam user-policy-create](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_iamibmcloud_iam_user_policy_create).
3. Assign access to All Account Management services with the Operator role:

ibmcloud iam service-policy-create name@example.com --roles Administrator --account-management --api-version v2
4. Use the following example of a temporary time-based access policy in JSON schema to create your own conditions:

{
"type": "access",
"description": "time-based conditions policy example restricting access to the full day of 2022-12-23 UTC",
"control": {
"grant": {
"roles": [
{
"role_id": "crn:v1:bluemix:public:iam::::role:Operator"
}
]
}
},
"resource": {
"attributes": [
{
"operator": "stringEquals",
"value": "d4b763ad0cbd4dca8dd1edb427d7a77e",
"key": "accountId"
},
Access the newly created service instance from the [Resource List](https://cloud.ibm.com/resources) under the Integration section.



2. Go to Topics and click Create topic.



1. Set the Topic Name to webserver and click Next.
2. Select 1 partition and click Next.
3. Set message retention to 1 Day and click the Create topic button.



3. Under Service credentials, click on New credential.



1. Provide a name for the credential - es-for-log-analysis.
2. select Writer as the role and click Add.



4. Make note of the values or remember where they can be located. They will be used in the kcat.config file in the next section.







 Encrypt your data and secure your keys 

Key Protect helps you provision encrypted keys for apps across IBM Cloud services.

In this tutorial, Key Protect service will be used to encrypt the storage bucket, stored Data Engine jobs and securely store the service ID for stream landing.



1. Create an instance of [Key Protect](https://cloud.ibm.com/catalog/services/kms).



1. Select a location.
2. Set the name to log-analysis-kp.
3. Select the same resource group as earlier.
4. Click Create.



2. Under Keys, click the Add button to create a new root key.



1. Set the key type to Root key.
2. Set the name to log-analysis-root-enckey.
3. Then Add key.









 Setup storage to persist the messages from Event Streams 



1. Create an instance of [Object Storage](https://cloud.ibm.com/catalog/services/cloud-object-storage).



1. Select the Standard plan.
2. Set Service name to log-analysis-cos.
3. Select the same Resource group as the above service and click Create.



2.