vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Configuration Modification None Providing subject matter expertise and modification of your environment 







 Identity and access management 

Identity and access management includes tasks such as authentication, authorization, access control policies, and approving, granting, and revoking access.



Table 3. Responsibilities for identity and access management

 IBM Responsibilities Your responsibilities 

 Initial root password Ensuring customers have IBM Cloud console access to initial root and nsroot passwords at provisioning Notifying IBM of any issues experienced during provisioning 
 All subsequent password changes None Ensuring root passwords remain consistent in the IBM Cloud console and on production systems 
 Account administration None Designing and implementing VPX user account design goals 







 Security and regulation compliance 

Security and regulation compliance includes tasks such as security controls implementation and compliance certification.



Table 4. Responsibilities for security and regulation compliance

 IBM responsibilities Your responsibilities 

 Critical Patch Notification Notifying customers of the need for critical patches through Event Management Implementing and applying required patches 







 Disaster recovery 

Disaster recovery includes tasks such as providing dependencies on disaster recovery sites, provisioning disaster recovery environments, data and configuration backup, replicating data and configuration to the disaster recovery environment, and failover on disaster events.



Table 5. Responsibilities for disaster recovery

 IBM responsibilities Your responsibilities 

 Backups Applying customer held backups during disaster recovery Keeping up-to-date backups of your current environment
