Technical Articles
S/4HANA 1909 FPS1 Fully-Activated Appliance standard installation
Please refer to S/4HANA SQUARE ONE for other blogs
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
sid-hdb-s4h:/sapmedia# unzip 51054391_1.ZIP sid-hdb-s4h:/sapmedia# unzip 51054391_2.ZIP sid-hdb-s4h:/sapmedia# unzip 51054391_3.ZIP sid-hdb-s4h:/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-hdb-s4h:/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
Then extract the files: sid-hdb-s4h:/usr/sap #cd 51054391_1/SAPS4HANA1909FPS01SAPHANADB20basedonSAPNetweaverASABAP754_1 cat sapmnt.tgz-* | tar -zpxvf - -C / cat usrsap.tgz-* | tar -zpxvf - -C /
sid-hdb-s4h: #/hana/shared/HDB/hdblcm/hdblcm --action=register_rename_system
sid-hdb-s4h: #/usr/sap/hostctrl/exe/sapcontrol -nr 02 -function GetProcessList
sid-hdb-s4h:/install #/sapmnt/S4H/exe/uc/linuxx86_64/SAPCAR -xvf /sapmedia/SWPM20SP05_8-80003424.SAR
STEP 6:RENAME SAP SYSTEM Rename instance using sapinst, although we want to keep SID same as standard – S4H we need to run the procedure so that the process installs the missing items.
sid-hdb-s4h:/install # ./sapinst SAPINST_USE_HOSTNAME=vhcals4hci SAPINST_ACCEPT_INTERNAL_SIGNATURE=true SAPINST_SLP_MODE=false
Copy below URL into chrome browser to start sapinst rename process:
https://sid-hdb-s4h.dummy.nodomain:4237/sapinst/docs/index.html
At the screen Rename Tenant Database click on NextAt 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.
You can manually start the SAP instance S4H
sid-hdb-s4h:/install # /usr/sap/hostctrl/exe/sapcontrol -nr 01 -function StartSystem ALL sid-hdb-s4h:/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.
Standard users are as follows:
HANA DB – Instance 02 SYSTEM /<Master Password>
Web Dispatcher access : bpinst/Welcome1
STEP 7: 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
Host name / port in table HTTPURLLOC
Adapt RFC Connections if needed
ABAP connections:
• LOCAL_RFC
• S4HCLNT100 (and other clients)
• S4H_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
Adapt the Fiori notification URL
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.
Adapt any SAP parameters required
The database is provided with log mode overwrite and you may like to change that as needed.
PART3: INSTALL SAP NW JAVA / ADS
STEP 1: 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.
sid-j2e:/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
sid-j2e:/sapmedia# cat dblog.tgz-* | tar -zpxvf - -C / sid-j2e:/sapmedia# cat dbexe.tgz-* | tar -zpxvf - -C / sid-j2e:/sapmedia# cat dbdata.tgz-* | tar -zpxvf - -C / sid-j2e:/sapmedia# cat sapmnt.tgz-* | tar -zpxvf - -C / sid-j2e:/sapmedia# cat usrsap.tgz-* | tar -zpxvf - -C /
sid-j2e:/install #/sapmnt/J2E/exe/uc/linuxx86_64/SAPCAR -xvf /sapmedia/SWPM10SP28_7-20009701.SAR
sid-j2e:/install # ./sapinst SAPINST_USE_HOSTNAME=vhcalj2eci SAPINST_ACCEPT_INTERNAL_SIGNATURE=true SAPINST_SLP_MODE=false
Copy below URL into chrome browser to start sapinst rename process:
https://sid-j2e.dummy.nodomain:4237/sapinst/docs/index.html
At the screen Operating System User for SAP Database Administrator enter the password for sybj2e and User ID and 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 Medis 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
sid-j2e:/install # su - j2eadm sid-j2e:j2eadm > startsap
To access JAVA server as SAP Netweaver Adminstrator the URL is:
https://sid-j2e.dummy.nodomain:50000/nwa
Standard users are as follows:
JAVA Administrator – Adminitstrator / <Master Password> ;
Java user BPINST/Welcome1
STEP 6: 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 1909 Fully Activated Appliance: Known Issues
SAP S/4HANA Fully-Activated Appliance: Demo Guides
Blog with known issues in the SAP S/4HANA 1809 appliances (constantly updated)
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
Very nice introduction Mahesh, with MP customers need all the help they can get with HANA implementations and Application deployment plans.
Great Job !
Hi Graham,
Thank you.
- Mahesh
Hi Mahesh,
I'm grateful to see your blog.
I'm a beginner and don't have in depth knowledge, might have knowledge but not coming to the point in doing practical. Is there anyway to install and configure JAVA ADS system on the same VM on which S/4HANA FA Appl has installed.
Thanks!
Dear Mahesh Sardesai,
Great help!
For the download part,
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.
I just failed to find : SWPM20SP05_8-80003424.SAR and SWPM10SP28_7-20009701.SAR.
Could you correct me where to find it now?
Hi Sean,
You can find the corresponding latest releases of swpm
they should be available in software download.
After accessing url for software download, go to sltools and select swpm. After that it is swpm1 and swpm2
Hello,
I forgot to maintain a new license in t-code slicense, and now I cannot log into the AS to install the new license.
GUI gives me the error message Logon not possible (error in license check).
Is there's a possible way to login through GUI to install the new license using slicense t-code?
Thanks,
Hi Mohamed,
Sorry for delayed reply.
You can login using sap* using SAPGUI and install the license.
- Mahesh
Hi Mahesh
getting this error while performing the rename -
Logs - rename.log
17:43:48.406 - INFO: Sending HTTP request, function = Start, maximum number of retries = 3
17:43:52.481 - INFO: Starting 11 processes on host 'vhcalhdbdb' (worker):
17:43:52.481 - INFO: Starting on 'vhcalhdbdb' (worker): hdbdaemon, hdbcompileserver, hdbdiserver (HDB), hdbdocstore (HDB), hdbdpserver (HDB), hdbindexserver (HDB), hdbnameserver, hdbpreprocessor, hdbs
criptserver (HDB), hdbwebdispatcher, hdbxsengine (HDB)
17:43:56.485 - INFO: Starting on 'vhcalhdbdb' (worker): hdbdaemon
17:44:36.524 - ERR : FAIL: The following processes are not running:
17:44:36.525 - ERR : Start instance 02 on host 'vhcalhdbdb' (worker) failed.
17:44:36.525 - INFO: Messages from trace files of database 'SYSTEMDB'
17:44:36.531 - INFO: daemon_vhcalhdbdb.30200.008.trc: [16887]{-1}[-1/-1] 2022-03-18 17:43:51.987826 e Daemon Daemon.cpp(00360) : No executable-name for program cacheserver
17:44:36.531 - INFO: daemon_vhcalhdbdb.30200.008.trc: [16887]{-1}[-1/-1] 2022-03-18 17:43:51.988477 e Daemon Daemon.cpp(00360) : No executable-name for program rdsyncserver
17:44:36.532 - INFO: daemon_vhcalhdbdb.30200.008.trc: [16887]{-1}[-1/-1] 2022-03-18 17:43:56.103924 e Daemon DaemonLoop.cpp(00296) : Unexpected child code: "WAITCHILD_EXIT"
17:44:36.533 - INFO: nameserver_alert_vhcalhdbdb.trc: [16922]{-1}[-1/-1] 2022-03-18 17:43:55.431189 e Crypto CommonCryptoLib.cpp(00333) : SECUDIR unknown or default SECUDIR not found in environm
ent
17:44:36.533 - INFO: nameserver_alert_vhcalhdbdb.trc: [16922]{-1}[-1/-1] 2022-03-18 17:43:55.431225 e Crypto CommonCryptoLib.cpp(00333) : SECUDIR unknown or default SECUDIR not found in environm
ent
17:44:36.533 - INFO: nameserver_alert_vhcalhdbdb.trc: [16922]{-1}[-1/-1] 2022-03-18 17:43:55.431237 e Crypto CommonCryptoLib.cpp(00333) : SECUDIR unknown or default SECUDIR not found in environm
ent
17:44:36.533 - INFO: nameserver_alert_vhcalhdbdb.trc: [16922]{-1}[-1/-1] 2022-03-18 17:43:55.431238 e Crypto Configuration.cpp(00552) : Configuration::setNewExternalConfiguration: crypto provide
r 'commoncrypto' not available:
17:44:36.533 - INFO: nameserver_alert_vhcalhdbdb.trc: [16922]{-1}[-1/-1] 2022-03-18 17:43:55.431587 e commlib commlibError.cpp(00267) : Internal Error Details. Crypto/Configuration/Configuration.
cpp:553: Invalid SSL configuration: crypto provider 'commoncrypto' not available:
17:44:36.534 - INFO: nameserver_alert_vhcalhdbdb.trc: [16922]{-1}[-1/-1] 2022-03-18 17:43:55.431648 f TrexNet Engine.cpp(00679) : initialization failed with rc=ssl: internal error
17:44:36.534 - INFO: nameserver_alert_vhcalhdbdb.trc: [16922]{-1}[-1/-1] 2022-03-18 17:43:55.431759 f Service TrexService.cpp(00450) : FATAL: initialization of communication failed with exception
NetInitException : communication was not initialized
17:44:36.534 - INFO: nameserver_alert_vhcalhdbdb.trc: [16964]{-1}[-1/-1] 2022-03-18 17:43:55.515223 e NameServer TREXNameServer.cpp(00597) : shared memory not initialized after 12 retries (state=Ini
t). disabling shared memory
17:44:36.534 - INFO: nameserver_vhcalhdbdb.30201.300.trc: [16922]{-1}[-1/-1] 2022-03-18 17:43:55.431189 e Crypto CommonCryptoLib.cpp(00333) : SECUDIR unknown or default SECUDIR not found in envi
ronment
17:44:36.534 - INFO: nameserver_vhcalhdbdb.30201.300.trc: [16922]{-1}[-1/-1] 2022-03-18 17:43:55.431225 e Crypto CommonCryptoLib.cpp(00333) : SECUDIR unknown or default SECUDIR not found in envi
ronment
17:44:36.535 - INFO: nameserver_vhcalhdbdb.30201.300.trc: [16922]{-1}[-1/-1] 2022-03-18 17:43:55.431237 e Crypto CommonCryptoLib.cpp(00333) : SECUDIR unknown or default SECUDIR not found in envi
ronment
17:44:36.535 - INFO: nameserver_vhcalhdbdb.30201.300.trc: [16922]{-1}[-1/-1] 2022-03-18 17:43:55.431238 e Crypto Configuration.cpp(00552) : Configuration::setNewExternalConfiguration: crypto pro
vider 'commoncrypto' not available:
17:44:36.535 - INFO: nameserver_vhcalhdbdb.30201.300.trc: [16922]{-1}[-1/-1] 2022-03-18 17:43:55.431587 e commlib commlibError.cpp(00267) : Internal Error Details. Crypto/Configuration/Configurat
ion.cpp:553: Invalid SSL configuration: crypto provider 'commoncrypto' not available:
17:44:36.535 - INFO: nameserver_vhcalhdbdb.30201.300.trc: [16922]{-1}[-1/-1] 2022-03-18 17:43:55.431648 f TrexNet Engine.cpp(00679) : initialization failed with rc=ssl: internal error
17:44:36.535 - INFO: nameserver_vhcalhdbdb.30201.300.trc: [16922]{-1}[-1/-1] 2022-03-18 17:43:55.431759 f Service TrexService.cpp(00450) : FATAL: initialization of communication failed with excep
tion NetInitException : communication was not initialized
17:44:36.535 - INFO: nameserver_vhcalhdbdb.30201.300.trc: [16964]{-1}[-1/-1] 2022-03-18 17:43:55.515223 e NameServer TREXNameServer.cpp(00597) : shared memory not initialized after 12 retries (state
=Init). disabling shared memory
17:44:36.551 - INFO: Messages from trace files of database 'HDB'
17:44:36.552 - ERR : Check the log file for SAP HANA Database error messages
17:44:36.553 - ERR : Cannot start instance HDB (HDB02) on host 'vhcalhdbdb'
17:44:36.553 - ERR : Renaming master failed!
17:44:36.553 - ERR : Renaming SAP HANA instance failed!
17:44:36.553 - INFO: Summary of critical errors
17:44:36.553 - ERR : Renaming SAP HANA instance failed!
17:44:36.553 - ERR : Renaming master failed!
17:44:36.553 - ERR : Cannot start instance HDB (HDB02) on host 'vhcalhdbdb'
17:44:36.525 - ERR : Start instance 02 on host 'vhcalhdbdb' (worker) failed.
17:44:36.524 - ERR : FAIL: The following processes are not running:
17:44:36.525 - ERR : hdbdaemon HDB Daemon
Please advice.
Dear Mahesh,
Thanks for the great blog. We have installed the S4 system and able to login in 000 client with password provided in archives but the same password is not working for any other client (100, 200, 400)
Appreciate your support on this.
Hey,
just had the same problem.
Login into 100, 200, 400 with BPINST/Welcome1 and change Passwords for the DDIC Users.
BR,
Qobad Amid