HANA Single-Node Instance
This simple scenario deploys a single-node HANA instance and an optional bastion host in the Azure Cloud.
Table of contents
The following options can be customized in the single-node scenario:
|HANA version||Which version of HDB Server to install|
|HANA 1.0 SPS12 (PL13 or higher)||
|HANA 2.0 SPS2 or higher||
|Database containers *||Whether to install HDB with single or multiple database containers (tenants)|
|Single container (HANA 1.0 only)||
|Multi-database containers (MDC)||
|Bastion host *||Whether to deploy a bastion host ("jump box") through which the HANA VM can be accessed|
|No bastion host||
|Windows bastion host (incl. HANA Studio)||
|Linux bastion host (incl. HANA Studio)||
|SAP Applications||Which SAP applications to install on top of HANA (if any)|
|SAP HANA Cockpit (requires XSA)||
|SHINE Demo Content (requires XSA)||
|WebIDE (requires XSA)||
(Note: Features marked with an * are work in progress and not fully available yet.)
If you haven't already done so, please make sure you prepare your Azure Cloud Shell.
(Note: Please review the list of SAP downloads; depending on which features and applications you would like to include in your HANA installation, you may need additional packages.)
In your Azure Cloud Shell, change into the directory for the HANA single-node scenario:
terraform.tfvarsfile for your deployment. You can use the provided Boilerplate template for single-node scenarios as a starting point and adjust the variables according to your requirements.
(Note: You need to rename the boilerplate template from
terraform.tfvars before you can use it.)
Should you wish to delete your HANA single-node instance at a later point, you can simply follow the general instructions on the overview page.