: [Grafeas](https://grafeas.io) is an open source CI/CD service that provides a common way for how to retrieve, store, and exchange metadata during the software supply chain process. For example, if you integrate Grafeas into your app build process, Grafeas can store information about the initiator of the build request, vulnerability scan results, and quality assurance sign-off so that you can make an informed decision if an app can be deployed to production. You can use this metadata in audits or to prove compliance for your software supply chain.

IBM® Continuous Delivery Pipeline for IBM Cloud®
: With your app configuration files organized in a source control management system such as Git, you can build your pipeline to test and deploy code to different environments, such as test and prod. IBM Cloud® Continuous Delivery allows you to automate your app builds and container deployments to Kubernetes clusters by using a toolchain. To get started, see [Setting up a continuous delivery pipeline for a cluster](https://cloud.ibm.com/docs/containers?topic=containers-cicdcontinuous-delivery-pipeline). You can also check out [this tutorial on Continuous Deployment to Kubernetes](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-continuous-deployment-to-kubernetescontinuous-deployment-to-kubernetes).

Helm
: [Helm](https://helm.sh) is a Kubernetes package manager. You can create new Helm charts or use preexisting Helm charts to define, install, and upgrade complex Kubernetes applications that run in IBM Cloud Kubernetes Service clusters. For example, you can specify all Kubernetes resources that your app requires in a Helm chart. Then, you can use Helm to create the YAML configuration files and deploy these files in your cluster. You can also [integrate IBM Cloud-provided Helm charts](https://cloud.ibm.com/kubernetes/helm) to extend your cluster's capabilities, such as with a block storage plug-in.
Administering Planning Analytics as a Service 

Administering Planning Analytics as a Service includes managing users and groups, administering databases, managing environments, migrating assets, and other administrative actions. You access the Administration page from the Administration tile on the Planning Analytics Workspace home page.



* [Administration taks unique to Planning Analytics as a Service](https://www.ibm.com/docs/en/planning-analytics/latest?topic=workspace-administration-capabilities-planning-analytics-as-service)



Most administration tasks are common between Planning Analytics on Cloud and Planning Analytics as a Service. However, some tasks such as quota monitoring, environment management, and some aspects of database management, are unique to Planning Analytics as a Service.



* [Manage users and groups](https://www.ibm.com/docs/en/planning-analytics/latest?topic=workspace-administer-users-groups)



Access to objects and data in Planning Analytics is controlled through users and groups.



* [Migrate assets with Lifecycle Management](https://www.ibm.com/docs/en/planning-analytics/latest?topic=workspace-migrate-assets-lifecycle-management)



Assets such as books and views can be migrated by an administrator from a source environment to target environment using Lifecycle Management.



* [Manage features](https://www.ibm.com/docs/en/planning-analytics/latest?topic=workspace-manage-features)



When some new features are introduced to Planning Analytics as a Service, you can choose to enable or disable the features in your environment. You can manage when and how your users are exposed to new functionality.



* [Set permissions for assets](https://www.ibm.com/docs/en/planning-analytics/latest?topic=workspace-set-permissions-assets)



You must have the Full control permission on an asset to set permissions for that asset.



* [Set permissions on the Shared folder and subfolders](https://www.ibm.com/docs/en/planning-analytics/latest?topic=workspace-set-permissions-shared-folder-subfolders)
A set of business terms that are embedded into a blockchain and executed with transactions. A smart contract can also include a digital representation of a set of business rules and defines conditions under which transfers occur. A smart contract is implemented using chaincode.





 SoE 

See [system of engagement](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx6528306).





 software as a service (SaaS) 

A model of software deployment whereby software including business processes, enterprise applications, and collaboration tools, are provided as a service to customers through the cloud.





 SOLO 

A consensus plugin implementation for Hyperledger Fabric that results in a single ordering service node in the blockchain network.





 SOR 

See [system of record](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx6735061).





 source control management (SCM) 

An aspect of software configuration management that involves managing changes to collections of files.





 SPA 

See [single-page application](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx9829514).





 space 

A sub-group within an IBM Cloud org. Users who are members of an org are given access to one or more of its spaces, with permissions associated with a particular role (such as developer, manager, or auditor). Any member of the space can view apps, but only members with the developer role can create apps and add service instances to the space. Apps and service instances are associated with spaces. See also [organization](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2032585).





 SSH 

See [Secure Shell](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx3574365).





 SSL 

See [Secure Sockets Layer](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2038004).





 SSO
For more information about secrets references, see [Protecting your sensitive data in Continuous Delivery](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-cd_data_securitycd_secure_credentials). 
 evidence_namespace required, updatable String evidence_namespace The type of pipeline evidence to display in Security and Compliance Center for this toolchain. Valid values are cd (uses evidence that is generated by a continuous deployment pipeline) or cc (uses evidence that is generated by a continuous compliance pipeline). 
 evidence_repo_name required, updatable String evidence_repo_url The URL of a Git repo evidence locker. The DevSecOps toolchain templates collect and store evidence for scans and tasks in an evidence repo. Make sure that this URL matches the repo_url for a Git tool integration in this toolchain. The DevSecOps toolchain goals in the Security and Compliance Center check the evidence repo for the pass or fail results for those goals. 
 name required, updatable String name The name of this tool integration. 
 profile optional, updatable, deprecated String profile Deprecated. The name of a Security and Compliance Center hybrid cloud profile. You can use the predefined IBM Cloud Security Best Practices v1.0.0 profile that contains the DevSecOps toolchain goals. Or, you can use a user-authored customized profile that is configured to contain those goals. When the trigger_scan parameter is set to enabled, the Validation scan uses the controls and goals in the configured profile. If the configuration contains a profile that does not check the DevSecOps toolchain goals, it might incorrectly indicate the toolchain status as passed even though some of the DevSecOps scans failed. This parameter is relevant only when the trigger_scan parameter is enabled. 
 scope optional, updatable, deprecated String scope Deprecated. The name of a Security and Compliance Center scope that was previously created in that service. When the trigger_scan parameter is set to enabled, the Validation scan scans all of the resources in that scope.
* Automate the mounting of backups and scanning by your cybertoolsets
* Creating sandboxes



* Sandboxes can be provisioned by using VMware NSX-T™ overlay segments, logical routing, distributed firewall, and network address translation to provide network-isolated zones to mount cyber-recovery backups for inspection by your cybertoolsets.
* Cybertoolsets are customer-supplied tools that run as virtual machines in the isolated recovery environment and access your cyber-backups for verification and analysis.
* Cyberadmins are customer personnel who are authorized to access the isolated recovery environment and should be different than admins that manage the production and disaster recovery environments to promote separation of duties.
* Jump servers are used by your cyberadmins to access the isolated recovery environment.
* The air gap enables network connectivity between the production environment and the isolated recovery environment only when required.
* The solution architecture is independent of the location of the production environment. However, network connectivity is required between the production environment and the cyber-recovery site.



[The definitive guide to ransomware: readiness, response, and remediation](https://www.ibm.com/downloads/cas/EV6NAQR4) provides an overview of ransomware history, its current prevalence, and resources to help fortify organizations and technical-level guidance on techniques to protect networks before an attack can happen. Also, a recovery guidance if an attacker makes it through defenses.



 How to 

Consider using a separate IBM Cloud account to deploy your cyber-recovery instance into. This process promotes separation of duties between ownership of any other production or disaster recovery solution that you might host in IBM Cloud.

To create your custom cyber-recovery solution based on a VMware vCenter Server instance, follow the [procedure to order vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-procedure):



1. In Step 4, select Primary.
2. In Step 7, order a gateway cluster with your preferred firewall option:
curl -X GET https://api.us-south.ae.cloud.ibm.com/v3/analytics_engines/{instance_id} -H "Authorization: Bearer $token"

Sample response:

{
"id": "dc0e-eab2-4t9e-9441-56620949",
"state": "created",
"state_change_time": "2021-04-21T04:24:01Z",
"default_runtime": {
"spark_version": "3.1",
"instance_home": {
"provider": "ibm-cos",
"type": "objectstore",
"region": "us-south",
"endpoint": "https://s3.direct.us-south.cloud-object-storage.appdomain.cloud",
"bucket": "ae-bucket-do-not-delete-dc0e-eab2-4t-9441-566209499546",
"hmac_access_key": "eHg=",
"hmac_secret_key": "4d76"
},
"default_config": {
"spark.driver.memory": "4g",
"spark.driver.cores": 1
}
}
}
Show more
2. Check the value of the "state" attribute. It must be active before you can start running applications in the instance.







 Learn more 

When provisioning serverless instances, follow the recommended [Best practices](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-best-practices-serverless).
If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-command-options-logpush-job-create" "> --><-- <section "id="section-command-example-logpush-job-create" "> --> Examples Create a log push job for domain 31984fea73a15b45779fa0df4ef62f9b. ibmcloud cis logpush-job-create 31984fea73a15b45779fa0df4ef62f9b --destination cos://cis-test-bucket/logs?region=us&instance-id=f75e6d90-4212-4026-851c-d572071146cd --name logpushcreate --enable true --fields all --timestamps rfc3339 --dataset http_requests --frequency low -i cis-demo --output JSON
<-- </section "id="section-command-example-logpush-job-create" "> --><-- </section "id="section-logpush-job-create" "> --><-- <section "id="section-logpush-job-update" "> --> ibmcloud cis logpush-job-update Update a log push job for a given domain (Enterprise plan only). ibmcloud cis logpush-job-update DNS_DOMAIN_ID --destination DESTINATION_URL] --enable true|false] --fields FIELDS | all] --timestamps format] --dataset DATASET] --jobid JOB_ID] --frequency FREQUENCY] -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-command-options-logpush-job-update" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain.
Placement groups 

High availability (HA) is an important aspect of any cloud deployment. Whether it’s the website for your e-commerce business or a production database that is used by your company’s key application—it needs to stay up. To this end, building out resilient infrastructure is something our IT architect clients work hard to implement in the pursuit of ever-higher percentages of “uptime.” Although uptime is closely monitored within IT organizations, it can fall under key levels or take on substantial outages, which are huge problems for the entire business.

Building in redundancy at each level of your infrastructure to eliminate any Single Point of Failure (SPOF) is key to performing well on this metric. For workloads that are running on virtual servers, you can implement failover solutions with multiple virtual servers to automatically cover for each other during a failure.

However, unless your public virtual servers are provisioned into different data centers, your virtual servers can't determine where they are placed in relation to each other. This unknown can be problematic if you’re 1) building for HA and 2) your virtual servers are on the same physical host, leaving them vulnerable to an outage on a single piece of hardware. While that placement is unlikely, IT managers can’t have the possibility of a SPOF for critical applications. Building across data centers is an option, but this option can introduce some network challenges that require extra appliances or increase latency, especially in regions with only a single data center.

The design of placement groups for IBM Cloud® virtual servers solves this issue. Placement groups give you a measure of control over the host on which a new public virtual server is placed. With this release, a “spread” rule is implemented. Meaning that virtual servers within a placement group are all spread onto different hosts. You can build a high availability application within a data center and know that your virtual servers are isolated from each other.

Placement groups with the “spread” rule are available to create in select IBM Cloud data centers. After a "spread" rule is created, you can provision a virtual server into that group and guarantee that won't be on the same host as any of your other virtual servers. The best part? There’s absolutely no charge for using this feature.
Understanding high availability for Security and Compliance Center 

High availability(HA) is a core discipline in an IT infrastructure to keep your apps up and running, even after a partial or full site failure. The main purpose of high availability is to eliminate potential points of failures in an IT infrastructure.



  Responsibilities 

To find out more about responsibility ownership for using IBM Cloud products between IBM and the customer, see [Shared responsibilities for IBM Cloud products](https://cloud.ibm.com/docs/overview?topic=overview-shared-responsibilities).





  What level of availability do I need? 

You can achieve high availability on different levels in your IT infrastructure and within different components of your cluster. The level of availability that is ideal for you depends on several factors. These factors include your business requirements, the service level agreements (SLAs) that you have with your customers, and the resources that you want to expend.





  What level of availability does IBM Cloud offer? 

The level of availability that you set up for your cluster impacts your coverage under the IBM Cloud high availability service level agreement terms.

Service level objectives (SLOs) describe the design points that the IBM Cloud services are engineered to meet. Security and Compliance Center is designed to achieve an availability target of 99.9%.

The SLO is not a warranty and IBM does not issue credits for failure to meet an objective. Refer to the SLAs for commitments and credits that are issued for failure to meet any committed SLAs. For a summary of all SLOs, see [IBM Cloud service level objectives](https://cloud.ibm.com/docs/overview?topic=overview-slo).





  Locations 

For more information about service availability within regions and data centers, see [Service and infrastructure availability by location](https://cloud.ibm.com/docs/overview?topic=overview-services_region).
Scope of Services 

Tririga Application Suite Managed Services - Scope

IBM TRIRIGA Application Suite Managed Service (TAS-MS) is an offering supported by IBM's Cloud Delivery Services and Development Operations team. The Managed Services team is solely focused on TRIRIGA Application Suite delivery, providing expert IT administration for both infrastructure and operations and support for customers through the IBM Support Community Portal. Customers interact with the IBM Managed Services team members via case creation, interaction and followup.

Team members are based out of Canada, the United States, Brazil, Ireland, India, China and Australia. TAS-MS is a subscription based hosting service exclusively offered on the IBM Cloud platform.
The value must match the regular expression /u0008[0-9a-f]{8}u0008-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-u0008[0-9a-f]{12}u0008/.





 Examples 

ibmcloud analytics-engine-v3 instance state --output json

ibmcloud analytics-engine-v3 instance state --id=e64c907a-e82f-46fd-addc-ccfafbd28b09 --output json





 Example output 

{
"id" : "dc0e9889-eab2-4t9e-9441-566209499546",
"state" : "active"
}







 ibmcloud analytics-engine-v3 instance home-set 

Provide the details of the Cloud Object Storage instance to associate with the Analytics Engine instance and use as 'instance home' if 'instance home' has not already been set.

Note: You can set 'instance home' again if the instance is in 'instance_home_creation_failure' state.

ibmcloud analytics-engine-v3 instance home-set [--id ID] [--instance-home-id INSTANCE-HOME-ID] [--endpoint ENDPOINT] [--hmac-access-key HMAC-ACCESS-KEY] [--hmac-secret-key HMAC-SECRET-KEY]



 Command options 

-i, --id (string)
: The ID of the Analytics Engine instance for which 'instance home' is to be set. When specified, it overrides the target instance ID if it was set. Required, if the target instance was not set.
BASIC_AUTH_CREDENTIALS_SOURCE | Set to URL. This instructs the SerDes to use HTTP basic authentication using the credentials supplied in the Schema Registry URL.

You can also optionally provide the following properties to control the schema selection (subject naming strategy):



 Property name Value 

 VALUE_SUBJECT_NAME_STRATEGY TopicNameStrategy(default), RecordNameStrategy, and TopicRecordNameStrategy are supported. For example, to specify that the schema for the message value is selected using a TopicRecordNameStrategy, you might use the following client properties: configs.put(KafkaAvroSerializerConfig.VALUE_SUBJECT_NAME_STRATEGY, TopicRecordNameStrategy.class.getName()); 
 KEY_SUBJECT_NAME_STRATEGY TopicNameStrategy (default), RecordNameStrategy, and TopicRecordNameStrategy are supported. See VALUE_SUBJECT_NAME_STRATEGY for an example. 



The following diagram shows an example of the properties that are required to create a Kafka producer that uses the Confluent SerDes and can be connected to the Event Streams service:

Zoom

![Kafka properties for Confluent Serdes](https://cloud.ibm.com/docs-content/v1/content/e0c3acba1296ff980e76d5db456d53adefaabba4/EventStreams/schema_registry7.png)

Figure 1. Kafka properties for Confluent Serdes

If a message is sent by using a schema that isn’t in the registry, the SerDes attempts to create the new schema, or version of the schema, in the registry. If this behavior is not required, it can be disabled by removing the writer permission for schema resources from the application. See [Managing access to the Schema Registry](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-securitymanaging_access_schemas).

The normalize option for schema lookups and registration is not supported.
The IBM SRE team do not have front end application access to customer environmentd. Customers are required to check general applicaton functionality and any business critical components. Additionally, any customer specific integrations (JMS) or custom configurations (automation scripts, applications, etc) will need to be validated as well.





 Emergency Maintenance 

In exceptional cases such as critical security patching, the The IBM Maximo Application Suite Dedicated Services team may need to schedule unplanned emergency maintenance outages outside of a Planned Maintenance window for Production systems. The IBM Maximo Application Suite Dedicated team will provide as much advanced notice as possible, however depending on criticality of the security patch, 5-10 business days notice may not be possible. Emergency Maintenance will be communicated via the [Client Communications Center (CCC)](https://cloud.ibm.com/docs/mas-ms?topic=mas-ms-client-communications-center).

See below slidedeck for more information on upgrades, Continuous Delivery and Long Term Support

[MAS Continuous Delivery and Long Term Support Presentation](https://ibm.box.com/shared/static/xqn8znqlk69p8glipsxbxg9suxli643i.pptx)