Hello and welcome to the SAP HANA Academy.
The topic of this video tutorial series is SAP HANA Cockpit and in this video we will
discuss the installation of SAP HANA cockpit in a shared database deployment scenario and
this is part two where we look into resource registration.
This video has been recorded on release SAP HANA 2.0 SPS 03 (April 2018) and SAP HANA
cockpit 2.0 SP 07 from August 2018.
For earlier or later releases, please check the playlist on the SAP HANA Academy.
Hi, I am Denys van Kempen.
OK — in the previous video we looked at how we can perform a shared database installation
for SAP HANA cockpit and we left the stage at the end of the installation with this screen
of the SAP HANA Lifecycle Management tool with the URLs for the SAP HANA cockpit and
SAP HANA cockpit manager.
The best place to start is with the cockpit manager, with port-based routing that would
be 5-10-30, and then log on with the XS Advanced Administration account.
By default, this would be xsa_admin but in case you changed it, this is the screen where
you might have done this.
For those that performed cockpit installations in the past, you might be tempted to log on
as COCKPIT_ADMIN but there is no such user created in a shared database scenario, so
XSA_ADMIN it is.
The password is the one you defined and then we should get this screen: Not Authorized.
To use the SAP HANA Cockpit Manager you need a role collection based on the role template
COCKPIT_ADMIN.
Do you want to have this role collection automatically created and assigned to you?
Well, I hope you want this as much as I did, otherwise we get stuck at this stage.
You only get this screen when you logon as XSA_ADMIN and you only get it once, if not
mistaken.
So, should you answer No here, we might be in a bit of trouble.
Probably some way how we could reset this, but you would have to call SAP Support.
It is not documented.
So, click Yes.
Returns Success.
Role collection created and assigned.
Please log on again.
OK
Now we are connected to the Cockpit Manager.
Here we can register resources, collect them in groups, create users to manage them and
configure settings.
Click Register a Resource
Enter the host name.
If you want, you can change the resource name — the registration name — to a user-defined
one, not required to stick with the default database@system label.
The instance number.
Container: multiple, in most cases, and here I will start with the system database.
A description, if you like and then
Step 2.
Technical User
Should be an existing technical database user.
This user is only used for resource health information, from the landscape overview page
And you should not use this user to connect to a resource.
In other words, you should not use XSA_ADMIN.
You should not use SYSTEM.
We need to have a, preferably, dedicated user, a technical user, for this tasks.
How to proceed?
Well, what we could do, at this stage, is return to our terminal session and run the
SAP HANA interactive terminal, hdbsql, and maybe use a script to create this user.
Let me switch to the SAP HANA Cockpit Installation and Update Guide.
Next Steps.
It's not possible to create the technical user required to register an SAP HANA system
in the SAP HANA cockpit using the cockpit.
You need to create this user and grant the necessary authorization using SQL.
And here we have the script.
OK — Fair enough.
Let’s cancel.
Changes will be lost.
Yes.
Go to SAP HANA cockpit.
First time, this will take some time.
Execute SQL
SAP HANA Database Explorer for SAP HANA Cockpit
Loading
You should get this pop-up, otherwise just click the plus.
It looks like you have not added any databases to the Database Explorer.
Do you want to add on now?
Well, yes.
Thanks for asking.
And then
Database Type is SAP HANA Database (Multitenant).
Paste in the host again.
Instance number
Database
And then username, password.
You need a user with the CREATE USER system privilege.
This is a complete new system.
Just installed.
So, I will be using SYSTEM.
You might have another DBA account setup, you can use that as well.
OK— save user and password in the secure store, if you want.
And here we have our system.
To save some time, I will add the default tenant of this system as well
HA0
Fast forward a bit
And also the cockpitdb tenant.
The one that just has been created by the installer.
So we can manage cockpit in cockpit.
OK —here we have our three databases.
Let’s start with the system database.
Open a SQL Console
Paste in the SQL from the installation guide.
I will change the username to _cockpit_statistics.
Just a name.
Whatever makes sense to you.
And change the password.
The command disables the change password on first logon feature, so you might want to
pick a more sensible password.
Something hard to crack.
Then update the GRANT statements as well with the username.
OK — and then we can execute the statement.
Switch systems to the other tenant: HA0.
Execute.
Switch system to the cockpit tenant.
Execute.
And we’re done.
Now, let’s return to cockpit manager.
Register resource again.
Paste in the host name, instance number
And now in Step 2, we have our technical user: _COCKPIT_STATISTICS
Step 3.
Connection.
Here we should really use encryption for the connection to the database and the start/stop
service.
However, for this to work we need an imported trusted certificate.
We need to set this up.
How you can do this, we will cover in another video.
For now, I will deselect the encryption option.
Step 4.
Resource Group
Step 5.
Contact Information
You can populate these fields if you want.
Not required.
Review
Register
Excellent.
Now you would need to do the same for the default tenant and for the cockpitdb tenant.
I will skip that.
You get the idea.
Go to the SAP HANA Cockpit.
Here we have the landscape page again.
Let’s open the directory.
Make the screen a bit bigger.
Here we can see Usage: Custom.
You always get an availability alert for new systems as you do not have a backup yet.
That’s why we see: Running with issues.
Let’s first enter the user logon credentials.
This should be user you want to use for database administration.
Not the technical user for cockpit resource registration.
It would not have enough privileges.
You may have already created a dedicated user for this purpose.
That would be a best practice.
I will be using the system user here, for now.
Typically, you should not use this user here.
Too many privileges.
Best practice would be to create a dedicated user and disable SYSTEM.
OK — we can also add the SAP Control Credentials.
This concerns the operating system administration account for HANA.
That would be the +adm.
We would need this to start the system up, or when we need to recover a system.
If you are interested in how this all works, I have posted a blog with a link to a tutorial
video about SAP Control and sapinit and the SAP Start Service on Linux — Under the Hood
—
Let’s connect to our resource.
The System Overview page opens with the new Fiori-style look and feel introduced in SP
07.
And then we can just click the Alert.
This will open the Alerts view.
Database backup does not exist.
Without a data backup, your database cannot be recovered.
OK.
Let’s fix this.
Go to Backup.
Backup opens
Select Create Backup
Complete.
File.
Prefix.
Destination.
Back Up.
Backup in progress.
Backup Details and we are done.
There are many more things we can do, of course, for post-installation, but this might give
you a good place to start.
Create your technical user in the SQL Console of Database Explorer.
Register your resource in cockpit manager.
And then enter user credentials for database administration in the resource directory.
That’s pretty much it.
OK - So much for installing SAP HANA cockpit on a shared database, part 2.
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.