Script Backup
Hi, I am Denys van Kempen, SAP HANA Academy, SAP Partner Engineering,
This video is part of a series where we cover what’s new with SAP HANA Cloud.
In this video, we continue with system administration and cover system configuration with SAP HANA
cockpit.
This video was recorded in April 2020.
For the latest material on this topic, please check the playlist.
As with the other videos, we have posted a blog with additional information and references.
See the description of this video below for the link.
If have a question, feel free to post your comments below the video or the blog.
SAP HANA Cockpit, System Overview Filter area monitoring and Administration
Here we have the Database Administration card with three links
Manage system configuration, the topic of this video
a link to the database explorer and a link to manage workload classes, which
we will cover in another video Select it to open the System Configuration
app In the header we have the name of our instance,
the host name, and the version Two tabs: parameters and snapshots.
Snapshot enable you to take a picture of your current configuration
For example, initial configuration we will use this in a minute to check our
changes back to the parameters tab
system parameters are organised by service, which are stored, persisted, in a configuration
file, with INI extension, here we see the computeserver.INI file, for
example.
In total, this tenant database has 109 system parameter and 11 configuration files.
Now, not all files are populated, contain parameters
attributes.ini is empty, and so are some others.
docstore.ini, for example, configures the document store,
this feature is currently not available but it is on the agenda for a future release.
In the video tutorial about manage services in this playlist we talked about HANA services,
if we go back for a moment and open manage services
we can see them listed the shared services are managed from the system
database, managed by SAP for our tenant, we can only manage indexserver,
data provisioning, and deployment infrastructure if we then return to system configuration
and select dpserver.ini we can see that for this file, in section
jwt_identify_provider, the system parameter issuer is defined with a value.
It is set at the system layer and the database layer.
we cannot define, we cannot set parameters at the system level.
this happens at the system database but we can overrule this value by entering
a value here at the database level, our tenant.
most parameter concern the indexserver service, the actual database
there are a number of sections, this helps to organise the parameters
authentication, authorisation, password policy, session, sql, and so on
let’s take password policy host will always be the local host as HANA
Cloud is a single-host system at the time.
13 parameters are defined layer is default - those are system defaults
to make changes, select override value for example, for first password change
there is a description of what the parameter does
default value is true, we can set this to false (or off, no, or 0, which all means the
same - a bit curious, these options)) add a comment
and click OK we can see that this parameter is now also
set at the database level we can now compare our environment with the
snapshot selecting show differences only
and this returns our parameter we could take another snapshot at this stage,
this might be useful should we have made more changes and want to maintain a baseline
Now, you may be familiar with the password policy editor
Note that the card already provides a clue as it is no longer default but customised
Password Change Required on First Logon = no edit
set default Password change required is now yes
save force_first_password_change is now back to
its default value and our change is undone.
change history inform us about these changes the point is that the SAP HANA cockpit provides
several user interfaces to configure system parameters
behind the screens we are executing SQL statements ALTER SYSTEM
and this results in INI files being modified why files?
Well, first we need to persist changes but for this we could also have used tables, of
course but secondly, many system parameters configure
the system and need to be set at system startup when the database is not yet open.
which is why we use INI files.
now there are lot more parameters and in the blog for this video I will list some resources
where you can find more information on this topic.
but there is also the online help of course.
You need the INIFILE ADMIN system privilege to modify system parameters.
Thats’s it.
Thanks for watching.