Introduction
As of 7.30, SAP has decided to use Software Provisioning Manager to handle the actual install and updates. The install manager has been deprecated. As of writing this doc, the current vanilla install of using the 7.20 (non EXT) version of the UC kernel produces the error shown on the bottom left corner of Fig 1.1.
Figure 1 – 7.20 (non EXT) kernel error.
To resolve this problem, please make sure to download at least the: 720_EXT UC Kernel for SWPM SP03 – Linux on x86_64 64bit along with the SL Controller 720 for SWPM SP03.
Assuming you do not have access to the X-windows of the server, I have shown screen captures of how initialize a vncserver on the suse server and to connect using a vncviewer to conduct the install.
Setting up a VNCServer
Starting a vncserver on Suse
Conveniently, suse comes with a vncserver out of the box. All we’ll need to do is to issue the following command:
> vncserver :
suse2:~ # vncserver :10
You will require a password to access your desktops.
Password:
Verify:
Would you like to enter a view-only password (y/n)? n
New ‘X’ desktop is suse2:10
Creating default startup script /root/.vnc/xstartup
Starting applications specified in /root/.vnc/xstartup
Log file is /root/.vnc/suse2:10.log
Connecting to a vncserver
Download vncviewer
In order to connect to a vnceserver, you’ll need to download the free vncviewser. It can be found:
http://www.realvnc.com/download/viewer/
Connect to the vncserver
Connecting is simple. Merely provide it the IP or hostname followed by a colon and the port number. Upon clicking connect, you’ll be prompted for the password you had setup initially for this user’s connection. This is to prevent other random users from connecting into your server as that user to potentially do harm. For example, in our previous scenario it would be:
Figure 2 – VNC Connection
Result of a vnc connection.
The following shows a screenshot of what the vncviewer should look like.
Figure 3 – VNC Initial Screen
SAP Netweaver Install
Once we are able to make the connection to the server via the vncviewer. We’ll need to have the install files ready. In my case, I have mounted these files in /sapmedia.
Launching the Software Provisioning Manager ( SWPM )
From within the /sapmedia/SWPM, I called the script sapinst which loads the Software Delivery Tool as shown in the figure below: (note the arrows)
Figure 4 – sapinst initial screen
Select the Netweaver 7.31 Standard System
- In this screen, we are going to pick which SAP product we are going to install. For our setup, we are going to install the Standard System
Figure 5 – Selecting the NW7.31 – Standard System
Parameter Settings
- The parameter mode we wish to install using. Typical option will select many of the default settings. Whereas the custom mode allows you to configure many aspects of the installation ranging from ports, domain, drives and etc. For our install, we have chosen custom to show all the screens that are available to the end user.
Figure 6 – Parameter Selecting
SAP System Parameter
- Here you’ll set the SID of the SAP install. The SID is exactly three uppercase alphanumeric unique character set. The following reserved sets that should not be used:
- ADD ADM ALL AMD AND ANY ARE ASC AUX AVG BIT CDC COM CON DBA END EPS FOR GET GID IBM INT KEY LOG LPT MAP MAX MIN MON NIX NOT NUL OFF OLD OMS OUT PAD PRN RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID USE USR VAR
Figure 7 – SAP SID Selection
DNS Domain Name
- The DNS allows you to access the machine anywhere within the network. In our case, we have created an Anchor record at thusjanthan.com domain for saplinux. Thus, we can set that as the FQDN to be able to access the service via FQDN on the internet.
Figure 8 – Domain setting
Media Browser
IMPORTANT: Here is where you’ll need to give the updated 720 EXT UC Kernel.
Figure 9 – Selecting the Kernel
Master Password
- This screen you will select the master password which is used throughout the installation. Keep this password safe as this will be the default password for many of the SAP services.
Figure 10 – Master Password
Operating System Users
- adm password section. Again, this has taken the master password from Figure 10.
Figure 11 – OS User passwords
Database System
- Here generally you’ll set the DBSID as the same sid as the SAP sid. In our case NW1
Figure 12 – DB SID
Database Administrator Password
- Note, now if you don’t enter any passwords for any users, the default password will be the master password you set in Figure 10.
Figure 13 – DB Admin Pass
SAP Admin Password
Figure 14 – SAP Admin Pass
Export Directory
Figure 15 – Export Directory
Database Parameters
Figure 16 – DB Parameters
Database Maxdata file Size
Figure 17 – max data file size
Database Accounts
Database Media Browser
Figure 18 – RDBMS Media browser
Database Oracle Listener
Figure 19 – Database Listener
Database Import
- Here, the parallel jobs can be adjusted based on the number of cores in the system. 2-3 jobs per core. This system is a quad core but to be on the safe side putting 6 parallel jobs.
Figure 20 – Parallel jobs
Database Statistics
Primary Application Instance and ABAP Central Instance
- Set the identifier number of the PAS and ABAP instances here. Remember the instances correlate with the port numbers. In our case, PAS will run on 3600 and ASCS will run on 3601.
Figure 21 – Instance numbers
ABAP Message Server Ports
Figure 22 – ABAP message server ports
ICM User Management
Database Client Media Browser
IMPORTANT: Because we are using a custom Kernel, it requires we provide the SL Controller as the Kernel at the time does not come with the SL Controller.
Figure 23 – DB Client Media
Diagnostics Agent
- I have chosen to not show the DAA screens here. Please follow through the screens for the DAA install.
Figure 24 – DAA Initial screen
Install Screen
Figure 25 – Installing Screen
Oracle Install
During the middle of the SAP Install a prompt will come up asking to install the Oracle RDBMS. The following figure shows what that will look like.
Figure 26 – Oracle Installer Popup.
VNCServer as Oracle User
You’ll need to do the same VNCServer setup. Only this time you’ll need to do it as the ora user.
Example:
suse2:~ # su – oranw1
suse2:~ # vncserver :11
You will require a password to access your desktops.
Password:
Verify:
Would you like to enter a view-only password (y/n)? n
New ‘X’ desktop is suse2:10
Creating default startup script /oracle/NW1/.vnc/xstartup
Starting applications specified in /oracle/NW1/.vnc/xstartup
Log file is /oracle/NW1/.vnc/suse2:11.log
Load up another vncviewer using the port 11 this time so for example:
Figure 27 – VNC Viewser for the oracle user.
Preinstall Check
Before installing the oracle, it might be a good idea to run the preinstaller to see if you need to install any packages or run any fixes. Note: The directory which we use to run the install. It is actually an SAP directory within the database. SAP has done a few customization’s to the installer to fit its needs. Please make sure to run the installers from within there.
Click on the Fix & Check again. This will create a script for you with all the changes that needs to be deployed.
Remember to Run the script as “Root”.
If no errors, you’ll end up with a screen like this and you are ready to run the installer.
Installing Oracle
Now you are ready to install the database. Run the RUNINSTALLER from within the SAP directory. You can choose to ignore the email address if you wish.
Software Updates
I have chosen to skip software updates.
Install Options
Install the database software only.
Continue with the installation by selecting the defaults for the install…
For the Warning about installing the Central Inventory in the Oracle base. Click Yes and continue.
Perform Install
Post Database Installing
Once the database installs, it will ask you to run one or two scripts as root. This will setup symbolic links and such for the database you have chosen to install. Please perform these as root. Screen capture below:
Commands on the prompt as “root”
suse2:~ # /oracle/oraInventory/orainstRoot.sh
Changing permissions of /oracle/oraInventory.
Adding read,write permissions for group.
Removing read,write,execute permissions for world.
Changing groupname of /oracle/oraInventory to dba.
The execution of the script is complete.
suse2:~ # /oracle/NW1/11203/root.sh
Performing root user operation for Oracle 11g
The following environment variables are set as:
ORACLE_OWNER= oranw1
ORACLE_HOME= /oracle/NW1/11203
Enter the full pathname of the local bin directory: [/usr/local/bin]:
Copying dbhome to /usr/local/bin …
Copying oraenv to /usr/local/bin …
Copying coraenv to /usr/local/bin …
Creating /etc/oratab file…
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Finished product-specific root actions.
Patching Oracle
As per the instructions on Figure 26 prompting us to install the Database Server; there is also a patch that needs to be applied depending on the server. In our case the Note is: 1431799 and in the event you have Oracle 10.2, the Note: 871096 will apply to you. All you’ll have to do is go to: https://websmp103.sap-ag.de/oracle-download to fetch the latest patch for your server.
To patch the system, make sure oracle is not running and run the following: (make sure to use the correct paths to where you have the patch files)
suse2:~ # su – oranw1
suse2:oranw1 11> cp -R /sapmedia/Oracle\ Patches/mopatch-2_1_12.zip 112_64/
suse2:oranw1 12> cd !$
cd 112_64/
suse2:oranw1 13> unzip mopatch-2_1_12.zip
Archive: mopatch-2_1_12.zip
replace MOPatch/readme.txt? [y]es, [n]o, [A]ll, [N]one, [r]ename: A
inflating: MOPatch/readme.txt
inflating: MOPatch/mpkill.sh
inflating: MOPatch/mopatch.sh
suse2:oranw1 14> cd
suse2:oranw1 15> cp -R /sapmedia/Oracle\ Patches/SAP_112036_201306_LINX8664.zip ./
suse2:oranw1 16> /bin/sh $ORACLE_HOME/MOPatch/mopatch.sh -v -s ./SAP_112036_201306_LINX8664.zip
Final Steps
Once patched, we can now resume the remainder of the install on SAP. Click Ok and the setup should continue and finish.
Installation Complete
As you can see, it has gone past the “Create ICM userstore” where it used to hang. The rest of the installation should go smoothly.
Congratulations! You have now installed SAP Netweaver 7.31 on top of Suse using Oracle 11g
Thusjanthan Kubendranathan M.Sc.