vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If you see no errors, you can proceed with the installation.





 Is there a central SAP Note for installing NetWeaver on Oracle? 

[SAP Note 2172935 - Installation - SAP Systems based on SAP NetWeaver: Oracle Database](https://launchpad.support.sap.com//notes/2172935) provides hardware and storage requirements for Oracle and details the required file systems and mount points.





 Is there a central SAP Note for using MaxDB for NetWeaver installations? 

[SAP Note 2365014 - Installation of SAP Systems Based on SAP NetWeaver: SAP MaxDB](https://launchpad.support.sap.com//notes/2365014) outlines the installation and provides other useful information for MaxDB users.







 SAP HANA generic questions 



 What hardware database virtualization/sharing/isolation options are supported in the IBM Cloud infrastructure? 

IBM Cloud SAP-certified infrastructure offerings are certified for SAP and do not include database virtualization/sharing/isolation options such as Multitenant Database Containers (MDC) testing. The customer is responsible for following SAP guidance to:



* Correctly set up the SAP HANA features and functions
* Ensure that the infrastructure remains compliant with the SAP certification







 Is scale-out supported for SAP HANA? 

Yes. For OLTP (i.e. SAP S/4HANA) see [SAP S/4HANA - Scale-up/Scale-out](https://cloud.ibm.com/docs/sap?topic=sap-s4hanas4hana-hana-scaling), and for OLAP (i.e. BW/4HANA) see [SAP BW/4HANA - Scale-up/Scale-out](https://cloud.ibm.com/docs/sap?topic=sap-bw4hanabw4hana-hana-scaling). Alternatively view the latest top specific available in the summary table on [FAQ of Profile List with Benchmarks and Specifications](https://cloud.ibm.com/docs/sap?topic=sap-faq-profile-specsfaq-profile-specs-maximums).





 How do I back up my SAP HANA-certified servers?
* UI
* API







 Creating a product 

During the onboarding process, you can add a new product or import an existing product. Importing an existing product is limited to software that was previously added to a private catalog.



 Adding a new product by using the console 



1. From the My products page in Partner Center, click Create.
2. Enter the name of your product. Make sure that the name meets the following requirements:



* Use 60 characters or less.
* Do not include "IBM Cloud".
* Do not include the name of your company, former product names, or details like deployment targets and pricing. You can include this information in your readme file.



3. Select the product type. The product type is used for tax assessment purposes. You can review the following list of product types. For more information, see [Selling on IBM Cloud](https://cloud.ibm.com/docs/sell?topic=sell-selling-clouds).



* Software as a service
* Infrastructure as a service
* Platform as a service
* Deployable software



4. Click Add.







 Importing an existing product by using the console 

If you previously onboarded software to your account, you can import the software to Partner Center. For more information about adding software to a private catalog, see [Onboarding software to your account](https://cloud.ibm.com/docs/account?topic=account-create-private-catalog).



1. From the My products page in Partner Center, click Create.
2. Select Import existing product.
3. Select the private catalog that contains your product and click Select catalog.
4. Select the product that you would like to import and click Import.







 Creating a product by using the API 

You can programmatically create a product by calling the [Partner Center Sell API](https://cloud.ibm.com/apidocs/partner-center-sellcreate-product) as shown in the following sample request. The example creates a product that is named My new product:

curl --request POST --url https://product-
(https://cloud.ibm.com/docs-content/v1/content/b6066ebcc4ff31f2a8b558531f2ee791d108a7e1/cloud-pak-multicloud-management/images/setup_appliance.png)

Figure 17. Welcome to the Appliance Console
3. Press Enter to manually configure settings.

Note: Networking is already configured. You can skip this step.
4. Select 5) Configure database from the menu.



* You are prompted to create or fetch an encryption key. If this instance is the first CloudForms appliance, select 1) Create key.
* If this is not the first CloudForms appliance, select 2) Fetch key from remote system to fetch the key from the first appliance. For worker and multi-region setups, use this option to copy key from another appliance.



Note: All CloudForms appliances in a multi-region deployment must use the same key.
5. Select 1) Create Internal Database for the database location.
6. Choose a disk for the database. The disk can be either a disk you attached previously, or a partition on the current disk.

Important: Best practice is using a separate disk for the database.

If an unpartitioned disk is attached to the virtual machine, the dialog shows the options. For example,

1) /dev/vdb: 20480
2) Don't partition the disk



* Enter 1 to choose /dev/vdb for the database location. This option creates a logical volume by using this device and mounts the volume to the appliance in a location appropriate for storing the database. The default location is /var/lib/pgsql, which can be found in the environment variable $APPLIANCE_PG_MOUNT_POINT.
* Enter 2 to continue without partitioning the disk. A second prompt confirms this choice. Selecting this option results in using the root file system for the data directory (not advised in most cases).



7.
After the channel members specified in the lifecycle endorsement policy approve the definition, any of them can [commit](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2-commit) the definition, at which point the smart contract can start to process transactions on the peers. 
 Install a smart contract on my peers If the smart contract has not yet been proposed to the channel, navigate to the Channels tab and click Propose smart contract definition. See [Install and propose a smart contract](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2-install-propose) for more details. <br> <br>Otherwise, open the smart contract tile on the Channels tab. Next to your organization, click Begin approval process or Update package details (if you have already approved the proposal) and either upload a package or select an existing package to install, then select one or more peers to install it on. <br> <br>Note: It is still possible to install a smart contract on a peer from the peer tile on the Nodes tab. But this only installs the smart contract on the peer, it does not propose it to the channel. 
 Propose a new smart contract definition From the Channels tab, click Propose smart contract definition. As the proposal originator, you are required to either, upload a new smart contract package and install it on at least one peer, or select an existing package from one of your organization peers. Because you are proposing a new smart contract, a smart contract proposal with the same definition name cannot already exist. If it does, it will get replaced by this proposal. 
 Install a different smart contract package than what is included in the smart contract proposal If there are no differences in the agreed to business logic in your smart contract package, you can use your own package instead. From the Channels tab, open the smart contract tile and click either Begin approval process next to your organization. Click Add file to upload your own package or Existing package to select a package that is already installed on a peer in your organization.
AnyDB - SAP ASE 

The SAP systems in a landscape have specific requirements for servers, operating systems, network setup, and supported storage.

Deployment of SAP AnyDB on IBM Cloud is similar to deployments with infrastructure with on-premises data centers. Therefore, use the information that is provided from SAP and the RDBMS providers.

To assist your project's planning phase, more design considerations are provided for SAP AnyDB - SAP ASE with IBM Cloud® for SAP.



 Overview of SAP ASE with IBM Cloud® 

Before you start the software deployment of SAP ASE, ensure that:



* Check all relevant SAP ASE information and prerequisites (for example, SAP Notes)
* All required packages are installed for the relevant OS that is used for SAP ASE





 Documentation of SAP ASE 

A good entry point into the documentation is the [SAP Community page for SAP Adaptive Server Enterprise (ASE)](https://community.sap.com/topics/applications-on-ase)){: external}.

SAP ASE documentation:



* [SAP Help Portal - SAP Adaptive Server Enterprise (ASE)](https://help.sap.com/viewer/product/SAP_ASE/latest/en-US)



* [SAP Help Portal - SAP Adaptive Server Enterprise (ASE) Installation and Upgrade Guide for Linux®](https://help.sap.com/viewer/23c3bb4a29be443ea887fa10871a30f8/latest/en-US)
* [SAP Help Portal - SAP Adaptive Server Enterprise (ASE) Installation and Upgrade Guide for IBM AIX](https://help.sap.com/viewer/07e2d10774874e3bb4d991ef08d678e8/latest/en-US)
* [SAP Help Portal - SAP Adaptive Server Enterprise (ASE) Installation and Upgrade Guide for Windows](https://help.sap.com/viewer/36031975851a4f82b1022a9df877280b/latest/en-US)
WebSphere Application Server



* What products can I install with WebSphere Application Server?

You can install a WebSphere Application Server traditional environment on a virtual server instance (VSI) on IBM Cloud. For a description of the topologies that you can install with WebSphere Application Server, see [Topologies](https://cloud.ibm.com/docs/was-for-vsi?topic=was-for-vsi-topologies).
* What permissions do I need to use this tile?

You need Manager role on the Schematics service in at least one resource group. You also need Administrator role for VPC Infrastructure Services in the resource group for the Schematics workspace, VPC, and VSIs.
* Where can I see the installation logs?

To see the Installation logs, look under the [Schematics workspace](https://cloud.ibm.com/schematics/workspaces).
* Where can I see my installation history?

To see the installation history, look under the [Schematics workspace](https://cloud.ibm.com/schematics/workspaces).
* How do I uninstall?

Follow the instructions in [Uninstalling your workspace or resources](https://cloud.ibm.com/docs/was-for-vsi?topic=was-for-vsi-uninstalling).
* Do I get charged for using the tile?

No, but you get charged for the infrastructure. Refer to [Topologies](https://cloud.ibm.com/docs/was-for-vsi?topic=was-for-vsi-topologies) for infrastructure resources provisioned and to [Pricing](https://www.ibm.com/cloud/vpc/pricing) for the associated cost.
* Can I use the tile to upgrade WebSphere Application Server after initial installation?

No, you can use the tile only for one installation. After the initial installation, it is your responsibility to manage and upgrade the installation.



Integration Event Streams



* How do I use Kafka APIs to create and delete topics?
For more information, see [IaaS, PaaS, and SaaS - IBM Cloud service models](https://www.ibm.com/cloud/learn/iaas-paas-saas)![External link icon](https://cloud.ibm.com/docs-content/v1/content/8aa0853d34cf2349f1d2db8e5c61e6422a580169/icons/launch-glyph.svg).

Zoom

![Cloud service models.](https://cloud.ibm.com/docs-content/v1/content/8aa0853d34cf2349f1d2db8e5c61e6422a580169/cloud-infrastructure/images/cloud-svc-models.svg)

Figure 1. Cloud service models

With the IaaS model, your provider is responsible for maintaining the underlying infrastructure only and optionally installing software, such as operating systems, applications, and databases. Your access to the underlying infrastructure is limited, and you're responsible for installing your software or have your service provider install it. You're also responsible for all other maintenance, which includes service packs, virus software, and patches.

With the PaaS model, your provider is responsible for the systems through the operating system and for all infrastructure management, which includes OS patches, hardware repairs, and network settings. You build and maintain the application, and you or your provider can install middleware, including databases or other types. This model is used to develop and test software. For more information, see [A practical guide to platform as a service: What is PaaS ![External link icon](https://cloud.ibm.com/docs-content/v1/content/8aa0853d34cf2349f1d2db8e5c61e6422a580169/icons/launch-glyph.svg)](https://www.ibm.com/blogs/cloud-computing/2016/08/10/practical-guide-paas/).

With the SaaS model, your provider maintains the systems through the actual application.
: Wait and track the progress of the Schematics workspace job. If true, installation waits. If false, the software installs immediately. Default is true.

--override-values VALUES|FILENAME (optional)
: Provide any custom configurations for the installation. You can provide this value either inline or by using a JSON or TXT file. For example, override-values values.json. When validating a virtual server image for VPC, the following fields must be provided: vsi_instance_name, vsi_id, vpc_profile, subnet_id, vpc_id, subnet_zone, ssh_key_id, vpc_region

--workspace-tf-version VERSION (optional)
: Provide a workspace terraform version.

--workspace-region REGION (optional)
: Provide a workspace region.

--workspace-rg-id ID (optional)
: Provide a workspace resource group ID.

--schematics-destroy (optional)
: Provide this flag to delete the workspace resources after validation and installation.

--schematics-delete VALUE (optional)
: Provide this flag to delete the Schematics workspace after validation and installation.





 Example validating a product using a cluster 

Validate a product with the version locator b636d651-8489-4425-bd6a-f30af1603577.18aad484-c78b-4269-808b-52027621abd4 in a cluster with the ID bn5ebho206o7fg45f2e0 within a namespace called test-namespace. This installation has custom configurations, so the values are provided by using a values.json file.
Before you begin, [review the packages that are included with the JavaScript runtime](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-runtimesopenwhisk_ref_javascript_environments) to see whether a dependency of your app is already included with the runtime. If your dependency is not included, you must package it with your app. The following steps assume that you are running the commands on a Linux-based distribution on a processor with AMD64-based architecture.



1. In the root directory, create the package.json and my-action.js file.

Examplepackage.json

{
"name": "my-action",
"main": "my-action.js",
"dependencies" : {
"left-pad" : "1.1.3"
}
}

my-action.js

function myAction(args) {
const leftPad = require("left-pad")
const lines = args.lines || [];
return { padded: lines.map(l => leftPad(l, 30, ".")) }
}

exports.main = myAction;
2. Install all dependencies locally.

npm install <dependency>

While most npm packages install JavaScript sources on npm install, some packages also install and compile platform-dependent binary file artifacts. Because this environment is Linux AMD64-based, the npm install must be executed on a similar platform. Otherwise the action invocations might not succeed.
3. Create an archive that contains all files, including all dependencies.

zip -r action.zip 

Windows users Using the Windows Explorer action for creating the compressed file results in an incorrect file structure. Cloud Functions archive actions must have package.json at the root of the archive, but Windows Explorer places it inside a nested folder. Use the zip command instead.







 NPM libraries with native dependencies
Attaching an ISO 

Use the following steps to attach an ISO.



1. On the Kernel-based Virtual Machine (KVM) viewer, select Virtual media > Virtual storage. Your operating system and Java version might require you to allow access to start the Java-based viewer.
2. Click the CD and ISO tab in the Virtual Storage window. For the Logical Drive Type, select ISO file and click Open image.
3. Go to the ESXi ISO and click OK. Then, click Plug-in.
4. After the ISO is plugged into the session, click OK.
5. Go back to the IPMI webpage and click Remote > Control > Reset server > Perform action to restart the server.





 Installing network configuration 

Use the following steps to install network configuration.



1. Install ESXi.

After the installation is complete, make sure to Plug out the ISO so that you can restart the server.
2. Restart the server.
3. Configure the IP address of the server after it restarts.
4. Gather the details from the Configuration tab of the device.



You can now manage the ESXi host.

For more information about setting up endurance or performance block storage, see the following links.



* [Provisioning endurance storage](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-Aboutprovendurance)
* [Provisioning performance block storage](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-Aboutprovperformance)



For more information about setting up QuantaStor, see [Architecture guide for QuantaStor](https://cloud.ibm.com/docs/vmware?topic=vmware-quantastor-architecture-guide).
* The new partition is listed with the disk, similar to XXXp1, followed by the size, Type (83), and Linux®.
* Take a note of the partition name, you need it in the next step. (The XXXp1 represents the partition name.)
* Create the file system:

mkfs.ext3 /dev/mapper/XXXp1



4. Create a mount point for the file system, and mount it.



* Create a partition name PerfDisk or where you want to mount the file system.

mkdir /PerfDisk
* Mount the storage with the partition name.

mount /dev/mapper/XXXp1 /PerfDisk
* Check that you see your new file system listed.

df -h



5. Add the new file system to the system's /etc/fstab file to enable automatic mounting on boot.



* Append the following line to the end of /etc/fstab (with the partition name from Step 3).

/dev/mapper/XXXp1 /PerfDisk ext3 defaults,_netdev 0 1









 Creating a file system with parted 

On many Linux® distributions, parted comes preinstalled. However, if you need to you can install it by issuing the following command.

 dnf install parted

To create a file system with parted, follow these steps.



1. Start the interactive parted shell.

parted
2. Create a partition on the disk.



1. Unless it is specified otherwise, parted uses your primary drive, which is /dev/sda in most cases. Switch to the disk that you want to partition by using the command select. Replace XXX with your new device name.

select /dev/mapper/XXX
2. Run print to confirm that you are on the right disk.

print
3. Create a GPT partition table.

mklabel gpt
4. Parted can be used to create primary and logical disk partitions, the steps that are involved are the same.
Instance storage is a feature of VPC where you can request virtual server instances with fast, local storage attached. For more information about instance storage, refer to [About instance storage](https://cloud.ibm.com/docs/vpc?topic=vpc-instance-storage).

By default, when you provision a virtual server instance with instance storage and then log in to that server for the first time, the instance storage disks are not configured. They show up as block devices (for example /dev/vdb), and need the following done before you can use them with a file system:



* Partition the device.
* Format the partition with a file system.
* Mount the file system.



These activities can also be performed automatically when you use the User Data field to provision the virtual instance. The cloud-config script defines these actions:



* Instructs the cloud initialization process to run during first boot of your virtual instance.
* Automatically partitions the device.
* Formats the partition with an ext4 file system.
* Mounts the file system.



Do not specify the User Data field to automatically configure an instance storage disk that is not part of the virtual instance definition. Attempting to automatically configure an instance storage disk that is not part of the virtual instance definition would target dev/vdb device and might point to the cloud-init data source, which would corrupt the cloud-init configurations such as hostname and ssh keys.

The following example shows user data that automatically configures an instance storage disk. This example can be used with an instance profile that specifies a single disk.

cloud-config
 Cloud-init supports simple partition and file system config.
 This user data yaml will create a full partition on the first
 virtio_blk device after the boot device, initialize ext4 on it and
 mount it on a folder matching the label.

disk_setup:
  /dev/vdb:
    table_type: 'mbr'
    layout:
    - 100
    overwrite: false

fs_setup:
  - label: /mnt/inststg1
For more information, see [ibmcloud plugin install](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_settingsibmcloud_plugin_install).







 Confirming installed plug-ins 

Use the plugin list command to confirm that all required plug-ins are installed in IBM Cloud CLI. The plugin list command returns the following information for each plugin that is installed:



* The plug-in name.
* The current version of the plug-in.
* Whether a more recent version of the plugin is available.
* Whether the plug-in version supports private endpoint use.



ibmcloud plugin list





 Updating installed plug-ins 

Use the plugin update command to update the plug-ins that are installed in IBM Cloud CLI. The plugin update command returns the following information for each plugin that is installed:



* The current plug-in version.
* The latest plug-in version that is available.



ibmcloud plugin update





 Related information 

You can also install a plug-in from a URL, download a plug-in, or install a plug-in binary locally:



* To install a plug-in locally or from a URL, see [ibmcloud plugin install](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_settingsibmcloud_plugin_install).
* To download a plug-in, see [How do I download a plug-in?](https://cloud.ibm.com/docs/cli?topic=cli-ibm-cli-faqcli-install-download-local)
id (optional)
: The product ID. The ID is not required if the name value is set.

name (optional)
: Programmatic name of the product.

kind
: The format kind of the dependency.

version
: A version or range of versions to include as dependencies in SemVer format.

flavors (optional)
: List of variations that the architecture depends on.

release_notes_url
: URL to the architecture's release notes.

configuration
: Section header for configuration information, including configuration key, type, default values, display names, and descriptions. Most values are already set during the onboarding process, but you might need to override the values generated during onboarding, or set values that are not configured during the onboarding process.

required
: Indicates if users are required to specify the parameter during installation.

hidden
: Indicates if the parameter should be hidden from users during installation.

options
: An array of options that users can choose from for a parameter.

custom_config
: Section header use to indicate that a custom configuration can be used.

type
: The ID of the widget type used for configuration

grouping
: Where the configuration type should appear in the catalog. Valid values are Target, Resource, and Deployment.

original_grouping
: Where the configuration type originally appeared. Valid values are Target, Resource, and Deployment.

grouping_index
: The order of this configuration item when there are mulitple.

config_constraints
: Map of constraint parameters that are given to the custom widget.

associations
: Section header for parameters that are associated with the configuration.

parameters
: List of parameters.

terraform_version
: The Terraform version needed to validate and install the version. Setting this value overrides what is specified in the source code.

outputs
: Section header for information about output values.

key
: Specifies the output value.

description
: A short summary of the output value.

install_type
: Specifies whether a deployable architecture is full stack or extension.