Installation of SAP BO 4.1 on Redhat Linux 6.7

Prerequisites for SAP BO 4.1 :
Assuming that you have already installed Red Hat 6.7 Enterprise Linux installation I had written this blog if you not completed the installation click here
[root@sap]# useradd sapuser
[root@sap]# passwd sapuser
Changing password for user sapuser.
New password:
Retype new password:
passwd: all authentication tokens updated successfully.

Add the user to wheel group so that he can have the sudo rights to execute the commands and installation 
# gpasswd -a username wheel
# vi /etc/sudoers

Add this line below ## Allow root to run any commands anywhere
root    ALL=(ALL)       ALL

username    ALL=(ALL)       ALL
To ensure that host name is reachable when we ping IP address to Hostname and Hostname to IP address, edit the hosts files in etc folder
[root@sap]# vi /etc/hosts

127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.2.101 hadoop.cgiad.com   hadoop

General
Only 64-bit Operating systems are supported
Installation target must have adequate disk space ~20gb (will require much more to account for applying patches and SP's).
Temporary filesystem space ~2gb
Create a user account and group under which the BI4.1 SP01 software will run.  This account does not require root privileges
Locale: Configure a supported UTF-8 locale by setting LC_ALL and LANG environment variables.

Example:
[root@sap]# export LANG=en_US.utf8
[root@sap]# export LC_ALL=en_US.utf8

ulimit settings must be set to unlimited by using the ulimit command or editing
[root@sap]# vi /etc/security/limits.conf manually.
read, write and execute permission to the installation target destination directory
or
Run the command
[root@sap]#  ulimit -f unlimited

For a complete list of requirements and a Final Checklist please reference:
SAP BusinessObjects Business Intelligence platform 4.1 Support Package 1 Installation Guide for Unix

Prerequisite Red Hat libraries:
Before installing on Red Hat Linux, 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:

[root@sap ~]# yum install compat-libstdc++-33-3.2.3-69.el6.i686
[root@sap ~]# yum install compat-libstdc++-33.i686
[root@sap ~]# yum install compat-libstdc++-33-3.x86_x64
[root@sap ~]# yum install glibc.i686
[root@sap ~]# yum install libstdc++.i686
[root@sap ~]# yum install libX11-1.3-2.el6.i686

Here when we run yum install libX11-1.3-2.el6.i686 we face an issue saying that we have already library installed with version libX11-1.6.0-6.el6.x86_64
[root@sap ~]# yum install  libXext-1.1-3.el6.i686
[root@sap ~]# yum install libXext-1.1-3.el6.x86_64
[root@sap ~]# yum install libXext-devel-1.1-3.el6.i686
[root@sap ~]# yum install libXext-devel-1.1-3.el6.x86_64

*Note:
Failure to apply these prerequisite libraries can cause instability in the BI4.1 environment.
Please reference these KBA articles to learn more about the consquences:
1692724 - Cannot open Shared object file: No such file or directory
1692679 - Bad ELF interpreter: No such file or directory
1692695 - Error while loading shared libraries: libX11.so.6: cannot open shared object file: No such file or directory
1875824 - LDAP Plugin missing from CMC on Red Hat Operating systems
Difficulties installing via YUM? See:
1972307 - Error: Protected multilib versions when installing BI4 prerequisite libraries
Checking Prerequisites :
Checking to see if these libraries are installed is quick and simple using the following commands:
[root@sap ~]# locale
LANG=en_US.utf8
LC_CTYPE="en_US.utf8"
LC_NUMERIC="en_US.utf8"
LC_TIME="en_US.utf8"
LC_COLLATE="en_US.utf8"
LC_MONETARY="en_US.utf8"
LC_MESSAGES="en_US.utf8"
LC_PAPER="en_US.utf8"
LC_NAME="en_US.utf8"
LC_ADDRESS="en_US.utf8"
LC_TELEPHONE="en_US.utf8"
LC_MEASUREMENT="en_US.utf8"
LC_IDENTIFICATION="en_US.utf8"
LC_ALL=en_US.utf8

[root@sap ~]# rpm -qa compat-libstdc++*
compat-libstdc++-33-3.2.3-69.el6.i686

[root@sap ~]# rpm -qa glibc
glibc-2.12-1.166.el6_7.3.x86_64
glibc-2.12-1.166.el6_7.3.i686

[root@sap ~]# rpm -qa glibc
glibc-2.12-1.166.el6_7.3.x86_64
glibc-2.12-1.166.el6_7.3.i686

[root@sap ~]# rpm -qa libstdc++
libstdc++-4.4.7-16.el6.x86_64
libstdc++-4.4.7-16.el6.i686

[root@sap ~]# rpm -qa libX11
libX11-1.6.0-6.el6.i686
libX11-1.6.0-6.el6.x86_64

[root@sap ~]# ulimit
4096

[root@sap ~]# ulimit -u
9186


Starting the BI4.1 Setup
To Start the installation insert the BI4.1 Installation media login to the sapuser which we created and continue the installation
Before starting the installation make sure we run this command
[sapuser@sap BusinessObjectsServer_lnx]$ ulimit -u 9186

[sapuser@sap BusinessObjectsServer_lnx]$ ./setup.sh


Select English and Press Enter
Select the Installation Location

Press Enter
It will check for the Pre-requestes

It Show some errors which are optional but while configuring the real time environment we have to take care of all these things, Press Enter to continue
This will display the Copyright information, Press Enter to Continue

This will display copyrights information, Press Enter to Accept the Agrement.
Provide the Product Key which is supplies with the Media or subscription
Select the Additional Language packages to install with the installat
ion

Sele
ct the type of Installation you want to do
Select Default Database of Existing Database



Select the Java Web Application Server Type

Select the Subversion Management


Configure the SIA Server Intelegent Agent


Provide the Node Name and Port No u want to give I select default only
Configure Central Management Server (CMS), Enter the Port No , I select default

Enter the Password for Adminstrator Account and CMS Cluster Key

Enter the password for Sybase SQL Any where Port and Pa
ssword



E
nter the Tomcat Ports information, we can change the ports if we want to 

Enter the Sybas SQL Anywhere Information and set 'dba' account password 





Enter the HTTP Listening port information 


Select 'Do not configure connectivity to SMD Agent'
 Select 'Do not configure connectivity to Introscope Enterprise Manager'





Press Enter SAP BO Installation started wait till it completed 100%




Post Installation


Press Enter to Continue



Access the url
http://192.168.2.101:8080/BOE/BI


























Keywords: SAP, SAP BI, BO, SAP BO 4.1, SAP BO, Business Objects, Bi Lauch Pad, Lib Library installation, Red hat installation 
Location: Hyderabad, Telangana, India

Comments

Post a Comment

Popular posts from this blog

Observium: Configuring Microsoft Windows 2008 Server SNMP Agent

Image
1 . Open Control Pannel. 2. Right click on “ Programs & Features ” and click on “ Turn Windows Features on or off" 3 . Expand “ SNMP Services ” and select “ SNMP Service ” click Next 4. Click Install 5. Close  Programs & Features ” 6. Open Ädministraive Tools and clicket Services 7. Expand Configuration and select Services,  Select SNMP Service , right click and select properties 8 . Select the “ Agent ” tab 9. Type the contact name responsible for this server or email address 10 . Type the location eg, Hyderabad,India. 11 . Tick the following  Physical Datalink and subnetwork  SNMP Trap Service - Agent 12 . Select the “ Traps ” tab 13 . Type in the community string you are using in your environment and select “ Add to list ” 14 . Click “ Add ” 15 . Type the IP of the Observium ServerSNMP Trap Service - Traps 16 . Select “ Security ” tab 17 . Ensure “ Send authentication trap ” is
Read more

AWS: Upgrade PV Drivers on Windows Instances

Image
Amazon Windows AMIs contain a set of drivers to permit access to Xen virtualized hardware. These drivers are used by Amazon EC2 to map instance store and Amazon EBS volumes to their devices. If your Windows instance is launched from a Windows Server 2012 R2 AMI, it uses AWS PV drivers. If your Windows instance uses RedHat drivers, you can upgrade to Citrix drivers. If you are already using Citrix drivers, you can upgrade the Citrix Xen guest agent service. To verify which driver your Windows instance uses , open  Network Connections  in Control Panel and view the  Local Area Connection . Check whether the driver is one of the following: AWS PV Network Device Citrix PV Ethernet Adapter RedHat PV NIC Driver Alternatively, you can check the output from the  pnputil -e  command. AWS PV Drivers Windows Server 2012 R2 AMIs include AWS PV drivers. The AWS PV drivers are stored in the %ProgramFiles%\Amazon\Xentools directory. This directory also contains public symbo
Read more

How to configure Incremental backups for MSSQL Database

Image
Incremental Database Backup : Create a folder for the backup in the Hardisk (Ex: C:\SQL_backup\Incrementail) 1. Open SQL Server Management Studio and connect using windows credentials. 2. Click Management   and select Maintenance Plans . 3. Right-Click on Maintenance Plans and select New Maintenance Plans, Give naming Convention as Incremental_DB_Backup . 4. In Left side of Server Management Studio there will be a Tool Box within Maintenance Plan Tasks   5. Drag and drop the Back Up Database Task and Maintenance Clean Task in the Incremental_DB_Backup   Design area.   6. Right Click on the Back Up Database Task and select Edit .   7. Select the Type of Backup you want to do as Differential 8. Select the Database In Database(s)   in these database list (Ex: TestDB.)   9. Select Create a Backup file for every database , select Create a sub-directory for each database 10. Give the path where we want to store the database backup as C:\SQL_backup\I
Read more