vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Review the Preview table to confirm your selections, and click Update.
5. Verify your updates in the catalog by going to Catalog > Services.
6. Expand the list of accounts in the console menu bar and select a child account to verify that the catalog includes only the products you selected.







 Managing products for child account groups and accounts 

To build on the example in the previous section, all account groups and accounts in your enterprise have access to Developer tools products provided by IBM. You can further restrict access to a subset of products for child account groups and accounts. For example, you might want to limit a specific account group, and its child accounts, to work with only the products that are Financial Services Validated.



1. Go to Manage > Catalogs > Settings in the IBM Cloud console.
2. Expand the enterprise hierarchy, and select the specific account group.
3. Select Exclude all products in the IBM Cloud catalog.
4. Select Compliance > Financial Services Validated.
5. Review the Preview table to confirm your selections, and click Update.
6. Switch to a child account in the account group by selecting it from the list of accounts in console menu bar.
7. Verify your updates in the catalog by going to Catalog > Services.







 Managing products at the enterprise level by using the CLI 

This action can be done only in the console or through the API or SDKs. To see the steps, switch to the UI or API instructions.





 Managing products for child account groups and accounts by using the CLI 

You can restrict access to a subset of products for child account groups and accounts. For example, within your enterprise you might want to limit a specific account group, and its child accounts, to work with only the products that are Financial Services Validated.



1. Create a new filter.

ibmcloud catalog filter create [--catalog CATALOG] [--category CATEGORY] [--compliance COMPLIANCE] [--deployment-target TARGET] [--exclude-list LIST] [--include-all ALL] [--include-list LIST] [--offering-format FORMAT] [--pricing-plan PLAN] [--provider PROVIDER] [--release RELEASE] [--type TYPE]
* You must include the settings information in the data section of the request.
* You must pass the data that is configured for each setting.

Data that is configured and not included in an update request is deleted.
* Update the data for the fields that need changing.



You can use the following cURL command to update settings:

curl -X PATCH https://<ENDPOINT>/api/v3/settings
-H "Authorization: Bearer <IAM_TOKEN>"
-H 'accept: application/json'
-d '{
"default_targets": [
{
"id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}
],
"permitted_target_regions": ["us-south", "us-east"],
"primary_metadata_region": "us-south",
"backup_metadata_region": "us-east",
"private_api_endpoint_only": false
}'

Where:

