MSCS: Manual Installation of SAP Content Server Database in MSCS Environment by Irshad Rather

-MSCS: Manual Installation of SAP Content Server

SAP Content Server is a standalone component in which a large quantity of electronic documents of any
format and with any content can be stored. The documents can be saved either in one or more MaxDB
instances or in the file system

Environment

• Windows Operating System;

Reproducing the Issue

This document shows an example of the installation of a Content Server database and its integration into
MSCS.

Resolution

Preparation

1 of 18
MSCS: Manual Installation of SAP Content Server Database in MSCS Environment by Irshad Rather

No other MaxDB databases may exist before the installation.

At the moment the usage of multiple MaxDB instances in the Microsoft cluster is not supported. The SAP
MaxDB Database Studio must not be installed in the cluster environment.

1. Installing the Content Server Database using the SAP SWPM provisioning manager

Selecting the installation service

As of SAP Content Server 640 there is a built in service in SWPM for the SAP Content Server.

Start the SAPINST program and select the corresponding installation service.

2 of 18
MSCS: Manual Installation of SAP Content Server Database in MSCS Environment by Irshad Rather

1.1 Selection of the Content Server Database.

In the dialog with the selection of the databases, only one database may be selected for use in the cluster
environment.
Even if the installation will allow to install the Content Server database and Cache Server database at once,
the multiple usage of MaxDB databases in the cluster is not supported!

3 of 18
MSCS: Manual Installation of SAP Content Server Database in MSCS Environment by Irshad Rather

1.2 Defining the MaxDB software destinations

In the dialog for the MaxDB software destination select as Global Program Drive the local drive and as Global
Data Drive the cluster disk (in this example it is I: ).
The Private Data Path has to be located on the cluster disk and the server software on the local drive.
However, the installation dialog
provides the same location for the private data and for the server software.

Select here the local drive. This document will show how to migrate the private data to the cluster disk later
after the installation is completed.

4 of 18
MSCS: Manual Installation of SAP Content Server Database in MSCS Environment by Irshad Rather

1.3 Setting password information for the Content Server database

Due to wrong handling of the long passwords within MSCS environment we suggest to use a password with
the maximal length of 8 characters.

5 of 18
MSCS: Manual Installation of SAP Content Server Database in MSCS Environment by Irshad Rather

1.4 Defining the locations for the MaxDB data and log volumes

The volumes must be located on the cluster disks. Select the corresponding paths for the volumes (in this
example cluster disks I: and J: are used.)

1.5 Checking the parameters in the summary dialog

Use the summary dialog of the SWPM tool to check all entries. Select ‘Next’ to start the installation.

6 of 18
MSCS: Manual Installation of SAP Content Server Database in MSCS Environment by Irshad Rather

After the installation is completed follow next steps to migrate the private data path to the cluster disk.

2. Migration of the private data path to the cluster disk after installation

2.1 Checking the installation state with the MaxDB xinstinfo tool

The xinstinfo tool with the database name as option returns the current configuration of the installed software:

The private data path is installed locally and needs to be moved to the cluster disc.

2.2 Checking the Database State before migration

The database must be offline. You can stop it via service console, or using the dbmcli command.

7 of 18
MSCS: Manual Installation of SAP Content Server Database in MSCS Environment by Irshad Rather

2.3 Execute the migration using MaxDB tool SDBUPD

The SDBUPD tool is located on the MaxDB installation DVD. Beside upgrade tasks it provides the migration
for the private data path.
Change into the directory with MaxDB installation medium. Execute SDBUPD and provide as options
database name and the target location for the private data path.
In this example the private data will be moved to the drive I:. The SAP convention for the private data path of
a MaxDB instance is: <drive>:\sapdb\<DBID>\data
The upgrade tool will ask you for the database manager operator, which is control, and for its password.

After execution is completed:

check the path configuration again with the xinstinfo tool:

8 of 18
MSCS: Manual Installation of SAP Content Server Database in MSCS Environment by Irshad Rather

Now the integration of the Content Server database into MSCS can be started.

3. Integration of the Content Server Database into MSCS

The following example will show the step by step integration of the previously installed database into the
MSCS environment.

3.1 Node A

3.1.1 Installation of MaxDB cluster software

The activity begins with the replacement of some MaxDB binaries with the cluster-enabled binaries.
- Stop the database and the communication services

As alternative you can use Microsoft services console:

- Create c:\sapdb\SDB\db\noncluster subfolder to store the original binaries and move the original binaries:
dbmsrv.exe, serv.exe, service.exe, strt.exe, stop.exe from C:\sapdb\SDB\db\pgm into this folder.

9 of 18
MSCS: Manual Installation of SAP Content Server Database in MSCS Environment by Irshad Rather

- Copy the *_clu.exe binaries from the C:\sapdb\SDB\db\cluster folder into the C:\sapdb\SDB\db\pgm
folder, rename the files removing ‘_clu’ extension.

- After renaming the original file name can only be seen in the properties dialog:

10 of 18
MSCS: Manual Installation of SAP Content Server Database in MSCS Environment by Irshad Rather

3.1.2 Installation of the MaxDB cluster management software

Next the MaxDB cluster libraries and MaxDB cluster manager executables must be installed. Copy it from
MaxDB cluster directory into Windows cluster system directory:

11 of 18
MSCS: Manual Installation of SAP Content Server Database in MSCS Environment by Irshad Rather

3.1.3 Creation of the MaxDB cluster resource types

Execute from the administration command prompt the command SAPDBMSCSMan.exe –C. You can see
further command options with -help option:

