SAP BO 4 Installation on Linux Part1

If you will get task to instal SAP BusenessObjects on Linux OS and you never work with terminal, the task could seem challenging:)

Lets, try to install SAP BO.

Before installing on Red Hat Linux according SAP BO installation manual, you must ensure all the required libraries are installed. Ensure you have root access, then use the Yum software installation tool to run the following commands:

• ●  yum install compat-libstdc++-33-3.2.3-69.el6.i686
  
• ●  yum install compat-libstdc++-33.i686
  
• ●  yum install compat-libstdc++-33-3.x86_64
  
• ●  yum install glibc.i686
  
• ●  yum install libstdc++.i686
  
• ●  yum install libX11-1.3-2.el6.i686 
  

1. Add user for our bo installation, perform command:   #useradd bo4user , create folder for BO installation #mkdir /data/bo4user and assign it to new user #chown bo4user bo4user
2. Change our user to new one: #sudo -iu bo4user

3. Go to location of SAP BO distributive. (of course we should download it and copy to new folder):

#cd /opt/bo4_distri/DATA_UNITS/BusinessObjectsServer_lnx

4. #./setup.sh

5. Choose Language

6. Specify the Destination Folder, for bo installation:

7. Prerequisite check

And here I got some problems:

7.1  Failed: Operating system patch level (Optional)

        Information: Missing patch: unsupported.linux.release

7.2 Failed: Integrated database - home directory (Optional)

        Information: DB2 requires 755 permissions to be set in the user's

home directory.  Please set the permissions if you wish to install the

integrated DB2 database.

7.3 Failed: Network settings (Critical)

        Information: Running ping failed against localhost, 127.0.0.1, or

the machine's hostname.  Please configure your machine to allow it to be

contacted in order to proceed.  INS00293

7.4 Important one, but not my case - if you choose DB2 as repository DB you should setup kernel parameters according to DB2 requirements:

7.4.1 Modifying kernel parameters (Linux)* from http://pic.dhe.ibm.com

Starting with Version 9.7 Fix Pack 2, you no longer need to update Linux kernel parameters related to interprocess communication (IPC). For Version 9.7 Fix Pack 1 or earlier, the enforced minimum settings for particular kernel parameters might not be sufficient to run a DB2®database system and you might need to update them before installing a DB2 database product.

Before you begin

You must have root authority to modify kernel parameters.

Procedure

To update kernel parameters on Red Hat and SUSE Linux:

1. Run the ipcs -l command to list the current kernel parameter settings.
2. Analyze the command output to determine whether you have to change kernel settings or not by comparing the current values with the enforced minimum settings for Version 9.7 Fix Pack 2 or later fix packs in Kernel parameter requirements ( Linux ). The following text is an example of the ipcs command output with comments added after // to show what the parameter names are:

      # ipcs -l
   
      ------ Shared Memory Limits --------
      max number of segments = 4096               // SHMMNI 
      max seg size (kbytes) = 32768               // SHMMAX
      max total shared memory (kbytes) = 8388608  // SHMALL
      min seg size (bytes) = 1
   
      ------ Semaphore Limits --------
      max number of arrays = 1024                 // SEMMNI
      max semaphores per array = 250              // SEMMSL
      max semaphores system wide = 256000         // SEMMNS
      max ops per semop call = 32                 // SEMOPM
      semaphore max value = 32767
   
      ------ Messages: Limits --------
      max queues system wide = 1024               // MSGMNI
      max size of message (bytes) = 65536         // MSGMAX
      default max size of queue (bytes) = 65536   // MSGMNB

3. Modify the kernel parameters that you have to adjust by editing the /etc/sysctl.conf file. If this file does not exist, create it.The following lines are examples of what should be placed into the file:

   #Example for a computer with 16GB of RAM:
   kernel.shmmni=4096
   kernel.shmmax=17179869184
   kernel.shmall=8388608
   #kernel.sem=<SEMMSL> <SEMMNS> <SEMOPM> <SEMMNI>
   kernel.sem=250 256000 32 4096
   kernel.msgmni=16384
   kernel.msgmax=65536
   kernel.msgmnb=65536

4. Run sysctl with -p parameter to load in sysctl settings from the default file /etc/sysctl.conf:

      sysctl -p

5. To have the changes persist after every reboot:
• (SUSE Linux) Make boot.sysctl active.
• (Red Hat) The rc.sysinit initialization script reads the /etc/sysctl.conf file automatically.

I will continue in part2 after fixing current issues.