vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Generally, the entire infrastructure for the operation of all closely coupled runtime components of an SAP software solution must be installed on either Intel Virtual Servers (Gen2) or on Bare Metal Servers from IBM Cloud.

To assist customers looking to combine performance for the database and flexibility for the application solution/s, testing has been performed when combining environments and networks.

Intel Bare Metal Servers from IBM Cloud in the IBM Cloud Classic Infrastructure environment may offer greater performance capabilities. Notably this includes larger memory, local SSD storage in RAID arrays, access to IPMI, and more. Intel Virtual Servers (Gen2), on the other hand provide more flexibility.

RDBMs on Intel Bare Metal Servers in the older IBM Cloud Classic Infrastructure environment that comply to [SAP Note 2414097](https://launchpad.support.sap.com//notes/2414097), are supported when connected to the SAP AS on Intel Virtual Server (Gen2) in the IBM Cloud VPC Infrastructure environment - when placed in the same location (i.e. Datacenter / Availability Zone) and using an IBM Cloud Transit Gateway local routing.





 Mapping CPUs derived from SAPS to an IBM Power Virtual Server 

This is a complementary offering from IBM Power Systems, with low latency access to IBM Cloud services

When you create a IBM Power Systems Virtual Server by using the IBM Cloud console:



* For SAP NetWeaver, you select the number of CPUs of your server
* For SAP HANA, you select an instance profile with a predefined number of CPUs and memory size that suits your workload



While your data must fit into the instance memory with space for data growth defined by the business and SAP Sizing process, choosing an instance profile with more CPUs improves performance.

To find SAP certified profiles for Cloud IaaS, see [SAP Certified and Supported SAP HANA Hardware Directory - Certified IaaS Platforms - IBM Cloud](https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN//solutions?filters=iaas;ve:28); this includes IBM Power Virtual Servers which can be found by using filter "CPU Architeceture" and selecting IBM POWER9.
For more information, see [Data backup and recovery by using BRMS and IBM Cloud Storage Solutions for i](https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_74/rzai8/rzai8backupandrecoveryusingBRMSandICC.htm) and [BRMS with Cloud Storage Solutions for i considerations and requirements](https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_74/rzai8/rzai8brmscloudrequireandconsider.htm).

For a complete tutorial on migrating your IBM i workloads to Power Systems Virtual Servers, see [Migrating IBM i to IBM Power Systems Virtual Servers](https://cloud.ibm.com/media/docs/downloads/power-iaas-tutorials/PowerVS_IBMi_Migration_Tutorial_v1.pdf).





 Logical Replication with Geographic Mirroring and PowerHA SystemMirror for AIX Enterprise Edition 

GeoMirroring enables IBM i disk mirroring technology on multiple system environments and supports host-based and logical replication across geographically distant sites. Geomirroring supports synchronous and asynchronous modes. You can integrate PowerHA SystemMirror (Enterprise Edition) for network monitoring and automated failover support.



* [Geographic mirroring](https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_73/rzaue/rzalygeographicmirror.htm)
* [IBM PowerHA SystemMirror for i: Using Geographic Mirroring](https://www.redbooks.ibm.com/redbooks/pdfs/sg248401.pdf)
IBM Resiliency Orchestrator architecture is flexible and adaptable through the API extension.

Zoom

![Open adaptable architecture](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/overview/images/BCDR-Architecture-Open-Adaptable-Architecture.svg)

Figure 3. An architecture diagram for open adaptable architecture



* North-bound API provides interfaces to integrate with existing web GUIs, monitoring systems, ticketing, and billing.
* South-bound API provides interfaces with technologies, platforms, or other platform and product orchestrators or managers.
* West-bound API interfaces local plug-ins by using command line or API and local developed RAL extension.
* East-bound API interfaces other reporting engines and user authentication systems.







 RALs concept 

Flexibility in the architecture is combined with a complete recovery stack leveraging on more than 400 plus predefined patterns for efficient implementation. These patterns, called Recovery Automation Libraries (RALs), are a set of pre-packaged, pre-defined, and verified procedures to apply to specific components of the DR solution that must be orchestrated by IBM CRO.

The recovery stack operates on these different layers:



* Application Application environment, startup, shutdown
* Database RPO, Dump and Apply, Health
* Network Failover-DNS, NAT, NetScalar
* OS Health, bring up, shutdown
* Replication/Storage Health, data lag, start, stop, split/join
* Cloud/Infrastructure Create/start/stop instance, provision storage, network, security groups



IBM CRO works with several platforms and technologies.

As you might find in the following table, few of the technologies reported are not supported on the public cloud space, but they are included here since IBM CRO works in the hybrid space and provides a full management of a Hybrid DR solution.



Table 1. Platform and technologies that work with IBM CRO

 Platforms Applications Replication* 

 Linux flavors WebSphere, WebLogic, IIS NetApp SnapMirror 
 Windows SAP EMC SRDF, RecoverPoint
: We're pleased to announce our new IBM Cloud Direct Link Service Provider Program, which enables enterprises to select from a robust ecosystem of local and global providers and create the private connections to IBM Cloud that best suit their needs. We work closely to provide technical enablement and training to help ensure that service providers can offer enterprises reliable connectivity to the cloud from anywhere in the world. This gives our joint customers greater choice to select the right provider, speed of service, location, and deployment model to create a secure, highly available hybrid connection.

Colt offers direct access to IBM Cloud Direct Link
: IBM Cloud is pleased to announce our extended collaboration with Colt. Thanks to Colt's Dedicated Cloud Access (DCA) service, customers can now establish private connectivity from their data center, office, or colocation environment. This helps to reduce network costs, increase bandwidth throughput, and provide a more consistent network experience than internet-based connections.





 07 May 2018 

May highlights
: 7 May: Megaport is now active on a single Router in WDC02 for Connect. Diversity follows in a few weeks.
: 2 May: Equinix in NY02 and NY03 were delivered for Exchange, and are now live in the portal (with Diversity).





 27 April 2018 

April highlights
: 27 April: Arelion (formerly Telia) is now turned up for Connect in Stockholm.
: 25 April: LONDON 03 is now online with Equinix via Exchange. Diversity is in place, and confirmed in Portal.
: 25 April: Primary / Secondary NNIs @ AMS02 is now installed and tested for Colt.
: 25 April: Colt is now tested with Diversity in Frankfurt 1 PoP for Connect. Verified in Portal.





 01 March 2018 

PacketFabric Offers Connectivity to IBM Cloud
: PacketFabric customers have access to IBM Cloud services in Dallas, Texas; San Francisco, California; and Washington, D.C., from any location on the PacketFabric network.





 01 February 2018 

IBM Cloud Direct Link Connect is available.
IBM Cloud DevOps 

Delivering software and services at the speed the market demands requires teams to iterate and experiment rapidly. They must deploy new versions frequently, driven by feedback and data. The most successful cloud development teams adopt modern DevSecOps culture and practices, embrace cloud-native architectures, and assemble toolchains from best-in-class tools to unleash their productivity. Doing these things quickly is a key competitive advantage.

The [IBM Cloud Garage Method](https://www.ibm.com/garage/method) describes architectures, practices, and DevOps toolchains to allow enterprises to innovate at scale. Use the IBM Cloud Garage Method to help you to transform your culture and use the tools effectively and fast.

An enterprise application Developer can start building and deploying cloud-native applications in minutes. They can use a full set of services to build cognitive, IoT, blockchain, mobile, and data-intensive applications. With the IBM Cloud App Service, an individual Developer can create a project and deploy a production-ready application to IBM Cloud. The platform's code generation technology creates a starter application in the Developer's preferred language and framework, which is tailored to their needs and use case. Any services that are required in support of the use case, such as Watson Conversation, are provisioned automatically. Developers can debug and test on their local workstation or in the cloud, and use a DevOps toolchain to collaborate with others and automate the delivery process.

As team members join a project, they need an integrated set of tools that span development, deployment, and production operations. IBM's Open Toolchain architecture enables a team to rapidly provision best-in-class DevSecOps tools from IBM, open source, and others. Integrations between these tools are configured automatically. Toolchains are a first class concept on the platform, so Developers can quickly organize everything that they need in one place, and evolve the toolchain over time.
PrimaryIO HDM on IBM Cloud overview 

PrimaryIO Hybrid Cloud Data Management (HDM) on IBM Cloud decouples virtual machines (VMs) and storage (VMDKs) to seamlessly move workloads to and from IBM Cloud® faster and efficiently. The PrimaryIO HDM solution enables a hybrid cloud environment to extend on-premises VMware® environments to the public cloud for on-demand compute capacity. PrimaryIO HDM on IBM Cloud is a non-IBM product that is offered under terms and conditions from PrimaryIO, not IBM.

HDM has built-in functions to identify frequently used data, called hot data. Hot data is moved into an intelligent cloud cache, while less used data is moved to the background. This way, HDM can provision workloads in the IBM Cloud within minutes.

HDM combines data I/O analysis with an intelligent cloud cache to decouple VMs and VMDKs for workload portability. It accomplishes workload mobility in three steps:



1. Analyze - Analyzes on-premises VMs and VMDKs and identifies VMs that are most suitable for the cloud.



1. Identifies active data (hot data set) between VMs and VMDKs.
2. Predicts the active data set to prefetch data.
3. Recommends the minimal size of cache that is required for the VMs to quickly run in the cloud.



2. Cloud cache - Copies only the hot data set into the cloud cache instead of replicating the entire VMDK in the cloud storage. Minimizes the data footprint in the cloud.
3. Flex - Securely migrates the VMs (compute only) to the cloud, by using the hot data set in the cloud cache.





 Key benefits of HDM 

PrimaryIO HDM enables the following use cases:



* VM I/O Profiling. HDM gives visibility into a VM’s disk I/O performance, including read/write patterns and disk access block size histograms for read/write transactions from and to the VMDKs.
* Try-Before-Commit. HDM enables rapid testing of applications in the cloud.
IBM Cloud Direct Link provides diversity, and customers are responsible for implementing redundancy through their BGP schemas.

If you select ECMP for redundancy, both BGP sessions must exist on the same XCR; therefore, you give up router diversity and are exposed to risk if the router fails. You gain Layer-3 redundancy, but you lose router diversity.





 More about using VRF 

All accounts that use an IBM Cloud Direct Link solution must migrate to a VRF. By using VRF, customers advertise the available routes to their self-defined remote networks. This configuration does not permit you to use self-defined IP addresses on the IBM Cloud network.

Migrating to a VRF is done during the setup process. It requires a short outage window (up to 30 minutes for large accounts with multiple VLANs/locations), during which the backend network VLANs lose mutual connectivity while they are moved to the VRF. The VRF migration is scheduled with the implementing engineer.

VRF eliminates the "VLAN Spanning" option for your account, including any account-to-account VLAN spanning capabilities, because all VLANs are able to communicate unless a gateway appliance is introduced to manage traffic. VRF also limits the ability to use IBM Cloud VPN services because it is not compatible with IBM Cloud SSL and IPsec VPN services.

An alternative is to use the IBM Cloud Direct Link offering itself to manage your servers, or to run your own VPN solution (such as a Vyatta) that can be configured with different types of VPN. After migrating to a VRF, SSL VPN typically works when a VPN connection is made to the same data center location in which a compute VM is running, but it does not allow access globally.





 Using BYOIP and NAT with Direct Link 

IBM Cloud Direct Link does not offer BYOIP on the private network. Therefore, traffic with a destination IP address that was not assigned by IBM Cloud is dropped. However, customers can encapsulate traffic between the remote network and their IBM Cloud network that uses GRE, IPsec, or VLAN.
Government use cases for IBM Cloud 

These use cases highlight how workloads on IBM Cloud® Kubernetes Service benefit from the public cloud. These workloads are isolated in global regions for data sovereignty, use Watson machine learning instead of net-new code, and connect to on-premises databases.



 Regional government improves collaboration and velocity with community Developers who combine public-private data 

An Open-Government Data Program Executive needs to share public data with the community and private sector, but the data is locked in an on-premises monolithic system.

With IBM Cloud Kubernetes Service, the Exec delivers the value of combined public-private data. Likewise, the service provides the public cloud platform to refactor and expose microservices from monolithic on-premises apps. Also, the public cloud allows government and the public partnerships to use external cloud services and collaboration-friendly open-source tools.



 Context 



* An “open government” model is the future, but this regional government agency can't make the leap with their on-premises systems.
* They want to support innovation and foster co-development between private sector, citizens, and public agencies.
* Disparate groups of Developers from the government and private organizations don’t have a unified open-source platform where they can share APIs and data easily.
* Government data is locked in on-premises systems with no easy public access.







 Solution 

An open-government transformation must be built on a foundation that provides performance, resilience, business continuity, and security. As innovation and co-development move ahead, agencies and citizens depend on software, services, and infrastructure companies to “protect and serve.”

To bust bureaucracy and transform government’s relationship with its constituency, they turned to open standards to build a platform for co-creation.



* OPEN DATA – data storage where citizens, government agencies, and businesses access, share, and enhance data freely
* OPEN APIs – a development platform where APIs are contributed by and reused with all community partners
* OPEN INNOVATION – a set of cloud services that allow developers to use plug-in innovation instead of manually coding it



To start, the government uses IBM Cloud Object Storage to store its public data in the cloud.
Run the following command to publish your private offering to the IBM Cloud catalog for all users to see and use. To get to this step in the publication process, you must first publish the offering to your account and to all IBMers to complete the testing process. After your testing is complete, you can run this command.

This option requires approval. As soon as your approval is complete, your tile is available for all IBM Cloud customers.

ibmcloud catalog offering publish public [--catalog CATALOG]



 Command options 

--catalog CATALOG
: The catalog name or ID.

--offering OFFERING
: The product name or ID.







 ibmcloud catalog offering deprecate-offering 

Run the following command to deprecate a previously published offering version in the IBM Cloud catalog.

ibmcloud catalog offering deprecate-offering [--catalog CATALOG]



 Command options 

--catalog CATALOG
: The catalog name or ID.

--offering OFFERING
: The product name or ID.







 ibmcloud catalog offering restore-offering 

Run the following command to restore a previously deprecated product in the IBM Cloud catalog. After you validate a version of your product, you can restore it to the published state that it was in before it was deprecated.

ibmcloud catalog offering restore-offering [--catalog CATALOG]



 Command options 

--catalog CATALOG
: The catalog name or ID.

--offering OFFERING
: The product name or ID.







 ibmcloud catalog offering version restore-version 

Run the following command to restore a previously deprecated version of a product in the IBM Cloud catalog. Restoring it places the version in draft state. After you validate it, you can restore the original version to the published state that it was in before it was deprecated.

ibmcloud catalog offering version restore-version [--catalog CATALOG] [--include-config]



 Command options 

--catalog CATALOG
: The catalog name or ID.

--offering OFFERING
: The product name or ID.

--include-config (optional)
: If provided, all configuration values are included and available when you add the product.
Resource Group The resource group where the workspace is created. 
 Location The location where the workspace is created. 



You can find the IBM Cloud Schematics workspaces in [Workspaces](https://cloud.ibm.com/schematics/workspaces). Alternatively, go to [IBM Cloud®](https://cloud.ibm.com) and go to the IBM Cloud Schematics workspaces by clicking Menu![Menu icon](https://cloud.ibm.com/docs-content/v1/content/880fa35b13cb9428675d718aa36ca2825b4c87c8/icons/icon_hamburger.svg), then clicking Schematics, and then Workspaces.

Create and deploy the DevSecOps continuous integration (CI), continuous deployment (CD), and continuous compliance (CC) toolchains by using the default variables.







 Deploying 

To deploy DevSecOps Application Lifecycle Management toolchains by using Schematics, take the following steps:



1. Open the [IBM Cloud® Catalog Solution Library](https://cloud.ibm.com/catalog) page.
2. Open the catalog tile for DevSecOps Application Lifecycle Management.
3. Select an architecture version (default is the latest version).
4. On the overview page, agree to the terms and conditions and click Review deployment options.
5. On the DevSecOps Application Lifecycle Management catalog page, click the Deploy with IBM Cloud® Schematics option.
6. Specify a resource group and select a location in the Configure your workspace.
7. Scroll down to Set the input variables and complete the Required input variables. For more information on required variables, see [Required input variables](https://cloud.ibm.com/docs/devsecops-alm?topic=devsecops-alm-devsecops-alm-varsdevsecops-alm-min).
8. Optional. Click Optional input variables and modify any optional variables to extend the out of the box experience.
About Direct Link on Classic 

IBM Cloud® Direct Link on Classic offerings provide connectivity from an external source into a customer's IBM Cloud private network. Direct Link on Classic can be viewed as an alternative to a traditional site-to-site VPN solution, which is designed for customers that need more consistent, higher-throughput connectivity between a remote network and their IBM Cloud environments.



 Direct Link on Classic offerings 

Four types of connections are available:



* Direct Link Connect on Classic allows customers to use a connection through our Carrier partners who own and operate a facility-based network. A Connect provider is a network service provider (NSP) that is already connected to the IBM Cloud network, by using multi-tenant, high capacity links (also known as a network-to-network interface, or NNI). Customers typically can purchase a virtual circuit at this provider, bringing connectivity at a reduced cost, because the physical connectivity from IBM Cloud to the Connect provider is in place already, shared among other customers.
* Direct Link Dedicated on Classic allows customers to terminate a single-tenant, fiber-based cross-connect into the IBM Cloud network. This offering can be used by customers with colocation premises that are next to IBM Cloud PoPs and data centers; as well as network service providers that deliver circuits to customer premises or other data centers.
* Direct Link Dedicated Hosting on Classic provides connectivity similar to Direct Link Dedicated, but the connection point is next to an IBM Cloud data center, which improves latency for higher-performance use cases. IBM Cloud offers various customizable colocation services with this solution.
* Direct Link Exchange on Classic allows customers to use an Exchange provider to deliver connectivity to their IBM Cloud. An Exchange provider is a colocation or data center provider that is already connected to the IBM Cloud network, by using multi-tenant, high capacity links (also known as a network-to-network interface, or NNI). Customers typically can purchase a virtual circuit at this provider, bringing connectivity at a reduced cost, because the physical connectivity from IBM Cloud to the Exchange provider is in place already, shared among other customers.



The IBM Cloud Direct Link service is a routed, OSI Layer-3 service. It offers a direct connection to the IBM Cloud private network backbone, with low latency and speeds up to 10 Gbps.