vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Make sure that you know the character encoding of your corpus text files. The service preserves the encoding that it finds in the text files. You must use that same encoding when working with custom words in the custom model. For more information, see [Character encoding for custom words](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-manageWordscharEncoding).



 Using the sounds_like field 

The sounds_like field specifies how a word is pronounced by speakers in audio. By default, the service does not automatically attempt to generate a sounds-like pronunciation for a word for which you do not provide one. You can add sounds-likes for any words that do not have them. After adding or modifying words, you must validate the words resource to ensure that each word's definition is complete and valid. For more information, see [Validating a words resource for next-generation models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-corporaWords-ngvalidateModel-ng).

You can provide as many as five alternative pronunciations for a word that is difficult to pronounce or that can be pronounced in different ways. Some possible uses of the field follow:



* Provide different pronunciations for acronyms. For example, the acronym NCAA can be pronounced as it is spelled or colloquially as N C double A The following example adds both of these sounds-like pronunciations for the word NCAA:

IBM Cloud

curl -X PUT -u "apikey:{apikey}" --header "Content-Type: application/json" --data "{"sounds_like": ["N C A A", "N C double A"]}" "{url}/v1/customizations/{customization_id}/words/NCAA"

IBM Cloud Pak for Data
Solution:You need to either encode the special character or surround the URL with the single quotation marks. For example, becomes %21, or the command looks like: ./fabric-ca-client enroll -u 'https://admin:C25A062870@ash-zbc07c.4.secure.blockchain.ibm.com:21241' --tls.certfiles $HOME/fabric-ca-remote/cert.pem --caname PeerOrg1CA
<-- </section "id="section-ibp-v2-apis-config-enroll-error2" "> --><-- </section "id="section-ibp-v2-apis-config-troubleshooting" "> --><-- </section "id="section-ibp-v2-apis-config-fabric-ca-client" "> --><-- <section "id="section-ibp-v2-apis-msp" "> --> Creating an organization MSP definition You can use the APIs to create an organization MSP definition by calling POST /ak/api/v2/components/msp]POST _ak_api_v2_components_msp 1] ! . This MSP contains certificates that define your organization in a blockchain consortium, as well as the admin certificates that you can use to operate your network. If you followed the step above, you have already generated the certificates that are needed to create an organization MSP. Use the following steps to complete the request body of the API call.<-- <ol> -->1. Select an MSP ID for your organization. The MSP ID is the formal name of your organization within the consortium. The MSP ID used to create the organization MSP needs to be the same that you use to deploy your peers.2. Select a display name for your MSP.3. You need to provide the signCert, in base64 format, of your organization administrator that you registered and enrolled by using the Fabric CA client.
The value of the domain then would be pa-0803-ocp43-0defdaa0c51bd4a2dcb024eab4bf04a1-0000.us-south.containers.appdomain.cloud, after you remove console-openshift-console and /k8s/ns/pa0804/clusterserviceversions/ibm-blockchain.v2.5.4/ibp.comv1beta1IBPConsole/new.



You also need to make additional edits to the file depending on your choices in the deployment process. For example, if you created a new storage class for your network, provide the storage class that you created to the class: field.

If you are running OpenShift on Azure, you also need to change the storage class from default to azure-standard, unless you created your own storage class.

When you are satisfied with your edits to the specification, click Create.

The console can take a few minutes to deploy.

