vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If you have a federated user ID, instead use the following command to log in with your single sign-on ID. See [Logging in with a federated ID](https://cloud.ibm.com/docs/account?topic=account-federated_id) to learn more.

ibmcloud login --sso
2. Target a Cloud Foundry org and space:

ibmcloud target --cf

If you don't have an org or a space set up, see [Adding orgs and spaces](https://cloud.ibm.com/docs/account?topic=account-orgsspacesusers).
3. From within the get-started-php directory push your app to IBM Cloud

ibmcloud cf push

This can take a minute. If there is an error in the deployment process you can use the command ibmcloud cf logs <Your-App-Name> --recent to troubleshoot.



When deployment completes you should a message indicating that your app is running. View your app at the URL listed in the output of the push command. You can also issue the following command to view your apps status and see the URL.

ibmcloud cf apps

You can also go to the IBM Cloud [resource list](https://cloud.ibm.com/resources) to view your app.





 Step 5: Add a database 

Next, we'll add an IBM Cloudant NoSQL database to this app and set up the app so that it can run locally and on IBM Cloud.



1. In your browser, log in to IBM Cloud and go to the Dashboard. Select Create resource.
2. Search for IBM Cloudant, and select the service.
3. For Available authentication methods, select Use both legacy credentials and IAM. You can leave the default settings for the other fields. Click Create to create the service.
4. In the navigation, go to Connections, then click Create connection. Select your app, and click Connect.
5. Using the default values, click Connect & restage app to connect the database to your app. Click Restage when prompted.
[MAS-MS-IBMid-Create-Account](https://cloud.ibm.com/docs-content/v1/content/ce5408d6eecb7244ea40dac01f6d3acf7ff60148/mas-saas/images/MAS-MS-IBMid-Create-Account.png)

Figure 5. IBMid Create Account
6. Accept IBM Account Privacy notification by clicking Proceed

Zoom

![MAS-MS-IBMid-Privacy](https://cloud.ibm.com/docs-content/v1/content/ce5408d6eecb7244ea40dac01f6d3acf7ff60148/mas-saas/images/MAS-MS-IBMid-Privacy.png)

Figure 6. IBMid Privacy Notification
7. Your new IBMid will be created and registration completed:

Zoom

![MAS-MS-IBMid-Ready](https://cloud.ibm.com/docs-content/v1/content/ce5408d6eecb7244ea40dac01f6d3acf7ff60148/mas-saas/images/MAS-MS-IBMid-Ready.png)

Figure 7. IBMid Ready

Zoom

![MAS-MS-IBMid-Activated](https://cloud.ibm.com/docs-content/v1/content/ce5408d6eecb7244ea40dac01f6d3acf7ff60148/mas-saas/images/MAS-MS-IBMid-Activated.png)

Figure 8. IBMid Activated



After verification/creation of your IBMid is complete, proceed to the next section [How to Register for MAS SaaS Support Services](https://cloud.ibm.com/docs/mas-saashow-to-register-for-mas-support)





 How to Register for Maximo Application Suite Support 

Maximo Application Suite Support covers support for both the application and your MAS SaaS environments.



1.
[Key Protect](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-tutorial-kp-encrypt-bucket)

Before you get started, you need:



* An instance of [IBM Cloud™ Key Protect](https://cloud.ibm.com/docs/key-protect?topic=key-protect-getting-started-tutorial)
* [Grant service authorization](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-kpkp-sa) to Object Storage in IBM Key Protect.





1. Toggle Key management disabled to enable encryption and click on Create new instance.
2. Choose a region that corresponds with the bucket, give it a memorable name, and click Create and continue.
3. Give the root key a name and click Create and continue.



[Activity Tracker](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-tracking-cos-events)

Before you get started, you need:



* An instance of [Activity Tracker](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-getting-started)
* A user ID with [administrator platform permissions](https://cloud.ibm.com/docs/account?topic=account-userroles) and the service access [writer role](https://cloud.ibm.com/docs/account?topic=account-userrolesservice_access_roles).





1. Scroll down to the Monitoring and activity tracking section and toggle the radio button to Activity tracking enabled. Select an appropriate plan, and give the new instance a memorable name. As you may likely want to create the Activity Tracker instance in the same region as the bucket (e.g. us-east) you could name the instance something like US East AT so that you can easily find it later.
2. Click to enable Track data events and select both read & write from the drop-down list.
Install the IBM Cloud CLI and the VPC CLI plug-in (see the [CLI prerequisites](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentcli-prerequisites-setup)).
2. After the installation of the VPC CLI plug-in, set the target to generation 2 by running the ibmcloud is target --gen 2 command.
3. Make sure that you [created an IBM Cloud VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-clicreate-a-vpc-cli).
4. Configure a floating IP so that you can ping the virtual servers over the floating IP address and SSH into them.
5. Create a trusted profile. For more information, see [Establishing trust with compute resources](https://cloud.ibm.com/docs/account?topic=account-create-trusted-profile&interface=uicreate-profile-compute-ui).







 IAM authorizations for linking trusted profiles 

To link a trusted profile to an instance, you must have sufficient authorization. With the correct IAM permissions, you can see all trusted profiles that are linked to an instance in the UI.

Verify that your access permissions are assigned as Administrator or Editor:

In the UI,



1. Go to [Manage access and users](https://cloud.ibm.com/iam/users).
2. Click Users, select your name, and click Access policies.



From the API, make a GET /iam-identity.profile.get call.

If you need to update your profile, make these calls:



* POST /iam-identity.profile.update
* POST /iam-identity.profile.linkToResource



For more information, see the [IAM API reference](https://cloud.ibm.com/apidocs/iam-identity-token-apicreate-link-permissions).





 Using trusted profiles for compute resource identities
Step 3. Create a bucket 

Buckets are a way to organize your data in an IBM Cloud Object Storage instance.

To manage buckets, your user must be granted permissions to work with buckets on the IBM Cloud Object Storage instance. For more information about roles, see [Identity and Access Management roles](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-iam).

To create a bucket, your user must have manager or writer permissions for the IBM Cloud Object Storage instance.

Complete the following steps to create a bucket:



1. From the Navigation menu, select Resource List.
2. Select the IBM Cloud Object Storage instance where you plan to create the bucket.
3. Select Buckets. Then, click Create Bucket.

If you are configuring archiving in an EU-managed location, you must configure a bucket that complies with the EU-managed and GDPR regulations.
4. Enter a bucket name for the Unique bucket name field.

Note: All buckets in all regions across the globe share a single namespace.

You can use as part of the bucket name your IBM Cloud Activity Tracker instance name. For example, for an instance with name logging-1, you can use accountN-logging-1 as your bucket name.

You will need this name to configure archiving through the IBM Cloud Activity Tracker web UI.
5. Choose the type of resiliency and a location where you would like your data to be physically stored.

Resiliency refers to the scope and scale of the geographic area across which your data is distributed.

Cross Region resiliency will spread your data across several metropolitan areas.

Regional resiliency will spread data across a single metropolitan area.

A Single Data Center will only distribute data across devices within a single site.

For more information, see [Select regions and endpoints](https://cloud.ibm.com/docs/services/cloud-object-storage?topic=cloud-object-storage-endpoints).
6. Choose the type of Storage class.

You can create buckets with different storage classes.
Choose one of the following options to grant your user permissions:



* [Using the console to assign access](https://cloud.ibm.com/docs/account?topic=account-account-servicesconsole-acct-mgmt)
* [Using the CLI to assign access](https://cloud.ibm.com/docs/account?topic=account-account-servicesusing-the-cli-to-assign-access)
* [Using the API to assign access](https://cloud.ibm.com/docs/account?topic=account-account-servicesapi-acct-mgmt). Use the serviceNameatracker.







 Step 3: Provision an Activity Tracker hosted event search instance 

Complete the following steps:



1. Provision an Activity Tracker event search instance. See [Provisioning an instance](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-provision).
2. [Copy the ingestion key](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-ingestion_key).







 Step 4: Define a target 

After you create the instance, you can configure a target in a region. The target defines where auditing events in that region are collected.

Complete the following steps to create a target in the US-South region in your account:



1. Get an access token.

You need an IAM access token to authenticate in IBM Cloud.

To generate an IAM access token, run the following command:

export ACCESS_TOKEN=ibmcloud iam oauth-tokens | grep IAM | cut -d : -f 2 | sed 's/^ //'

The access token is only valid for 1 hour.
2. [Create a target](https://cloud.ibm.com/docs/atracker?topic=atracker-targettarget-create). Run the following cURL command:
Creating member of pool r134-3b66d605-6aa5-4166-9f66-b16054da3cb0 under account IBM Cloud Network Services as user test@ibm.com...

ID r134-61f8b000-a90d-4abe-909e-c507dffec565
Port 9090
Target 0716_6acdd058-4607-4463-af08-d4999d983945
Weight 70
Health unknown
Created 2020-08-27T14:59:55.446-05:00
Provision status create_pending
6. Create a listener:

ibmcloud is load-balancer-listener-create r134-99b5ab45-6357-42db-8b32-5d2c8aa62776 7070 tcp --default-pool r134-3b66d605-6aa5-4166-9f66-b16054da3cb0

Sample output:

Creating listener of load balancer r134-99b5ab45-6357-42db-8b32-5d2c8aa62776 under account IBM Cloud Network Services as user test@ibm.com...

ID r134-2847a948-f9b6-4fc1-91c6-f1c49dac3eba
Certificate instance -
Connection limit -
Idle connection timeout 50
Port 7070
Protocol tcp
Default pool r134-3b66d605-6aa5-4166-9f66-b16054da3cb0
Provision status create_pending
Created 2020-08-27T15:16:08.643-05:00
7. Get details about your load balancer:

ibmcloud is load-balancer r134-99b5ab45-6357-42db-8b32-5d2c8aa62776

Sample output:
[Create an instance of the IBM Cloud service](https://cloud.ibm.com/docs/account?topic=account-externalappexternalapp).



* Some IBM Cloud services are available only in select regions. You can bind a service to your cluster only if the service is available in the same region as your cluster. In addition, if you want to create a service instance in the Washington DC zone, you must use the CLI.
* For IAM-enabled services: You must create the service instance in the same resource group as your cluster. A service can be created in only one resource group that you can't change afterward.
* Make sure that the service name is in the format myservice or example.com. Spaces and underscores are not allowed.



2. Check the type of service that you created and make note of the service instance Name.



* Cloud Foundry services:

ibmcloud service list

Example output

NAME service plan bound apps last operation
<cf_service_instance_name> <service_name> spark create succeeded
* IBM Cloud IAM-enabled services:

ibmcloud resource service-instances

Example output

NAME Location State Type Tags
<iam_service_instance_name> <region> active service_instance



You can also see the different service types in your IBM Cloud dashboard as Cloud Foundry Services and Services.
3. Identify the cluster namespace that you want to use to add your service.

kubectl get namespaces
4. Bind the service to your cluster to create service credentials for your service that use the public cloud service endpoint and store the credentials in a Kubernetes secret. If you have existing service credentials, use the --key option to specify the name of the credentials. For IAM-enabled services, the credentials are automatically created with the Writer service access role, but you can use the --role option to specify a different service access role. If you use the --key option, don't include the --role option.
Step 1: Provide your company name 



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 > Get started.
2. Enter the name of your company as you want it to be displayed in the catalog, and click Save. For this tutorial, enter Example Corp as the company name.







 Step 2: Create your test environment 

You, or a member of your team, uses the test environment to onboard the Operator bundle and validate that it can be deployed to a Red Hat OpenShift on IBM Cloud cluster. Your test environment includes a private catalog in which you import the Operator bundle from the Red Hat Certified registry.



1. Click Create in the Create your test environment section.
2. Enter Example Corp Catalog as the name of the private catalog, and click Create.







 Step 3: Set up access for your team 

You can enlist team members to help with the onboarding process by assigning them specific levels of IBM Cloud Identity and Access Management (IAM) access. Create an access group to streamline the process of assigning access.



1. Click Assign in the Assign access section.
2. Enter Example Corp Bundle as the name of the access group, and click Create. The following roles are assigned to the access group by default:



* Administrator on the Catalog Management service
* Editor on the Partner Center - Sell service
* Editor on the User Management service
* Editor on the IAM Access Groups service
* Viewer on all account management services





For more information about the actions associated with each role, see [Actions and roles for account management services](https://cloud.ibm.com/docs/sell?topic=account-account-servicesaccount-management-actions-roles).





 Step 4: Add team members to your account 

After you create the Example Corp Bundle access group, you're ready to add team members to your account and access group.
Generate an API key, then request a refresh token. For more information, see [Generating an IBM Cloud IAM token by using an API key](https://cloud.ibm.com/docs/account?topic=account-iamtoken_from_apikey).
2. Copy one of the following example requests and replace the variables that you want to use.

Example request to create a version 2.2 configuration.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ "config-name": "string", "controller": "string", "storage-class-parameters": [ { "additionalProp1": "string", "additionalProp2": "string", "additionalProp3": "string" } ], "storage-template-name": "ibm-object-storage-plugin", "storage-template-version": "2.2", "update-assignments": true, "user-config-parameters": { "entry.name": "HELM-RELEASE-NAME", { "entry.name": "PARAMETERS", { "entry.name": "LICENSE", { "entry.name": "S3PROVIDER", { "entry.name": "COS-STORAGECLASS", { "entry.name": "COS-ENDPOINT","user-secret-parameters": }







 Creating a storage assignment in the console 

If you didn't assign your configuration to a cluster or service when you created it, you can create an assignment by completing the following steps.



1. Open the [Satellite console](https://cloud.ibm.com/satellite/locations) in your browser.
2. Select the location where you created your storage configuration.
3. Click the Locations tab, then click Storage.
4. Click the storage configuration that you want to assign to a cluster group.
5.
Complete the following steps to provision a VPC VSI so that you can run cURL commands to create a target and a route in your account:



1. [Generate an ssh key](https://cloud.ibm.com/docs/vpc?topic=vpc-ssh-keys).
2. [Create a VSI](https://test.cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers) in your account.
3. [Connect to the VSI](https://test.cloud.ibm.com/docs/vpc?topic=vpc-vsi_is_connecting_linux) from a terminal in your local environment.
4. After you ssh into the VSI, [install the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli). Run the following command:

curl -fsSL https://clis.cloud.ibm.com/install/linux | sh



You can run the following command to check that you can access the private endpoints:

ping private.{region}.atracker.cloud.ibm.com

For example, you can run the following command to check access to the Dallas region:

ping private.us-south.atracker.cloud.ibm.com
In the IBM Cloud console, click Manage > Access (IAM), and select Authorizations.
2. Click Create.
3. Select a source account.



* If the source service that needs access to the target service is in this account, select This account.
* If the source service that needs access to the target service is in a different account, select Other account. Then, enter the Account ID of the source account.



4. Select a Source service as App Configuration.
5. Specify whether you want the authorization to be for all resources or Resources based on selected attributes. If you selected Resources based on selected attributes, then specify the Add attributes: only source resource group or only source service instance.
6. Select a Target service as Event Notifications.
7. For the target service, specify whether you want the authorization to be for all instances, only to a specific instance in the account, or instances only in a certain resource group.
8. Select a role to assign access to the source service that accesses the target service.
9. Click Authorize.







 Creating an authorization by using the CLI 

To authorize a source service to access a target service, run the ibmcloud iam authorization-policy-create command.

For more information about all of the parameters that are available for this command, see [ibmcloud iam authorization-policy-create](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_iamibmcloud_iam_authorization_policy_create).
If the CLI is installed, continue with the next step.
2. Log in to the region in the IBM Cloud where you want to provision the instance. Run the following command: [ibmcloud login](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cliibmcloud_login)
3. Set the resource group where you want to provision the instance. Run the following command: [ibmcloud target](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cliibmcloud_target)

By default, the default resource group is set.
4. Create the instance. Run the [ibmcloud resource service-instance-create](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_service_instance_create) command:

ibmcloud resource service-instance-create NAME sysdig-secure SERVICE_PLAN_NAME LOCATION

Where

NAME is the name of the instance.

service-name is the name of the IBM Cloud Security and Compliance Center Workload Protection service name in the IBM Cloud.

SERVICE_PLAN_NAME is the type of plan. See [Service plans](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-pricing_plans) to get the plan name.

LOCATION is the region where the instance is created.
5. Create the service key that connects to the instance [ibmcloud resource service-key-create](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_service_key_create)

ibmcloud resource service-key-create NAME ROLE_NAME --instance-name SERVICE_INSTANCE_NAME

Where

NAME is the name of your new service key

ROLE_NAME is either Administrator, Manager, Writer, or Reader

SERVICE_INSTANCE_NAME is the name of the instance you created
[MAS-MS-IBMid-Enter-Applicable-Information](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/MAS-MS-IBMid-Enter-Applicable-Information.png)

Figure 2. IBMid - Enter Applicable Information
4. Upon submission, a confirmation code will be sent from ibmacct@iam.ibm.com to the email address you provided

Zoom

![MAS-MS-IBMid-Confirmation-Code](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/MAS-MS-IBMid-Confirmation-Code.png)

Figure 3. MAS-Dedicated IBMid Confirmation Code
5. Open your email and copy & paste the 7 digit confirmation code (Verification token). Click Create Account to activate your IBMid

Zoom

![MAS-MS-IBMid-Confirmation-Code-Email](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/MAS-MS-IBMid-Confirmation-Code-Email.png)

Figure 4. MAS-Dedicated IBMid Confirmation Code Email

Zoom

![MAS-MS-IBMid-Create-Account](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/MAS-MS-IBMid-Create-Account.png)

Figure 5. MAS-Dedicated IBMid Create Account
6. Accept IBM Account Privacy notification by clicking Proceed

Zoom

!
For more information, see the tutorial for [Getting started with Terraform on IBM Cloud®](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started). The plug-in abstracts the IBM Cloud APIs that are used to complete this task.
* Create a Terraform configuration file that is named main.tf. In this file, you define resources by using HashiCorp Configuration Language. For more information, see the [Terraform documentation](https://www.terraform.io/docs/language/index.html).







 Inviting users in the console 

To invite users, complete the following steps:



1. In the IBM Cloud console, click Manage > Access (IAM), and select Users.
2. Click Invite users.
3. Specify the email addresses of the users. If you are inviting more than one user with a single invitation, they are all assigned the same access.

You can restrict membership to your account based on the domain of the users that are invited. This way, only users from a specific domain can be invited to the account. For more information, see [Restrict user domains for account invitations](https://cloud.ibm.com/docs/account?topic=account-restrict-acct-invite).
4. Add one or more of the access options that you manage. You must assign at least one access option. For any access options that you don't add and configure, the default value of No access is assigned. Depending on the options that you are authorized to manage, you can assign the following types of access:



* Add users to access groups. Click Add for each access group that you want the users to belong to.
* Manually assign users access. Expand the section to assign individual IAM access policies or classic infrastructure permissions.



* Select Classic infrastructure, and then choose from the three permission sets.
* Select a group of services like All Identity and Access enabled services, All Account management services, and All IAM Account Management services, or a specific service.