Hello and welcome to the SAP HANA Academy.
The topic of this video tutorial series is SAP HANA as a Service and in this video we
will take a look at how we create SAP HANA databases, as a service, in the Neo environment
on the SAP Cloud Platform.
This video has been recorded in December 2018.
For earlier or later releases, please check the playlist on the SAP HANA Academy.
Hi, I am Denys van Kempen.
This video is part of a series.
In the first video, we provided a bit of background and showed you where to find more information.
In this second video, we will look at database creation in the Neo environment and in the
next, we repeat the exercise for Cloud Foundry.
There are already videos about how to create HANA databases on the Cloud Platform, so I
am not going to repeat that material here.
The focus will be on the differences between both environments, so you will know which
one to choose.
OK — Hands on
I am connected here to the SAP Cloud Platform Cockpit.
My Home is in Amsterdam.
If we look at the services, search of HANA, we get SAP HANA, create and consume SAP HANA
databases.
So, there is a single service, available in different regions, in different environments,
and the documentation will point you to the help portal, we already looked at that; further
information points to the cloudplatform.sap.com.
If we go into our global account, before we go into our subaccounts, which will be associated
with a particular environment, you need to check your entitlements.
Filter on HANA (there are two entries but they display the same list).
What you will see here depends on your contract.
Basically we have an entry for the SAP HANA Service in the Cloud Foundry environment and
for the one in Neo.
You can edit them and change the assignments.
In Neo, this works with 64GB units.
In Cloud Foundry, the size is decided upon at a later stage, we will see that in the
next video.
Here you just indicate how many standard or enterprise units you want.
If we then go to Subaccounts, you can see that we have one for Cloud Foundry (Cloud
Frankfurt) and one for Neo (Neo Amsterdam), both in Europe.
In this video we will look at Neo.
Here we have our Overview page.
I don’t have any Java or HTML5 (XS classic) apps.
I will just focus on the database side.
Enhanced Disaster Recovery is not enabled but this is an option.
Basically, this would setup replication, SAP HANA system replication, between two sites.
High Availability on Cloud Foundry works differently, as we will see in the next video.
For the databases to appear in the menu, we first need to enable the service for this
subaccount.
Services
So, now we are looking at the services for this Neo Subaccount, availability of services
depends on the environment and the region: HANA under Data Management.
It needs to be enabled.
Select it will bring us to Databases & Schemas:
I have created a single tenant database, named it tenant, and it is part of the ha1 database
system (HANA MDC).
MDC stands for multiple database containers.
If we select the system,
We can see that we one database system ha1 (HANA MDC) with a single tenant.
The version is 1.0 (HANA 1.0) revision 122, that’s a maintenance release for SPS 12.
To create an entirely new HANA system, click New Database System.
This will trigger account information collection and then we get the Create Database System
dialog.
Here you select the type, either MDC or XS.
Now, XS is just a label here.
It could have been SDC as well, single database container system, because that is what it
is.
Maybe for those less familiar, HANA 1.0 started out as a single database, meaning that a HANA
system and a HANA database were synonyms: same thing.
In SPS 09, November 2014, multi-tenant database containers were introduced with the objective
to share hardware more efficiently and as of SAP HANA 2.0 SPS 01, from last year, multi-tenant
is the only database mode, but here on Neo, as we just saw, we are on SPS 12, so we get
to choose.
Select the version, at the time of the recording, the options are the latest SPS 12 maintenance
releases with a link to the SAP Note for more information.
Then the amount of memory, the available quota you want to allocate.
The name, needs to be in lowercase.
And the network visibility, internal or external, and then click Start.
This will take some time.
Note that I have selected HANA XS, here this means a single-tenant system.
HANA XS, the built-in application server, is also available in the MDC environment,
in each tenant in fact, so it is not that you have choose between XS and MDC.
XS here is just a label.
The creation, or provisioning I should say, takes a fair amount of time.
Fast forward, eventually, we will have a new database system: ha1 MDC, ha2 XS.
XS is also listed with 1 tenant but if we select it, we cannot add any additional tenant.
So, for an MDC system we can add tenants.
For an XS system, we cannot.
Now the purists amongst us might argue that a single container system does not have tenants
but we will leave that for now.
For the rest, the UI works the same for both types.
We have an overview page,
It is online.
We can restart the system
Note that we cannot stop and start it.
There is no stop button.
We can check for updates.
This will launch the Platform Lifecycle Management tool (PLM).
Those who have worked with SAP HANA installations in on-premise environments will recognise
this, same tool.
Similarly, we can add components.
Again, this launches PLM.
Works the same way.
Here you can add APL, SHINE or Smart Data Streaming, this is HANA 1.0.
For HANA 2.0, this would be Streaming Analytics, same product for Complex Event Processing.
You can uninstall components and you can delete your system here as well.
The whole system, not just the tenant database.
High Availability and Distastes Recovery can be configure here: this would set up system
replication.
The System ID is HANA_A3J_FACTORYEU3.
EU3 is the subdomain for Neo.
We get the memory size.
You cannot change this, at least not with self-service, this would require a service
request.
Metrics view details goes to the monitoring section.
Shows a number of alerts, some charts: metrics history.
Memory Usage, is only available for an MDC system and HANA XS is single-container, as
we just discussed.
Tenant Database goes to the Databases page.
Before we click on the entry ha2 in the Database ID column, let’s also review our MDC system.
Like I said, works exactly the same except that we now get some data for memory usage
and here we can see that we have a SYSTEMDB and a tenant.
However, if we go to our databases page, we only see tenant listed.
Not systemdb, we can only connect to our tenant.
C’est la vie.
OK — select it, and the tenant Overview page opens.
Note that this time we can stop our tenant (and start it again, obviously).
We can delete the tenant, not the system, just the tenant.
And we can configure it, and this covers this area here.
Web access, enabled or not, XS engine, the built-in application server for HANA 1.0,
embedded or not (this is a technical implementation detail).
Memory limit for the index server and whether the Script Server and Data Provisioning server
are enabled for this tenant.
Data provisioning is for SDI, smart data integration.
The script server is used for the predictive analysis library, amongst others.
If we click Configure, we can change web access and set a memory limit for this tenant.
If we want to change the other parameters, we could decide to create a new tenant database,
or, this should work as well, log a service request.
So, if we return to our system.
Databases.
And click New Database
We get the same parameters we just saw.
XS engine embedded or standalone
If stand-alone, we can limit the memory allocation.
Index server memory allocation.
Script Server, Data Provisioning.
Note that we also define the SYSTEM password here.
When we created our database system, we were not prompted for a password.
If we look at the same page for a single-container system, it looks a little different.
We do not have any buttons to stop or start the database and we cannot configure it.
It is what it is.
From the Overview page, we can connect to our actual database tools and we also have
the JDBC URL, should you want to connect some other tools.
If we binded any apps to the database, this would be listed here as well.
From here we can then connect to the SAP HANA Web-based Development Workbench and to Cockpit
for HANA 1.0
Single-container will list the system identifier in the header (we did not get to specify one),
this will be randomly assigned, or, in case of a tenant, NEO, some string, name of the
database (tenant in our case) @ and then the system identifier.
OK —That’s it.
SAP HANA as a Service for the Neo environment.
Thanks for watching.
You can find more video tutorials on our YouTube channel.
If you would like to be informed about new video tutorials, please subscribe to our channel.
You can connect with us on LinkedIn or follow us on Twitter, as well for updates, and if
you are watching this video on YouTube, do not hesitate to leave your comments to the
video page and, if you like, give us your vote on this video.
Thank you for watching.