After you create the console, you can verify that the console deployment is succeeded. See [Step four: Verify the console installation](https://cloud.ibm.com/docs/blockchain?topic=blockchain-deploy-ocp-rhmconsole-deploy-ocp-verify-install) for instructions on verifying and accessing the console.



 Advanced deployment options 

Before you deploy the console, you can edit console specification to allocate more resources to your console or use zones for high availability in a multizone cluster. To take advantage of these deployment options, you can use the console resource definition with the resources: and clusterdata: sections added:

apiVersion: ibp.com/v1beta1
kind: IBPConsole
metadata:
name: ibpconsole
namespace: your-project
labels:
app.kubernetes.io/name: "ibp"
app.kubernetes.io/instance: "ibp"
app.kubernetes.io/managed-by: "ibm-ibp"
spec:
email: <EMAIL>
password: <PASSWORD>
Because an MSP is the representation of an organization in the network, you select the MSP definition when you deploy your nodes (identifying the organization the node belongs to), are joined to the consortium (by an ordering service admin), create a channel, join a channel, edit a channel, or perform any action where you have to specify the organization that is performing the action.





 Downloading a connection profile 

After you create an organization MSP definition and create peers with that organization MSP definition, you can download a connection profile that can be used by a client application to connect to your network via one or more gateway peers. The gateway peers are the peers that are specified in the connection profile, and they are used to perform service discovery to find all of the endorsing peers in the network that will endorse transactions.

Click the Organization MSP tile for the organization that your client application interacts with. Click Create connection profile to open a side panel where you can build and download your connection profile.

![Create connection profile panel](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/create-connx-profile.png)

If you plan to use the client application to register and enroll users with the organization CA, you need to include the Certificate Authority in the connection profile definition.

Select the peers to include in the connection profile definition. When a peer is not available to process requests from a client application, service discovery ensures that the request is automatically sent to a different peer. Therefore, to accommodate for peer downtime during a maintenance cycle for example, it is recommended that you select more than one peer for redundancy. In addition to peers created by using the console or APIs, imported peers that have been imported into the console are eligible to be selected as well.

The list of channels that the selected peers have joined is also provided for your information. If a channel is missing from the list, it is likely because the peer joined to it is currently unavailable.

You can then download the connection profile to your local file system and use it with your client application to generate certificates and invoke smart contracts.
Where HOSTNAME is the name of a host providing platform logs. For example, to return IBM Cloud database logs specify the following query:

host:ibm-cloud-databases-prod





 Query by log criticallity 

Each log has a level field that defines the level of threat the log issue might have.

Valid values in ascending order of severity are shown in the following table.



Table 2. Levels

 Value Description 

 N/A Log entries with no level specified. 
 INFO An informational log entry providing information about the routine operations of the service. 
 REQUEST A log entry indicating a request to the service. 
 METADATA A log entry indicating a change to the service metadata. 
 DEBUG A log entry used to provide additional troubleshooting information. 
 WARN A log entry providing information about an issue that might potentially indicate a problem. 
 ERROR A log entry indicating a problem with the operation of the service. 
 CRIT A log entry indicating a critial issue with the operation of the service. 



This is a list of possible values. The actual available values will vary depending on the service or host generating the logs.

You can enter the following query to search for these type of logs entries:

level:<VALUE>

For example, to query for ERROR log entries, you can run the following query:

level:ERROR





 Query by label 

You can also query by labels specified in the log entries.

To see the available labels, open a log entry in the IBM Log Analysis UI. Available labels will be listed in the LABELS section.

For example, to filter to all the log entries for the ibm-cloud-databases-prod host with the postgresql label, run the following query:

host:ibm-cloud-databases-prod AND label.database:postgresql







 Step 3. Create a custom view 

After you apply the search query to the Everything view or to an existing custom view, complete the following steps to save the outcome as a custom view:



1. In the web UI, click Unsaved View.
2. Select Save as new view. The Create new view page opens.
3. Enter a name for the view in the Name field.
[Learn more](https://cloud.ibm.com/docs/services/activity-tracker?topic=activity-tracker-iam_view_eventsiam_view_events).
* You must check that the auditing instance has the export feature enabled.







 Export API 

Use ENDPOINT/v1/export?QUERY_PARAMETERS" -u SERVICE_KEY: to export events.

ENDPOINT represents the entry point to the service. Each region has a different URL. To export events from an auditing instance, see [Endpoints](https://cloud.ibm.com/docs/services/activity-tracker?topic=activity-tracker-endpointsendpoints).

QUERY_PARAMETERS are parameters that define the filtering criteria that is applied to the export request.

SERVICE_KEY is an API key that you must use to validate your credentials with the auditing instance.

The : after SERVICE_KEY is required.





 Query parameters 

You can define query parameters to refine the events that you want to export.

The following table lists the query parameters that you can set:



Query parameters

 Query parameter Type Status Description 

 from int32 Required Start time. Set as UNIX timestamp in seconds or milliseconds. 
 to int32 Required End time. Set as UNIX timestamp in seconds or milliseconds. 
 size string Optional Number of event lines to include in the export. 
 hosts string Optional Comma-separated list of services.<br><br>To get the value that you can set for a specific service, you can check the label Source in an event that is generated by the service. 
 apps string Optional Comma-separated list of service instances represented as CRNs. <br>To get the value that you can set for a specific service, you can check the label App in an event that is generated by the service. 
 levels string Optional Comma-separated list of severities. <br>Use this field to set the severity of the events that you want to export. 
 query string Optional [Search query](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-viewsviews_step2).
: The repository definition file is updated to pull images from the IBM Cloud Registry. For more information, see [Deploying the Secure Build Server as a Hyper Protect Virtual Server](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-imagebuilddeploysecurebuild).





 16 June 2021 

Updated: The hpvs registration-create command.
: You can now add Linux capabilities by using the hpvs registration-create command. For more information, see [Using your own image](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-byoi).





 15 June 2021 

Added: Monitoring logs of Hyper Protect Virtual Servers instances.
: You can monitor many kinds of logs of the Hyper Protect Virtual Servers instances by using IBM Log Analysis with LogDNA on the Hyper Protect Virtual Servers instance. For more information, see [Monitoring logs](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-monitoring).





 21 May 2021 

Updated: Deploying the Secure Build Server as a Hyper Protect Virtual Server.
: The IBM Cloud command line interface can be used to create a registration definition file, and the gpg registration key. You can also manually add Linux capabilities to the registration definition file. The registration definition file for SBS is updated for security compliance. For more information, see [Deploying the Secure Build Server as a Hyper Protect Virtual Server](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-imagebuilddeploysecurebuild).





 26 February 2021 

Added: IBM Cloud® Hyper Protect Virtual Servers Secure Build Server feature.
: You can now use IBM Cloud® Hyper Protect Virtual Servers Secure Build Server to securely build an image, which you then can use to provision a virtual server. For more information, see [Deploying the Secure Build Server as a Hyper Protect Virtual Server](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-imagebuilddeploysecurebuild).
![toolkit-add-new-api.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/toolkit-add-new-api.png)
6. Click Create API to complete the wizard.
7. After your API is created, the Design tab is selected.
8. Scroll to the Host panel. Enter $(catalog.host) as the value if the field is not automatically completed.
9. Scroll to the Security tab and delete the "clientIDHeader (API Key)" that was auto-generated.
(We'll visit security with API Keys in the next tutorial.)
10. In the Paths panel, create a path by clicking +. a. Name the new path "/current".
b. In the same Paths panel, select the GET /current section.
c. In the GET /current section, add a Parameter. As you noticed while exploring the sample app, the weather service requires zipcode as a parameter.



* Name: zipcode
* Located in: Query
* Required: Yes
* Type: string
![path-current-1.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/path-current-1.png) d. Save your API.



11. With your query parameters defined in the previous step, you are ready to define the response object, which is returned when you invoke the weather API. Scroll to the Definitions panel.



1. Add a new definition.
2. Name the new definition Current.
3. Set the Type of Object.
4. Add new properties for the Current definition as shown in Table 1.



Table 1. Properties for the Current definition
Set as UNIX timestamp in seconds or Javascript (milliseconds). 
 to int32 Required End time. Set as UNIX timestamp in seconds or Javascript (milliseconds). 
 size int32 Optional Number of log lines to include in each page of the export. The maximum and default is 10000. 
 hosts string Optional Comma-separated list of hosts. 
 apps string Optional Comma-separated list of applications. 
 levels string Optional Comma-separated list of log levels. 
 tags string Optional Comma-separated list of tags. 
 query string Optional Search query. For more information, see [Search Logs](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-view_logsview_logs_step6). 
 prefer string Optional Defines the log lines that you want to export. Valid values are head, first log lines, and tail, last log lines. If not specified, defaults to tail. 
 pagination_id string Optional Indicates which page of results is retrieved from an export. For the initial export request, this parameter should be omitted. Subsequent requests for pagination should provide the token sent in the response to this parameter. 



For example, you can define a set of parameters to include information:

ENDPOINT/v2/export?to=START_TIME&from=END_TIME&hosts=LIST_OF_HOSTS<=vels=LIST_OF_LEVELS&size=N&query=(SEARCH_QUERY)" -u $TOKEN:





 Exporting logs 

Complete the following steps to export logs programmatically:



 Step 1. Get a service key 

[Get a service key](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-service_keys).





 Step 2. Identify the data to pass through the export parameters 

To verify that the query that you use in the export returns the set of logs that you are looking for, define the search query through the logging web UI. Refine the query until you can only see the logs that you want to export. Then, map the data to the query parameters.
![definition-current-1.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/definition-current-1.png)

e. Save your API.
12. Create a new definition: Today.
13. Add new properties for the Today definition as shown in Table 2.



Table 2. Properties for the Today definition

 Name Type 

 zip string 
 hi integer 
 lowe integer 
 nighthumidity integer 
 dayhumidity integer 
 city string 
 state string 



14. With our data formats defined, we can create invocation paths. In the navigation bar, click Paths. Create a new path by clicking +.
a. Name the new path "/current".
b. In the same Paths panel, select the GET /current section.
c. In the GET /current section, add a new Parameter. As you noticed while exploring the sample app, the weather service requires zipcode as a parameter.



* Name: zipcode
* Located in: Query
* Required: Yes
* Type: string



![path-current-1.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/path-current-1.png)

d. Scroll down. In the Responses section, change the SCHEMA to Current.

![path-current-responses.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/path-current-responses.png)

e. Save your API.
15.
For more information, see [Hotlink protection](https://cloud.ibm.com/docs/CDN?topic=CDN-about-content-delivery-networks-cdn-hotlink-protection).
* Token authentication - Provide the token key, set the escape input and ignore query string, and then select the HMAC algorithm. Optionally, specify the token name, token delimiter, ACL delimiter, and transition key. If you do not specify a value for an optional parameter, the default value is used. For more information, see [Token authentication](https://cloud.ibm.com/docs/CDN?topic=CDN-about-content-delivery-networks-cdn-token-authentication).

You cannot set the token and ACL delimiters to the same value.



5. Click Add to save the configuration. The newly added rule is listed in the table.
6. After you add a rule, you can click the overflow menu ![Overflow menu](https://cloud.ibm.com/docs-content/v1/content/006fd22ab2811b7d19804c763a00568b3da4c03a/CDN/images/overflow.png) to Edit or Delete the rule.

You cannot change the path of the rule.
Understanding secondary zones 



  Secondary zone definition 

A secondary zone is a read-only copy of the primary DNS zone. Instead of getting information from local files, secondary zones receive pertinent information from a primary server in a communication process known as a zone transfer.

With secondary zones, you can duplicate records from your on-premises DNS server to your DNS Services custom resolver. The custom resolver gives fine-grain control of name resolution and also enables forwarding DNS queries to and from on-premises DNS servers. You can make DNS queries for transferred zones within your VPC and receive the same records as if the query was made to your on-premises DNS server.

Existing custom resolvers automatically support the secondary zone feature, but you will have to create a secondary zone manually.





  Configuring secondary zones 

When configuring secondary zones, take the following into consideration:



*  Server must have the zone configured
*  Server must enable DNS transfer to all custom resolver locations
*  Currently, custom resolver only perform AXFR, and not IXFR
*  Custom resolver uses port 53 to communicate with DNS server
*  Each custom resolver can have a maximum of 5 secondary zones







  Example for secondary zone 

In this example, a customer has a zone onprem.customer.com which is managed by the DNS server 10.230.9.2. In IBM Cloud, the customer has workloads running in VPCs which need to resolve resource record database.onprem.customer.com. Using custom resolvers and forwarding rules the customer can resolve the name by forwarding the query to DNS server 10.230.9.2, but if the DNS server is down or has connectivity issues, the name resolution fails. To avoid this, instead of a forwarding rule the customer can configure a secondary zone rule in their custom resolver and on-premises DNS server. Then, even if there are intermittent connectivity issues reaching the on-premises DNS server, the custom resolver locations can resolve the resource record requests.
--registration-key-public-path PRIVATE-KEY-PATH
: The path for the public key from the registration key pair. Ensure that you use the same key that you had used when you created the virtual instance the first time. You must save these keys in a safe and secure location for future use.

--registration-key-private-path PUBLIC-KEY-PATH
: The path for the private key from the registration key pair. Ensure that you use the same key that you had used when you created the virtual instance the first time. You must save these keys in a safe and secure location for future use.

--gpg-passphrase-path PASS-PHRASE
: The path to a file that contains the gpg passphrase used for the private part of the registration key. The passphrase must consist of at least 6 characters. To make sure that a new line is not appended, use echo with -n or cat with EOF.

--cap-add CAPABILITIES
: The Linux capabilities to be enabled are specified as a comma separated list.

--isv-secrets ISV-SECRETS
: The Linux secrets to be used in BYOI. The secrets are added in the /isv_secrets/secrets.json file, within the container.

The ISV secrets is a key value pair that is separated by a colon, and you can specify a list secrets that are separated by a comma. Avoid adding spaces after the comma when you are specifying multiple secrets. If the size of the secret is large, it is recommended that you specify it by using the --isv-secrets command parameter. To update ISV secrets, you must create a new registration definition file with the updated ISV secrets and use the same registration definition file when running the hpvs instance-update command to update the instance.

--no-isv-secrets
: If the image does not require any isv secrets, this parameter can be set. You need not provide the isv-secrets parameter, and if you do, it will be ignored.
"name": "rowguid",
"datatype": "CHAR(36)",
"nullable": false,
"label": "Rowguid",
"usage": "identifier",
"regularAggregate": "countDistinct"
}, {
"name": "ModifiedDate",
"datatype": "TIMESTAMP",
"nullable": false,
"label": "Modified Date",
"usage": "identifier",
"regularAggregate": "countDistinct",
"taxonomyFamily": "cDate"
}
]
},
"label": "Module Name",
"identifier": "moduleId"
}

Show more









 CSV data sources 

Alternatively, you can use a CSV file as a data source for a dashboard. Instead of defining the JDBC connection information, a URL that contains the location, where the CSV file is stored is passed in, in the sourceUrl field below.

Do not change the sourceUrl when it is defined. Make sure that the server that provides the file uses standard HTTP cache control response headers. IBM® Cognos Dashboard Embedded can now cache the response locally for better query performance.

If you need IBM® Cognos Dashboard Embedded to pass extra headers on the request for the CSV file, to for example, facilitate authentication, you can add headers to the module definition as shown.

Notes:



* The maximum supported size for CSV files is 1 GB.
* The CSV file is accessed using a GET request to the sourceUrl provided. Provide a secure (https) URL.





 Sample CSV source specification: 

{
"xsd": "https://ibm.com/daas/module/1.0/module.xsd",
"source": {
"id": "StringID",
"srcUrl": {