Hello and welcome to the SAP HANA Academy.
The topic of this video tutorial series is Getting Started with SAP HANA on the Google Cloud Platform
and in this video we will perform some of the reconfiguration steps for the
SAP HANA, express edition VM, the one we created in the previous video.
Hi, I am Denys van Kempen.
I am connect here to the Console and in the menu Products & Services, I will select Deployment Manager,
here, in the Tools section.
Now, you may recall that we pinned this item, so it appears on here under Home.
This will allow us to quickly get to location we want in the console.
There are a lot of products and services here on Google Cloud Platform and we are not concerned
with all of them for SAP HANA, so you might want to pin the ones you use.
In the previous video, we used Cloud Launcher to deploy the SAP HANA, express edition solution.
The Deployment Manager keeps a list of all our Cloud Launcher deployments.
We can see that Jinja is used to run a python script (.py) to create a virtual machine instance
and a number of firewall rules.
If you are familiar with Jinja and the Python script language, you can create your own deployments,
we may look at that in a future video, but for now let’s focus on what we got here.
If you select the menu, and then in the Compute section, point to Compute Engine, VM instances
- you may want to pin Compute Engine as well, we will need it again -
and this will open up the Compute Engine menu.
VM instances at the top.
Here we also have Instance templates, Disks, Snapshots, Images;
Under Settings, you can define the default location.
Remember that when I deployed HANA express, I changed the location from the US to Europe.
If you want your preferred region to be selected each time you create a VM, you can set this here.
I will pick europe-west1 as region and west1-b as zone.
Hoover over the question mark and open 'Learn more' to get to the documentation about regions and zones.
Basically, zones provide fault tolerance for a particular region.
Some resources are zonal, that is, restricted to a particular zone, like a an VM or a disk.
So if you want to attach a disk to a VM, they need to be in the same zone.
Other resources are regional, like a fixed IP, for example.
And then we also have global resources, like images, or firewall rules.
In Operations, we can see what has happened under Compute Engine.
Operations are REST requests, we can read.
Everything you do in the console with your mouse, typically also can be done with an
HTTP call to the REST API and this normally would affect billing as well.
Create an instance?
You get billed.
Stop an instance?
Billing is stopped and so on.
Now, when we deployed the SAP HANA express edition solution, the instance was created.
Here we can see that it took about 3 minutes, a little less,
and the firewall rules were created in couple of seconds.
Note that a service account was used to create the resources
but my account was used to stop the instance.
If you want to learn more, click the link,
here you can also see the API call.
We will talk about images and snapshots and templates in a future video.
For now, let’s go to the VM instances.
Here, you can create an instance from scratch. So, without using the Cloud Launcher, and also
stop and start your instance, get the IP address and even connect using SSH, secure shell.
After the instance was created, I had stopped it
- as I had to go home and walk the dog -
so, let’s first start it up again.
You are informed that billing will start.
Click Start to start the VM.
It is pretty quick.
We can see the internal IP, this will be useful once you have other VM’s in the same network,
and the external IP and this is how you can connect to your instance from anywhere on the internet.
The external IP currently is ephemeral which means that
each time we stop and start the VM, we will get a new IP.
Later in this video we will look at how we can change that.
We can connect to the VM using SSH, secure shell.
That’s a Linux/UNIX feature, so you can connect from one computer to another on the command line.
Transferring keys - GCP is creating a secure connection for us -
and then here we have our shell.
SUSE Linux Enterprise Server 12 Wishing us a lot of fun.
Well, I can’t promise you we are going to have a lot of fun but we might get to learn
a few new tricks.
To start with, I can barely read this, so let’s select the gear icon.
For color theme, I will use white.
And for text size, I will use large.
That should be better.
Now, if we return to our deployment, you may recall the suggested next steps.
Change Master Database password and assign static IP.
Let’s start with the password.
At least 8 characters, containing one capital letter, one lowercase and one digit.
And then the command
sudo (superuser do)
su (switch user) dash (source the environment)
hxeadm - and that’s the SAP HANA system administration account, the software owner.
In other words, as the root user, change to the hxeadm user.
We have to do this as root as we don’t know the password of the hxeadm user at this stage.
So let’s go.
You can click the copy-paste icon here, to copy the command to the clipboard and then
with Control-V or Command-V or Edit > Paste from the browser menu, we can paste the command.
Enter.
Welcome to SAP HANA, express edition 2.0.
System must be configured before use.
Special characters are allowed except backslash, double quotes and backtick.
It is called the HANA database master password, although if you look it up in the SAP HANA
documentation, you won’t find it anywhere.
It is a, let’s say, feature, of HANA express.
A single password is set for the operating system administration account and the database
super user SYSTEM and a couple of more accounts - we will take a look at that later.
Let’s use my favourite password: Welcome1 - the only one I can remember.
Too bad.
Not a dictionary word.
The password policy of SUSE Linux is governing this, here.
Let’s try another one.
Appears to work.
Proceed with configuration? Yes
The script is giving us some info.
Change system user password on SystemDB database Change system user password on HXE database.
So we have two databases, systemDB and a tenant HXE.
Security keys change summary Change SSFS Master keys
Change root key for SystemDB database Change root key for HXE database.
So the root keys are changed as well.
I will not go into the topic of security keys here - there is a video in the academy that
already explains this in some detail.
For HANA express 1.0, you had to do this manually.
A bit of a hurdle, for some.
So, now it is done automatically.
It should really be done.
Each system needs to have its own unique root keys.
They will be used for encryption.
Encrypting data in-flight: SSL for communication between the different components and
encrypting data at-rest: data volume, redo logs, backup,
and also encrypting sensitive data in memory at the application layer,
and then we are congratulated: HANA is configured.
Very good.
The other suggested step from the Cloud Launcher concerned a fixed IP.
For this, select the menu and then Networking, also under Compute Engine.
I will pin this one as well.
Select External IP addresses.
Why would you need to do this?
Well, in the current configuration, the external IP of the VM will change each time we stop
and start it.
It is an ephemeral IP.
Now for those of you that already connected the HANA studio tool to the HANA database before
know that you need to provide a hostname or IP and the instance number.
Well, the hostname of the HANA express VM is local.
It is not registered with a Domain Name server anywhere, so can’t use it, and if the IP
changes every time, this means that each time we want to connect HANA studio,
we need to update the connection configuration.
Well, if you are the only one working on the system that may still work but if there are
more of you, it will get very confusing, very soon.
So, a fixed IP is needed.
It is not for free.
You are charged for a fixed IP but not much.
You can look it up under Billing, Transactions; we discussed this in a previous video.
A static IP is a 24x7 resource.
Once you have reserved it, it is there all the time.
You cannot stop and start it.
You can release it, of course, but you cannot request to get the same IP the next time.
It is optional but very convenient although it will cost you a few cents.
Select Reserve static address.
You need to give it a name.
I will use sap-hana-academy-express-1 IPv4
Regional will be OK for now.
Don’t need it to be global.
My default region is already selected.
I will attach it to the Express VM.
Click Reserve.
Note that as long as a static IP is in use, you cannot release it.
So, you would have to select Change Attached to None, and now you can release
it.
Let’s attach it to our VM again.
IP is 35.190.215.99 If we go back to Compute Engine, VM instances
We see the same external IP And should we stop and start the VM, it will
stay the same, as mentioned.
If we open a terminal client - I am using Terminal here on the Mac,
on Windows you can use PuTTY, for example -
and run the ping command we get a response.
We can also put the IP in the browser and add the HTTP port for the HANA XS classic
model application server; 80 + instance number, so 8-0-9-0 and then we get the message that
XSEngine is up and running.
OK. With the suggested steps performed we can now start to interact with the HANA server
and this we will do in the next video.
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 we also have a page on Facebook and Google+.
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 his video.
Thank you for watching.