vania-janet/multiturn-rag-retrieval-data huggingface dataset:
From the IBM Cloud console, click Manage > Access (IAM).
2. Click Authorizations.



You can also access your authorizations on the [Manage authorizations](https://cloud.ibm.com/iam/authorizations) page.

You can also create the authorization manually, if required. To successfully resolve App Configuration references, your toolchain instance must have both Viewer and Reader access to the correct App Configuration service instance.





 Configuring App Configuration by using the API 

The App Configuration tool integration supports the following configuration parameters that you can use with the [Toolchain HTTP API and SDKs](https://cloud.ibm.com/apidocs/toolchain) when you [create](https://cloud.ibm.com/apidocs/toolchaincreate-tool), [read](https://cloud.ibm.com/apidocs/toolchainget-tool-by-id), and [update](https://cloud.ibm.com/apidocs/toolchainupdate-tool) tool integrations.

You must specify the tool_type_id property in the request body with the appconfig value.



Table 1. App Configuration tool integration parameters

 Parameter Usage Type Terraform argument Description 

 collection-name required, updatable String collection_id The ID of the App Configuration collection. 
 environment-name required, updatable String environment_id The ID of the App Configuration environment. 
 instance-name required, updatable String instance_id The guid of the App Configuration service instance. 
 name required, updatable String name The name of this tool integration. App Configuration references include this name to identify the App Configuration instance where the configuration values reside. Make sure that each of the App Configuration tools that are integrated into a toolchain have a unique name for resolution to function properly. 
 region required, updatable String location The IBM Cloud location where the App Configuration service instance is located. 
 resource-group required, updatable String resource_group_name The name of the resource group where the App Configuration service instance is located. 







 Learn more about App Configuration
[Actions icon](https://cloud.ibm.com/docs-content/v1/content/icons/action-menu-icon.svg)> Configure.
6. When you are finished updating the settings, click Save Integration.







 Updating a tool integration with the API 

If you configured a tool integration when you created a toolchain, you can update the configuration settings with the API.



1. [Obtain an IAM bearer token](https://cloud.ibm.com/apidocs/toolchainauthentication). Alternatively, if you are using an SDK, [obtain an IAM API key](https://cloud.ibm.com/iam/apikeys) and set the client options by using environment variables.

export CD_TOOLCHAIN_AUTH_TYPE=iam && export CD_TOOLCHAIN_APIKEY={iam_api_key} && export CD_TOOLCHAIN_URL={base_url}
2. [Look up the ID of the toolchain](https://cloud.ibm.com/apidocs/toolchainlist-toolchains) where the tool integration exists.
3. Using the ID of the toolchain, [look up the ID of the tool integration](https://cloud.ibm.com/apidocs/toolchainlist-tools).
4. Update the tool integration within the targeted toolchain.



* Curl
* Java
* Node
* Python
* Go



curl -X PATCH --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" --header "Content-Type: application/merge-patch+json" --data '{ "name": "{new_tool_name}", "parameters": {new_tool_parameters} }' "{base_url}/toolchains/{toolchain_id}/tools/{tool_id}"

import com.ibm.cloud.continuous_delivery.cd_toolchain.v2.CdToolchain;
For more information about accessing the Schema Registry using an SDK, see [Event Streams Schema Registry REST API](https://github.com/IBM/eventstreams-go-sdk/blob/main/schema_operations.md).

For information about Event Streams resources and data sources on Terraform, see [resources and data sources](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-resources-datasource-listibm-event-streams_rd).





 Using the Schema Registry with the third-party SerDes 

Schema Registry supports the use of the following third-party SerDes:



* Confluent SerDes



To configure the Confluent SerDes to use the Schema Registry, you need to specify two properties in the configuration of your Kafka client:



 Property name Value 

 SCHEMA_REGISTRY_URL_CONFIG Set this to the URL of the Schema Registry, including your credentials as basic authentication, and with a path of /confluent. For example, if $APIKEY is the API key to use and $HOST is the host from the kafka_http_url field in the Service Credentials tab, the value has the form: 



https://token:{$APIKEY}@{$HOST}/{confluent}

BASIC_AUTH_CREDENTIALS_SOURCE | Set to URL. This instructs the SerDes to use HTTP basic authentication using the credentials supplied in the Schema Registry URL.

You can also optionally provide the following properties to control the schema selection (subject naming strategy):



 Property name Value 

 VALUE_SUBJECT_NAME_STRATEGY TopicNameStrategy(default), RecordNameStrategy, and TopicRecordNameStrategy are supported.
Configuring your account 

IBM Cloud® Security and Compliance Center Workload Protection provides a configuration page for administrators to fine-tune the way that the agent processes network data.



 Accessing the configuration page 

To access the configuration page, do the following:



1. Open the [Workload Protection UI](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-launch).
2. Click the Network icon ![Network icon](https://cloud.ibm.com/docs-content/v1/content/667adc0b8a7fdb0b349b1158d8e128640b5bc72b/workload-protection//images/network.png).
3. Click Configuration.







 Configuring workload labels 

IBM Cloud Security and Compliance Center Workload Protection automatically detects labels used for the Kubernetes objects in a cluster.

You might find there are many more labels than needed for network security purposes. You can use the Workload Labels to configure the default behavior for labels and whether to include or exclude specific labels for individual clusters. Excluded labels will not be displayed in the UI or included in network policies.

You can add multiple conditions selecting clusters, namespace labels, and workload labels as required.

Conditions you no longer need can be deleted with the exception of the Default condition. You must have a Default condition defined.





 Configuring actions for unresolved IPs 

If the agent cannot resolve an IP address to a structure (for example, Service, Deployment, Daemonset, and so on), the IP address will be flagged as "unresolved" in the [Ingress and Egress views](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-netsec_policyknp_coms). In addition to resolving these IP addresses in the Ingress and Egress views you can add unresolved IP addresses or CIDR blocks in the Unresolved IP Configuration section of the Configuration page.
Creating a Deploy to IBM Cloud button 

The Deploy to IBM Cloud button is an efficient way to share your public Git-sourced app so that other people can experiment with the code and deploy it to IBM Cloud by using a toolchain. The button requires minimal configuration and you can insert it anywhere that supports markup. Anyone who clicks the button creates a cloned copy of the code in a new Git repository (repo) so that your original app remains unaffected.

When someone clicks your button, these actions occur:



1. If the person does not have an active IBM Cloud account, they must create an account. They can create a trial account or a real account.
2. The person can select a region, resource group, and app name by clicking the Delivery Pipeline icon. The suggested app name is the same as the toolchain name, which is constructed from the name of your original Git repo and the time. The toolchain name can also be edited.
3. A toolchain is created that includes a new private clone of your Git repo, a pipeline for building and deploying code changes, and an issue tracker.

If the .bluemix directory contains a toolchain.yml file, the file is used to specify the tool integrations for the toolchain. For more information about the toolchain.yml file, see [Creating custom toolchain templates](https://github.com/open-toolchain/sdk/wiki/Creating-Custom-Toolchain-Templates).
4. If the app requires a build file, the build file is detected automatically and the app is built.
5. If a pipeline is configured for the build and deployment process, a pipeline.yml file is used to deploy the app.
6. If the app requires a container, a pipeline.yml file that defines the IBM Cloud Kubernetes Service and a Dockerfile that defines an image are used to deploy the app in the IBM Cloud Kubernetes Service.
7. The app is deployed to the IBM Cloud organization that the person selected.





 Examples of the button
For more information, see the [API and SDK documentation](https://cloud.ibm.com/apidocs/cloudantgetcorsinformation) about the configuration endpoints for CORS.





 Dashboard 

CORS support is available in the IBM Cloudant Dashboard.

You can update your CORS settings by using the CORS tab within the dashboard. See the following screenshot:

Zoom

![CORS dashboard lets you connect to remote servers directly from the brower. Using CORS, you can host browser-based apps on static pages, and load data directly from IBM Cloudant.](https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant/images/corsdashboard.png)

Figure 1. CORS dashboard

To see the current CORS configuration, open Account > CORS in the dashboard.

You can enable or disable CORS by using Enable CORS. This setting corresponds to the [enable_cors option](https://cloud.ibm.com/apidocs/cloudantputcorsconfiguration). when you change the CORS configuration from within an application.

To specify that CORS is enabled for all domains, select the All domains () option.

To specify that CORS is enabled only for exact origin domains, list each of the domains or subdomains by using the Restrict to specific domains option. For each domain, provide a full URL, preferably by using the https prefix for better security.
[Architecture](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution68-trusted-profile-for-enterprise-security/TrustedProfile_with_CR_architecture.svg)

Solution architecture



* The container image for the application is pulled from the Container Registry and deployed to the Kubernetes cluster into a namespace.
* The user connects to the application.
* The application reads a special access token from the Kubernetes environment and turns it into an IAM access token for a trusted profile.
* IAM logs events to Activity Tracker.







 Before you begin 

This tutorial does not require any installation and is only using the [IBM Cloud console](https://cloud.ibm.com/).

An instance of [Activity Tracker](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-getting-startedgs_objectives) in the Frankfurt region is required to see global IAM events produced when utilizing trusted profiles. An instance with streaming logs is sufficient, but persisted logs are recommended.





 Overview: Trusted profiles 

Similar to users and service IDs, [trusted profiles](https://cloud.ibm.com/docs/account?topic=account-identity-overviewtrustedprofiles-bestpract) are identities that can be granted access in IAM policies. Trusted profiles differ in that they cannot create and own API keys. They are an identity within a specific account which serves as "gateway" for someone or something else to work within that account without the need for an API key. They can assume the identity of that trusted profile.

You configure that someone or something else (see below) as part of the trusted profile setup. All the usual options are available, the IBM Cloud API, CLI, any of the available SDKs, Terraform or the IBM Cloud console.

In the console, as part of the IAM category, [trusted profiles](https://cloud.ibm.com/iam/trusted-profiles) have their own section.
Deploying your infrastructure 

This topic contains information on how to deploy and set up SAP HANA and SAP NetWeaver on VMware that runs on IBM Cloud. You will find references to previous topics, including setting up your network, security, storage, and operating system (OS).

There are variations of VMware available from IBM Cloud that support SAP. You need to decide whether you want to build your own VMware SDDC or use an automated build and configuration according to VMware best practices. For more information on these two choices, see:



* [IBM Cloud Intel Bare Metal and VMware vSphere (ESXi OS)](https://cloud.ibm.com/docs/vmware?topic=vmware-about-vmware) for the manual VMware setup and configuration
* [IBM Cloud for VMware Solutions Dedicated](https://cloud.ibm.com/docs/vmwaresolutions) for fully automated VMware SDDC setup and configuration, which includes optional BYOL, configuration of different VMware components (such as VMware NSX, VMware vRealize) and access to advanced VMware capabilities (such as VMware HCX)



* vCenter Server (VCS) solution type, where the entire VMware SDDC setup is automated and creates a hosted vSphere stack as a service
* VMware vSphere (VSS) solution type, where selectable VMware SDDC components setup is automated and creates a customizable VMware with maximum flexibility. This solution type is the intermediary between manual with Bare Metal and fully auotmated from IBM Cloud for VMware Solutions.





Due to these variations, provisioning of a server, adding network storage, and configuring network connectivity and interfaces differ for each. The process to order a VMware setup for manual configuration is similar to [Provisioning your Bare Metal server](https://cloud.ibm.com/docs/sap?topic=sap-bm-set-up-infrastructurebm-provision-server). Therefore, the sections to follow will not cover this option.
Configuring Activity Tracker in the account by using Terraform 

Terraform on IBM Cloud® enables predictable and consistent provisioning of IBM Cloud services so that you can rapidly build complex, multitier cloud environments that follow Infrastructure as Code (IaC) principles. Similar to using the IBM Cloud CLI or API and SDKs, you can automate the creation, update, and deletion of your Activity Tracker Event Routing resources by using HashiCorp Configuration Language (HCL).

Looking for a managed Terraform on IBM Cloud solution? Try out [IBM Cloud® Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-getting-started). With Schematics, you can use the Terraform scripting language that you are familiar with, but you don't need to worry about setting up and maintaining the Terraform command line and the IBM Cloud Provider plug-in. Schematics also provides pre-defined Terraform templates that you can install from the IBM Cloud catalog.

Before you begin, ensure that you have the [required access](https://cloud.ibm.com/docs/atracker?topic=atracker-iam) to create and work with Activity Tracker Event Routing resources. You also need permissions to manage the target resources.



 Step 1. Install the Terraform CLI 

Complete the following steps to install the Terraform CLI:



1. Create a terraform folder on your local machine, and navigate to your terraform folder.

mkdir terraform && cd terraform
2. Download the Terraform version that you want. For example, you can download terraform_0.15.5_darwin_amd64.zip for a MacOS.

The IBM Cloud Provider plug-in for Terraform currently supports Terraform version 0.12.x, 0.13.x, and 0.14.x only. Make sure to select a supported Terraform version.
3. Extract the Terraform zip file and copy the files to your terraform directory.
4. Set the environment PATH variable to your Terraform files.

export PATH=$PATH:<terraform-directory>/terraform
import com.ibm.cloud.sdk.core.http.Response;
import com.ibm.cloud.sdk.core.security.;
import java.util.HashMap;

private static IbmAnalyticsEngineApi ibmAnalyticsEngineApiService;

private static String IAM_API_KEY = "{apikey}";
private static String IAE_ENDPOINT_URL = "{url}";
private static String API_AUTH_URL = "{api auth url}";

public static void main(String[] args)
{
HashMap<String, String> config = new HashMap<String, String>();
config.put("APIKEY",IAM_API_KEY );
config.put("AUTH_URL", API_AUTH_URL);

try {
// Create an IAM authenticator.
Authenticator authenticator = IamAuthenticator.fromConfiguration(config);
// Construct the service client.
ibmAnalyticsEngineApiService = new IbmAnalyticsEngineApi(IbmAnalyticsEngineApi.DEFAULT_SERVICE_NAME, authenticator);
// Set our service URL.
ibmAnalyticsEngineApiService.setServiceUrl(IAE_ENDPOINT_URL);

} catch (Exception e) {
System.out.println("Exception");
}
}
Show more
* Retrieve the details of a single instance.:

ServiceCall<Instance> getInstance(GetInstanceOptions getInstanceOptions)

Example request:

// Construct an instance of the GetInstanceOptions model
GetInstanceOptions getInstanceOptionsModel = new GetInstanceOptions.Builder()
.instanceId("dc0e9889-eab2-4t9e-9441-566209499546")
.build();
Configuration reference 

You can create your own Discovery ingestion configuration in JSON if your data has special [conversion](https://cloud.ibm.com/docs/discovery?topic=discovery-configrefconversion), [enrichment](https://cloud.ibm.com/docs/discovery?topic=discovery-configrefenrichment), or [normalization](https://cloud.ibm.com/docs/discovery?topic=discovery-configrefnormalization) needs.

The following sections detail the structure of this JSON and the object that can be defined in it. Also see the Configurations section of the [API reference](https://cloud.ibm.com/apidocs/discoveryadd-configuration).

If you configure your collection using [Smart Document Understanding](https://cloud.ibm.com/docs/discovery?topic=discovery-sdu), the PDF and Word conversion settings listed are not used, so changing these conversion settings are ignored.



 Configuration structure 

A Discovery configuration is structured as follows:

{
"name": "Configuration Name",
"description": "Descriptive text about the configuration",
"conversions": {
"word": {},
"pdf": {},
"html": {},
"segment": {},
"json_normalizations": []
},
"enrichments": [],
"normalizations": []
}

The base JSON object contains the following items:



* "name": "Configuration Name" - The name of your configuration
* "description": "Descriptive text about the configuration" - A description of your configuration



The following objects and arrays must be defined to convert, enrich and normalize documents that are uploaded to your collection.



* "conversions": {} - How documents are transformed into JSON that can be enriched.
* "enrichments": [] - Which enrichments are applied to which parts of the JSON.
* "normalizations": [] - Any post enrichment adjustments that are required before the document is stored.
HashMap<String, String> config = new HashMap<String, String>();
config.put("APIKEY",IAM_API_KEY );
config.put("AUTH_URL", API_AUTH_URL);

try {
// Create an IAM authenticator.
Authenticator authenticator = IamAuthenticator.fromConfiguration(config);
// Construct the service client.
ibmAnalyticsEngineApiService = new IbmAnalyticsEngineApi(IbmAnalyticsEngineApi.DEFAULT_SERVICE_NAME, authenticator);
// Set our service URL.
ibmAnalyticsEngineApiService.setServiceUrl(IAE_ENDPOINT_URL);

} catch (Exception e) {
System.out.println("Exception");
}
}
Show more









 Code Samples 

In addition to the sample code snippets in this section, you can work with Java code samples from the [IBM Analytics Engine V3 API reference](https://cloud.ibm.com/apidocs/ibm-analytics-engine-v3?code=javaintroduction).

The following code samples show you how to:



* Access the IBM Analytics Engine service instance:

import com.ibm.cloud.iaesdk.ibm_analytics_engine_api.v3.IbmAnalyticsEngineApi;
import com.ibm.cloud.iaesdk.ibm_analytics_engine_api.v3.model.;
import com.ibm.cloud.sdk.core.http.Response;
import com.ibm.cloud.sdk.core.security.;
import java.util.HashMap;

private static IbmAnalyticsEngineApi ibmAnalyticsEngineApiService;

private static String IAM_API_KEY = "{apikey}";
private static String IAE_ENDPOINT_URL = "{url}";
Download the libertySample-1.0.0.war file from [GitHub](https://github.com/ibm-cloud-security/appid-sample-code-snippets/tree/master/liberty-for-java) and place it in your server's apps folder. For example, if your server is named defaultServer, the war file would go here target/liberty/wlp/usr/servers/defaultServer/apps/.
4. Configure SSL by adding the following to your server.xml file. You also need to create a truststore.

<keyStore id="defaultKeyStore" password="myPassword"/>
<keyStore id="appidtruststore" password="Liberty" location="${server.config.dir}/mytruststore.jks"/>
<ssl id="defaultSSLConfig" keyStoreRef="defaultKeyStore" trustStoreRef="appidtruststore"/>



By default SSL configuration requires the truststore be configured for OpenID Connect. Learn more about [configuring an OpenID Connect Client in Liberty](https://www.ibm.com/docs/en/was-liberty/base?topic=connect-configuring-openid-client-in-liberty).







 Configuring Spring Boot for Java SDK 

You can configure App ID to work with your Spring Boot applications.



 Before you begin 

You must have the following prerequisites:



* An instance of the App ID service
* A set of service credentials
* A Java + Maven project
* Apache Maven 3.5 or higher
* Java 1.8
* Spring Boot 2.0 and Security OAuth 2.0 or higher







 Initializing the Spring Boot framework 



1. Add the following code between the <project> </project> tags in your Maven pom.xml file.

<parent>
<groupId>org.springframework.boot</groupId>
DaysAfterInitiation Non-negative integer None AbortIncompleteMultipartUpload Must be a value greater than 0. 



The body of the request must contain an XML block with the schema that is addressed in the table (see Example 1).

<LifecycleConfiguration>
<Rule>
<ID>delete-after-3-days</ID>
<Filter />
<Status>Enabled</Status>
<AbortIncompleteMultipartUpload>
<DaysAfterInitiation>3</DaysAfterInitiation>
</AbortIncompleteMultipartUpload>
</Rule>
</LifecycleConfiguration>

Syntax

PUT https://{endpoint}/{bucket}?lifecycle path style
PUT https://{bucket}.{endpoint}?lifecycle virtual host style

Example request

PUT /images?lifecycle HTTP/1.1
Host: s3.us.cloud-object-storage.appdomain.cloud
Date: Wed, 7 Feb 2018 17:50:00 GMT
Authorization: authorization string
Content-Type: text/plain
Content-MD5: M625BaNwd/OytcM7O5gIaQ==
Content-Length: 305

<LifecycleConfiguration>
<Rule>
<ID>delete-after-3-days</ID>
<Filter />
<Status>Enabled</Status>
<AbortIncompleteMultipartUpload>
<DaysAfterInitiation>3</DaysAfterInitiation>
</AbortIncompleteMultipartUpload>
</Rule>
</LifecycleConfiguration>
Show more

Code sample for use with NodeJS COS SDK

Using the IBM Cloud® Object Storage SDKs only requires calling the appropriate functions with the correct parameters and proper configuration.

var aws = require('ibm-cos-sdk');
import com.ibm.cloud.objectstorage.services.s3.AmazonS3ClientBuilder;
import com.ibm.cloud.objectstorage.services.s3.model.Bucket;
import com.ibm.cloud.objectstorage.services.s3.model.BucketLifecycleConfiguration;
import com.ibm.cloud.objectstorage.services.s3.model.ListObjectsRequest;
import com.ibm.cloud.objectstorage.services.s3.model.ObjectListing;
import com.ibm.cloud.objectstorage.services.s3.model.S3ObjectSummary;
import com.ibm.cloud.objectstorage.oauth.BasicIBMOAuthCredentials;

public class App
{
private static AmazonS3 _cosClient;

/
* @param args
/
public static void main(String[] args)
{
SDKGlobalConfiguration.IAM_ENDPOINT = "https://iam.cloud.ibm.com/identity/token";
String bucketName = "<sample-bucket-name>";
String api_key = "ZRZDoNoUseOLL7bRO8SAMPLEHPUzUL_-fsampleyYE";
String service_instance_id = "85SAMPLE-eDOb-4NOT-bUSE-86nnnb31eaxx"
String endpoint_url = "https://s3.us-south.cloud-object-storage.appdomain.cloud";

String storageClass = "us-south";
String location = "us";

_cosClient = createClient(api_key, service_instance_id, endpoint_url, location);

// Delete the configuration.
_cosClient.deleteBucketLifecycleConfiguration(bucketName);

// Verify that the configuration has been deleted by attempting to retrieve it.
config = _cosClient.getBucketLifecycleConfiguration(bucketName);