vania-janet/multiturn-rag-retrieval-data huggingface dataset:
This table has row and column headers. The row headers provide the service role name and the column headers identify the specific information available about each role.

 Role Description 

 Manager As a manager, you have permissions beyond the writer role to complete privileged actions as defined by the service. In addition, you can create and edit service-specific resources. 
 Reader As a reader, you can perform read-only actions within a service such as viewing service-specific resources. 
 Writer As a writer, you have permissions beyond the reader role, including creating and editing service-specific resources. 







 Globalization Pipeline 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use g11n-pipeline for the service name.

Platform roles

Service roles

Actions



Table 60. Platform roles - Globalization Pipeline
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users. 
 Editor As an editor, you can perform all platform actions except for managing the account and assigning access policies. 
 Operator As an operator, you can perform platform actions required to configure and operate service instances, such as viewing a service's dashboard. 







 GhoST API 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use ghost-api for the service name.

No supported roles.





 GhoST Tagging Service 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use ghost-tags for the service name.

Platform roles

Actions



Table 62. Platform roles - GhoST Tagging Service
Use the tab buttons to change the context of the table. This table has row and column headers.
The row headers provide the service role name and the column headers identify the specific information available about each role.

 Role Description 

 Manager As a manager, you have permissions beyond the writer role to complete privileged actions as defined by the service. In addition, you can create and edit service-specific resources. 
 Reader As a reader, you can perform read-only actions within a service such as viewing service-specific resources. 







 HDM Workload Migrator 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use primaryio-hdm-workload-migrator for the service name.

Platform roles

Actions



Table 130. Platform roles - HDM Workload Migrator
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users. 
 Editor As an editor, you can perform all platform actions except for managing the account and assigning access policies. 
 Operator As an operator, you can perform platform actions required to configure and operate service instances, such as viewing a service's dashboard. 
 Viewer As a viewer, you can view service instances, but you can't modify them. 







 Privileged Access Gateway 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use privileged-access-gateway for the service name.

Platform roles

Service roles

Actions



