Technical Articles
S/4HANA 1909 FPS1 Fully-Activated Appliance custom installation
Please refer to S/4HANA SQUARE ONE for other blogs
If you want to do standard installation with no change in hostname and sid please refer to other blog In this blog the procedure is simplified for standard installation with NO HOSTNAME OR SID CHANGE. The advantage with this is that you don’t have to do many of the steps related to SID change and it does make sense if you will be installing the instance temporarily.
PART1: SOFTWARE DOWNLOAD
Please download the software media from https://launchpad.support.sap.com/#/softwarecenter
SAP S/4HANA => SAP S/4HANA 1909 => S/4HANA FULLY-ACTIVATED APPLIANCE => SAP S/4HANA 1909 FPS01 FA APPL
Download the 51054391_* files and SWPM20SP05_8-80003424.SAR on SAP S/4HANA Server.
Download the 51054392, SWPM10SP28_7-20009701.SAR and 51050829_JAVA_part 1 & 2 – NW 7.5 Java based SW Comp on the SAP NW JAVA / ADS server.
PART2: INSTALL SAP S/4HANA
Plan the change of SID, hostname, instance number. Please refer to the notes below for reserved SIDs SAP Note 1979280 – Reserved SAP System Identifiers (SAPSID) with Software Provisioning Manager and hostnames SAP Note 611361 – Hostnames of SAP ABAP Platform servers
The table below shows standard SID and hostnames and what we are changing it to.
sid-hdd-s4d:/sapmedia# unzip 51054391_1.ZIP sid-hdd-s4d:/sapmedia# unzip 51054391_2.ZIP sid-hdd-s4d:/sapmedia# unzip 51054391_3.ZIP sid-hdd-s4d:/sapmedia# unzip 51054391_4.ZIP
Allow approx 2 hours for extraction.
We will install Central system with DB and App on same server. Please move all *.tgz-* files to /sapmedia/51054391_1/SAPS4HANA1909FPS01SAPHANADB20basedonSAPNetweaverASABAP754_1
cd /sapmedia/51054391_1/SAPS4HANA1909FPS01SAPHANADB20basedonSAPNetweaverASABAP754_1
mv /sapmedia/51054391_?/SAPS4HANA1909FPS01SAPHANADB20basedonSAPNetweaverASABAP754_?/*.tgz-* .
sid-hdd-s4d:/sapmedia/# cd 51054391_1/SAPS4HANA1909FPS01SAPHANADB20basedonSAPNetweaverASABAP754_1
cat dblog.tgz-* | tar -zpxvf - -C /
Similarly extract the remaining files:
cat dbexe.tgz-* | tar -zpxvf - -C / cat dbdata.tgz-* | tar -zpxvf - -C /
It takes about an hour for extraction.
Below two Application related archives may be extracted on a separate app server for distributed installation. These files will be extracted under /sapmnt/S4H and /usr/sap/S4H so if you are changing the SID, then you will have to first extract to SID-S4H and then create links to your own SID like S4D
Then extract the files: sid-hdd-s4d:/usr/sap #cd 51054391_1/SAPS4HANA1909FPS01SAPHANADB20basedonSAPNetweaverASABAP754_1 cat usrsap.tgz-* | tar -zpxvf - -C / cat sapmnt.tgz-* | tar -zpxvf - -C /
Execute HANA database specific steps as below:
sid-hdd-s4d: #/hana/shared/HDB/hdblcm/hdblcm --action=register_rename_system
TIP: Places where you need to enter data is indicated, rest all are default options
sid-hdd-s4d: #/usr/sap/hostctrl/exe/sapcontrol -nr 02 -function GetProcessList
sid-hdd-s4d: #/hana/shared/HDB/hdblcm/hdblcm --action=rename_system --hostmap=vhcalhdbdb=vhcalhdddb
sid-hdd-s4d:/install # /usr/sap/hostctrl/exe/sapcontrol -nr 02 -function StopSystem sid-hdd-s4d:/install # /usr/sap/hostctrl/exe/sapcontrol -nr 02 -function StopService
You can take a full OS backup at this point and rename mount points /hana/shared/HDD; /hana/data/HDD; /hana/log/HDD; /sapmnt/S4D; /usr/sap/S4D. The old standard mount points do not have to exist. You can remove the db old hostname vhcalhdbdb and also reboot the system to ensure consistency in config. After reboot ensure all new renamed mount points are valid.
IMPORTANT: Do not rename /hana/shared/HDD/HDB02.
Then execute the command for database SID rename:
sid-hdd-s4d: # cd /hana/shared/HDD/hdblcm
sid-hdd-s4d: /hana/shared/HDD/hdblcm # ./hdblcm --action=register_rename_system
You can also rename the instance number with the command below:
sid-hdd-s4d: #/hana/shared/HDD/hdblcm/hdblcm --action=rename_system --number=<new instance number> TIP: At this point it is necessary to install the HANA database license as the database will be started in restricted mode.
sid-hdd-s4d:/install #/sapmnt/S4D/exe/uc/linuxx86_64/SAPCAR -xvf /sapmedia/SWPM20SP05_8-80003424.SAR
STEP 6: RENAME SAP SYSTEM Rename instance using sapinst
sid-hdd-s4d:/install # ./sapinst SAPINST_USE_HOSTNAME=vhcals4dci SAPINST_ACCEPT_INTERNAL_SIGNATURE=true SAPINST_SLP_MODE=false
Copy below URL into chrome browser to start sapinst rename process:
https://sid-hdd-s4d.dummy.nodomain:4237/sapinst/docs/index.html
At the screen Secure Storage for Database Connection select HANA Secure User tore (hdbuserstore) click on Next
At the screen Operating System Users accept master password or enter password Xxxxxxxn
At the screen Secure Storage Key Generation accept radio button – Individual Key (Recommended for Productive Systems) On the Next
At next screen Warning click OK
At the screen DNS Domain Name checkmark Set FQDN for SAP System and enter domain name dummy.nodomain Click on Next
At the screen Install License Key keep unchecked Install License Key. Click on Next
TIP: It is much easier to install the license by providing the file than doing it later through the appolication.
At next screen Cleanup of Operating System Users checkmark on Yes cleanup os users and click on Next
Here is the Parameter Summary Click on Next to confirm and begin the installation.
RESOLUTION: Follow SAP Note 2800204 – SSFX-0362: Value file “-” does not start with the UTF-8 byte order mark
Ensure the environment variable LC_CTYPE of the user running sapinst is set as LC_CTYPE=en_US.
Stop the current sapinst and restart it. Continue with the existing option.
sid-hdd-s4d:/install # /usr/sap/hostctrl/exe/sapcontrol -nr 01 -function StartSystem ALL sid-hdd-s4d:/install # /usr/sap/hostctrl/exe/sapcontrol -nr 00 -function StartSystem ALL
After instance is started and confirmed you can delete the sapmedia folder and remove temporary links to S4H as well as temporary hostnames.
Standard users are as follows:
HANA DB – Instance 02 SYSTEM /<Master Password> or as you changed in above
Web Dispatcher access : bpinst/Welcome1
STEP 7: POST STEPS Follow steps from guide attached to SAP Note 2041140 – First Steps for on-premise installations.pdf => Section 5 Technical Post-deployment Activities
Adapt HANA connections in DBACOCKPIT (nothing was required to be done here).
Adapt RFC Connections
ABAP connections:
• LOCAL_RFC
• S4DCLNT100, S4DCLNT200, S4DCLNT400
• S4D_RFC
HTTP connections:
• ADS (pointing to the JAVA server after PART3: INSTALL SAP NW JAVA /ADS)
• LOCAL_HTTP
• LOCAL_HTTPS
• S4FIN_HTTPS
SAP Enable Now Web Assistant enter tCode /UI2/FLP_CUS_CONF
Adapt the Fiori notification URL. enter tCode /UI2/FLP_SYS_CONF
Adapt Enterprise Search
Apply product license keys
Install software product license key: Technical restrictions may apply if you don’t install the license. Use the link to obtain license key.
HANA DB license key can be installed via HANA Studio (Preferences -> License)
In SAP S/4HANA 1909 the license key is installed via SAP logon tCode SLICENSE
Further post-installation checks
Install SAP client tools on your local computers
You can take a full backup and remove the temporary links that were setup for S4H
In client 000 fix transport configuration. Enter tCode SE06 and reinstall CTS transport system, Change originals to S4D, Delete old TMS config, delete old versions of transport routes
Adapt any SAP parameters due to changed SID
The database should be with log mode overwrite and you may like to change that as needed.Please carry out the the other basis steps that are usually done with SID change/System refresh :
SPAD – Spool Administration
SCC4 – Client Administration – Logical System
RZ10- Instance profiles
SP01 – Spool delete old spool requests
PART3: INSTALL SAP NW JAVA / ADS
STEP 1: PREPARE SYSTEM Prepare Linux Server as below for the appliance. The values in Used column below show the minimum size needed. Total filesystem needed is min 50GB for installation.
Plan the change of SID, hostname, instance number. Please refer to the notes below for reserved SIDs SAP Note 1979280 – Reserved SAP System Identifiers (SAPSID) with Software Provisioning Manager and hostnames SAP Note 611361 – Hostnames of SAP ABAP Platform servers
sid-j2d:/sapmedia# unzip 51054391.ZIP
We will install Java instance from files in /sapmedia/51054392/SAPNetWeaver750SP16ASJAVAwithAdobeDocumentServices_1
cd /sapmedia/51054392/SAPNetWeaver750SP16ASJAVAwithAdobeDocumentServices_1
These files will be extracted under /sapmnt/J2E; /usr/sap/J2E and /sybase/J2E. After these are extracted you can rename the filesystem or remount with changed mount points.
sid-j2d:/sapmedia# cat dblog.tgz-* | tar -zpxvf - -C / sid-j2d:/sapmedia# cat dbexe.tgz-* | tar -zpxvf - -C / sid-j2d:/sapmedia# cat dbdata.tgz-* | tar -zpxvf - -C / sid-j2d:/sapmedia# cat sapmnt.tgz-* | tar -zpxvf - -C / sid-j2d:/sapmedia# cat usrsap.tgz-* | tar -zpxvf - -C /
sid-j2d:/install #/sapmnt/J2D/exe/uc/linuxx86_64/SAPCAR -xvf /sapmedia/SWPM10SP28_7-20009701.SAR
sid-j2d:/install # ./sapinst SAPINST_USE_HOSTNAME=vhcalj2dci SAPINST_ACCEPT_INTERNAL_SIGNATURE=true SAPINST_SLP_MODE=false
Copy below URL into chrome browser to start sapinst rename process:
https://sid-j2d.dummy.nodomain:4237/sapinst/docs/index.html
At the screen Operating System User for SAP Database Administrator enter the password for sybj2d and User ID and Click on Next
At the screen SAP ASE Database System Parameters accept or change ports and Click on NextAt the screen Database User Pasawords enter the passwords for user sa, sapsa, sapsso, SAPSR3DB which is Welcome99. Click on Next
At the screen DNS Domain Name checkmark Set FQDN for SAP System and enter domain name dummy.nodomain Click on Next
At the screen Media Browser select the media Package Location and Click on Next
At next screen Cleanup of Operating System Users checkmark on Yes cleanup os users and click on Next
Here is the Parameter Summary Click on Next to confirm and begin the installation.
After about 10mins, the installation process will stop at this point.
Please take note and proceed.
After the sapinst installation is complete, you can manually start/stop the SAP Java instance J2D using old startsap / stopsap commands
sid-j2d:/install # su - j2dadm sid-j2d:j2dadm > startsap
To access JAVA server as SAP Netweaver Adminstrator the URL is:
https://sid-j2d.dummy.nodomain:50000/nwa
Standard users are as follows:
JAVA Administrator – Adminitstrator / <Master Password> ;
Java user BPINST/Welcome1
STEP 7: POST STEPS Follow steps from guide attached to SAP Note 2041140 – First Steps for on-premise installations.pdf – Section 5 Technical Post-deployment Activities
Apply product license keys
Install software product license key: Technical restrictions may apply if you don’t install the license. Use the link to obtain license key. SAPNetweaver 7.5 J2EE license key has to be installed via SAP Netweaver Administrator
Further post-installation checks
Adapt any SAP parameters due to changed SID
After instance is started and confirmed you can delete the sapmedia folder.
SUPPORT TICKETS:
If you have any difficulty downloading the media open OSS message using component XX-SER-SAPSMP-SWC. If you have issues with technical deployment open message with component BC-INS-SRN.
OTHER REFERENCES:
SAP S/4HANA Fully-Activated Appliance: Create your SAP S/4HANA system in a fraction of the usual setup time
SAP S/4HANA 1909 Fully Activated Appliance: Known Issues
Blog with known issues in the SAP S/4HANA 1809 appliances (constantly updated)
SAP S/4HANA Fully-Activated Appliance: Demo Guides
2041140 – Order an SAP pre-assembled Best Practices software appliance (as partner or customer)
Thank you. Hope you enjoyed the installation.
Mahesh Sardesai
Product Expert – S/4HANA
Nice document covering all steps.
Regards,
Thanks Mahesh.
HI Mahesh, thanks for the nice documentation. Your recommendations regarding disk sizes are already quite helpful. Do you also have any recommendations regarding CPU&RAM when installing in a VMware environment?
Update.: Also any ideas regarding availability of the 2020 release as a fully activated trial?
Thanks & best regards,
Mark
Hi Mark,
Please follow the guide attached to Note 2041140 - Order an SAP S/4HANA fully-activated appliance for on-premise deployment. - First_Steps_S4H_1909_FPS01_Download_BluRay_EN_1_0.pdf
Fully Activated appliance for S/4HAA 2020 is under preparation and will be available end of the year.
Dear Sir,
Once I extract db files successfully and running the "hdblcm" for system renaming, I got this error.
Enter Target System ID [HDB]:
Group 'sapsys' has wrong id '79' (expected: '1000')!
Kindly help me to sort this problem out.
Thank you.
Hi Mohamed,
You can check using command if linux group 100 is free, if it is, then to change to sapsys group to 1000.
If 1000 is already taken then please create an incident with Product Support within each component that is affected.
- Mahesh.
Worked fine for me, also for installing the 2020 SP00 appliance.
Thx a lot - safed a lot of time!
Dear,
In the step number 5: RENAME DATABASE HOST, it asks me to put Source System Administrator (hdbadm) Password, I tried "Welcome99" but it gives me an error " Unknown user password combination.
Could you please advice me?
Thanks
Hi Mohamed,
The password may be different for the release you are installing. Please open the file SAP_Software_Appliance.xml in a notepad and find out the password.
I found the password Clean_123 in the XML file, but it gives me this error
still cannot rename the database host.
Hi Mohamed,
You can create a ticket as somebody will have to look into the system.
Did you start installation on a clean system that did not have any user already on the system like hdbadm or sidadm ? If this is the case, it is possible that hdbadm password may be a local host user password already defined before and that is the reason it is not able to change. If it is possible, try cleaning system with no user and SAP installation directory and then try.
Dear,
How can i install Central system with DB and App on different server ? Is that any parameter have to change before rename job???
Now, I have rename HANA database and it works fine, But when i rename App on other server, it is successfully ,but start fail, the disp+work process is gray!
Could you please help me?
Thanks
Hi Lin,
If you want to install App on different server you have to ensure that DB client is configured properly and app is able to connect. The issue you are facing may be a typical App to DB connectivity issue.
Please follow the specific steps in the guide SAP_SoftwareAppliance_Installation_Guide_06_12_2019.pdf attached to SAP Note 2041140
Thanks,
Dear Mahesh,
Thank you so much !
Thank you very much for covering even minute details! I was able to deploy S/4HANA 2021 FA following this article!
Regards,
Sid
Dear Sir,
Recently, anyone trying to change or doing any modification in material using t-codes: mm01 and mm02 got the following error:
A database error occured. The error message in the database was: "authentication failed".
Can you please advice me what to do to sort this issue out.
Thank You.
Hi Mohaned,
This will have to be investigated by setting up a trace, support will have to look at the system.
If you get a tcode ST22 dump with this error, that will have to be analysed to find out the root cause.
Please create a ticket.
- Mahesh
Dear ,
follow the step i meet some error, i had try many times but the issue still .
error message show:
"22:17:52.716 - INFO: nameserver_alert_vhcalhdbdb.trc: [10721]{-1}[-1/-1] 2022-07-09 22:17:11.378301 e Crypto CommonCryptoLib.cpp(00333) : SECUDIR unknown or default SECUDIR not found in environment
22:17:52.716 - INFO: nameserver_alert_vhcalhdbdb.trc: [10721]{-1}[-1/-1] 2022-07-09 22:17:11.378354 e Crypto CommonCryptoLib.cpp(00333) : SECUDIR unknown or default SECUDIR not found in environment
22:17:52.716 - INFO: nameserver_alert_vhcalhdbdb.trc: [10721]{-1}[-1/-1] 2022-07-09 22:17:11.378378 e Crypto CommonCryptoLib.cpp(00333) : SECUDIR unknown or default SECUDIR not found in environment
22:17:52.716 - INFO: nameserver_alert_vhcalhdbdb.trc: [10721]{-1}[-1/-1] 2022-07-09 22:17:11.378380 e Crypto Configuration.cpp(00552) : Configuration::setNewExternalConfiguration: crypto provider 'commoncrypto' not available:
22:17:52.716 - INFO: nameserver_alert_vhcalhdbdb.trc: [10721]{-1}[-1/-1] 2022-07-09 22:17:11.378752 e commlib commlibError.cpp(00267) : Internal Error Details. Crypto/Configuration/Configuration.cpp:553: Invalid SSL configuration: crypto provider 'commoncrypto' not available:
22:17:52.716 - INFO: nameserver_alert_vhcalhdbdb.trc: [10721]{-1}[-1/-1] 2022-07-09 22:17:11.378808 f TrexNet Engine.cpp(00679) : initialization failed with rc=ssl: internal error
22:17:52.716 - INFO: nameserver_alert_vhcalhdbdb.trc: [10721]{-1}[-1/-1] 2022-07-09 22:17:11.378952 f Service TrexService.cpp(00450) : FATAL: initialization of communication failed with exception NetInitException : communication was not initialized
22:17:52.716 - INFO: nameserver_alert_vhcalhdbdb.trc: [10794]{-1}[-1/-1] 2022-07-09 22:17:11.606723 e NameServer TREXNameServer.cpp(00597) : shared memory not initialized after 12 retries (state=Init). disabling shared memory
22:17:52.720 - INFO: nameserver_vhcalhdbdb.30201.300.trc: [10721]{-1}[-1/-1] 2022-07-09 22:17:11.378301 e Crypto CommonCryptoLib.cpp(00333) : SECUDIR unknown or default SECUDIR not found in environment
22:17:52.720 - INFO: nameserver_vhcalhdbdb.30201.300.trc: [10721]{-1}[-1/-1] 2022-07-09 22:17:11.378354 e Crypto CommonCryptoLib.cpp(00333) : SECUDIR unknown or default SECUDIR not found in environment
22:17:52.720 - INFO: nameserver_vhcalhdbdb.30201.300.trc: [10721]{-1}[-1/-1] 2022-07-09 22:17:11.378378 e Crypto CommonCryptoLib.cpp(00333) : SECUDIR unknown or default SECUDIR not found in environment
22:17:52.720 - INFO: nameserver_vhcalhdbdb.30201.300.trc: [10721]{-1}[-1/-1] 2022-07-09 22:17:11.378380 e Crypto Configuration.cpp(00552) : Configuration::setNewExternalConfiguration: crypto provider 'commoncrypto' not available:
22:17:52.720 - INFO: nameserver_vhcalhdbdb.30201.300.trc: [10721]{-1}[-1/-1] 2022-07-09 22:17:11.378752 e commlib commlibError.cpp(00267) : Internal Error Details. Crypto/Configuration/Configuration.cpp:553: Invalid SSL configuration: crypto provider 'commoncrypto' not available:
22:17:52.720 - INFO: nameserver_vhcalhdbdb.30201.300.trc: [10721]{-1}[-1/-1] 2022-07-09 22:17:11.378808 f TrexNet Engine.cpp(00679) : initialization failed with rc=ssl: internal error
22:17:52.720 - INFO: nameserver_vhcalhdbdb.30201.300.trc: [10721]{-1}[-1/-1] 2022-07-09 22:17:11.378952 f Service TrexService.cpp(00450) : FATAL: initialization of communication failed with exception NetInitException : communication was not initialized
22:17:52.720 - INFO: nameserver_vhcalhdbdb.30201.300.trc: [10794]{-1}[-1/-1] 2022-07-09 22:17:11.606723 e NameServer TREXNameServer.cpp(00597) : shared memory not initialized after 12 retries (state=Init). disabling shared memory
22:17:52.730 - INFO: daemon_vhcalhdbdb.30200.008.trc: [10695]{-1}[-1/-1] 2022-07-09 22:17:06.150673 e Daemon Daemon.cpp(00360) : No executable-name for program cacheserver
22:17:52.730 - INFO: daemon_vhcalhdbdb.30200.008.trc: [10695]{-1}[-1/-1] 2022-07-09 22:17:06.152183 e Daemon Daemon.cpp(00360) : No executable-name for program rdsyncserver
22:17:52.730 - INFO: daemon_vhcalhdbdb.30200.008.trc: [10695]{-1}[-1/-1] 2022-07-09 22:17:12.299104 e Daemon DaemonLoop.cpp(00296) : Unexpected child code: "WAITCHILD_EXIT""
Hi xin,
Please create a ticket as somebody will have to take a look at ths system.
Alternatively, in caase you want to retry again, I would like to mention that it is required to completely cleanup the system of the traces of previous hana db or sap installation like remove the sidadm hdbadm id's or user home directories and /usr/sap* /sapmnt/*. You can try cleaning up system and start installation again.
The blog you reference has the high level steps but there is more detailed information on the required configuration in the pdfs attached to the note 2041140 - Order an SAP S/4HANA fully-activated appliance for on-premise deployment referenced in the blog, are all required perquisites and configuration in place for the renaming as per the pdf's attached to note 2041140 - Order an SAP S/4HANA fully-activated appliance for on-premise deployment ?
If the perquisites and configuration is correct as per the note can you please collect the SAP HANA Database log files at OS level for both the SYSTEM DB and the Tenant DB as per the attached note 1732157.
As per the note 1732157 you can collect the logs at OS level.
Please attach the logs for the SYSTEMDB and the Tenant DB to the case.
- Mahesh
roger,thanks for your reply ,i will check my system and try again!
hello sir,
follow the note 1732157 step 2,when i logged on as the operating system administrator hdbadm show some message:
sid-hdb-s4h:~ # su - hdbadm
sid-hdb-s4h:hdbadm 2> cd $DIR_INSTANCE/exe/python_support
DIR_INSTANCE: Undefined variable.
Hi Xin,
It would be good to create a ticket.
Let me know the media number you are installaing and for which release. for example
S/4HANA 2021 FPS1 - 51055381
Hi Mahesh.
my media number SAP S/4HANA 2021SP00 FAA -51055259