ENDPOINT
: Is the API endpoint in the region where you plan to configure or manage a target. For more information, see [Endpoints](https://cloud.ibm.com/docs/metrics_router?topic=metrics_router-endpointsendpoints_api).

default_targets
: Is a list of target IDs. If no routing rules cause metrics to be sent to other targets, these targets will received the metrics.

permitted_target_regions
: Is the list of regions that can be used to define a target. A maximum of two permitted target regions can be specified.

primary_metadata_region
: Is the region where the metadata associated with route and target definitions is stored.

backup_metadata_region
: Is the region where the metadata associated with route and target definitions is stored for backup purposes.

private_api_endpoint_only
: Specifies whether or not a private endpoint can be used. If true only a private endpoint can be used.
If the update is successful, the current settings will be displayed.







 API settings and actions 

The following table lists the actions that you can run to manage settings:



Table 1. Settings actions by using the IBM Cloud Activity Tracker Event Routing REST API

 Action REST API Method API_URL 

 Get settings information GET <ENDPOINT>/api/v2/settings 
 Update settings PUT <ENDPOINT>/api/v2/settings 



You can use private and public endpoints to manage settings. For more information about the list of ENDPOINTS that are available, see [Endpoints](https://cloud.ibm.com/docs/atracker?topic=atracker-endpoints).



* By default, you can manage settings from the private network. You must use an API endpoint with the following format: https://private.<region>.atracker.cloud.ibm.com
* You can also enable public endpoints in a region to manage settings. For more information, see [Managing endpoints](https://cloud.ibm.com/docs/atracker?topic=atracker-endpoints_manage).



For more information about the REST API, see [the settings API](https://cloud.ibm.com/apidocs/atracker/atracker-v2get-settings).





 API prerequsites 

To make API calls to manage settings, complete the following steps:



1. Get an IAM access token. For more information, see [Retrieving IAM access tokens](https://cloud.ibm.com/docs/atracker?topic=atracker-retrieve-iam-token).
2. Identify the API endpoint in the region where you plan to configure or manage settings. For more information, see [Endpoints](https://cloud.ibm.com/docs/atracker?topic=atracker-endpointsendpoints_api).







 Getting settings using the API 

You can use the following cURL command to get existing settings information:
Updates to the service are posted on our [What's New](https://www.ibm.com/support/pages/whats-new-ibm-db2-warehouse-cloud) page.

You can find pricing information and deploy a Db2 Warehouse on Cloud instance through the IBM Cloud [catalog](https://cloud.ibm.com/catalog/services/db2-warehouse) page for IBM Cloud. To learn more, contact [IBM Sales](https://www.ibm.com/contact/us/en/).





 Where can I find help for a problem that I'm having? 

For information about posting questions on a forum or opening a support ticket, see [Help & support](https://cloud.ibm.com/docs/Db2whc?topic=Db2whc-help_support).
For more information, see the [IAM Policy Management](https://cloud.ibm.com/apidocs/iam-policy-managementupdate-policy) API.





 Updating session duration 

To update the session duration for federated users, call the following:

curl -X PUT 'https://iam.cloud.ibm.com/v1/profiles/PROFILE_ID/rules/CLAIM_RULE_ID'
-H 'Authorization: Bearer TOKEN'
-H 'If-Match: <value of etag header from GET request>'
-H 'Content-Type: application/json'
-H 'Accept: application/json'
-d '{
"type": "Profile-SAML",
"realm_name": "https://w3id.sso.ibm.com/auth/sps/samlidp2/saml20",
"expiration": 10000,
"conditions": [
{
"claim": "groups",
"operator": "CONTAINS",
"value": ""cloud-docs-ops""
}
]
}'
Click the new Plan (New Plan 1) to expand the details.
3. Click the Title field and set the Plan title to: Demo.
4. Click the Name field and set the Plan name to demo-plan.
5. Click + to add a new rate limit.
6. Rename the new rate limit to demo-rate-limit, and ensure it is set to 1 / 1 Minute.
7. Check the Enforce hard limit checkbox. When Enforce hard limit is enabled, an application receives an error if it exceeds the rate limit by callin an API more times that allowed in hte specified time period.
8. Accept the remaining default settings and save the Product.

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







 Staging & publishing an updated Product to the Sandbox Catalog 

In previous examples, you might have published your Product using the test tool, which calls your API with a pre-supplied test application's credentials. The test application is not subject to rate limits, so you must create a new application for rate limiting purposes. For more information on creating products, see the [IBM Knowledge Center content for API Connect](https://www.ibm.com/support/knowledgecenter/SSFS6T/com.ibm.apic.toolkit.doc/tapim_create_product.html).



1. Click the Publish icon to stage the Product to the Sandbox Catalog. Staging the Product adds it to the selected Catalog. We need to publish the Product changes next, to make them available to consumers via the Developer Portal. ![stageproduct.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/stageproduct.png)
2.
* Anonymous usage statistics are no longer collected for those that had previously opted in to usage statistics collection. The --usage-stats-collect flag is removed from the config command.
* Improved performance of several commands involving resource groups.
* New command to toggle the Intelligent Platform Management Interface (IPMI) on and off: sl hardware toggle-ipmi.
* The add --output flag is added to the resource service-key-create command.
* For the iam access-groups command, Public Access is included in the output.
* Upgrade to Go language Golang 1.15.5.



For more details about Version 1.3.0, see the [IBM Cloud CLI release notes](https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases/).

For more information about the CLI, see [Getting started with the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).





 10 December 2020 

Enhanced payments & invoicing for new US-based Pay-As-You-Go accounts with credit card billing
: We are excited to announce our latest unification project for new US-based IBM Cloud Pay-As-You-Go accounts with credit card billing. For increased clarification and consistency, the unified experience includes the following enhancements:



* A single invoice that includes comprehensive usage details for all your products
* The ability to download the invoice directly from the console
* The ability to update a credit card in the console without being redirected to a different website
* A one-to-one mapping between your invoice and your usage dashboard in the console



For more details, including a video walk-through of the enhancements, see [The Enhanced Unified Billing and Payment Experience in IBM Cloud](https://www.ibm.com/cloud/blog/announcements/enhanced-unified-billing-and-payment-experience-in-ibm-cloud).





 04 December 2020 

Enhancements to the IBM Cloud Status page
Review the estimated monthly order summary for your geography and new pricing.
6. If you're satisfied, click Save and continue.



Your new IOPS allocation is realized when you restart the instance.





 Adjust IOPS from the CLI 



 Adjust IOPS for a Custom or dp2 profile 

From the CLI, use the share-update command with the --iops property to indicate the new IOPS size for a custom or dp2 profile. The IOPS that you indicate must be within the range for the size of the file share (see [Custom IOPS profile](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles&interface=uicustom) or [dp2](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilesdp2-profile)).

ibmcloud is share-update SHARE_NAME --iops IOPS

The following example shows an increase of IOPS from 100 IOPS to 1,200 IOPS for a 100 GB file share based on a 100 - 499 custom profile. (The IOPS range for this custom band is 100 - 6,000 IOPS.)

ibmcloud is share-update my-file-share --profile custom-iops --iops 1200
Updating file share my-file-share under account VPC1 as user user1@mycompany.com...

ID e1180bae-6799-4156-8bb7-e4d24013cda2
Name my-file-share
CRN crn:v1:staging:public:is:us-south-1:a/0ef3f509-04f4-465e-88c6-2d60b164d805::share:e1180bae-6799-4156-8bb7-e4d24013cda2
Lifecycle state updating
Zone us-south-1
Profile custom-iops
Size(GB) 100
IOPS 1200
Encryption provider_managed
Mount targets ID Name VPC ID VPC Name
To view these events, you must [provision an instance](https://cloud.ibm.com/docs/services/activity-tracker?topic=activity-tracker-provisionprovision) of the IBM Cloud Activity Tracker service in the Frankfurt (eu-de) region. Then, you must [open the IBM Cloud Activity Tracker UI](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-launchlaunch_cloud_ui).





 Analyzing events 



 Catalog events 

You can find the value unavailable in catalog events. This value indicates when an update is made, but specific details about the update aren't included.





 User management events 

This section explains events that are generated when you manage users from the Manage > Access IAM > Users dashboard.

When you analyze user management events, target.name is set to the user ID of the user on which the action is requested.



 Modify the status of a user 

When you modify the status of a user by selecting a user, clicking Edit in the Details section, and changing the User status, you get the following event:



* Event with action user-management.user.update that reports a request in the account to modify the user's properties.



For example, see the action field for the event user-management.user.update:

"action": "user-management.user.update",
"message": "User management service: update user"
"initiator": {
"id": "IBMid-12345",
"typeURI": "service/security/account/user",
"name": "example@ibm.com",
"host": {
"agent": "",
"address": "...",
"addressType": "IPv4"
},
"credential": {
"type": "token"
}
},
"target": {
"id": "crn:v1:bluemix:public:user-management:global:a/account1234:::",
"typeURI": "user-management/user",
* UI







 Managing virtual server instance bandwidth 

You can add bandwidth when you provision virtual server instances. You can upgrade bandwidth by purchasing larger allocations at a reduced cost compared to the bandwidth overage rate.



 Selecting bandwidth while provisioning virtual server instances 

To add bandwidth while provisioning a virtual server instance by using the UI, follow these steps:



1. From your browser, open the [IBM Cloud console](https://cloud.ibm.com/login) and log in to your account.
2. Select Catalog from the menu bar on the header.
3. Select the Virtual Server for Classic tile and [provision your new virtual server instance](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-ordering-vs-public).
4. In the Network interface section, find the Public egress - bandwidth option. Then, select the amount of bandwidth that you want to add to your server.

Public bandwidth usage over GB allocation is charged per GB. Also, public bandwidth egress (or bandwidth allocation) pricing depends on regions as indicated in Pricing plans by region on the [Bandwidth packages from IBM Cloud](https://www.ibm.com/cloud/bandwidth) website.







 Upgrading bandwidth on a virtual server instance 

To upgrade bandwidth on a virtual server instance by using the UI, follow these steps:



1. From your browser, open the [IBM Cloud console](https://cloud.ibm.com/login) and log in to your account.
2. Select the Navigation menu ![Navigation menu](https://cloud.ibm.com/docs-content/v1/content/62b0b227c55ca35d2081883daccc11ef3a59022a/icons/icon_hamburger.svg), then click Classic Infrastructure.
3. Select Devices > Device list.
4. Click the name of the virtual server instance that you are modifying.
5. On the device's details page, find the Network Details section, then the Public bandwidth allocation section. Beside the Current billing cycle bandwidth allocation details, click Modify.
6.
After you review your version details, click Next.





 Step 3: Set the license requirements 

If users are required to accept any license agreements beyond the IBM Cloud Services Agreement, provide the URL to each agreement.



1. From the Add license agreements tab, click Add license.
2. Enter the name and URL, and click Add license.
3. Enter all additional license agreements, and click Next.







 Step 4: Review your readme file 

When users install the software, they can view product information by clicking the Readme file link. This information is generated from the readme file that you uploaded to your source repository.



1. From the Edit readme tab, click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/edit-tagging.svg).
2. Preview how the information in the readme file will be displayed to users when they are installing the Operator bundle.
3. If you need to make changes, edit the information in the source file and import the updated Operator bundle to your private catalog.
4. Click Save > Next.







 Step 5: Validate the software version 

Before you can publish the Operator bundle, you need to validate it to make sure that the version can be deployed to the intended target.



1. From the Validate product tab, select the Update channel that you would like to receive updates from.
2. Select whether you want to apply updates automatically or manually.
3. Select a Red Hat OpenShift on IBM Cloud cluster.
4. Select a project.
5. Click Next.
6. Confirm or edit your workspace name.
7. Select a resource group.
8. Select a Schematics region.
9. Enter tags for your workspace. Tags provide a way to organize, track usage costs, and manage access to the resources in your account.
10. Click Next > Validate.
4. Enter a description for each feature.



* You can remove any feature that you add by clicking Remove feature.



5. Click Save.







 Step 6: Review and submit the digital platform reseller agreement 

If you plan to offer usage-based pricing plans, it is required to review and submit the IBM Digital Platform Reseller Agreement. This legal agreement sets the terms and conditions under which providers can onboard and sell products in IBM Cloud. Or, you can upload a custom digital provider agreement in .pdf, .doc, or .docx file format.

Digital platform reseller agreements and custom digital provider agreements must be reviewed and approved by IBM, which increases the time it takes for you to complete the onboarding process. If you upload a custom digital provider agreement, the uploaded files are scanned for viruses, which might take a few minutes to complete. If a virus is detected, it is recommended to run another virus scan on your file, and then try uploading it again.

Complete the following steps to review and submit the IBM Digital Platform Reseller Agreement:



1. From the My products page in the IBM Cloud Partner Center, click Go to My company in the notification that explains that company details are required.
2. Choose I plan to offer usage-based pricing plans from the Agreements section.
3. Click the IBM Digital Platform Reseller Agreement to review the agreement.
4. Select I read and agree to the IBM Digital Platform Reseller Agreement, and click Save.







 Next steps 

Submit your [request to publish your service](https://cloud.ibm.com/docs/sell?topic=sell-svc-publish) to the IBM Cloud catalog.
* UI
* API







 Updating your company and product details 

As an account administrator, you can update your company and product details in the IBM Cloud® Partner Center. The details include the name of the product that you're onboarding and the name and email address of the primary contact for the product.



 Updating your partner information by using the console 



1. In the IBM Cloud console, click the Navigation Menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/icon_hamburger.svg) > Partner Center > Sell > My Products.
2. Select your product.
3. Click Dashboard.
4. To update the company name or primary contact, click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/edit-tagging.svg) next to each field.

To update the primary contact, the user must already be a member of your account. For more information, see [Inviting team members to help onboard software](https://cloud.ibm.com/docs/sell?topic=sell-sw-invite-team).







 Updating your partner information by using the API 

You can update your partner information only through the UI. To view the steps, go to updating your partner information by using the console.





 Updating your company information by using the console 



1. In the IBM Cloud console, click the Navigation Menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/icon_hamburger.svg) > Partner Center > Sell > My products.
2. Select your product.
3. Click Edit company in the Company section.
ENCRYPTION Optional. To provision your service instance to use customer-managed encryption, append -p '{"kms_info": {"id": <kms_instance_id>, "url": <kms_url>}, "kms_key": {"id": <kms_root_key_id>, "crn": <kms_transaction_crn>}}. 
 INSTANCE_NAME The name for your service instance. 
 PLAN The name or ID of the pricing plan that you want to use. To find the names and IDs of the available plans, run ibmcloud catalog service continuous-delivery. 
 REGION The region in which to provision the service instance. For example, us-south. 
 RESOURCE_GROUP The name or ID of the resource group in which to provision the service instance. To find the names and IDs of the available resource groups, run ibmcloud resource groups. 



For more information about plan IDs or about how to update your service plan after you create an instance, see [Updating your service plan](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-changing).





 Creating a Continuous Delivery service instance with the API 



1. [Obtain an IAM bearer token](https://cloud.ibm.com/apidocs/resource-controllerauthentication). 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 RESOURCE_CONTROLLER_APIKEY={iam_api_key}
2. [Look up the ID of the resource group](https://cloud.ibm.com/apidocs/resource-controller/resource-managerlist-resource-groups) in which you want to create your instance.
3. Choose the region in which you want to create your instance.
4. [Look up the ID of the service plan](https://globalcatalog.cloud.ibm.com/search?q=continuous-delivery) of the instance that you want to create.
After you accept the commitment quote, you receive an additional email to confirm that your payment information is processed and that the commitment is added to your account.





 Viewing your commitment quote 

After you contact [IBM Cloud Sales](https://www.ibm.com/cloud?contactmodule) and sign up for a commitment, you receive a quote. The commitment quote details your contract period, duration of the commitment, billing frequency, UOM, discount, and commitment terms. The sales team will email you a copy of your quote.





 Viewing your commitment usage 

The Commitments and subscriptions page provides the usage details for any commitment on the account. You can track your usage month to month for a detailed view of your commitment usage history. To access this information, you need an access policy with the viewer role or higher on the billing account management service. See [IAM access](https://cloud.ibm.com/docs/account?topic=account-userroles) for more information.

To view your platform and service subscription usage in the IBM Cloud® console, go to Manage > Billing and usage, and select Commitments and subscriptions.



* Click the tabs to view information about active or upcoming commitments. Active commitments are commitments that still have a remaining committed amount to spend and time that's left in the commitment term. Upcoming commitments are commitments that were added to the account but haven't yet reached their term period. A commitment is inactive if its term expires or all of its committed amount is spent.
* Use the graph to view what you've spent toward your overall committed amount. You can view the days remaining in the commitment, discount, billing method, and billing frequency.
* View a monthly breakdown of the spending history for the commitment. Monthly spending is broken out by month. You can manage your commitment by viewing any change in spending month to month and by viewing your spending trends over time.







 Remaining commitment 

If you don't spend the total committed amount by the end of the commitment term, you are invoiced for the amount that you didn't consume.