Table 131. Platform roles - Privileged Access Gateway
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users.
[Managing and exposing apps in the service mesh](https://cloud.ibm.com/docs/containers?topic=containers-istio-meshistio-mesh)



* [Understanding the BookInfo sample app](https://cloud.ibm.com/docs/containers?topic=containers-istio-meshistio_bookinfo)
* [Setting up the BookInfo sample app](https://cloud.ibm.com/docs/containers?topic=containers-istio-meshbookinfo_setup)
* [Publicly accessing BookInfo](https://cloud.ibm.com/docs/containers?topic=containers-istio-meshistio_access_bookinfo)



* [Creating a gateway URL in Classic clusters](https://cloud.ibm.com/docs/containers?topic=containers-istio-meshistio_create_gatewayURL_classic)
* [Creating a gateway URL in VPC clusters](https://cloud.ibm.com/docs/containers?topic=containers-istio-meshcreate-gateway-vpc)
* [Viewing the BookInfo web page in a browser](https://cloud.ibm.com/docs/containers?topic=containers-istio-meshviewing-bookinfo)
* [Exposing BookInfo by using an IBM-provided subdomain without TLS](https://cloud.ibm.com/docs/containers?topic=containers-istio-meshistio_expose_bookinfo)
* [Exposing BookInfo by using an IBM-provided subdomain with TLS](https://cloud.ibm.com/docs/containers?topic=containers-istio-meshistio_expose_bookinfo_tls)
* [Configuring the bookinfo-gateway to use TLS termination](https://cloud.ibm.com/docs/containers?topic=containers-istio-meshbookinfo-tls)
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the service role name and the column headers identify the specific information available about each role.

 Role Description 

 KeyPurge Role for purging key. 
 Manager As a manager, you have permissions beyond the writer role to complete privileged actions as defined by the service. In addition, you can create and edit service-specific resources. 
 Reader As a reader, you can perform read-only actions within a service such as viewing service-specific resources. 
 ReaderPlus As a reader plus, you can perform read-only actions within Key Protect such as viewing service-specific resources. You can also access key material for standard keys. 
 Writer As a writer, you have permissions beyond the reader role, including creating and editing service-specific resources. 







 Knowledge Studio 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use knowledge-studio for the service name.

Platform roles

Service roles

Actions



Table 106. Platform roles - Knowledge Studio
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users. 
 Editor As an editor, you can perform all platform actions except for managing the account and assigning access policies. 
 Viewer As a viewer, you can view service instances, but you can't modify them. 







 IBM Lakehouse 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use lakehouse for the service name.

Platform roles

Service roles

Actions



Table 107. Platform roles - IBM Lakehouse
Use the tab buttons to change the context of the table. This table has row and column headers.
Click Save to save the settings. If the Detection path is unreachable, the optimal route for dynamic content acceleration is impacted.







 Understanding DCA concepts 



 Detection path 

Detection path is used by Akamai Edge servers to find the best optimized route from Edge servers to origin. The best path to origin must be known at the time a user’s request arrives at an Edge server because any inline analysis or detection would defeat the purpose of speeding up things.

To accomplish this, you are asked to place a test object on your origin. Edge servers periodically fetch the test object from the origin using each of the candidate paths, including the direct path (the default path through the internet from Edge to Origin).

The fetches of the test object are called the races. When a real request comes in, the Edge consults the most recent race data to send that request over the fastest path to the origin. You can download the provided [test object](https://public.dhe.ibm.com/cloud/bluemix/network/cdn/route-detection-test-object.html) and upload it to the origin server, or you can use your own test object.

A valid test object must:



* Get HTTP 200 response without authentication
* Not contact a database or do any back-end processing
* Be a static text file of content-type text/HTML
* Be approximately the size of an average page, but no less than 8 KB



Detection path is designed to work only for HTTPS domain mapping (SAN HTTPS or Wildcard HTTPS).





 Prefetching 

Prefetching is to inspect HTML responses and prefetch embedded objects in the HTML files. Prefetch works on any page that includes <img>, <script>, or <link> tags that specify relative paths. It also works when the resource hostname matches the request domain in the HTML file, and it is part of a fully qualified URI.
Detection path is designed to work only for HTTPS domain mapping (SAN HTTPS or Wildcard HTTPS).





 Prefetching 

Prefetching is to inspect HTML responses and prefetch embedded objects in the HTML files. Prefetch works on any page that includes <img>, <script>, or <link> tags that specify relative paths. It also works when the resource hostname matches the request domain in the HTML file, and it is part of a fully qualified URI. When it is set to On, Edge servers prefetch objects with the following file extensions: aif, aiff, au, avi, bin, bmp, cab, carb, cct, cdf, class, css, doc, dcr, dtd, exe, flv, gcf, gff, gif, grv, hdml, hqx, ico, ini, jpeg, jpg, js, mov, mp3, nc, pct, pdf, png, ppc, pws, swa, swf, txt, vbs, w32, wav, wbmp, wml, wmlc, wmls, wmlsc, xsd, and zip.





 Image compression 

Serving compressed images reduces the amount of content that is required to load a page. This helps offset less robust connections, such as those formed with mobile devices. If your site visitors have slow network speeds, Image Compressing technology can automatically increase compression of JPEG images to speed up loading. However, Image Compressing results in lossy compression or irreversible compression, and might affect the quality of the images on your site.

Image Compression supported file extensions: .jpg, .jpeg, .jpe, .jif, .jfif, and .jfi.

In order for the feature Image Compression to work for DCA, you must make sure that the path of the image files is cacheable. See [Caching](https://cloud.ibm.com/docs/CDN?topic=CDN-dynamic-content-accelerationcaching-cache-content) to set the images cacheable.







 Caching
curl -X POST -u "apikey:{apikey}" --header "Content-Type: application/json" --header "Accept: audio/wav" --data "{"text":"<ibm:prompt id='goodbye'/>"}" "{url}/v1/synthesize?customization_id=82f4809a-bf63-89a6-52ca-22731fe467ba&voice=en-US_AllisonV3Voice"

IBM Cloud Pak for Data

curl -X POST --header "Authorization: Bearer {token}" --header "Content-Type: application/json" --header "Accept: audio/wav" --data "{"text":"<ibm:prompt id='goodbye'/>"}" "{url}/v1/synthesize?customization_id=82f4809a-bf63-89a6-52ca-22731fe467ba&voice=en-US_AllisonV3Voice"

For more information about using prompts with speech synthesis, see [Using a custom prompt for speech synthesis](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-tbe-use).



 Resolving evaluation problems for custom prompts 

A custom prompt can suffer from different types of problems for different reasons. In some cases, you might need to rerecord and resubmit a prompt as many as a handful of times to address the following possible issues:



* The service might fail to detect a mismatch between the prompt’s text and audio. This problem is more likely to occur with longer prompts. Multiple shorter prompts are preferable to a single long prompt.
* The text of a prompt might include a word that the service does not recognize. In this case, you can add a custom word/translation pair to the prompt's custom model to tell the service how to pronounce the word.
The srConnectionChanged() hook improves the ability of the cluster to detect a status change of HANA System Replication that requires an action from the cluster. The goal is to prevent data loss and corruption by preventing accidental takeovers.



 Activating the srConnectionChanged() hook on all SAP HANA instances 



1. Stop the cluster.

On NODE1, run the following command.

pcs cluster stop --all
2. Install the hook script that is provided by the resource-agents-sap-hana package in the /hana/shared/myHooks directory for each HANA instance, and set the required ownership.

On both nodes, run the following commands.

mkdir -p /hana/shared/myHooks

cp /usr/share/SAPHanaSR/srHook/SAPHanaSR.py /hana/shared/myHooks

chown -R ${sid}adm:sapsys /hana/shared/myHooks
3. Update the global.ini file on each HANA node to enable the hook script.

On both nodes, run the following command.

sudo -i -u ${sid}adm -- <<EOT
python $DIR_INSTANCE/exe/python_support/setParameter.py -set SYSTEM/global.ini/ha_dr_provider_SAPHanaSR/provider=SAPHanaSR -set SYSTEM/global.ini/ha_dr_provider_SAPHanaSR/path=/hana/shared/myHooks -set SYSTEM/global.ini/ha_dr_provider_SAPHanaSR/execution_order=1 -set SYSTEM/global.ini/trace/ha_dr_saphanasr=info
EOT
4. Verify the changed file.

On both nodes, run the following command.

cat /hana/shared/${SID}/global/hdb/custom/config/global.ini
5. Create sudo settings for SAP HANA OS user.

You need the following sudo settings to allow the ${sid}adm user script can update the node attributes when the srConnectionChanged() hook runs.
Setting up Bidirectional Forwarding Detection (BFD) 

Bidirectional Forwarding Detection (BFD) quickly detects faults in a network between two routers or switches connected by a link. It provides a single, standardized method for failover detection at any protocol layer over any media. BFD also provides a way for network administrators to detect forwarding-path failures at a uniform rate, rather than the variable rates of different routing protocol hello mechanisms. Network profiling and planning is easier, and reconvergence time is predictable, consistent, and significantly faster.

BFD support comes pre-enabled with your direct link. However, BFD doesn’t start working until you activate the feature during direct link creation, or on an existing direct link. No prerequisites are required. Simply configure this feature with the following values:



*  Interval – The interval is the minimum time (in milliseconds) expected to occur between when the local routing device sends BFD hello packets and the reply from its neighbor. This value can range from 300 to 255,000 milliseconds.
*  Multiplier – The multiplier is the number of times that a hello packet is missed before BFD declares the neighbor down. This value can range from 1 to 255. The default multiplier value is 3.



When using BFD, avoid using graceful restart on the Direct Link BGP session. Graceful restart helper is configured on the Direct Link router. If the customer side of the BGP session is configured with graceful restart, then the routes that the IBM router receives remain in the routing table for 300 seconds, even if BFD is triggered.



  Related link 

[Activating and deactivating Bidirectional Forwarding Detection (BFD)](https://cloud.ibm.com/docs/dl?topic=dl-activate-deactivate-bfd)
noeviction Does not evict keys and returns an error when the maxmemory limit is reached. 
 allkeys-lru Evicts less recently used (LRU) keys first. 
 volatile-lru Evicts less recently used (LRU) keys from the set of keys that expire first. 
 allkeys-random Evicts keys randomly. 
 volatile-random Evicts keys randomly from the set of keys that expire. 
 volatile-ttl Evicts keys that expire, and tries to evict keys with a shorter time to live (TTL) first. 



With an allkeys policy, the algorithm chooses which keys to evict from the set of all keys. With a volatile policy, the algorithm chooses to evict keys that have either [expired](https://redis.io/commands/expire) or have a [time-to-live (TTL)](https://redis.io/commands/ttl) set. In a volatile policy, if no keys match the policy, no keys are evicted.





 Other settings 



Table 2. Redis cache settings

 Policy Behavior Notes 

 appendonly Default value, yes. Enables Redis data to be written to disk. If you are caching data, you want to set this value to no. 
 stop-writes-on-bgsave-error Default value, yes. Redis stops accepting writes if it detects an unsuccessful backup snapshot. For caching, you can set to no. 
 maxmemory-samples Tunes the LRU algorithm, default value 5. [Approximated LRU algorithm](https://redis.io/topics/lru-cacheapproximated-lru-algorithm) 









 Setting an Example Cache 

To adjust the configuration of your deployment, send a JSON object with the settings that you want to change and their new values.

You are able to use CONFIG SET directly from a Redis cli-client, but changes made there are not permanent.
For example, barrio isn't detected if barrió is in the training set; and barrió isn't detected if barrio is in the training set.

You are expected to train the system with the proper characters and accents. For example, if you are expecting barrió as a response, put barrió into the training set.

Although not an accent mark, the same applies to words that use the Spanish letter ñ versus the letter n, such as "uña" versus "una". In this case, the letter ñ is not simply an n with an accent; it is a unique, Spanish-specific letter.





 Using multilingual downloads for translation 

You can enable the download of language data files, in CSV format, so you can translate training examples and assistant responses into other languages and use in other assistants.

Each CSV file includes translatable_string data that you can use with a machine or human translation service.

Each CSV file also includes id, resource_type, and locator data that Watson Assistant can use in another assistant to re-create your source assistant. You don't need to edit this information.

The overview of the multilingual process is:



* [Enable multilingual download](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-admin-language-supportadmin-language-support-multilingual-enable): In your source assistant, enable multilingual download
* [Translate content](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-admin-language-supportadmin-language-support-multilingual-translate): Use the CSV files with a translation service
* [Upload to language-specific assistants](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-admin-language-supportadmin-language-support-multilingual-upload): In a destination assistant for another language, use the CSV files to upload translated training and responses





 Enabling multilingual download 

To enable multilingual download:



1. Open Assistant settings.
2. In the Download/Upload section, click Enable multilingual download.
CM-8 (3) - Automated Unauthorized Component Detection 



  Control requirements 

The organization:

CM-8 (3) (a)
:   Employs automated mechanisms [IBM Assignment: Continuously, using automated mechanisms with a maximum five-minute delay in detection] to detect the presence of unauthorized hardware, software, and firmware components within the information system; and

CM-8 (3) (b)
:   Takes the following actions when unauthorized components are detected: [Selection (one or more): disables network access by such components; isolates the components; notifies [Assignment: organization-defined personnel or roles] ].





  NIST supplemental guidance 

This control enhancement is applied in addition to the monitoring for unauthorized remote connections and mobile devices. Monitoring for unauthorized system components may be accomplished on an ongoing basis or by the periodic scanning of systems for that purpose. Automated mechanisms can be implemented within information systems or in other separate devices. Isolation can be achieved, for example, by placing unauthorized information system components in separate domains or subnets or otherwise quarantining such components. This type of component isolation is commonly referred to as sandboxing.
Use this format to pass a raw PCM file. Linear PCM audio can also be carried inside of a container Waveform Audio File Format (WAV) file. When you use the audio/l16 format, the service accepts extra required and optional parameters on the format specification.



Table 3. Parameters for audio/l16 format

 Parameter Description 

 rate <br>Required An integer that specifies the sampling rate at which the audio is captured. For example, specify the following parameter for audio data that is captured at 16 kHz:<br><br>audio/l16;rate=16000 
 channels <br>Optional By default, the service treats the audio as if it has a single channel. If the audio has more than one channel, you must specify an integer that identifies the number of channels. For example, specify the following parameter for two-channel audio data that is captured at 16 kHz:<br><br>audio/l16;rate=16000;channels=2<br><br>The service accepts a maximum of 16 channels. It downmixes the audio to one channel during transcoding. 
 endianness <br>Optional By default, the service auto-detects the endianness of incoming audio. But its auto-detection can sometimes fail and drop the connection for short audio in audio/l16 format. Specifying the endianness disables auto-detection. Specify either big-endian or little-endian. For example, specify the following parameter for audio data that is captured at 16 kHz in little-endian format:<br><br>audio/l16;rate=16000;endianness=little-endian<br><br>Section 5.1 of [Request for Comment (RFC) 2045](https://tools.ietf.org/html/rfc2045section-5.1) specifies big-endian format for audio/l16 data, but many people use little-endian format.