vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Managing and monitoring the deployment 

For deployment process monitoring, IBM Cloud Schematics monitoring interfaces are used. The same interface is used to audit and capture all user actions and relevant security events.

For more information, see [Getting started: IBM Cloud Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-getting-started), [Monitoring Schematics services by using IBM Cloud Monitoring](https://cloud.ibm.com/docs/schematics?topic=schematics-monitoring-instances) and [Auditing events](https://cloud.ibm.com/docs/schematics?topic=schematics-at_events).



  Infrastructure and landscape management and monitoring after deployment 

For monitoring and management of provisioned resources, VPC and PowerVS interfaces are used. The same interface is used to audit and capture all user actions and relevant security events.

For more information, see [IBM Cloud VPC documentation](https://cloud.ibm.com/docs/vpc?topic=vpc-about-vpc) and [IBM Cloud PowerVS documentation](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-getting-started).

The following landscape provisioning options are not deployed with this automation and can be added after deployment:



*  [IBM Spectrum Protect on IBM Cloud deployment guide](https://www.ibm.com/support/pages/node/6498661)
*  [Tutorial - HA configuration for SAP RHEL solutions](https://cloud.ibm.com/docs/sap?topic=sap-ha-rhel)
*  [High-availability configuration for SAP NetWeaver](https://cloud.ibm.com/docs/sap?topic=sap-netweaver-design-considerationsnetweaver-ha)
*  [SAP HANA High Availability and Disaster Recovery (HA/DR)](https://cloud.ibm.com/docs/sap?topic=sap-hana-design-considerationshana-ha)







  Lifecycle management 

Lifecycle management with SAP solution provisioning by using deployable architectures is limited to initial landscape deployments. Landscape update is not supported and must be done manually.
Managing gateways 

Manage gateways in API Connect Reserved by defining whether they are available to users, and whether they are included in new catalogs.



 Controlling a gateway's visibility 

A gateway's visibility setting determines which provider organizations can use the gateway. If you deploy multiple gateways, you might want to assign each gateway to a specific set of provider organizations.



1. On the administration console's home page, click Gateways.
2. On the "Gateways" page, locate the gateway in the table. At the end of the row, click ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/images/icon_options.png) > Set visibility.
3. On the "Set visibility of gateway" page, select the visibility level for the current gateway.
4. If you selected the Custom option, use the "Provider organizations" panel to specify which provider organizations can use the gateway:

a. Locate a provider organization:



* Click the Search for provider organizations field to display a list of provider organizations.
* Type a string in the Search for provider organizations field to filter the list of provider organizations.



b. Click the name of the provider organization to select it.
5. Click Save to save the visibility settings.







 Specifying default gateways for catalogs 

Members of a provider organization publish APIs by adding them to a product and then publishing the product to a catalog. The catalog must be assigned at least one gateway so that the APIs can be called using the gateway endpoint. To ensure that new catalogs have access to gateways, you can assign default gateways that are automatically added to every new catalog.



1. On the administration console's home page, click Settings.
2. On the "Default gateways" page, click Edit.
3. In the "Specify default gateways" page, select all of the gateways that you want to be available to new catalogs.
4. Click Save to apply the new setting.
[SSP-AM-Approve-Reject-Access-4](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-AM-Approve-Reject-Access-4.png)







 Access Re-Validation 

Continued business need (CBN) for accesses provided through the Self-Service portal access management tool must be validated annually.

The re-validation process is run on an annual basis for all users, so it is possible that you will be notified of the need to re-validate less than a year after access is granted. You will receive an email when validation is required. Until that time the “Re-validate CBN” button will not be available on the “Manage Access” tab as indicated below.

When notified of the need to re-validate, follow these steps to review your current accesses and re-validate your need to keep them.



1. Sign into the Self-Service Portal: [https://devops.maximo.com](https://devops.maximo.com)
2. Navigate to the Access Management application by selecting the drop down menu in the top left of the window and selecting Security → Access Management.

![SSP-AM-Access-Revalidation-1](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-AM-Access-Revalidation-1.png)
3. Select your IBMid from the list and proceed to the "Manage Access" tab. There you will see tables with all the assets and associated accesses. Remove any accesses you no longer have a business need for and press the “Save” button.

!
Managing roles and privileges 

A role is a set of privileges that is assigned to a user to allow the user to perform and manage certain tasks in IBM® watsonx.data.

watsonx.data provides a set of predefined roles: Administrator, User, Manager, Writer, and Reader.

Use the Access control page to manage users and roles in watsonx.data. For more information, see [Managing user access](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-manage_access).

The following tables describe the privileges that you can assign to roles and associated permissions:



 Engine (Presto) 



Table 1. Roles and privileges for an engine

 Privileges Administrator Manager User without a role 

 Delete an engine Y N N 
 Grant access Y N N 
 Revoke access Y N N 
 Pause an engine Y Y N 
 Resume an engine Y Y N 
 Restart an engine Y Y N 
 Associate a catalog Y Y N 
 Disassociate a catalog Y Y N 
 Access the Presto query monitor UI Y Y N 
 View existence Y Y N 







 Catalog 



Table 2. Roles and privileges for a catalog

 Privileges Administrator User User without a role 

 Delete a catalog Y N N 
 Grant access Y N N 
 Revoke access Y N N 
 Create any schema Y N N 
 Drop any schema Y N N 
 Select from data Y Y N 
 Drop own schema Y N N 
 View existance Y Y Y 







 Bucket 



Table 3. Roles and privileges for a bucket

 Privileges Administrator Writer Reader User without a role 

 Unregister Y N N N 
 Update bucket properties (credentials) Y N N N 
 Grant access Y N N N 
 Revoke access Y N N N 
 Create catalog Y N N N 
 Modify files into the bucket Y Y N N 
 Browse (bucket browser in UI) Y Y Y N 
 View existance Y Y Y Y 







 Database 



Table 4. Roles and privileges for a database

 Privileges Administrator Writer Reader User without a role 

 Unregister Y N N N 
 Update database connection properties (credentials) Y N N N
The new user will be created once the backend processing is completed. You will know the new user was successfully created when the user status changes to "ACTIVE". The new user will receive an email with instructions on how to login to the Self-Service Portal once their user is activated.







 How to Approve / Reject an Access Request 

Managers in the Access Management application are responsible for approving/rejecting access requests submitted by users assigned to their customer/vendor. Managers will receive an email when a user with their customer/vendor assignment submits an access request.

Follow these steps to review an access request if your user role is Manager.



1. Sign into the Self-Service Portal: [https://devops.maximo.com](https://devops.maximo.com)
2. Navigate to the Access Management application by selecting the drop down menu in the top left of the window and selecting Security → Access Management. The initial screen will show a list of users that you have access to manage and process access requests for.

![SSP-AM-Approve-Reject-Access-1](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-AM-Approve-Reject-Access-1.png)
3. Select your IBMid from the list and proceed to the "Access Approvals" tab. There you will see a table with all the access requests that you can process.

![SSP-AM-Approve-Reject-Access-2](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-AM-Approve-Reject-Access-2.png)
4. Open the details on the request you want to process by choosing the twistie (>) to the left of the user.

!
Managing VMware HCX 



 Accessing the HCX management consoles 

To manage the VMware HCX® service, you must access the HCX Cloud console or the HCX Manager Admin console:



1. Use the IBM Cloud® infrastructure VPN or a jump server to allow access to the IP address of the HCX Manager virtual appliance (HCX Manager). You can find the IP address on the HCX service details page in the IBM Cloud for VMware Solutions console.
2. To access the HCX Cloud console, click View HCX Cloud console on the HCX service details page, and then log in by using the VMware vCenter Server® credentials.
3. To access the HCX Manager Admin console, click View HCX Manager Admin console on the HCX service details page. Then, log in by using the HCX Manager credentials that are listed on the same service details page.



For more information, see [Ordering services for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservices).





 Applying updates to HCX 

HCX is deployed with the most recently tested build of VMware Hybrid Cloud Extension technology. VMware® provides updates to the builds regularly, which include important fixes and new features. These builds are pushed to HCX installations automatically, including on-premises HCX installations.

To apply any maintenance fixes pushed to your environment, you must use the HCX Manager Admin console in your on-premises data center and your vCenter Server instance.

Open an IBM Support ticket by following the steps in [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support) for the following situations:



* You do not see a build update that you are expecting
* You have problems with HCX
* You want to have the most recent HCX build pushed to your system immediately







 Related links
Managing VLANs 

You can manage the VLAN associated with your FortiGate Security Appliance (FSA) 10 Gbps with the instructions here.

First, go to the Device Overview page. Then, click VLANs in the side navigation, Manage in the Status Module, or the Manage All link in the VLAN module.



  Associating a VLAN with a firewall 

Click Add VLAN and select a VLAN from the menu. Then, click Save and confirm your selection. The VLAN association action does not route the VLAN through the firewall.





  Disassociating a VLAN with a firewall 

Select your VLAN by toggling the checkboxes. Then, click Disassociate and confirm your selection. If the VLAN is routed through the firewall, this action routes the VLAN around the firewall before disassociation.





  Routing a VLAN around a firewall 

Select your VLAN by toggling the checkboxes. Then, click Route Around and confirm your selection.





  Routing a VLAN through a firewall 

Select your VLAN by toggling the checkboxes. Then, click Route Through and confirm your selection.
Managing a REST Service in API Connect V5 

These tutorials provide options on how you can manage existing APIs.

To manage an existing API, you can start by importing or adding an OpenAPI file.



  IBM Cloud 



*  [Importing an OpenAPI file by using IBM Cloud](https://cloud.ibm.com/docs/apiconnect/tutorials?topic=apiconnect-tut_import_openapi_rest_bmtut_import_openapi_rest_bm)
*  [Creating an OpenAPI file by using IBM Cloud](https://cloud.ibm.com/docs/apiconnect/tutorials?topic=apiconnect-tut_add_openapi_rest_bm)







  Developer Toolkit 



*  [Importing an OpenAPI file by using the Developer Toolkit](https://cloud.ibm.com/docs/apiconnect/tutorials?topic=apiconnect-tut_import_openapi_rest_tk)
*  [Creating an OpenAPI file by using the Developer Toolkit](https://cloud.ibm.com/docs/apiconnect/tutorials?topic=apiconnect-tut_add_openapi_rest_tk)
Organizations can employ templates to help ensure consistent and timely development and implementation of configuration management plans. Such templates can represent a master configuration management plan for the organization at large with subsets of the plan implemented on a system by system basis. Configuration management approval processes include designation of key management stakeholders responsible for reviewing and approving proposed changes to information systems, and personnel that conduct security impact analyses prior to the implementation of changes to the systems. Configuration items are the information system items (hardware, software, firmware, and documentation) to be configuration-managed. As information systems continue through the system development life cycle, new configuration items may be identified and some existing configuration items may no longer need to be under configuration control.
Managing virtual appliances 

Virtual appliance is bring-your-own license model, where independent software vendors (ISV) can offer OVA (ISV software plus operating system of your choice) for quick deployment of Power Systems Virtual Server workloads. It is an appliance-as-a service that allows seamless management and metering of PowerVS. Software support is handled directly by the ISVs for virtual appliances.

With virtual appliances, you can use additional services within Power Systems Virtual Server such as virtual tape libraries. For more information, see [Managing Virtual tape library](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-managing-virtual-tape-library).



 Onboarding your virtual server images for Power Systems Virtual Servers 

Independent software vendors can sell software on the IBM Cloud platform by enrolling their account in the Partner Center and by completing the onboarding process from the IBM Cloud catalog. If you are an ISV and want to sell your software, see [Selling on IBM Cloud](https://cloud.ibm.com/docs/sell?topic=sell-selling-clouds).

As part of the onboarding process for selling Power Systems Virtual Server software, sellers must provide a public (shareable) virtual server image asset. To provide a public virtual server image for Power Systems Virtual Server, complete the following steps:



1. Create your [Power Systems Virtual Server instance](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-creating-power-virtual-server).
2. Create an instance of [IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage) and upload your image to a bucket.
3. Create your [HMAC credentials](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-uhc-hmac-credentials-main).
4.
Managing firewall device details 

You can see the device details for a FortiGate Security Appliance 10 Gbps by clicking the link for the device under the Firewall Name column. This link directs you to the Device Overview page.



  Restoring default firewall settings 

To reset your device back to its factory settings, select the overflow menu, then select Restore Defaults from the menu.





  Accessing the FSA portal 

To log in to the Device Portal, you need your management credentials. Locate the device username and password in the General Information section.

Toggle showing your device password by selecting the Eye icon.

In your web browser, enter the public IP for the FortiGate listed in the General Information section, making sure to precede it with https://. Then use your management credentials to log in.
Managing Users, Roles, and Privileges 

MySQL 5.7 uses a system of roles to manage database permissions. You are able to create users from both the UI and from [MySQL Shell](https://dev.mysql.com/doc/refman/5.7/en/privileges-provided.html). Users who are created from the UI have nearly identical privileges as admin, but cannot create other users. Since admin has both CREATE USER and GRANT options, it can create a user and give them all the privileges that it has, including the privilege to create new users.

mysql> SELECT DISTINCT GRANTEE FROM information_schema.user_privileges;
+-----------------------------+
 GRANTEE 
+-----------------------------+
 'ibm'@'localhost' 
 'mysql.session'@'localhost' 
 'mysql.sys'@'localhost' 
 'ibm-backup'@'localhost' 
 'admin'@'%' 
 'ibm-replication'@'%' 
 'ibm-monitor'@'%' 
+-----------------------------+
+-----------------+
 user 
+-----------------+
 admin 
 ibm-monitor 
 ibm-replication 
 ibm 
 ibm-backup 
 mysql.session 
 mysql.sys 
+-----------------+
Show more

The users below are maintained by IBM Cloud and shouldn't be altered or deleted by you:

 ibm-monitor 
 ibm-replication 
 ibm 
 ibm-backup
Access management in IBM Cloud 

After deciding how to [organize your accounts and resources](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-account-organization), you will need to properly manage access for deployments of the reference architectures that will help achieve [separation of duties and least privilege](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-least-privilege).



 Managing access with access groups 

An [access group](https://cloud.ibm.com/docs/account?topic=account-groups) is a grouping of user and service IDs to which the same IAM access can be granted. You can assign a single policy to the group instead of assigning the same access multiple times per individual user or service ID. A logical way to assign access is by creating one access group per wanted level of access.

Always use access groups for managing access. IAM policies should never be attached directly to users.

For more information:



* [IAM access](https://cloud.ibm.com/docs/account?topic=account-userroles) for definitions of platform management roles and service access roles.
* [Giving access to resources in resource groups](https://cloud.ibm.com/docs/account?topic=account-rgs_manage_access)
* [Best practices for assigning access](https://cloud.ibm.com/docs/account?topic=account-account_setup) for more details about working with IAM.



You must determine what set of access groups works well for your situation. Whatever structure you choose, repeat it for every account (whether a stand-alone account or part of an enterprise).



 Example access group structure 

For illustration, the following table shows one possible setup that provides for a reasonable separation of duties.



Table 1. Access groups

 Access Group Description 

 cloud-organization-admins Responsible for organizing the structure of the resources used by the organization.
Managing your IBM Cloud HSM 

From the Device List, you can manage your IBM Cloud® Hardware Security Module (HSM), virtual servers, and bare metal servers.



  Before you begin 



*  Go to your console's device menu. For more information, see [Navigating to devices](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-navigating-devices).
*  Make sure that you have any necessary account permissions and device access. Only the account owner, or a user with the Manage Users classic infrastructure permission, can adjust the permissions.



For more information about permissions, see [Classic infrastructure permissions](https://cloud.ibm.com/docs/account?topic=account-infrapermissioninfrapermission) and [Managing device access](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-device-access).

In the device list, virtual servers have a device type of Virtual. Bare metal servers are indicated with the device type of Server. Dedicated hosts have a device type of Dedicated Virtual Host. HSM has a device type Security Module.

Complete the following step to perform management tasks for your virtual servers from the Device List in the IBM Cloud infrastructure customer portal:



1.  Click Actions for the device that you want to manage and select the wanted management task.







  Deleting the server instance 

At any time, you can delete your hardware security module if you no longer need the instance and don't want to be charged.

To delete the HSM, go to the menu and select Cancel.





  Powering off an HSM 

While the HSM is powered off, you are still billed.

To power off the HSM, go to the menu and select Power On/Off.

If the HSM is powered off, it remains in the power off state and you must manually power it on.
Working with global IP addresses 

You can manage your global IP addresses in the Subnets page.



 Prerequisites 

You must have the following Classic infrastructure permissions to change the routing of global IP addresses:



* Manage Network Subnet Routes
* Allow Access To All Hardware
* Allow Access To All Virtual Servers







 Managing global IP addresses 

To manage global IP addresses, follow these steps:



1. From your browser, open the [IBM Cloud console](https://cloud.ibm.com/) and log in to your account.
2. From the dashboard, click the menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/88335aaac95959c46c027441a146a8971be515cd/icons/icon_hamburger.svg) and select Classic Infrastructure.
3. In the Classic Infrastructure navigation menu, select Network > IP Management > Subnets.
4. Find the global IP address you want to manage. If necessary, use the Filter subnets section, selecting Global as Type to show only the global IP addresses.
5. Click the overflow menu ![overflow menu](https://cloud.ibm.com/docs-content/v1/content/88335aaac95959c46c027441a146a8971be515cd/subnets/images/overflow.png) of the global IP you want to manage.

A global IP is a static IP address that can be routed to any server within the IBM Cloud network. The current static IP address offering can be routed only to an IP address within the same data center, but global IP addresses do not share this restriction.
6. Select the operation you want to perform from the overflow menu.
Managing speaker models 

The Tune by Example feature is beta functionality that is supported only for US English custom models and voices.

Tune by Example includes methods for listing speaker models, listing the prompts for a speaker model, and deleting a speaker model. It also includes the POST /v1/speakers method to create a speaker model; for more information, see [Create a speaker model](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-tbe-createtbe-create-speaker-model).



 Listing all speaker models 

To list all of the speaker models that are defined for a service instance, use the GET /v1/speakers method. The method returns a speakers array that provides the following information for each speaker model:



* speaker_id indicates the speaker model's Globally Unique Identifier (GUID). The GUID is used to identify the speaker in calls to the service.
* name is the user-specified name that was assigned to the speaker model when it was created.



The array is empty if no speaker models are defined for the service instance.



 List all speaker models example 

The following example returns all of the available speaker models for the specified service credentials:

IBM Cloud

curl -X GET -u "apikey:{apikey}" "{url}/v1/speakers"

IBM Cloud Pak for Data

curl -X GET --header "Authorization: Bearer {token}" "{url}/v1/speakers"

The credentials own two speaker models, speaker_one and speaker_two:

{
"speakers": [
{
"speaker_id": "56367f89-546d-4b37-891e-4eb0c13cc833",
"name": "speaker_one"
},
{
"speaker_id": "323e4476-63de-9825-7cd7-8120e45f8331",
"name": "speaker_two"
}
]
}







 Listing the custom prompts for a speaker model