- SAP Managed Tags
This blog covers installation of (1) SAP S/4HANA server and (2) SAP NW JAVA / ADS server as shown in the graphic below. The installation is based on file restore and is different from the standard installs using SWPM.
Please refer to S/4HANA SQUARE ONE for other blogs
In this blog the procedure is simplified for hostname change and SID change. Also if you want to change instance number the command, screens show where you can change the instance number. This would make sense if your network cannot accommodate the unique hostname and SID. Also if it is a more permanent installation you may like to change SID and hostname.
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.
This blog is based on a fresh installation of SUSE Linux for SAP OS without having any previous SAP instances created and deleted. I did not have to pre install hostagent, etc. There are mount points/links to be setup as shown in the right place in the directory structure. The steps in the guides provided with SAP Note 2041140 could be used as a reference in case there are issues specific to your environment. Just follow the steps below to install both systems shown in red square below:
Please find below the main note for ordering the appliance:
2041140 - Order an SAP pre-assembled Best Practices software appliance (as partner or customer)
PART1: SOFTWARE DOWNLOAD
Please download the software media from https://me.sap.com/softwarecenter
INSTALLATIONS & UPGRADES => By Alphabetical Index (A-Z) => S => SAP S/4HANA => SAP S/4HANA 2023 => S/4HANA FULLY-ACTIVATED APPLIANCE => SAP S/4HANA 2023 FPS03 FA APPL
On SAP S/4HANA Server, download the 51058694_1 to 51058694_5 files and SWPM20SP22_3-80003424.SAR (or later).
On SAP NW JAVA / ADS server, download the 51058694_5, SWPM10SP45_2-20009701.SAR and 51050829_JAVA_part 1 & 2 - NW 7.5 Java based SW Comp.
PART2: INSTALL SAP S/4HANA
STEP 1: PREPARE SYSTEM Prepare Linux Server as below for the appliance. The values in Used column below show the minimum size needed. For /sapmnt provide min 30GB, /hana/data space - min 500GB, /hana/log min 120GB. I have used /sapmedia - 200GB temporary separate mount that can be removed later.
WARNING: PLEASE NOTE THE MOUNT POINT ! This applies to S/4HANA 2023 FPS3 Fully-Activated Appliance with Media numbers 51058694_* with . HANA 2 SPS8 release 82 (may not apply to other FAA releases) , if you want to rename the SID, the mount point /hana/data, /hana/log and /hana/shared should be used instead of /hana/data/HDB, /hana/log/HDB and /hana/shared/HDB. Reason is - the hdblcm register_rename_system command will rename the filesystem for you. This applies for any other filesystem that contains DB SID, mount its parent directory and only applies to HANA DB. SAP filesystems continue to be mounted with target SID as before. After installation is completed, you can adjust the filesystems mount points if necessary according to your standard to keep it consistent for other systems.
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.
The /etc/hostname and /etc/host file is below. If you are changing hostname for db and sap add the standard and new hostname for DB but for SAP only provide new hostname. Also for J2E include the new hostname only as this is on separate instance. The standard hostname can be removed later as shown in the steps below. Please note that it has
STEP 2: EXTRACT FILES Extract files 51058694_* in /sapmedia
sid-hdb-s4d:/sapmedia# unzip 51058694_1.ZIP
sid-hdb-s4d:/sapmedia# unzip 51058694_2.ZIP
sid-hdb-s4d:/sapmedia# unzip 51058694_3.ZIP
sid-hdb-s4d:/sapmedia# unzip 51058694_4.ZIP
sid-hdb-s4d:/sapmedia# unzip 51058694_5.ZIP
Allow approx 2 hours for extraction.
We will install Central system with DB and App on same server. Please move all *.tgz-* files (from 51058694_1 to 51058694_4) to /sapmedia/51058694_1/SAPS4HANA2023FPS03SAPHANADB20_1
cd /sapmedia/51058694_1/SAPS4HANA2023FPS03SAPHANADB20_1
mv /sapmedia/51058694_2/SAPS4HANA2023FPS03SAPHANADB20_2/*.tgz-* .
mv /sapmedia/51058694_3/SAPS4HANA2023FPS03SAPHANADB20_3/*.tgz-* .
mv /sapmedia/51058694_4/SAPS4HANA2023FPS03SAPHANADB20_4/*.tgz-* .
mv /sapmedia/51058694_5/SAPS4HANA2023FPS03SAPHANADB20_5/*.tgz-* .
In the next step we will extract the above *.tgz files but please note the directories size is as follows so you can provide ample space:
Please use command below to extract the database related archives:
sid-hdb-s4d:/sapmedia/# cd 51058694_1/SAPS4HANA2023FPS03SAPHANADB20_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 51058694_1/SAPS4HANA2023FPS03SAPHANADB20_1
cat usrsap_s4h.tgz-* | tar -zpxvf - -C /
cat sapmnt_s4h.tgz-* | tar -zpxvf - -C /
STEP 3: GET PASSWORDS Download the file below and open the file in Internet Explorer to note passwords:
/sapmedia/51058694_1/SAPS4HANA2023FPS03SAPHANADB20_5/SAP_Software_Appliance.xml
Follow this procedure as it is a known issue, please refer SAP Note 2082466 - Known Issues in SAP HANA Platform Lifecycle Management (HDBLCM) (Issue# 69)
cd /hana/shared/HDB/HDB02/vhcalhdbdb
rm .daemon.ini.swp
vi daemon.ini
Edit section [localsecurestore] to change instances = 0
STEP 4: REGISTER DATABASE
The HANA DB hdblcm register_rename_system command will rename the filesystem for you according to the new target SID for Hana database instance. HDB => HDD.
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. Please note hdblcm now includes rename database host and a separate step with command to rename db host (hdblcm --action=rename_system --hostmap=vhcalhdbdb=vhcalhdddb) is not required. Also a separate step to rename mount points (hdblcm --action=register_rename_system) is not required.
This should bring up the database processes as below
sid-hdd-s4d: #/usr/sap/hostctrl/exe/sapcontrol -nr 02 -function GetProcessList
TIP: At this point it is necessary to install the HANA database license as the database will be started in restricted mode.
STEP 5: EXTRACT SWPM Extract SWPM in folder /install. Use the SAPCAR already available to extract.
sid-hdd-s4d:/install #/sapmnt/S4D/exe/uc/linuxx86_64/SAPCAR -xvf /sapmedia/SWPM20SP22_3-80003424.SAR
STEP 6: RENAME SAP SYSTEM Rename instance using sapinst
sid-hdd-s4d:/install # ./sapinst SAPINST_ENFORCE_CRL=false SAPINST_USE_HOSTNAME=vhcals4dci
Copy below URL into chrome browser to start sapinst rename process:
https://sid-hdd-s4d.dummy.nodomain:4237/sapinst/docs/index.html
In SAPINST select System Rename => Standard System => SAP System Rename
At screen SAP System Parameters enter Source System S4H and Target System S4D:
Click on Next.
At the screen Prerequisite Checker Results accept or fix the Prerequisite check results.
Click on Next. No if you dont want to repeat the test
At the screen SAP Instance Parameters accept or change the Target System Instance Numbers.
Click on Next.
At the screen SAP HANA Database Connectivity enter Instance Number 02(or changed number) and Password Welcome_2Welcome_2. Click on Next.
If you don't install HANA DB license you will get error below. Install license using HANA Studio and continue. License is required if there is a database SID change..
At the screen SAP HANA Database Parameter you can change Schema User , DBACOCKPIT and SYSTEM password. Please note it is also optional to change the schema user SAPHANADB password along with DBACOCKPIT and SYSTEM users.
At the screen Database Schema accept schema SAPHANADB password and confirm Schema password Xxxxxxxn click on Next.
At the screen Rename Tenant Database 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 application.
At next screen Cleanup of Encryption Key checkmark on Yes cleanup os users 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.
TIP: In case you get this ERROR:
(1) Error occurs when executing command 'changekey' using the command line tool 'rsecssfx'.
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.
(2) You may get Warning below for rename of profile parameter. Found possible references to the source system in the profile directory of the target system /sapmnt/S4D/profile
After sapinst process is finished you can manually start the SAP instance S4D
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).
Host name / port in table HTTPURLLOC using tcode httpurlloc
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 70GB 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
The table below shows standard SID and hostnames and what we are changing it to.
The /etc/hostname and /etc/host file is below:
STEP 2: EXTRACT FILES
Extract files 51058694_5.ZIP in /sapmedia
sid-j2d:/sapmedia# unzip 51058694_5.ZIP
We will install Java instance from files in /sapmedia/51058694_5/SAPNetWeaver750SP31ASJAVAwithAdobeDocumentServices
cd /sapmedia/51058694_5/SAPNetWeaver750SP31ASJAVAwithAdobeDocumentServices
In the next step we will extract the above *.tgz files but please note the directories size is as follows so you can provide ample space:
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_j2e.tgz-* | tar -zpxvf - -C /
sid-j2d:/sapmedia# cat usrsap_j2e.tgz-* | tar -zpxvf - -C /
STEP 3: GET PASSWORDS Download the file below and open the file in Internet Explorer to note passwords:
/sapmedia/51058694_5/SAPNetWeaver750SP31ASJAVAwithAdobeDocumentServices/SAP_Software_Appliance.xml
STEP 4: RENAME MOUNT POINTS You can take a full OS backup at this point and rename mount points or directories to /sybase/J2D; /sapmnt/J2D; /usr/sap/J2D. The old standard mount points do not have to exist. After reboot ensure all new renamed mount points are valid.
STEP 5 EXTRACT SWPM Extract SWPM in folder /install. Use the SAPCAR already available to extract.
sid-j2d:/install #/sapmnt/J2D/exe/uc/linuxx86_64/SAPCAR -xvf /sapmedia/SWPM10SP45_2-20009701.SAR
STEP 6 RENAME SAP SYSTEM Rename instance using sapinst
sid-j2d:/install # ./sapinst SAPINST_USE_HOSTNAME=vhcalj2dci
Copy below URL into chrome browser to start sapinst rename process:
https://sid-j2d.dummy.nodomain:4237/sapinst/docs/index.html
In SAPINST select System Rename => Standard System => SAP System Rename
At the screen Software Integrity click on Next
At screen SAP System Parameters enter Source System J2E and Target System J2D:
Click on Next.
At the screen Prerequisite Checker Results accept or fix the Prerequisite check results.
Click on Next. No if you don't want to repeat the test
At the screen SAP Instance Parameters accept or change the Target System Instance Numbers.
Click on Next.
At the screen Database System Type keep the default selection SAP Adaptive Server Enterprise for Business Suite
At the screen Operating System Users accept master password or enter password Xxxxxxxn
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 Next
At the screen Database User Passwords enter the passwords for user sa, sapsa, sapsso, SAPSR3DB which is Welcome_2Welcome_2. 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.
You may get Warning below for rename of profile parameter. Found possible references to the source system in the profile directory of the target system /sapmnt/J2D/profile
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 Administrator 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 if you haven't installed during swpm install step before. 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 set...
SAP S/4HANA Fully-Activated Appliance: Demo Guides
Blogs with known issues (2022 / 2021 / 2020), continuously 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
Bluesky| User | Count |
|---|---|
| 10 | |
| 9 | |
| 6 | |
| 5 | |
| 5 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 3 |
