vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If you install the IBM Cloud CLI in a custom directory, set the system property ibmcloud_eclipse_cli_path to the custom location of the IBM Cloud CLI installation. For example, -Dcom.ibmcloud.eclipse.cli.path=<path-to-ibmcloud-cli-installation>. Specify this location in the eclipse.ini file under vmargs.





 Installing the IBM Cloud CLI plug-in 

The IBM Cloud CLI plug-in can be installed from the [Eclipse marketplace](https://marketplace.eclipse.org/content/ibm-cloud-dev-tools-eclipse). Follow the instructions in the marketplace to complete the installation of the plug-in.





 Reporting issues 

If you want to report bugs or enhancement requests, open a work item in the [GitHub repo](https://github.com/IBM-Cloud/eclipse-ibmcloud-cli/issues).
Standard installation](https://cloud.ibm.com/docs-content/v1/content/f89cc64b006ca59b35404693959c83d5747fee3e/sap/images/refarch-sap-syb-std-only.svg)

Figure 2. SAP NetWeaver 7.x SYB standard installation with AAS

Architecture of SAP NetWeaver AS for ABAP

SAP tools create a PAS Instance and an ASCS Instance. This method is the standard for Java Stack (System) and is now standard for ABAP Stack.



1. The Primary Application Server (PAS) - An instance is an administrative unit that contains various components of an SAP system. The components of an instance are parameterized in a shared instance profile. Each instance is identified by a system ID and an instance number and includes:



* [SAP Web Dispatcher](https://help.sap.com/saphelp_snc700_ehp01/helpdata/en/f9/e2350eca7f4a109eb0a7bc63135e27/frameset.htm) & Work Process (DIA,BTC,UPD,SPOOL) - The SAP Web Dispatcher lies between the internet and your SAP system. The SAP Web Dispatcher is the entry point for HTTP and HTTPs requests into your system, which consists of one or more SAP NetWeaver application servers. As a “software web switch”, the SAP Web dispatcher can reject or accept connections. When it accepts a connection, it balances the load to ensure an even distribution across the servers. The SAP Web Dispatcher contributes to security and also balances the load in your SAP system.

You can use the SAP Web Dispatcher in ABAP and Java systems, in pure Java systems, and in pure ABAP systems.
"display_name": "Ubuntu Linux 20.04 LTS Focal Fossa Minimal Install (amd64)",
"family": "Ubuntu Linux",
"href": "https://us-south.iaas.cloud.ibm.com/v1/operating_systems/ubuntu-20-04-amd64",
"name": "ubuntu-20-04-amd64",
"vendor": "Canonical",
"version": "20.04 LTS Focal Fossa Minimal Install"
},
"resource_group": {
"href": "https://resource-controller.cloud.ibm.com/v2/resource_groups/678523bcbe2b4eada913d32640909956",
"id": "678523bcbe2b4eada913d32640909956",
"name": "Default"
},
"resource_type": "snapshot",
"service_tags": ],
"size": 1,
"source_image": {
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/images/de066f7d-b95f-4ca2-9aa0-b6362889e933",
"id": "de066f7d-b95f-4ca2-9aa0-b6362889e933",
"name": "ubuntu-20-04-minimal-amd64-1"
},
"source_volume": {
"crn": "crn:...]",
For more information, see [Install an NSX Edge on ESXi Using the vSphere GUI](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/installation/GUID-AECC66D0-C968-4EF2-9CAD-7772B0245BF6.htmlGUID-AECC66D0-C968-4EF2-9CAD-7772B0245BF6).
2. Create an NSX Edge cluster. For more information, see [Create an NSX Edge Cluster](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/installation/GUID-898099FC-4ED2-4553-809D-B81B494B67E7.htmlGUID-898099FC-4ED2-4553-809D-B81B494B67E7).



When installing NSX Edges, create two N-VDSs. One for overlay traffic and one for accessing VPC subnets.

When configuring uplink for TEP traffic in Edges, create a VLAN based segment for the vlan transport zone using with the VLAN ID, e.g. 400.

When you deploy an NSX-T edge cluster, you can think of it as an empty pool of compute resources. The NSX-T edge cluster does not do anything until you create Tier 0 and/or Tier 1 logical routers into it.

Refer to [VMware Solution Architectures for IBM Cloud VPC](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vpc-ryo-nsx-t) for naming and architectural considerations.





 Next steps 

The next step in the tutorial series is:
Each plug-in returns the current version installed, whether there is a more recent version available for update, and if the version of the plug-in installed supports private endpoint use.

ibmcloud plugin list





 ibmcloud plugin show 

Show details of an installed plug-in.

ibmcloud plugin show PLUGIN-NAME





 ibmcloud plugin install 

Install a specific version of a plug-in to IBM Cloud CLI from the specified path or repository, or all latest available plug-ins in the repository.

ibmcloud plugin install PLUGIN_PATH|PLUGIN_NAME [-r REPO_NAME] [-v VERSION] [-f]

ibmcloud plugin install [-a, --all] [-r REPO_NAME] [-f]

ibmcloud plugin install LOCAL-PATH/TO/PLUGIN | URL [-f]

If no repository is specified, the command uses the default plug-in repository IBM Cloud. If you are installing a single plug-in, and no version is specified, the command selects the latest available version to install. If the '-a, --all' flag is specified, the command installs all latest available plug-ins in the repository.

Command options:

PLUGIN_PATH|PLUGIN_NAME
: If -r REPO_NAME is not specified, the plug-in is installed from the specified local path or remote URL.

-a, --all (optional)
: Install all latest available plug-ins in the repository.

-r REPO_NAME (optional)
: The name of the repository where the plug-in binary is located. If no repository is specified, the command uses the default plug-in repository IBM Cloud.

-v VERSION (optional)
: Version of the plug-in to be installed. Accepts specific semantic version or constraint.

-f
: Force installs the plug-in without confirmation.

The IBM Cloud CLI has the official repository name of IBM Cloud.

Examples:

Install a plug-in from the local file:

ibmcloud plugin install /downloads/new_plugin

Install a plug-in from the remote URL:
* [Installation of SAP Systems based on the Application Server Java of SAP NetWeaver 7.1 to 7.5 on UNIX: IBM Db2 LUW](https://help.sap.com/viewer/e85af73ba3324e29834015d03d8eea84/CURRENT_VERSION/en-US)
* [SAP Note 1707361 - Inst. Systems based on NW 7.1 and Higher: UNIX Db2 for LUW](https://launchpad.support.sap.com//notes/1707361)



IBM Db2 and SAP NetWeaver on Windows:



* [Installation of SAP Systems based on the Application Server ABAP of SAP NetWeaver 7.1 to 7.52 on Windows: IBM Db2 LUW](https://help.sap.com/viewer/77e3a615f633437e9c4549891bb6bad7/CURRENT_VERSION/en-US)
* [Installation of SAP Systems based on the Application Server Java of SAP NetWeaver 7.1 to 7.5 on Windows: IBM Db2 LUW](https://help.sap.com/viewer/d65d4f66e8c34555ad9541734f9cd5b0/CURRENT_VERSION/en-US)
* [SAP Note 1707362 - Inst. Systems based on NW 7.1 and Higher: Windows Db2 LUW](https://launchpad.support.sap.com//notes/1707362)



In the IBM Knowledge Center for Db2, the documentation links provided refer to specific pages on an IBM Db2 version. You can switch to the correct version by clicking the "Change version or product" in the upper left area of the IBM Knowledge Center.





 SAP on IBM Db2 using Intel Bare Metal 

See [SAP Note 2414097 - SAP Applications on IBM Cloud Classic Infrastructure environment](https://launchpad.support.sap.com//notes/2414097) for supported IBM Db2 database versions.

A sample configuration is shown in:
-v VERSION (optional)
: Version of the plug-in to be installed. Accepts specific semantic version or constraint.

-f
: Force installs the plug-in without confirmation.

The IBM Cloud CLI has the official repository name of IBM Cloud.

Examples:

Install a plug-in from the local file:

ibmcloud plugin install /downloads/new_plugin

Install a plug-in from the remote URL:

ibmcloud plugin install http://example.com/downloads/my-plugin

Install the container-service plug-in of the latest version from the IBM Cloud repository:

ibmcloud plugin install container-service -r "IBM Cloud"

or you can run:

ibmcloud plugin install container-service

Install the container-service plug-in with the version 0.1.425 from the official plug-in repository:

ibmcloud plugin install container-service -v 0.1.425

Install all latest available plug-ins from the official plug-in repository:

ibmcloud plugin install --all

Install all latest available plug-ins from the official plug-in repository without confirmation:

ibmcloud plugin install --all -f

Install multiple plug-ins at the same time:

ibmcloud plugin install container-service@0.1.425 secrets-manager@0.1.25





 ibmcloud plugin download 

Download a specific version of a plug-in to IBM Cloud CLI from the specified repository, or all latest available plug-ins in the repository.

ibmcloud plugin download PLUGIN_NAME [-r REPO_NAME] [-v VERSION] [-d, --dest DOWNLOAD_DIRECTORY] [-f]

ibmcloud plugin download [-a, --all] [-r REPO_NAME] [-f]

ibmcloud plugin download URL [-f] [-d DOWNLOAD_DIRECTORY]

If no repository is specified, the command uses the default plug-in repository IBM Cloud. If you are downloading a single plug-in, and no version is specified, the command selects the latest available version to download.
Deploy vCenter appliance - Phase 1 

vCenter installation is split into two phases. In the first phase, the appliance is installed into the ESXi host.

Verify that vcenter.vmware.ibmcloud.local resolves to the correct IP address prior continuing.



1. Before continuing further with vCenter deployment, verify that vcenter.vmware.ibmcloud.local resolves to the correct IP address. List information about configured records in your DNS instance dns-vmware and zone vmware.ibmcloud.local, use the following command.

ibmcloud dns resource-records $VMWARE_DNS_ZONE -i dns-vmware
2. Validate that you get correct responses for each entry (including the listed esx hosts) from your Windows Jump host, for example using nslookup via Windows command line.

nslookup vcenter.vmware.ibmcloud.local

nslookup esx-001.vmware.ibmcloud.local
3. Start the VCSA UI installer (e.g. <drive_letter>:\vcsa-ui-installer\win32\installer.exe).
4. Click Install a new vCenter Server.
5. Deploy vcenter into BMS001 / esx-001 using the following parameters (match with your IP address plan and host names).



vCenter Parameters

 Parameter Value 

 Target ESXi host esx-001.vmware.ibmcloud.local 
 VM name vcenter 
 Deployment size Small 
 Storage size Default 
 Datastore datastore1, thin 
 Network pg-mgmt (VLAN ID 100) 
 IPv4 static 
 IP address 10.97.0.132 
 Host name vcenter.vmware.ibmcloud.local 
 Subnet mask or prefix length 25 
 Default gateway 10.97.0.129 
 DNS servers 161.26.0.7, 161.26.0.8 
 HTTP Port 80 
 HTTPS Port 443 









 Configure vCenter - Phase 2
For example, if you are using an RPM package, issue the following command:

rpm -ivhf <secure-gateway-rpm-package>

The client installer starts and installs the client, it will create a sgenvironment.conf file in /etc/ibm.
2. Optional: If you want to use the system's upstart process you must edit this file and provide the following for the client to start correctly. See [Using Upstart](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-auto-start-confauto-start-linux) for more information on editing this configuration file.
3. If you started the client using upstart, check the log file to make sure it is running correctly.

cat /var/log/securegateway/client_console.log
4. To check the status of your client installation, issue the following command:

rpm -q ibm-securegateway-client







 AIX Installation 



1. Ensure that executable permission is set for the package. If necessary, change the file permissions by issuing the following command:

chmod a+x <secure-gateway-bin-package>
2. Extract the package by issuing the following command:

./<secure-gateway-bin-package>



Note: Please ensure whether your AIX system satisfy the requirement for running Node.js and ksh installed.





 Starting an interactive client session 

To start the client, run the following commands:

cd /opt/ibm/securegateway/client
node lib/secgwclient.js <gateway ID> -t <security token>

Normally it takes two parameters, a Secure Gateway gateway ID and the gateway's security token, both of which are available via the Secure Gateway Dashboard.

Return to [Getting Started - Adding a Client](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-add-client).







 Windows 



 Installing the Client 

You may require administrative privileges to perform this installation, depending on your system's security setup.



1.
After you mount all of your volumes to all the nodes, your multi-node servers are configured and ready to install the SAP HANA multi-node database. Follow the steps in the [SAP HANA Server Installation and Update Guide)](https://help.sap.com/viewer/2c1988d620e04368aa4103bf26f17727/latest/en-US) to install an SAP HANA database of your required version.









 SAP HANA performance 

After an SAP HANA database server is operational, it is important to inspect the performance to ensure it will meet your business application requirements. This is particularly important for any deployments using the TDI deployment method.



 SAP HANA performance validation 

The [SAP HANA Hardware and Cloud Measurement Tools (HCMT)](https://help.sap.com/viewer/product/HANA_HW_CLOUD_TOOLS/latest/en-US) replaces the previous SAP HANA HW Configuration Check Tool (HWCCT). The HCMT binary executable is run before an SAP HANA installation (commonly), and performs a series of automated tests which analyses the system performance.

The output of the HCMT execution, is a result archive file - hcmtresult-[timestamp].zip.

This HCMT result archive file is then uploaded to the [SAP HANA Hardware and Cloud Measurement Analysis (HCMA)](https://hotui-supportportal.dispatcher.hana.ondemand.com) for detailed analysis.

For information about downloading, installing, and configuring the HCMT tool, see [SAP Note 2493172 - SAP HANA Hardware and Cloud Measurement Tools](https://launchpad.support.sap.com//notes/2493172).





 SAP HANA overheads impact on available memory 

Every SAP HANA database server reserves a small allocation of memory for the operating system and other services required to operate.

SAP provide a rule of thumb for these overheads:



* Reserved for OS = 10% of the first 64GB + 3% of all remaining memory
* Reserved for SAP HANA services and caches = 50GB
IA-5 (5) - Change Authenticators Prior to Delivery 



  Control requirements 

IA-5 (5) - 0
:   The organization requires developers/installers of information system components to provide unique authenticators or change default authenticators prior to delivery/installation.





  NIST supplemental guidance 

This control enhancement extends the requirement for organizations to change default authenticators upon information system installation, by requiring developers and/or installers to provide unique authenticators or change default authenticators for system components prior to delivery and/or installation. However, it typically does not apply to the developers of commercial off-the-shelve information technology products. Requirements for unique authenticators can be included in acquisition documents prepared by organizations when procuring information systems or system components.
Select Distributed System and install the ASCS and the database on the database server.
2. Install the Application Server ABAP on the application server. Be sure to use the private addresses for the ASCS and the database hostnames during installation of the application server.



The use of the private addresses and hostnames assures that network traffic between the application server and ASCS, or database, passes through the private network and not through the public network.









 Step 5: Sample multipath.conf 

The following sample multipath.conf is for Red Hat 7.X and NetApp-based iSCSI LUNs.

defaults {
user_friendly_names no
max_fds max
flush_on_last_del yes
queue_without_daemon no
dev_loss_tmo infinity
fast_io_fail_tmo 5
}

All data under blacklist must be specific to your system.

blacklist {
wwid "SAdaptec"
devnode "^hd[a-z]"
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]"
devnode "^cciss."
}
devices {
device {
vendor "NETAPP"
product "LUN"
path_grouping_policy group_by_prio
features "3 queue_if_no_path pg_init_retries 50"
prio "alua"
path_checker tur
failback immediate
path_selector "round-robin 0"
hardware_handler "1 alua"
rr_weight uniform
rr_min_io 128
}
}
Show more

Sample multipath.conf multipaths extension for ‘human readable’ device paths:

multipaths {
multipath {
wwid XXXXYYYZZZ
alias pathname
}
}
If you encounter the following error: Error: INSTALLATION FAILED: Kubernetes cluster unreachable: xxxxxx failed to refresh token: oauth2: cannot fetch token: 400 Bad Request, set your cluster context and try again.







 Update an agent 

To update the agent version by using Helm, complete the following steps:



1. Update the chart.

helm repo update
2. Find the values yaml file that you used to deploy the agent and modify the agent.image.tag with the version of the agent that you want to deploy.
3. Upgrade the agent.

helm upgrade -n ibm-observe sysdig-agent sysdig/sysdig-deploy -f agent-values-monitor-secure.yaml







 Remove an agent 

To delete the agent by using Helm, you must uninstall the chart.

Complete the following steps:



1. List the charts that are installed.

helm list -n ibm-observe

The output of the command lists charts as follows:

NAME 	NAMESPACE 	REVISION	UPDATED 	STATUS 	CHART 	APP VERSION
sysdig-agent	ibm-observe	1 	2023-03-24 15:02:58.408108 +0100 CET	deployed	sysdig-deploy-1.6.3
2. Uninstall the chart.

helm delete sysdig-agent -n ibm-observe

In terms of Helm, sysdig-agent is the name of the release.

If you forget to include the namespace in the command, you get the following error: Error: uninstall: Release not loaded: sysdig-agent: release: not found.
* You have a previous installation that is earlier than 4.6: [Replace the pre-4.6 agent](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-wfs-cp4dconnector-wfs-cp4d-prereq1-replace)
* You are using the connector for the first time: [Install the agent](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-wfs-cp4dconnector-wfs-cp4d-prereq1-new)





 Replace the pre-4.6 agent 

Required for deployments where a version of the IBM Watson Discovery Agent for Windows File Systems that is earlier than 4.6.0.0 is installed.

To replace an earlier version of the agent, complete the following steps:



1. Copy the configuration file that defines the shared network directories that the Windows File System agent can access to a directory that is outside the agent's file path, which is C:Program Files (x86)IBMes.

For example, copy the C:Program Files (x86)IBMesdistributedesadminconfigesfsexport.txt file to a directory such as C:temp directory.
2. From the Microsoft Windows Apps & features utility, find the earlier version of IBM Watson Discovery Agent for Windows File Systems, and then click Uninstall.
3. Choose Completely delete IBM Watson Discovery Agent for Windows File Systems, and then click Uninstall.
4. Restart your system.
5. Complete the steps in [Installing the agent](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-wfs-cp4dconnector-wfs-cp4d-prereq1-task) to install the latest version of the agent.
6. Replace the new version of the C:Program FilesIBMesdistributedesadminconfigesfsexport.txt file with the file that you copied in Step 1.
Plug-in 'code-engine 1.23.2' was successfully installed into /Users/username/.bluemix/plugins/code-engine. Use 'ibmcloud plugin show code-engine' to show its details.
$





 How do I install a plug-in from a URL? 

Use the ibmcloud plugin install URL command to install a plug-in directly from a URL. For example:

ibmcloud plugin install http://example.com/downloads/my-plugin





 Which CLI plug-ins support private endpoints? 

To find out which installed CLI plug-ins support private endpoints, use the [ibmcloud plugin list](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_settingsibmcloud_plugin_list) command.





 Which regions support private endpoints? 

Regions that support private endpoints are us-east and us-south.

A region must be targeted when a private endpoint is set in the IBM Cloud CLI.

For more information about regions, see [Locations for resource deployment](https://cloud.ibm.com/docs/overview?topic=overview-locations) and [Service and infrastructure availability by location](https://cloud.ibm.com/docs/overview?topic=overview-services_region).
You can install the chart by using a variables yaml file like the one that you configured in the previous step, or you can configure the variables directly.

Run the following command to install the agent by using the helm chart and the variables yaml file:

helm install -n ibm-observe sysdig-agent sysdig/sysdig-deploy -f agent-values-monitor-secure.yaml

Run the following command to install the agent by using the helm chart and setting the variables:

helm install sysdig-agent sysdig/sysdig-deploy --namespace ibm-observe --create-namespace --set global.sysdig.accessKey=<SERVICE_ACCESS_KEY> --set agent.collectorSettings.collectorHost=<INGESTION_ENDPOINT> --set nodeAnalyzer.nodeAnalyzer.apiEndpoint=<API_ENDPOINT> --set global.kspm.deploy=true --set nodeAnalyzer.nodeAnalyzer.benchmarkRunner.deploy=false --set global.clusterConfig.name=<CLUSTER_NAME> --set kspmCollector.apiEndpoint=<API_ENDPOINT> --set agent.image.registry=icr.io --set agent.slim.image.repository=ext/sysdig/agent-slim --set agent.slim.kmoduleImage.repository=ext/sysdig/agent-kmodule

Where



* CLUSTER_NAME is the name of the cluster where you are deploying the agent.
* SERVICE_ACCESS_KEY is the Workload Protection instance access key.
* INGESTION_ENDPOINT is the instance's ingestion endpoint.
* API_ENDPOINT is the intance's API endpoint.



For example, for the US-East region, a sample Helm install looks as follows:
lo0: flags=e08084b, c0<UP, BROADCAST, LOOPBACK, RUNNING, SIMPLEX, MULTICAST, GROUPRT, 64 BIT, LARGESEND, CHAIN>
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
inet6 ::1%1/128
tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1

Show more
2. Using the information from the previous step, add an entry for your hostname and IP address into /etc/hosts. For example, echo "192.168.0.15 aix-7100-05-04" >> /etc/hosts.
3. Confirm that a valid bos.vendor.profile exists by copying the /usr/lpp/bosinst/bos.vendor.profile into the installp/ppc directory of the source repository. For example, cp /usr/lpp/bosinst/bos.vendor.profile /usr/sys/inst.images/installp/ppc/.
4. Run the following command, nim_master_setup -a device=/usr/sys/inst.images -a mk_resource=no.

Creating a NIM master:

 echo "192.168.2.228 mpb-test-aix" >> /etc/hosts
 nim_master_setup -a device=/usr/sys/inst.images -a mk_resource=no

 NIM master setup 
During script execution, lpp_source and spot resource creation times may vary.
To view the install log at any time during nim_master_setup, run the command: tail -f /var/adm/ras/nim.setup in a separate screen.
Creating image.data file...
5. Once completed, the NIM master file set has been installed and the basic resource objects created. The administrator is now able to add more NIM clients and define resources.

NIM master installation summary: