vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Preparing for SAP’s Software Provisioning Manager (SWPM) {: prepare-swpm-wins step}

SWPM is the component that guides you through the steps to successfully prepare and complete an SAP installation. Together with the other required images you may store and unpack SWPM on an extra file share that you then can attach to several VSIs on which you want to install SAP workloads.

 Installing SAP software {: install-sap-software-wins step}

Follow the instructions in the [SAP NetWeaver Installation Guide](https://help.sap.com/viewer/77e3a615f633437e9c4549891bb6bad7/CURRENT_VERSION/en-US){: external}. Also, review the corresponding SAP notes. See more detailed information about SAP NetWeaver installation that uses Db2 as the RDBMS in [Considerations about IBM Db2](/docs/sap?topic=sap-anydb-ibm-db2).

(/images/quickstudy-intel-vs-gen2-image4.png "Data volumes"){: caption="Figure 13. Data volumes" caption-side="bottom"}Figure 2. SAP Application instances]

Figure 2 illustrates the basic SAP instances that will be installed to deploy the SAP NetWeaver ABAP application server onto one host. If you now want to complete the single server instance - i.e. just using VSI sap-wdb, you need to launch sapinst only one time on that server. In this case, you will first install the ABAP Central Services Instance (ASCS), then the Database Instance DB and finally the Primary Application Server (PAS).

If you go for the more complex implementation, a distributed SAP System, you will need to launch sapinst on sap-wdb, install the ASCS and the DB and then run sapinst on sap-wapp to install the PAS. Then, it is necessary that you open specific ports to allow inter-application communication between the application server and the database server. To accomplish this, you must use Windows Firewall tool.

1. Start Windows Firewall with Advanced Security - enter wf.msc in Windows search field
1.
Mirrored N/A

$ oem_setup_env
 create_ova -o /datafs -d risotopes13_lv1 -t sles -e -f /use rhel for RHEL
Initializing resources ...

Checking for resource group ROOTVG...
Checking for resource group PIPEVIEWER...already installed.
Checking /datafs space requirement...done

Checking for resource group linux_20200511101424.img...
20480+0 records in1.2MiB/s] [10.6MiB/s] [=======================================================================> ] 99% ETA 0:00:00
20480+0 records out
20GiB 0:32:15 [10.6MiB/s] [10.6MiB/s] [=======================================================================>] 100%
41943040+0 records in
41943040+0 records out
done

Checking for resource group linux_20200511101424.ova.gz...
Checking /datafs space requirement...done
a ./linux_20200511101424.ovf 4 blocks
a ./linux_20200511101424.img 41943040 blocks
After this command completes successfully, it generates a new MSP folder in the directory that you specified by using the -M flag. This directory contains the certificates that you need to use to operate your components. You can verify that the enroll command worked by using a tree command. Navigate to the directory where you stored your certificates. A tree command should generate a result similar to the following structure: cd $HOME/fabric-ca-client
tree
.
├── ca-admin
│ ├── fabric-ca-client-config.yaml
│ └── msp
│ ├── IssuerPublicKey
│ ├── IssuerRevocationPublicKey
│ ├── cacerts
│ │ └── 9-30-250-70-30395-SampleOrgCA.pem
│ ├── keystore
│ │ └── 425947b767936a8f31780390cbc399cae48663b643e906ceb6944500d57b322c_sk
│ ├── signcerts
│ │ └── cert.pem
│ └── user
├── catls
│ └── tls.pem
├── orderer-admin
│ └── msp
│ ├── IssuerPublicKey
│ ├── IssuerRevocationPublicKey
│ ├── cacerts
│ │ └── 9-30-250-70-30395-SampleOrgCA.pem
│ ├── keystore
│ │ └── 30a12af2359cd96ec02ff5f47ad7793d2fefe3cde2be574bace18b24d36ba015_sk
│ ├── signcerts
│ │ └── cert.pem
│ └── user
└── peer-admin
└── msp
├── IssuerPublicKey
├── IssuerRevocationPublicKey
├── cacerts
│ └── 9-30-250-70-30395-SampleOrgCA.pem
├── keystore
* [How can I review the Code Engine service terms?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-faqsreview-service-terms)
* [How can I give feedback?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-faqsgive-feedback)







 Learning paths for Code Engine 

[Learning paths for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-learning-pathslearning-paths)



* [Plan your deployments](https://cloud.ibm.com/docs/codeengine?topic=codeengine-learning-pathslp-plan-deployments)
* [Install the tools](https://cloud.ibm.com/docs/codeengine?topic=codeengine-learning-pathslp-install-tools)
* [Create your first project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-learning-pathslp-set-environment)
* [Develop your application, job, or function](https://cloud.ibm.com/docs/codeengine?topic=codeengine-learning-pathslp-develop-app-job)
* [Deploy your application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-learning-pathslp-deploy-app)
* [Run your job](https://cloud.ibm.com/docs/codeengine?topic=codeengine-learning-pathslp-run-job)
* [Run your Function](https://cloud.ibm.com/docs/codeengine?topic=codeengine-learning-pathslp-run-fun)
* [Log and monitor your workloads](https://cloud.ibm.com/docs/codeengine?topic=codeengine-learning-pathslp-log-mon)
Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.<-- </section "id="section-en-notice-def" "> --><-- <section "id="section-en-notice-source-code" "> --> 1. Source Code The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities.
The following line assumes that MY_APP_NAME and MY_BUILD_NUMBER environment variables have already been set. POLICY is the name of the policy being evaluated.
ibmcloud doi gate-evaluate --logicalappname="$MY_APP_NAME" --buildnumber="$MY_BUILD_NUMBER" --policy POLICY





 Viewing gate evaluation 

You can view the results of the gate evaluation on the Risk Analysis page in DevOps Insights. The Risk Analysis page relies on the presence of a gate after a staging deployment job. Make sure that you have a gate after you deploy to the staging environment, but before you deploy to a production environment. For more information about the Risk Analysis page, see [Your deployment environments](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-deployment-environment).
2022/11/18 10:33:45 Request: blueprintId=Blueprint_Basic.eaB.08d1, account=1f7277194bb748cdb1d35fd8fb85a7cb, owner=schematics@in.ibm.com, requestID=1f97fde7-4921-4a46-bb29-296fbe25df44
2022/11/18 10:33:45 Related Job: jobID=us-east.JOB.Blueprint_Basic.a14e1e36
2022/11/18 10:33:57 --- Ready to execute the blueprint flow install command ---
2022/11/18 10:33:57 Processing Module Entry us-east.workspace.basic-resource-group.99503dea
2022/11/18 10:33:59 Module Status for ModuleID=us-east.workspace.basic-resource-group.99503dea is INACTIVE
2022/11/18 10:35:26 Install activity completed for module ModuleID=us-east.workspace.basic-resource-group.99503dea
2022/11/18 10:35:28 Status for module ModuleID=us-east.workspace.basic-resource-group.99503dea is ACTIVE
2022/11/18 10:35:30 Processing Module Entry us-east.workspace.basic-cos-storage.99a35e10
2022/11/18 10:35:31 Module Status for ModuleID=us-east.workspace.basic-cos-storage.99a35e10 is INACTIVE
2022/11/18 10:37:11 Install activity completed for module ModuleID=us-east.workspace.basic-cos-storage.99a35e10
2022/11/18 10:37:13 Status for module ModuleID=us-east.workspace.basic-cos-storage.99a35e10 is ACTIVE
2022/11/18 10:37:16 ENVIRONMENT_INSTALL - ENVIRONMENT_SYSTEM_STATEENUM_job_finished
2022/11/18 10:37:17 Done with the blueprint install flow job
* [Running a container as non-root](https://cloud.ibm.com/docs/codeengine?topic=codeengine-dockerfilecontainer-non-root)







 Integrating Code Engine workloads with Continuous Delivery 

[Integrating Code Engine workloads with Continuous Delivery](https://cloud.ibm.com/docs/codeengine?topic=codeengine-toolchain-cetoolchain-ce)



* [Before you begin](https://cloud.ibm.com/docs/codeengine?topic=codeengine-toolchain-cetoolchain-begin)
* [Configuring access for your toolchain](https://cloud.ibm.com/docs/codeengine?topic=codeengine-toolchain-cepermissions-toolchain)
* [Creating a toolchain](https://cloud.ibm.com/docs/codeengine?topic=codeengine-toolchain-cecreate-toolchain)
* [Code Engine options in your toolchain](https://cloud.ibm.com/docs/codeengine?topic=codeengine-toolchain-cetoolchain-options)
* [Troubleshooting toolchain issues](https://cloud.ibm.com/docs/codeengine?topic=codeengine-toolchain-cets-toolchain)







 Setting up Terraform for Code Engine 

[Setting up Terraform for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-terraform-setup-ceterraform-setup-ce)



* [Installing Terraform and configuring resources for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-terraform-setup-ceinstall-terraform)
* [What's next?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-terraform-setup-ceterraform-setup-next)
Learning paths for Code Engine 

Find your path to accomplish what you want with IBM Cloud® Code Engine.



 Plan your deployments 

Before you start, [learn about Code Engine and some common terms](https://cloud.ibm.com/docs/codeengine?topic=codeengine-about).

Then, decide whether you want to deploy an application, create a job, or run a function by reading [planning for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-codeengine).

You can even try out our [application tutorial](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-app-tutorial), our [job tutorial](https://cloud.ibm.com/docs/codeengine?topic=codeengine-run-job-tutorial), or our [function tutorial](https://cloud.ibm.com/docs/codeengine?topic=codeengine-fun-tutorial).





 Install the tools 

If you plan to use the CLI, you must [install it](https://cloud.ibm.com/docs/codeengine?topic=codeengine-install-cli). As you work with your Code Engine workloads, refer to the [CLI command reference](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli) and track CLI version updates with the [CLI change log](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions). You can also [access the IBM Cloud Shell](https://cloud.ibm.com/docs/codeengine?topic=codeengine-install-clicloud-shell) in your web browser.

If you do not want to use the CLI, you can [work from the console](https://cloud.ibm.com/codeengine/overview).





 Create your first project
Planning your deployment 

Make sure that you are already familiar with the fundamental components and options that are provided by IBM Cloud Classic Infrastructure for SAP. Before you start with the deployment of servers, make sure that you also read the Get Started section.



  The 'Must-Reads' before you start deploying 

To ensure that your first deployment is a success, review the following information:



*  [Classic Infrastructure environment introduction](https://cloud.ibm.com/docs/sap?topic=sap-classic-env-introduction)
*  The Plan your SAP workloads topic group
*  The Infrastructure for SAP design considerations topic group





  Other useful documents 

See the respective topics in the Get Started section for the following information:



*  [SAP HANA design considerations for High Availability and Disaster Recovery (HA/DR)](https://cloud.ibm.com/docs/sap?topic=sap-hana-design-considerationshana-ha)
*  [SAP HANA backups - Storage impacts on Recovery Time Objective (RTO)](https://cloud.ibm.com/docs/sap?topic=sap-storage-design-considerationsstorage-performance-backup-rto)
*  [SAP NetWeaver design considerations for High Availability configuration](https://cloud.ibm.com/docs/sap?topic=sap-netweaver-design-considerationsnetweaver-ha)
Storage policy – The values here depend on what was provisioned in the instance. In this example, 4 IOPS/GB is used (VDC Default).
5. NICs – Check the box for connected and then in the drop-down field below network select the network created in the first step. In this example, net-application is used. In the drop-down below IP mode, select Static-IP Pool.



6. Leave all other values at their defaults and click OK when complete.



The new virtual machine will be created. Provisioning of the virtual machine may take several minutes to complete. Upon completion, the virtual machine will automatically power on. Repeat the process for the other virtual machines, application-server-1 and db-server-1.

Virtual machine db-server-1 requires two NICs, but as the default template only has one. So, you need to [add that post initial provisioning](https://docs.vmware.com/en/VMware-Cloud-Director/10.4/VMware-Cloud-Director-Tenant-Portal-Guide/GUID-FA8C101E-241E-41A5-A3C3-83BDBB4467F1.html). After the virtual machine has been created, click Details. Then select NICs under the Hardware, and you can add the 2nd NIC to the virtual machine and attach that to the correct network segment.

Review the other hardware options and see what you can change and how. See [Edit Virtual Machine Properties section on VMware Cloud Director Tenant Guide](https://docs.vmware.com/en/VMware-Cloud-Director/10.4/VMware-Cloud-Director-Tenant-Portal-Guide/GUID-FA8C101E-241E-41A5-A3C3-83BDBB4467F1.html) for more details.





 Step 3: Create IP Sets and Static Groups 

IP Sets and Static Groups are used as part of configuration of the firewall rules are required.
[Control plane in normal state](https://cloud.ibm.com/docs-content/v1/content/3505da55c475bf1edbe3eb3496324ba13941b783/databases-for-postgresql/includes/cloud-databases/includes/cloud-databases/images/cp-normal.png)

Figure 1. Control plane in normal state

Attempting to provision a database instance into a location without a running Control plane (that is, Normal state), causes provisioning to fail.







 Step 4: Provisioning ICD Satellite Deployment 

You can provision your ICD Satellite Deployment by selecting the Satellite location that you created in the Location menu of the provisioning page. For more information, see the relevant [Provisioning documentation](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-provisioning) for your ICD Satellite deployment. After you create a new service instance, this instance will appear in the IBM Cloud Resource List as Provisioned.

When you deploy the first database service instance, a service cluster is automatically deployed into your Satellite location. The deployment of the service cluster can take up to 1 hour.

You can verify in the IBM Cloud UI whether the service cluster is already created:



* From the left Navigation menu, select Satellite, then Locations.
* Select your Satellite location.
* Select Services



After the service cluster is created, you must create a storage assignment manually (see next step)before the database instance will be started. Subsequent database service instances provision more quickly since instances land on the same service cluster.





 Create a Storage Assignment 

When the service cluster is available in your Satellite location, the next step is to create a Satellite storage assignment. Creating the storage assignment allows the service cluster to create volumes on the previously configured storage.

The first database you provision into a location remains "Provision In Progress" until this step is complete.

For more information, see [AWS EBS IBM Cloud Satellite documentation](https://cloud.ibm.com/docs/satellite?topic=satellite-config-storage-ebs).
Planning your environment for Satellite 

Plan how to set up your infrastructure environment to use with IBM Cloud Satellite®. Your infrastructure environment can be an on-premises data center, in a public cloud provider, or on compatible edge devices anywhere.

Your Satellite location starts with your infrastructure, such as a public cloud provider or on-prem. Your infrastructure provides the basis for the hosts and zones that you use to build out your Satellite location. For more details on the different responsibilities for your infrastructure and Satellite resources, see [Your responsibilities](https://cloud.ibm.com/docs/satellite?topic=satellite-responsibilities).

Zoom

![Concept overview of planning your infrastructure](https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite//images/plan-sat-envirn.svg)

Figure 1. Your Satellite location is built atop the zones and hosts in your infrastructure provider.



 Planning your infrastructure 

Before you create your location, choose your infrastructure provider, infrastructure zones, and your infrastructure hosts.



 Plan your infrastructure provider 

Choose the infrastructure provider that you want to use to create a Satellite location.

On-premises
: You can use a data center with existing infrastructure. You might not even have a data center, but rather an edge location that meets the minimum hardware requirements, such as three racks at one of your company's local sites.

Supported bare metal servers
: You can use a supported bare metal server as a host attached to your Satellite location, including IBM Cloud® Bare Metal Servers for Classic. For more information, see [Bare Metal Server requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-assign-bare-metalsetup-bare-metal).

Non-IBM cloud provider
From the [IBM Cloud resource list](https://cloud.ibm.com/resources), find the Portworx service that you created.
4. Review the Status column to see if the installation succeeded or failed. The status might take a few minutes to update.
5. If the Status changes to Provision failure, follow the [instructions](https://cloud.ibm.com/docs/containers?topic=containers-debug-portworx) to start troubleshooting why your installation failed.
6. If the Status changes to Provisioned, verify that your Portworx installation completed successfully and that all your local disks were recognized and added to the Portworx storage layer.



1. List the Portworx pods in the kube-system namespace. The installation is successful when you see one or more portworx, stork, and stork-scheduler pods. The number of pods equals the number of worker nodes that are in your Portworx cluster. All pods must be in a Running state.

kubectl get pods -n kube-system | grep 'portworx|stork'

Example output

portworx-594rw 1/1 Running 0 20h
portworx-rn6wk 1/1 Running 0 20h
portworx-rx9vf 1/1 Running 0 20h
stork-6b99cf5579-5q6x4 1/1 Running 0 20h
stork-6b99cf5579-slqlr 1/1 Running 0 20h
stork-6b99cf5579-vz9j4 1/1 Running 0 20h
stork-scheduler-7dd8799cc-bl75b 1/1 Running 0 20h
stork-scheduler-7dd8799cc-j4rc9 1/1 Running 0 20h
stork-scheduler-7dd8799cc-knjwt 1/1 Running 0 20h
2.
If you are performing a mirrored installation (for example, in an air-gapped environment), you need to perform an additional step before completing either of the following steps:



* Step 7 [Mirroring the images to the private registry](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=registry-mirroring-images-bastion-nodereference_g4h_z1q_tpb__mirror-to-target) of Mirroring images with a bastion model
* Step 8 [Mirroring the images to the intermediary container registry](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=registry-mirroring-images-intermediary-containerpreinstall_container_registry_air_gapped__mirror-to-target) of Mirroring images with an intermediary container registry



This step is mandatory to copy the necessary images for the Minio datastore:

echo 'cp.icr.io,cp/opencontent-minio-client,1.1.4,sha256:7b4cf5e47a0455cfa7ca9ab246b80916e4dccbc1483b3e0f276fb7b0ab3e5c60,IMAGE,linux,x86_64,"",0,CASE,"",""' >> $CASE_PATH/ibm-watson-speech-4.0.5-images.csv

Failure to perform this step will cause installation errors for both Speech to Text and Text to Speech.

Important: Additional steps for performing a mirrored installation of new next-generation models
: Important: These steps are no longer needed if you install case package 4.0.6. For more information, see [28 January 2022 (Version 4.0.5)](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-release-notes-dataspeech-to-text-data-28january2022).
See [Configuring a CA, peer, or ordering node to use the HSM](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-cfg-hsm) for more information.







 Enable network policy 

Enable network policy will automatically install when the console is created. In the operator deployment specification, the operator needs to add an environment variable IBPOPERATOR_CONSOLE_APPLYNETWORKPOLICY and set its value to true.

kubectl edit deploy ibp-operator -n <offering-namespace>

In the environment section under spec.containers, add the following:

- name: IBPOPERATOR_CONSOLE_APPLYNETWORKPOLICY
value:"true"

When the option above is enabled, the operator will install two network policies during the console installation. These network policies are meant to give basic defensive security mechanism, and opens only the ports that the offering uses. This by no means is a policy that can replace a firewall. The policies applied provide ingress security, as blockchain network may require to call npm, gradle, maven servers to get chaincode modules as well as to communicate with the orderers/peers/applications running outside the cluster on internet we do not provide egress policies.

The following two policies are applied:



1. Deny-all-ingress.



This policy denies all ingress (ingress: []) network traffic to the pods (podSelector: {}) in the namespace it applies to. This ensure only the needed traffics go through.

kind: NetworkPolicy
apiVersion: networking.k8s.io/v1
metadata:
name: networkpolicy-denyall
namespace: <>
labels:
type: "ibp-console"
app.kubernetes.io/name: "ibp"
app.kubernetes.io/instance: "ibp-console"
app.kubernetes.io/managed-by: "ibp-operator"
release: "operator"