3.1.4 Creation of the MaxDB cluster resources and cluster group

This is done with the command SAPDBMSCSMan.exe -B. The option for this command consists of 4 parts:

- Network name , which can be found in the Networks View in the Cluster Failover Manager. In the current
example it is Cluster Network 3.

- Virtual IP Address of the cluster database server. Virtual IP address is provided by the network
administrator. It is not bounded to any real network device. Any ‘ping’ request will not return a response.
In this example the virtual host name is vhost and the bounded IP is xx.xx.xx.66:

- Network Mask. Which is found in the properties dialog of the corresponding network:

12 of 18
MSCS: Manual Installation of SAP Content Server Database in MSCS Environment by Irshad Rather

In the current example the network mask is 255.255.240.0.

- Disk resource where the global data of the MaxDB software is installed. The disk resource can be found in
the Storage view of the Cluster Failover Manager:

In the current example this is Cluster Disk 3.

- Communication Port. This is the port number, where the MaxDB instance specific listener communicates
with the client. It can be found in the output of the MaxDB dbmcli command with inst_enum.

In the current example the value is 7200.

Putting it together there would be following string for the MaxDB group creation: Cluster Network
3,xx.xx.xx.70,255.255.240.0,Cluster Disk 3,7200:

13 of 18
MSCS: Manual Installation of SAP Content Server Database in MSCS Environment by Irshad Rather

At the same time, the Cluster Failover Manager will show the MaxDB Cluster Group:

3.1.5 Completing of the MaxDB group, setting dependencies

The database resource must be added to the MaxDB group. This is done with the command:
SAPDBMSCSMan.exe -a <DBID>,<ClusterGroupName>

If there are further storages used by the database they should be added with the command
SAPDBMSCSMan -m “ResourceName,ClusterGroupName”. In our case, it is drive J: which is Cluster Disk 4
:

As a result the Cluster Failover Manager lists the SDB resource and one additional storage in the MaxDB
group. Right click on the SDB resource, select properties.
Go to the Dependencies tabulator and make the resource SDB dependent on other resources in this group.

14 of 18
MSCS: Manual Installation of SAP Content Server Database in MSCS Environment by Irshad Rather

The integration of the MaxDB instance SDB on the first cluster node is completed. It is important that all
resources except disk resources remain offline.

3.2 Node B

Integration of the MaxDB database on the node B consists of the MaxDB software installation, installation of
the cluster binaries and registration of the database instance.

3.2.1 Software Installation

- Login on the second node of the cluster

- Make the MaxDB installation medium available on the second node

- Open administration command prompt and change into directory with MaxDB installation.

The MaxDB software will be executed completely on the local drives. The paths for the Global Programs and
Server installation path must be the same as xinstinfo output on the first node.
In the current example the installation command looks like:

SDBINST -global_prog C:\sapdb\programs -global_data C:\sapdb\data -path C:\sapdb\SDB\db -

15 of 18
MSCS: Manual Installation of SAP Content Server Database in MSCS Environment by Irshad Rather

Press ENTER accepting the default values of the installation tool.

Installation should complete without errors:

3.2.2 Installation of the MaxDB cluster software

As already done on the first node, the same operations have to be executed on the second node:

- Create the folder c:\sapdb\SDB\db\noncluster

- Move MaxDB binaries dbmsrv.exe serv.exe, service.exe, strt.exe, stop.exe from c:\sapdb\SDB\db\pgm
to c:\sapdb\SDB\db\noncluster

- Copy the binaries dbmsrv_clu.exe, serv_clu.exe, service_clu.exe, strt_clu.exe and stop_clu.exe from
c:\sapdb\SDB\db\cluster to c:\sapdb\SDB\pgm\ and rename to them removing the _clu.

- Install MaxDB cluster management software: copy the binaries SAPDBMSCSEx.dll, sapdbmscsman.dll,
SAPDBMSCSMan.exe, SAPDBMSCSRes.dll from c:\sapdb\SDB\db\cluster to c:\windows\cluster\
directory.

3.2.3 Register the MaxDB cluster resource types in the second cluster node

Execute the command: C:\windows\cluster\SAPDBMSCSMan -C

3.2.4 Re-Register the Database Software

The SDBINST tool installed and registered the software in the local drives. Now the locations of the
GlobalData and private data must be re-registered to the same drive as on the first node.
The MaxDB tool sdbconfig is used for this. The following command will set the registration of the Global Data

16 of 18
MSCS: Manual Installation of SAP Content Server Database in MSCS Environment by Irshad Rather

to I:\sapdb\data:

c:\sapdb\programs\bni\sdbconfig IndepData=I:\sapdb\data

The next command will set the private data path registration to I:\sapdb\SDB\data:

c:\sapdb\programs\bin\sdbconfig -I -s C:\sapdb\SDB\db DataPath=I:\sapdb\SDB\data

3.2.5 Registering the Database in the second node

For this step it is necessary to move the MaxDB cluster group to the second node ( all resources except
storage are offline!):

Execute the command:

C:\sapdb\programs\pgm\dbmcli -R C:\sapdb\SDB\db db_register DB SDB control,XXX

3.2.6 Check the SDB integration on the second node

xinstinfo on the second node should provide the same information as it would do if the group switched back
to the first node:

17 of 18
MSCS: Manual Installation of SAP Content Server Database in MSCS Environment by Irshad Rather

Take the MaxDB group online and test several failover operations from the Windows failover manager.

The integration of MaxDB Database SDB into MSCS environment is completed.

18 of 18