Your S/4HANA environment – Part 1 – Maintenance Planner, System Installation and Update
S/4HANA introduces a lot of new functionality for customers. SAP gives the choice to deploy and use software as an on-premise installation or cloud service.
Over the few next days, I would like to present to you, how to deploy the whole S/4HANA environment:
1) How to install the S/4HANA system using Maintenance Planner and update it with SUM
2) How to perform initial configuration of SAP Gateway for S/4HANA
3) How to activate S/4HANA Best Practices
Today I will show you the first part – Installation and initial configuration of S/4HANA.
If you would like to follow my guide, you need to have:
1) Access to SAP Service Marketplace
2) Operating system installed and configured according to SAP requirements
I’m using SLES 12, but you can use also SLES 11 or Red Hat.
3) SAP HANA database already installed
You can convert it to MDC with this blog: Convert to a multi tenant HANA database.
4) A bit of time 🙂
Although I will try to show you the complete installation scenario, I’m expecting you have some understanding of SAP Netweaver and you have already performed a Netweaver installation before.
I highly recommend that you also read all available documentation (like Installation Guide, SAP Notes) before installation.
USE MAINTENANCE PLANNER TO PLAN A NEW SYSTEM
Maintenance planner is a place where our journey starts. It enables to us to plan a new installation and calculate the update path.
Link: Maintenance Planner
Just a few days ago, SAP released an update to Maintenance Planner and now you can find an additional tile just for S/4HANA.
During the next step we need to define our change scope:
- Installation of the new SAP S/4HANA system
- System conversion
Our task for this guide is to install a brand new system, so we choose the first option.
I found it very convenient that SAP already includes a link to the Installation Guide.
The ‘Select Backend System’ step allows us to define the exact system version we want to install. I chose the newest possible:
Target Version: SAP S/4HANA On-Premise 1511
Target Stack: FPS 02
Our goal is to have full environment consisting of two systems:
a) S/4HANA – back-end server
b) SAP Gateway – front-end server in Central Hub Deployment scenario
During this part we can choose which UI components we want to install along with Gateway:
Finally, we get confirmation that our preparation is complete. But that’s not the end. Now we need to confirm the files we want to download.
We are getting to the end of Maintenance Planner. On the last screen you can see the summary of selected files and the download stack file, that we will use in few moments to run Software Provisioning Manager.
After pushing files to Download Basket we can run Download Manager. Unfortunately, Maintenance Planner doesn’t show you the initial installation files. To get them, you need to follow the “old fashioned” way, by using SAP Marketplace and selecting the appropriate media.
During the download we can have a moment to install and prepare the SAP HANA database. I already have one working – the only thing I want to do is to create the tenant database that I will use for S/4HANA. It can easily be done executing SQL command:
It took around 2 minutes to have the database ready.
When the download is complete we can unpack archives and run SWPM. This time I decided to start it together with the stack file generated by Maintenance Planner.
SYSTEM INSTALLATION WITH SOFTWARE PROVISIONING MANAGER
The SWPM part is pretty straightforward, so I will focus on the most important and interesting parts.
The first screen let us choose what we want to install. But as we are using a stack file, we don’t have a big choice – list of available systems is limited to our previous choice from Maintenance Planner:
After typing our system SID, FQDN and master password, we need to point to our HANA database. Look that we need to give not only a password for the tenant database, but also for the system database.
On Software Package Browser we can point to SAR archives with SAP kernel – the easiest way is to type directory with our Download Folder. SWPM finds the files automatically.
Another nice idea is to configure STMS along with system installation, import newest SPAM package and import ABAP transports.
One of the last steps is to configure SUM. It will start directly after SWPM and enables us to import support packages.
The very last screen is confirmation of our parameters. After clicking Next, the installation starts:
The installation in my case took around 4 hours. As usual the longest part was Import ABAP.
To install the SAP system, we used a stack file, so the last task during the installation is to start Software Update Manager to import corrections.
To login to SUM we need to provide <sid>adm user and password. Execution of SUM is again pretty straightforward, so I will focus mainly on the important bits. SAP recently released new installation media with S/4HANA SR1, so SUM will update only minor components – all core components are already on the highest release.
SYSTEM UPDATE USING SOFTWARE UPDATE MANAGER
First thing after log in to SUM you need to provide stack file. It’s exactly the same file that was previously generated by Maintenance Planner and was used as the input for SWPM.
As usual during an update process we can choose configuration. To make the update quickest I chose Single System without creating shadow instance.
We can now check what components will be updated. In our case there are not too many changes, but when a new release comes, the following screens will contain more information.
During the update you will be prompted to perform a system backup – this is of course highly recommended.
Finally, when SUM execution is finished, we receive the relevant message:
Now we can finally enter the system.
When we go to menu System -> Status we can see the exact S/4HANA version.
That’s all for today. I hope you enjoyed this course. In a few days I will publish the next episode where I focus mainly on front-end server configuration and connection to S/4HANA back-end.