See my other SAP tips / blogs: sap_tips

Fresh install of 2007s isa on ubuntu (hedgy) 64 bits


I use Ubuntu rather than Suse, because Suse is not a good Desktop distro and RPM just sucks.

Installing Ubuntu

I simply burned an Ubuntu CD (Hardy Heron x86 64 bits) and install it to my drive (regular Desktop installation)

Fixing Ubuntu so that the SAP installer will work

SAP only supports Redhat / Suse out of the box, so a few fixes where required to get Ubuntu ready for SAP.

make sure your /etc/hosts contains lines like those, otherwise visual admin won't work right (and maybe other things)       localhost localhost.localdomain       desktop     desktop
Make sure you have both and your ip address(ex: resolving to your hostname.
Otherwise Install/Upgrade will fail miserably (login errors) and it's VERY hard to track down !!

Dash / Bash

This drove me insane for a while, but the SAP installer was failing and i could not figure out why.
Turn out that Ubuntu uses Dash as the standard shell, rather that Bash !! and because of that sapinst would fail. (said somethign stupid like 'dirname --p nos such option' )

So anyhow, we fix that by setting bash as the default shell (better anyway in my opinion)
sudo ln -s -f /bin/bash /bin/sh


SAP relies on older libraries and other packages.
Here are the main things i had to install:
sudo apt-get install pdksh unzip original-awk csh zsh libstdc++5 libperl-dev

SAP system settings

As explained in SAP notes, you should adjust some settings.

vi /etc/sysctl.conf
kernel.shmall = 1879048192
kernel.shmmax = 1879048192
kernel.msgmni = 128
fs.file-max = 8192

then run sysctl -p

vi /etc/security/limits.conf
* hard nofile 32800
* soft nofile 32800

Chkconfig isssue

During the installation SAP tries to use the Redhat?Suse specific "chkconfig" script to setup some services.
This does not exist on debian Hardy but we can install a version of it (from Intrepid) as wellas insserv and it will then work ok.

Go to: and download chkconfig (intrepid) and install it with GDBI (the browser will open it with GDBI by default, just click Install")

We also need to install insserv: (Suse service manager)

sudo apt-get install insserv

installing insserv removed the standard initscripts which might result in an unbootable system.
So note which packages are removed and make sure you reinstall them after installing SAP and before rebooting.
For me here where the removed packages: apparmor apparmor-utils initscripts system-services ubuntu-minimal upstart-compat-sysv

On my machine, this would fail because of a loop between urandom and umountfs, i edited /etc/init.d/umountfs and removed "urandom" from Required-Start, then ran it again.
This helped a bit:

Installing java

We need a 64 Bit JDK, best one to use, is IBM JDK for sap:

We use the IBM jvm(64bits) (see note: 1090932 & 861215).
This is the best VM for linux x86 64 bits.
We download the new version here:

It will ask for an access key that is found in the sap note.
Then downloaded latest tgz (Ex: IBMJava2-AMD64-142-SDK-1.4.2-xyz-tgz) to here:

Then extract it to:

tar xzvf IBMJava2-AMD64-142-SDK-1.4.2-xyz.tgz /usr/lib/jvm/

Installing SAP


Here are the SAP DVD's i used (from sap marketplace)

We use 2007 SP1.
We also that use maxdb as the Database, it's free and more lightweight than oracle, thus better for a developer workstation.

You will need the following CD's/DVD's, as they will be requested by sapinst :

551033089_8 : SAP_CRM_2007_Installation_Master_Lin64
51033262_9 : NW_2004s_SR2_Kernel_LNX_X86
51033265 : 2007_java_components
51032922: MaxDB 7.7.02 Build 10 Linux X86 64

They are all on my sap share:

Installer will request those (in order):

Running sapinst

xhost +
su -
export DISPLAY=:0.0
cd 551033089_8/IM_LINUX_x86_64

Choose a system of type:
crm2007->sap systems->maxdb->central system->central inst

choose "typical"

Update: on most of my coworker machines, selecting JCRM here would cause the installer to hang at the "Deploying Application" step after deploying the CRM packages and fail the whole installation. (i think maybe it runs out of memory - unsure)
So: Do not select JCRM, instead after the installation just run JSPM and do "new packages" and deploy the CRM packages then (at least SAP-CRMAPP, SAP-CRMDIC and SAP-SHRAPP) this is quicker anyway.

When asked for the type of install, choose the JCRM java components & "AS-java" ONLY
Give it the CD's it's asking for when asked. (51033265_2007_java_components)

Provide the path to jdk 1.4 (previously installed). Ex: /usr/lib/jvm/IBM....
Provide the path to the JCE policy: /sapcd/Others/java_installers/Java Cryptolib ssl/

Give a system ID(ex: ZTB) and password.
DO not forget those password ever, you will probably need to remember in 2 years while doing an upgrade.
MaxDb settings: Specify "mirror logs" as requested in Upgrade guide. Set to use 2 cpu if you have them.

It will ask for the other DVD's listed above (kernel, maxdb etc..).

Register into the SLD if you wish.

It will also ask you for a SAP solution manager key, go get one, you will have to add your new system into SAP sol. manager and generate that key.

Service packs

Upgrading to 2007 SP1 from 2007 SP0
Upgrading ISA to 2007 SP3

Post Install

Reinstall packages removed by insserv

installing insserv removed the standard initscripts which might result in an unbootable system.
So note which packages are removed and make sure you reinstall them after installing SAP and before rebooting.
apt-get install apparmor apparmor-utils initscripts system-services ubuntu-minimal upstart-compat-sysv

MaxDB stupid log system

Unless you tell it otherwise, MaxDB standard practice is that once the log files gets full, it will just stop operating, the best part about it:
  • It will just stop working whenever that happens
  • It usually will give you an error about what it was trying to do at the time rather than tell you clearly the log is full.

Anyway in the case of ISA we really don't give a damn much about loosing the data in that DB, let alone the log files of the DB.

So we need to tell maxdb, to automatically start the log over when they are full (~ circular log) rather than crap out.

Here is how it's done:

# log as the sap user on the box, where ZTB is your instance ID and DB name
su - ZTBadm
# log into the db
dbmcli -U c_J2EE -d ZTB
#In the db shell, turn on log overwrite:
    util_execute SET LOG AUTO OVERWRITE ON
# it should say OK, then leave the db shell

Connection to TREX server

Unless you configure the trex connection on the ISA box, all the B2B. B2C catalog won't work and display an error
The catalog that you have selected is currently unavailable, try again later.

See Note: 980678
I don't understand why they don't retrieve this data from the TREX CRM connection as it did in earlier version, now(since 2007) you have to maintain this manually both on the ISA and the CRM box !
Anyway, what you have to do is:
  • Use SAGUI to connect to the CRM box and launch transaction SM59(rfc's) go to tcp/ip and find the TREX connection, and note that RFC's name (EX: TRX_RFC_XYZ)
  • Start transaction SE37 (edit/run functions) and find "TREX_EXT_SHOW_SERVERS" and run it with those arguments: Server Type = '4', IS_ACTIVE = 'X', RFC: TRX_RFC_XYZ (use the actual RFC name you found in the previous step), run the transaction
  • Look at the transaction results, and you should find the TREX connection settings, such as: host:, port: 30301, remember those

Now that we got this data, we need to go put it in visual administrator:
  • Start visual administrator and connect to the ISA server (local)
  • Browse to SID/server/services/TREX service
  • Select "communication.nonproxyhosts" and enter your trex server hostname here (Ex: and click update
  • Select "nameserver.address" and enter a value like: tcpip:<nameserverhost>:<nameserverport> Ex: click Update
  • Select "nameserver.backupserverlist" and enter the same data (unless you do have backup trex servers) and click Update
  • Press Save (floppy icon) and quit visualadmin
  • Restart the sap engine (stopsap,startsap)

Start/Stop scripts

created in /usr/local/adm folder
in there created with content
gksu su - sidadm -c startsap

and created with content
gksu su - sidadm -c stoptsap

Then Chmod +x those files

You can setup shortcuts for visual admin & config tool

Visual admin and configtool shortcuts:
vi /usr/local/adm/
# run this script with sudo: Ex: gksudo
xhost +
#export JAVA_HOME=/usr/lib/jvm/IBMJava2-amd64-142/
su - sidadm -c "setenv DISPLAY :0.0;cd /usr/sap/SID/JC00/j2ee/configtool/;./"
xhost -

vi /usr/local/adm/
# run this script with sudo: Ex: gksudo
xhost +
#export JAVA_HOME=/usr/lib/jvm/IBMJava2-amd64-142/
su - sidadm -c "setenv DISPLAY :0.0;/usr/sap/SID/JC00/j2ee/admin/go"
xhost -

Then Chmod +x those files
As it said in the scripts, you will want to run them as root (Ex: sudo or have an icon run Ex: "gksudo"

ISA: Password expiration and number of tries

Sap auto-expire the password of admin after 90 days, it does so the first time you "login" after 90 days, unfortunately it seem to always be when you have important work to do like changing a setting or redeploying an app, on a production system you don't want this to happen by itself at a bad time, but should make your own policy to change that password at scheduled times.

Also after 5 errors it will lock=up, and the last thing you want is the admin password to get locked up on your production system because it might take hours to fix this.

Anyway this settings can be changed in the visual administrator: (set it to a big number, say 900 days)
server->services->ume provider->ume.logon.security_policy.password_expire_days

And the number of attempts: (set this high to be safe say 20)

Port number

For historic reason and the way our firewall is setup we want the http port of the J2ee to be 50100 (50101 for https).
So in visual admin go to:
dispatcher->services->http provider
and edit the "ports' line appropriately then click "update" and then the "save" icon.

Setup B2c/B2B XCM

See here on how to setup the ISA XCM server/B2B/B2C sites
Saving/Loading iSA B2B/B2C XCM config

The Sap Consultant Handbook: Your Sourcebook to Lasting Success in an Sap Consulting Career


You can go to:

and verify all your components are at the correct patch level.

Kernel should be at 144
MaxDB should be at 7.7.02
Java components should be at SP15

CRM comps at 6.0 SP2 (except crmdic: 5.0SP12)




Add a new Comment