The instalation

The instalation of SAP DMS is a easy task if you came from infrastruture or see Linux servers as a buddy.
But, if you aren´t a infra guy, or Linux isn´t your best friend, the instalation of the SAP DMS will not be
too easy as the SAP manual tells it is. Of course, if you have background with Linux it will be easy, but,
strong background with Operational Systems and Database as well, it is not a “pre-requisite” to be a Basis
guy.

I buit this little and simple manual to help you to install SAP Content Server (called by the old school as
“SAP DMS”) and turn your life more simple and easy. But do not forgeth: Always use the SAP networks,
Forums and notes before start any instalation. Thousands of new notes are released every single day and
maybe, the way you judge is the right, isn´t anymore.

Preparation
As part of a SAP product, the instalation must be prepared. If your infrasture guy is smart and he if he did
any instalation for SAP products before, maybe the server will be ready to the instalatio. But belongs to the
BASIS as normal activities, revision of the server instalation and if it is compliance with SAP
requirements. Here I will describe the most importants:

Hostname

Check if the hostname has equal or less than 13 characters. Check SAP Note 611361 – Hostnames of SAP
servers

Swap

Check if the server has enough SWAP configured. Check SAP note 1597355 – Swap-space
recommendation for Linux

Linux

Check if the Linux is supported by SAP. Check SAP note 171356 – SAP Software on Linux: General
information
Language

Check if the Linux is installed using English as default language.

Updates

Check if the server is updated.

Midias

Check if all midias for the instalation are available. It is better if it is copied to local folder/mount point.
For the Content Server, it will be necessary:

1. SWPM
2. MAXDB RDBMS
3. Files for install of the Apache webserver (available http://www.apache.org/dyn/closer.cgi)

Enough space

Of course, you need to check if there is enough space for the instalation and for mainly for save your
documents in according of the Size done for the amount of the documents. A simple way to check it is
using the command df-kh

This is an example of disks configuration for DEV server. For this landscape, it is not necessary large
disks because that´s no reasons to use this server to save all documents, but for production servers,
consider use scalable large disks

Instalation
The instalation procedure has three phases:

 Users creation
 Apache instalation
 SWPM

Following I will describe in details each one.

Users creation
For instalation of SAP Content Server over Linux, the first step is to create the credentials that Apache will
use to run. Avoid run apache under root credentials due security issues.

These credentials that will be created now is for use of the Apache HTTP. The recommendation is create
the user with home folders. Later, the Apache will be installed on these users Home. These credentials
don´t need special PIDs or functions and the naming you decide that. For convenience, create the users in a
way you can remenber the proposal for that. On this example, I created the user CSDCS. Let me explain
the name:

1. The first 2 letters refers to SAP Product

2. D refers for development; Following this idea, Q for QAS and P for Production
3. CS for Content Server. The Content Server product is compounded by Content Server and Cache
Server. The both will have his own Apache and Databases.

This is just a way to create, but you deal.

If you plan to install cache server, you must create the user for cache server apache. Here an example for user
creation for Content Server and Cache Server.

Apache instalation
Get the Apache instalation files from Apace foundation. Extract the source files and change the owner of it
for the users you´ve created.

I decided to use the following folders structure

Where:

SRC_APACHE is the folder where resides the source of the Apache (in the future can be removed).

HTTP is the folder where the Apache will be installed and run.
Note that each one CSDCS and CCDCS have the same structure.

Once you have extracted the files, enter in the folder and run make and before make install

Check the results of these commands and if no error message occurs. If no error found, its time to install
the Apache on the home folders. To do that, run the command:

./configure –prefix=/<where you want to installApache instance> –enable-mods-shared=most –with-

mpm=prefork

Do that for the Cache Server user as the same way.

SWPM
The SWPM is the tool developed by SAP to install his softwares. From now, you just ask the tool with the
informations you have been collected for the install.
Open the
SWPM and
select Conten
Server and
Cache server
on Generic
Instalation
Options. This
will install
Content
Server and
Cache server
on the server
The next
window, the
SWPM will
ask you if the
both or each
one product
will be
installed.
Select as you
needs

Note that you

must choose
the SID for th
database and
size for
datafile.
Here, inform
to SWPM
where are the
media files fo
the instalation
of Content
Server.
This is a very
important
step:
Remember
the folder you
installed the
Apache for
each
instance? Use
the folder of
the installatio
on this screen
It is very
important the
executable fo
Apache being
available on
this folder,
otherwise
SWPM will
complains thi
is not the righ
place for
Apache
installation.
Inform the
SWPM where
are the files
for MaxDB.
Different from
Oracle install,
the instalation
of MAXDB is
done by
SWPM.
This step is a
optional area
to store the
files. For
content
Server, you
have two
ways to store
files: on
Maxdb as par
of a database
or on file on
the file
system. Here
is the folder if
you decide to
store the files
on File
system.

It is important
you take
notes about
http port that
will be
configured for
SAP. You
need to
configure this
ports on ECC
Define the
password for
the Software
Owner. This
user has
owner rights
on the Maxdb
Define here
where MaxDB
will be
installed.
Define
password for
superdba and
control. Take
notes for
these users
and
passwords.
They will be
required for
administration
Define this
variables
according the
project needs
Define here
where the
Logs of
MaxDB will be
located. Not
that this isn´t
like Oracle
that the logs
are files and
can be
manipulated
but they are
datafiles from
MaxDB and
could not be
move without
proper
commands.
Define where
the Datafile fo
the database
of Content
Server will be
saved. As the
same way yo
are
configuring it
for Content
Server, you d
it for Cache
Server.
Define
password for
owner of
Cache server
on MaxDB.
Define the
passwords fo
superdba and
control. Note
that these
users are
different from
CSD. There
are two
different
scheemas on
MaxDB and
the superdba
from the
scheema “A”
is different
from the
scheema “B”.
Define this
according the
project needs
Define where
the Logs for
Cache server
will be saved.
Define where
the data files
for Cache
server will be
saved.
 Well done! It
is time to test
the instalation

If everything done right, you can test the Content Server by opening in the browser the application.

Try to open:

http://<IP for the server>:<port>/ContentServer/ContentServer.dll?serverinfo

If you got this message, congratulations! The server is runnig fine.