Skip to content

Latest commit

 

History

History
49 lines (27 loc) · 6.03 KB

netweaver.md

File metadata and controls

49 lines (27 loc) · 6.03 KB
Raw

NetWeaver

Besides the default SAP HANA and HA cluster environment, the project can be tuned to deploy a SAP NetWeaver environment too. This allows to have a NetWeaver landscape working with the SAP HANA database (by now, the project only works with SAP HANA as database). The next SAP NetWeaver components are available:

  • ASCS instance
  • ERS instance
  • PAS instance
  • AAS instance
  • Database instance (this adds the required users, tables, views, etc to the current HANA database)

The deployment will create 4 new virtual machines to host the NetWeaver environment and a new shared disk used by the ASCS and ERS instances.

Besides the standard installation, an additional HA cluster might be added in top of the ASCS and ERS communication to assure high availability between these two components using the sap_suse_cluster_connector (HA is enabled by default).

More details in the official Suse documentation:

SAP NetWeaver Enqueue Replication 1 High Availability Cluster - Setup Guide for SAP NetWeaver 7.40 and 7.50🔗 pdf (en)🔗

SAP S/4 HANA - Enqueue Replication 2 High Availability Cluster - Setup Guide🔗 pdf (en)🔗

The deployment is performed using the sapnwbootstrap-formula🔗.

Available for libvirt, azure, gcp and aws.

Quickstart

In order to deploy a SAP NetWeaver environment with SAP HANA some changes must be executed in terraform and salt folders. By default SAP NetWeaver is not enabled.

  • In order to enable/disable the NetWeaver deployment update the value of netweaver_enabled variable to true/false in the terraform.tfvars file.

  • Set the netweaver_ha_enabled option to create a ASCS, ERS, PAS and AAS environment. Setting this value to false will only create a ASCS and PAS without any HA functionality

  • In order to deploy a correct NetWeaver environment a NFS share is needed (SAP stores some shared files there). The NFS share must have the folders sapmnt and usrsapsys in the exposed folder. It's a good practice to store this folder with the NetWeaver SID name (for example /sapdata/HA1/sapmnt and /sapdata/HA1/usrsapsys). This subfolders content is removed by default during the deployment. This NFS share can be created using the provided drbd module deployment that fully automate this (drbd deployment is required for azure and gcp, aws uses the EFS storage by default).

  • For libvirt: Add the netweaver_inst_media variable to the terraform.tfvars with the address to the NFS share containing the NetWeaver installation software (swpm) folder, sapexe folder, NetWeaver Export folder and HANA HDB Client folders (NetWeaver Export and HANA HDB Client are required if the Database, PAS and AAS instances need to be installed). The netweaver.sls pillar file must also be updated with all this information. NetWeaver Export and HANA HDB Client folders must be provided in additional_dvds list.

  • For azure: Add the azure storage account variables to the terraform.tfvars with the , sapexe folder, NetWeaver Export folder and HANA HDB Client folders (NetWeaver Export and HANA HDB Client are required if the Database, PAS and AAS instances need to be installed). The netweaver.sls pillar file must also be updated with all this information. NetWeaver Export and HANA HDB Client folders must be provided in additional_dvds list.

  • For aws: Add the aws S3 bucket variable (netweaver_s3_bucket) to the terraform.tfvars with the , sapexe folder, NetWeaver Export folder and HANA HDB Client folders (NetWeaver Export and HANA HDB Client are required if the Database, PAS and AAS instances need to be installed). The netweaver.sls pillar file must also be updated with all this information. NetWeaver Export and HANA HDB Client folders must be provided in additional_dvds list. Note: NetWeaver will use the Amazon Elastic File System(EFS) for its NFS share by default, unless drbd option is enabled (using drbd_enabled variable).

  • For gcp: Add the gcp storage bucket variable to the terraform.tfvars with the , sapexe folder, NetWeaver Export folder and HANA HDB Client folders (NetWeaver Export and HANA HDB Client are required if the Database, PAS and AAS instances need to be installed). The netweaver.sls pillar file must also be updated with all this information. NetWeaver Export and HANA HDB Client folders must be provided in additional_dvds list.

  • Add new additional IP addresses to the variable nw_ips and nw_virtual_ips in the terraform.tfvars. This variable is a list containing the IP addresses of the new virtual machines hosting the NetWeaver components, so if 4 virtual machines are used (default option) 4 addresses must be added there in the same range than the machines hosting the HANA database.

  • Add the netweaver_nfs_share variable to the terraform.tfvars with the address to the NFS share containing the sapmnt and usrsapsys folders. Following the current example this would be nfs_address:/sapdata/HA1.

  • Modify the content of cluster.sls and netweaver.sls in directory ../pillar/netweaver/. The unique mandatory changes are swpm_folder, sapexe_folder and additional_dvds in the netweaver.sls file. Example files can be found in the example directory. These values must match with the folder of your sap_inst_media, the current values are just an example.

  • If the netweaver.sls pillar file from pillar_examples/automatic/netweaver is used, the parameters netweaver_swpm_folder, netweaver_sapexe_folder and netweaver_additional_dvds must be set in the tfvars file with the same data explained in the previous points.