You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"description": "'SAP ready PowerVS' variation of 'Power Virtual Server for SAP HANA' creates a basic and expandable SAP system landscape builds on the foundation of the 'Power Virtual Server with VPC landing zone'. PowerVS instances for SAP HANA and SAP NetWeaver are deployed and preconfigured for SAP installation.\n\nServices such as DNS, NTP and NFS running in VPC and provided by 'Power Virtual Server with VPC landing zone' are leveraged.\n\nThe resulting SAP landscape leverages the services such as Activity Tracker, Cloud Object Storage, Key Management and the network connectivity configuration provided by 'Power Virtual Server with VPC landing zone'."
@@ -767,7 +767,7 @@
767
767
{
768
768
"diagram": {
769
769
"caption": "Full SAP S/4HANA or BW/4HANA environment provisioned on a 'Power Virtual Server with VPC landing zone'",
"description": "'SAP S/4HANA or BW/4HANA' variation of 'Power Virtual Server for SAP HANA' creates a basic and expandable SAP system landscape builds on the foundation of 'Power Virtual Server with VPC landing zone'. PowerVS instances for SAP HANA and SAP NetWeaver are deployed and preconfigured for SAP installation. S/4HANA or BW/4HANA solution is installed based on selected version. \n\nServices such as DNS, NTP and NFS running in VPC and provided by 'Power Virtual Server with VPC landing zone' are leveraged.\n\nThe resulting SAP landscape leverages the services such as Activity Tracker, Cloud Object Storage, Key Management and the network connectivity configuration provided by the 'Power Virtual Server with VPC landing zone'. Additionally if a Monitoring Instance was configured in the 'Power Virtual Server with VPC landing zone' deployment, this solution will then install and enable SAP monitoring Dashboard."
@@ -55,6 +55,7 @@ The Power Virtual Server for SAP module automates the following tasks:
55
55
| <aname="input_pi_instance_init_linux"></a> [pi\_instance\_init\_linux](#input\_pi\_instance\_init\_linux)| Configures a PowerVS linux instance to have internet access by setting proxy on it, updates os and create filesystems using ansible collection [ibm.power\_linux\_sap collection](https://galaxy.ansible.com/ui/repo/published/ibm/power_linux_sap/) where 'bastion\_host\_ip' is public IP of bastion/jump host to access the 'ansible\_host\_or\_ip' private IP of ansible node. This ansible host must have access to the power virtual server instance and ansible host OS must be RHEL distribution. | <pre>object(<br/> {<br/> enable = bool<br/> bastion_host_ip = string<br/> ansible_host_or_ip = string<br/> ssh_private_key = string<br/> custom_os_registration = optional(object({<br/> username = string<br/> password = string<br/> }))<br/> }<br/> )</pre> | n/a | yes |
56
56
| <a name="input_pi_netweaver_instance"></a> [pi\_netweaver\_instance](#input\_pi\_netweaver\_instance) | PowerVS SAP NetWeaver instance hostname (non FQDN). Will get the form of <var.prefix>-<var.powervs\_netweaver\_instance\_name>-<number>. Max length of final hostname must be <= 13 characters. 'instance\_count' is number of SAP NetWeaver instances that should be created. 'instance\_count' cannot exceed 10. 'size' is in GB. 'count' specify over how many storage volumes the file system will be striped. 'tier' specifies the storage tier in PowerVS workspace. 'mount' specifies the target mount point on OS. | <pre>object({<br/> instance_count = number<br/> name = string<br/> image_id = string<br/> processors = string<br/> memory = string<br/> proc_type = string<br/> storage_config = list(object({<br/> name = string<br/> size = string<br/> count = string<br/> tier = string<br/> mount = string<br/> }))<br/> })</pre> | <pre>{<br/> "image_id": "insert_value_here",<br/> "instance_count": 1,<br/> "memory": "32",<br/> "name": "nw",<br/> "proc_type": "shared",<br/> "processors": "3",<br/> "storage_config": [<br/> {<br/> "count": "1",<br/> "mount": "/usr/sap",<br/> "name": "usrsap",<br/> "size": "50",<br/> "tier": "tier3"<br/> }<br/> ]<br/>}</pre> | no |
57
57
| <aname="input_pi_networks"></a> [pi\_networks](#input\_pi\_networks)| Existing list of subnets to be attached to PowerVS instances. The first element will become the primary interface. Run 'ibmcloud pi networks' to list available private subnets. | <pre>list(<br/> object({<br/> name = string<br/> id = string<br/> cidr = optional(string)<br/> })<br/> )</pre> | n/a | yes |
58
+
| <aname="input_pi_region"></a> [pi\_region](#input\_pi\_region)| The region of the PowerVS workspace where the instances will be deployed. Needed to determine server type for NetWeaver instances. |`string`| n/a | yes |
58
59
| <aname="input_pi_sap_network_cidr"></a> [pi\_sap\_network\_cidr](#input\_pi\_sap\_network\_cidr)| Additional private subnet for SAP communication which will be created. CIDR for SAP network. E.g., '10.53.0.0/24' |`string`|`"10.53.0.0/24"`| no |
Copy file name to clipboardExpand all lines: reference-architectures/sap-ready-to-go/deploy-arch-ibm-pvs-sap-ready-to-go.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
copyright:
4
4
years: 2024, 2025
5
-
lastupdated: "2025-03-26"
5
+
lastupdated: "2025-04-16"
6
6
keywords:
7
7
subcollection: deployable-reference-architectures
8
8
authors:
@@ -17,7 +17,7 @@ use-case: ITServiceManagement
17
17
industry: Technology
18
18
compliance: SAPCertified
19
19
content-type: reference-architecture
20
-
version: v4.0.0
20
+
version: v4.1.0
21
21
related_links:
22
22
- title: 'SAP in IBM Cloud documentation'
23
23
url: 'https://cloud.ibm.com/docs/sap'
@@ -39,7 +39,7 @@ related_links:
39
39
{: toc-industry="Technology"}
40
40
{: toc-use-case="ITServiceManagement"}
41
41
{: toc-compliance="SAPCertified"}
42
-
{: toc-version="v4.0.0"}
42
+
{: toc-version="v4.1.0"}
43
43
44
44
The SAP-ready PowerVS variation of the Power Virtual Server for SAP HANA creates a basic and expandable SAP system landscape. The variation builds on the foundation of the VPC landing zone and Power Virtual Server with VPC landing zone. PowerVS instances for SAP HANA and SAP NetWeaver are deployed and pre-configured for SAP installation.
Copy file name to clipboardExpand all lines: reference-architectures/sap-s4hana-bw4hana/deploy-arch-ibm-pvs-sap-s4hana-bw4hana.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
copyright:
4
4
years: 2024, 2025
5
-
lastupdated: "2025-03-26"
5
+
lastupdated: "2025-04-16"
6
6
keywords:
7
7
subcollection: deployable-reference-architectures
8
8
authors:
@@ -17,7 +17,7 @@ use-case: ITServiceManagement
17
17
industry: Technology
18
18
compliance: SAPCertified
19
19
content-type: reference-architecture
20
-
version: v4.0.0
20
+
version: v4.1.0
21
21
related_links:
22
22
- title: 'SAP in IBM Cloud documentation'
23
23
url: 'https://cloud.ibm.com/docs/sap'
@@ -39,7 +39,7 @@ related_links:
39
39
{: toc-industry="Technology"}
40
40
{: toc-use-case="ITServiceManagement"}
41
41
{: toc-compliance="SAPCertified"}
42
-
{: toc-version="v4.0.0"}
42
+
{: toc-version="v4.1.0"}
43
43
44
44
'SAP S/4HANA or BW/4HANA' variation of 'Power Virtual Server for SAP HANA' creates a basic and expandable SAP system landscape built on the foundation of 'Power Virtual Server with VPC landing zone'. PowerVS instances for SAP HANA and SAP NetWeaver are deployed and pre-configured for SAP installation. The S/4HANA or BW/4HANA solution is installed based on the selected version.
0 commit comments