vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If you reach the plan limit of versions you can have, you need to delete a version before you can publish another one.



Service plan published versions

 Service plan Published versions 

 Enterprise 50 
 Premium (legacy) 50 
 Plus 10 
 Trial 10 
 Lite 2 





 How to publish 



1. If changes are available to publish, click Publish.
2. Enter a description of the version.
3. Choose to publish to the live environment, or to create a version without publishing. If you choose to create a version, you can use the environment tab to publish that version later.

With the Enterprise plan, you can publish to an environment you added. For more information, see [Adding and using multiple environments](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-multiple-environments).
4. Click Publish:

Zoom

![Publish all content](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/publish-modal.png)

Publish all content
5. After you publish, the list is clear until you make more edits to your content.

Zoom

![No changes](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/no-new-changes-publish.png)

No changes







 What is being published? 

When you publish, a snapshot is taken of the current state of actions. All updates to actions content are published in a version, including the following updates:



* Creating an action
* Editing an action
* Editing actions settings
* Deleting actions
* Creating variables
* Editing variables
* Deleting variables
* When a source is recrawled, new documents are added, updated documents are modified to the current version, and deleted documents are deleted from the collection's index.
* All Discovery data source connectors are read-only. Regardless of the permissions that are granted to the crawl account, Discovery never writes, updates, or deletes any content in the original data source.



Discovery can crawl the following objects:



* Site Collections
* Sites
* SubSites
* Lists
* List Items
* Document Libraries
* List Item Attachments







 Data source requirements 

In addition to the [data source requirements](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-collection-typesrequirements) for all installed deployments, your SharePoint Online data source must meet the following requirements:



* The Site Collection that you connect to must be one that was created with an Enterprise plan. It cannot be a collection that was created with a frontline worker plan.
* Authentication support differs based on the principal type you specify when you configure the authentication method. Determine which principal type you want to use before you create the collection; you cannot change the principal type later. The following options are available:



* User: The following requirements must be met by the crawl user account:



* Account must have an Azure Active Directory user ID with permission to access all of the objects that you want to crawl. For example, admin_user@company.onmicrosoft.com. The user ID must have Site Collection Administrator permission.
* Account must have legacy authentication enabled. To enable legacy authentication, go to the [Azure portal](https://portal.azure.com/) or contact your Azure Active Directory administrator.

The connector supports the Password hash synchronization (PHS) method for enabling hybrid identity only. Use any other type (such as Pass-through authentication or Federation) at your own risk. Unless you created your SharePoint Online account before January 2020, two-factor authentication is enabled for the account by default. You must disable two-factor authentication.
* Only 1 instance in a location can be configured to collect logs automatically from [IBM Cloud enabled services](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-cloud_services) in that IBM Cloud location.
* Each location represents the geographic area where your IBM Log Analysis requests are handled and processed for that instance, and where data is resident.
* Each MZR location has three different data centers for redundancy. The data for each location is kept in the three data centers near that location. If all three data centers in a location fail, the IBM Log Analysis service for that location becomes unavailable.
* Each MZR configuration can accept a single data center failure.



When you choose the locations where you plan to provision IBM Log Analysis instances, check the regulatory and high availability (HA) specifications of each location.

For example, in Europe, only the Frankfurt region is EU-supported.

You can also check [ensure zero downtime](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimezero-downtime) to learn more about the high availability and disaster recovery standards in IBM Cloud.





 Platform logs 

To enable automatic collection of IBM Cloud enabled services, you must configure 1 instance in a location with the platform logs flag. [Learn more](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-config_svc_logs). When 1 instance is enabled to collect logs in a location, data from any instance of an enabled service in that location is collected automatically.

Define 1 instance per location with the platform logs flag enabled.

If you share staging, pre-production, and production services in the same IBM Cloud account, notice that users, that are granted access to view data in the logging instance with the platform logs flag in a location, can see data from any service instance provisioned in that location. To prevent users from viewing log data from all service's instances, consider moving from a single account model to an Enterprise account model.

If you cannot move to an enterprise account model, try reducing the number of users that are granted permissions to view the logs.
Thereafter, replacing the [$ARRAY_OF_INPUT_FIELDS] placeholder with ["sepal_length", "sepal_width", "petal_length","petal_width"], [$ARRAY_OF_VALUES_TO_BE_SCORED] placeholder with [5.1,3.5,1.4,0.2] and [$ANOTHER_ARRAY_OF_VALUES_TO_BE_SCORED] placeholder with [3.2,1.2,5.2,1.7] respectively.







 Step 6: Monitor your deployed model with IBM Watson OpenScale 

IBM® Watson OpenScale tracks and measures outcomes from your AI models, and helps ensure they remain fair, explainable, and compliant wherever your models were built or are running. Watson OpenScale also detects and helps correct the drift in accuracy when an AI model is in production.

For ease of understanding, the tutorial concentrates only on improving the quality (accuracy) of the AI model through Watson OpenScale service.



 Provision IBM Watson OpenScale service 

In this section, you will create a Watson OpenScale service to monitor the health, performance, accuracy and quality metrics of your deployed machine learning model.



1. Create a [IBM Watson OpenScale service](https://cloud.ibm.com/catalog/services/watson-openscale)



1. Select a region preferably Dallas. Create the service in the same region where you created the Machine Learning service.
2. Choose Lite plan.
3. Set the service name to watson-openscale-tutorial.
4. Select a resource group.
5. Click Create.



2. Once the service is provisioned, Click Manage on the left pane and click Launch Application.
3. Click on Manual setup to manually setup the monitors.







 Selecting a deployment 

In this section, as part of preparing your model for monitoring you will set up and enable monitors for each deployment that you are tracking with IBM Watson OpenScale.



1. By clicking on the Edit icon on the Database tile, choose Free lite plan database as your Database type and click Save.
From the row for the user that you want to assign access, select the Actions menu, and then click Assign access.
3. Select Assign access within a resource group.
4. Select a resource group.
5. If the user does not have a role already granted for the selected resource group, choose a role for the Assign access to a resource group field.

Depending on the role that you select, the user can view the resource group on their dashboard, edit the resource group name, or manage user access to the group.

You can select No access, if you want the user to only have access to the IBM Cloud Monitoring service in the resource group.
6. Select IBM Cloud Monitoring.
7. Select the platform role Administrator.
8. Click Assign.







 Step 2. Provision an instance of the Monitoring service 

To add monitoring features with IBM Cloud Monitoring in the IBM Cloud, you must provision an instance of the IBM Cloud Monitoring service.

Instances are provisioned in the context of a resource group. A resource group organizes your services for access control and billing purposes. You can provision the IBM Cloud Monitoring instance in the default resource group or in a custom resource group.

To provision an instance through the IBM Cloud UI, complete the following steps:



1. Log in to your IBM Cloud account.

Open the [IBM Cloud dashboard](https://cloud.ibm.com/login).

After you log in with your user ID and password, the IBM Cloud UI opens.
2. Click Catalog. The list of the services that are available in IBM Cloud opens.
3. To filter the list of services that is displayed, select the Logging and Monitoring category.
4. Click the IBM Cloud Monitoring tile.
5. Select the location.
6. Select a service plan. By default, the Lite plan is selected.

To provision an instance that only includes the Monitor component, select the plan Graduated Tier.

To provision an instance that include the Monitor and the Secure (Workload Protection) components, select the plan Graduated Tier - Sysdig Secure + Monitor.
Enterprise plan managed deployment 50 KB 5 5 



Use of the Analyze API from Discovery Cartridge for IBM Cloud Pak for Data affects license usage. For more information, see the [license information](https://www-40.ibm.com/software/sla/sladb.nsf/displaylis/F644E41EA1B29A96002587F10057A1C7?OpenDocument).





 Monitoring usage IBM Cloud Pak for Data 

You can monitor the usage of the Analyze API from the API usage page.

The API usage page is available from installed deployments only. For Enterprise plans, analyze method call information is combined with query method call information and is reported as part of the query metrics.

To access the API usage page, open the Projects page, select Data usage, then API usage.

Start date
: The start date of the API call-monitoring period.

End date
: The end date of the API call-monitoring period.

Thirty-day call total
: Number of calls to the Analyze API in the 30-day time interval that is indicated by the Start date and End date. The time interval is determined by calculating the consecutive time period with the highest number of API calls. The 30-day window updates as the time interval with the highest number of API call changes.

The API usage is not displayed until some time after API usage monitoring begins. A delay in displaying the final total number of the 30-day call total might occur, even if the 30-day period that is listed includes the current date.
SAP NetWeaver 7.x on Windows Servers with MS SQL on IBM Cloud® VPC 

MS SQL Server is one of several databases that can be deployed on SAP NetWeaver in the IBM Cloud®. The most common architecture deployments are standard and distributed systems. IBM Cloud is certified for running SAP NetWeaver application servers ABAP, Java, and SAP products based on these application server stacks.

The MS SQL Server database for SAP is supported only on Windows servers and using only the Enterprise Edition of the software. Other SQL Server editions are currently not supported.



 SAP NetWeaver architecture 

SAP NetWeaver is the core foundation of the SAP technology stacks and is the platform that is used for Advanced Business Application Programming (ABAP) and Java applications. SAP NetWeaver components are built on the SAP NetWeaver Application Server and are written in ABAP or Java Platform, Enterprise Edition. ABAP systems, Java systems, and dual-stack systems are distinct systems.



 Core platform features 

SAP NetWeaver uses ABAP or Java core platforms to support the SAP applications. SAP NetWeaver:



* Has application lifecycle management capabilities.
* Provides the basic structure for the on-premises versions of SAP Business Suite and other applications, as an application server.
* Is the foundation for the on-premises SAP S/4HANA next-generation business suite, with SAP HANA serving as the sole underlying database.



SAP provides a list of the [SAP versions](https://support.sap.com/en/my-support/software-downloads/support-package-stacks/product-versions.htmlsection_486851042) to learn more about the versions available in IBM Cloud. Each support package stack has a leading software component version. The support package level of each component version is a key part of the stack and a unique identifier for the support package stack.





 Installation types 

The three installation types for SAP NetWeaver Application Server are:



* ABAP System– You can run ABAP programs and some SAP Java apps
* Java System– You can run only Java Platform, Enterprise Edition apps. No ABAP programs can be run on a Java system
* Dual Stack – You can run both ABAP and Java Platform, Enterprise Edition in separate instances









 Architecture diagram
SAP NetWeaver 7.x with SAP HANA IBM Cloud® VPC 

SAP HANA is one of several databases that can be deployed on SAP NetWeaver in the IBM Cloud®. SAP HANA is an in-memory database installed on a dedicated database server. The main architecture deployments for SAP HANA are single-host or multiple-host systems. IBM Cloud is certified for running SAP NetWeaver application servers ABAP, Java, and SAP products based on these application server stacks.



 SAP NetWeaver architecture 

SAP NetWeaver is the core foundation of the SAP technology stacks and is the platform that is used for Advanced Business Application Programming (ABAP) and Java applications. SAP NetWeaver components are built on the SAP NetWeaver Application Server and are written in ABAP or Java Platform, Enterprise Edition. ABAP systems, Java systems, and dual-stack systems are distinct systems.



 Core platform features 

SAP NetWeaver uses ABAP or Java core platforms to support the SAP applications. SAP NetWeaver:



* Has application lifecycle management capabilities.
* Provides the basic structure for the on-premises versions of SAP Business Suite and other applications, as an application server.
* Is the foundation for the on-premises SAP S/4HANA next-generation business suite, with SAP HANA serving as the sole underlying database.



SAP provides a list of the [SAP versions](https://support.sap.com/en/my-support/software-downloads/support-package-stacks/product-versions.htmlsection_486851042) to learn more about the versions available in IBM Cloud. Each support package stack has a leading software component version. The support package level of each component version is a key part of the stack and a unique identifier for the support package stack.





 Installation types 

The three installation types for SAP NetWeaver Application Server are:



* ABAP System– You can run ABAP programs and some SAP Java apps
* Java System– You can run only Java Platform, Enterprise Edition apps. No ABAP programs can be run on a Java system
* Dual Stack – You can run both ABAP and Java Platform, Enterprise Edition in separate instances









 Architecture diagram
To create a new access policy for a user, run the ibmcloud iam user-policy-create command. In the command example, a JSON file is used to specify the policy details. Review the example in the [Assigning access by using the API](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-assign-access-enterpriseenterprise-api-policy) section for an example of what to include in the JSON file.

Create a user policy:

ibmcloud iam user-policy-create name@example.com -f policy.json

For more information, see [ibmcloud iam user-policy-create](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_iamibmcloud_iam_user_policy_create).





 Assigning access by using the API 

The following request example assigns a policy for a user with the Editor role on the Enterprise service in an enterprise account that is scoped to an account group. This type of policy is hierarchical and applies to all descendant objects in the hierarchy, which means all account groups or accounts within the specified target account group.



* Curl
* Java
* Python
* Go
* Node



curl -X POST 'https://iam.cloud.ibm.com/v1/policies' -H 'Authorization: Bearer $TOKEN' -H 'Content-Type: application/json' -d '{
"type": "access",
"description": "Editor role for SERVICE_NAME's RESOURCE_NAME",
"subjects": [
{
"attributes":
{
"name": "iam_id",
"value": "IBMid-123453user"
}
]
}'
],
"roles":[
{
"role_id": "crn:v1:bluemix:public:iam::::role:Editor"
}
],
"resources":[
{
"attributes":
{
Cloud application can use this function through [gRPC](https://grpc.io).

Enterprise PKCS #11 supports stateless cryptography use cases and allows for scaling and redundancy in an enterprise environment. For some use cases around asset protection, the keys can be managed outside the cryptographic service, while all sensitive operations are executed within the HSM boundary. You can use Enterprise PKCS #11 when state handling is an issue, especially for enterprise applications that benefit from the stateless character of Enterprise PKCS #11.

You as a cloud developer can use standard interfaces from your applications for cryptographic operations with data integrity and confidentiality. Hyper Protect Crypto Services supports secure connectivity from cloud application to cloud HSM, and allows for enterprise control of Cloud HSM for application keys.

As IBM is starting to provide a new set of capabilities to support your workloads to move to the cloud, you can benefit from the cryptographic capabilities of Hyper Protect Crypto Services for both your new and existing workloads. With the introduction of Enterprise PKCS #11 over gRPC (GREP11), you have access to a full range of cryptographic operations, such as signing, signature validation, message authentication codes, random number generation.

Some code samples for [using GREP11 with Golang](https://github.com/IBM-Cloud/hpcs-grep11-go) and [JavaScript](https://github.com/IBM-Cloud/hpcs-grep11-js) are available for you to try out.

Zoom

![EP11 HSM](https://cloud.ibm.com/docs-content/v1/content/217f108cc44e2ce15fb692d4b57b4c628464e908/hs-crypto//images/PKCS11.svg)

Figure 8. Cryptographic operations with Enterprise PKCS #11





 What's next 



* You can use Hyper Protect Crypto Services as the root key provider for other IBM Cloud services.
SAP NetWeaver 7.x on UNIX with Sybase on IBM Cloud® VPC 

Sybase is one of the many databases that can be run with SAP NetWeaver and that is supported on the IBM Cloud®. The most common architecture deployments are standard and distributed. IBM Cloud is certified for running SAP NetWeaver application servers ABAP, Java, and SAP products based on these application server stacks.



 SAP NetWeaver architecture 

SAP NetWeaver is the core foundation of the SAP technology stacks and is the platform that is used for Advanced Business Application Programming (ABAP) and Java applications. SAP NetWeaver components are built on the SAP NetWeaver Application Server and are written in ABAP or Java Platform, Enterprise Edition. ABAP systems, Java systems, and dual-stack systems are distinct systems.



 Core platform features 

SAP NetWeaver uses ABAP or Java core platforms to support the SAP applications. SAP NetWeaver:



* Has application lifecycle management capabilities.
* Provides the basic structure for the on-premises versions of SAP Business Suite and other applications, as an application server.
* Is the foundation for the on-premises SAP S/4HANA next-generation business suite, with SAP HANA serving as the sole underlying database.



SAP provides a list of the [SAP versions](https://support.sap.com/en/my-support/software-downloads/support-package-stacks/product-versions.htmlsection_486851042) to learn more about the versions available in IBM Cloud. Each support package stack has a leading software component version. The support package level of each component version is a key part of the stack and a unique identifier for the support package stack.





 Installation types 

The three installation types for SAP NetWeaver Application Server are:



* ABAP System– You can run ABAP programs and some SAP Java apps
* Java System– You can run only Java Platform, Enterprise Edition apps. No ABAP programs can be run on a Java system
* Dual Stack – You can run both ABAP and Java Platform, Enterprise Edition in separate instances









 Architecture diagram 

This diagram shows the SAP NetWeaver 7.X on Sybase DB integrated with IBM Cloud on the SAP NetWeaver 7.x architecture:

Zoom
To assign an access policy to an existing user in the enterprise account, complete the following steps:

You can set the target of the policy to be for the entire enterprise, a specific account group, which can include access to all accounts within it, or even a specific account in an account group.



1. In the IBM Cloud console, click Manage > Access (IAM), and select Users.
2. From the row for the user that you want to assign access, click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/d4595e5202a9a27767cf034e81b038cdf772e0d5/icons/action-menu-icon.svg), and click Assign access.
3. From the services, select Enterprise.
4. Click Next.
5. Scope the access to a resource group with specific child accounts, or all accounts in the enterprise. Then, click Next.
6. Select any combination of roles or permissions, and click Review.
7. Click Add to add your policy configuration to your policy summary.
8. (Optional) Repeat steps to add additional access.
9. Click Assign.



For more information about roles and actions to assign access in an enterprise account, see [Assigning access to account management services](https://cloud.ibm.com/docs/account?topic=account-account-servicesenterprise-account-management).





 Assigning access by using the CLI 

To create a new access policy for a user, run the ibmcloud iam user-policy-create command. In the command example, a JSON file is used to specify the policy details. Review the example in the [Assigning access by using the API](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-assign-access-enterpriseenterprise-api-policy) section for an example of what to include in the JSON file.

Create a user policy: