SAP BI 4.2笔记(基于linux)

  • 7
  • 3,336 views
  • A+
所属分类:SAP

SAP BI安装过程中会创建两个标准数据库:
BO_AUDIT、BO_CMS.
BO_AUDIT数据库是记录用户操作日志的库;
BO_CMS数据库是记录报表用户、服务器配置、文档信息的库,这个库是最重要的库;
The Central Management Server (CMS) collects audit information from the other BI platform servers and writes the details to the Auditing Data Store (ADS), known as the Auditing database. This information lets System Administrators manage their BI platform environment, and content usage, through reporting and analysis of ADS data.
The CMS system database is used to store BI platform information, such as user, server, folder, document, configuration, and authentication details. It is maintained by the Central Management Server (CMS), and in other documentation may be referred to as the system database or repository.
The databases that are used to store reporting data are referred to as reporting databases.
根据需要,我们还可以专门建立一个Reporting Database,用于存放比如人工导入的数据、其他地方抽过来的数据等。


SAP BI4.2自带的数据库是Sybase,在SqlAnywhere(sybase)下面是创建BO_AUDIT、BO_CMS,可能名字是BI4_Audit和BI4_CMS


默认安装完的时候BI4_Audit和BI4_CMS的容量都非常小:
BI4_Audit大约有6M,BI4_CMS大约有30M。
BI4_Audit可以在后台设置自动清理的时间,例如100天;
BI4_CMS主要用来记录一些用户权限、报表信息(属性、设置啥的),一般增长也不会太大。
因为BI报表的数据应该存放在BW数据仓库中,而不是BO的数据库!


BO标准数据库的迁移大概三小时内就能做完,其他数据库可以慢慢迁移。
一般来说,BI4_Audit大约有有2GB左右,BI4_CMS大约100M以内。
迁移的时候注意编码,MySQL端应该是utf8或者utf8mb4,防止后面打开BOE后乱码。


兼容的操作系统:RHEL6.8,SLES12兼容的数据库:
SAP BI 4.2笔记(基于linux)

http://dev.mysql.com/get/Downloads/MySQL-5.6/MySQL-5.6.34-1.el6.x86_64.rpm-bundle.tar


安装完BI,整体大约占用40GB硬盘(4GB的boot分区,‘10GB’的SWAP分区,15GB的BI数据,4GB的临时文件,其他为操作系统和常用应用)。
核心一点就是根分区和BI分区一定要预留够,否则后面很麻烦。


重要的路径:
/BIROOT/modifyOrRemoveProducts.sh   作用:卸载、更新、更改BI程序(组件)的安装。
/home/biconst/sqlanywhere   作用:数据库根目录(如果你的数据库不在此,那就在你定义的目录)
/home/biconst/sqlanywhere/database   作用:数据库数据,安装完约400MB
/home/biconst/sap_bobj   作用:BI核心程序的安装目录,安装完约15GB
/home/biconst/sap_bobj/enterprise_xi40   作用:BI核心应用中的核心,大约10GB
/home/biconst/sap_bobj/tomcat  作用:web容器根目录
/home/biconst/sap_bobj/tomcat/webapps   作用:java web应用,安装完约2GB
/home/biconst/sap_bobj/tomcat/work/Catalina/localhost  作用:tomcat的临时文件夹,安装完约2GB
/home/biconst/sap_bobj/logging  作用:BI系统的日志文件,报错了来这里查日志
SQLANYWHERE_CONFIGSCRIPT=/home/biconst/sqlanywhere/bin64/sa_config.sh
SQLANYWHERE_CMS_DBFILE=/home/biconst/sqlanywhere/database/BI4_CMS.db
SQLANYWHERE_AUDIT_DBFILE=/home/biconst/sqlanywhere/database/BI4_Audit.db
/home/biconst/sap_bobj/Data/PlatformSearchData  该目录不一定会有,但是如果有的话会占用非常大的空间,通常用100多GB。
4.2版的BI路径应该在这下面,和4.1有点不同。
WEB容器配置管理工具集:
注意:如果安装BI的过程中已经选择部署,则此处就不需要操作了。
/home/biconst/sap_bobj/enterprise_xi40/wdeploy

部署日志文件:
The WDeploy tool creates two log files with detailed information that may be useful for diagnosing problems or
monitoring activity.
wdeploy/logs/WDeploy_summary.log   概括性的日志
wdeploy/logs/WDeploy.log                          详细的日志
When a WDeploy command is issued, WDeploy_summary.log.01 is overwritten with the current command, and
WDeploy.log is appended.
As the WDeploy.log file grows to more than 512 KB, the file is renamed with a unique numbered suffix. For
example, WDeploy.log will be renamed to WDeploy.log.01. If a file named WDeploy.log.01 already exists,
WDeploy.log.02 will be created.

WAR文件集合:
/home/biconst/sap_bobj/enterprise_xi40/warfiles

workdir目录:
/home/biconst/sap_bobj/enterprise_xi40/wdeploy/workdir


start/stop
cd  /home/biconst/sap_bobj
./sqlanywhere_startup.sh
./sqlanywhere_shutdown.sh
./startservers
./stopservers
./tomcatstartup.sh
./tomcatshutdown.sh

访问:
http://domain/BOE/BI
http://domain/BOE/CMC


注意:由于各种原因,BI应用可能会发生内存溢出,发生时会在目录的logging下产生4GB左右的.hprof日志文件.
sap_bobj \logging\java_pid17204.hprof
这些文件会很快吞噬整块磁盘空间,导致最终没有可用空间,所以该目录需要每天监视!


配置iptables服务,将BI常用端口加入白名单

开启iptables,关闭selinux
配置iptables
以下配置的端口根据实际情况配置,注意数据库、SSH80tomcat的操作端口必须配置。
yum方式安装iptables
# yuminstall iptables-services
编辑防火墙配置文件
vi/etc/sysconfig/iptables
添加下面三句话到默认的22端口这条规则的下面
-A INPUT-p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 3306 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 8080 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 8443 -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 8005 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 6400 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 6410 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 6405 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 2638 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 5801 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 5901 -j ACCEPT

-AINPUT -p tcp -m state --state NEW -m tcp --dport 6001 -j ACCEPT

重启防火墙:
# /etc/init.d/iptables restart
必须要关闭系统自带的防火墙!!!(就因为这个问题,排查了一下午的错误,血与泪的教训啊,泥煤的MySQL报错不直接
简单的说,linux系统自带的SElinux是个垃圾,没法用,会导致MySQL等很多服务无缘无故启动不了,我们用iptables即可!!!
1. 永久关闭Selinux有效
  修改 /etc/selinux/config 文件中的 SELINUX="" 为 disabled ,然后重启。
2. 即时生效(重启后无效)
  setenforce 0

校验是否安装成功
http://:/BOE/CMC
Substitute for the hostname of the web application server and for the web application
server\\\\\\'s listening port. If you are using a custom web application server root context or BOE.war web application
context, the URL will be different.
Log on as the Administrator user by typing Administrator into the User Name field and entering the
administrative password that you entered into the installation program.


安装必备的软件包:
注意:请不要自行安装JDK,BI安装过程中会自动安装,自行安装JDK会导致新的问题。
安装系统常用功能:
yum groupinstall "Compatibility libraries" "Base" "Development tools"
yum groupinstall "debugging Tools" "Dial-up Networking Support"

安装系统常用功能:
yum -y install tree nmap sysstat lrzsz dos2unix gcc* g tinyxml kernel wget net-tools psmisc screen vim links pcre pcre-devel zlib zlib-devel openssl openssl-devel cmake make zip unzip gzip bzip2* uuidd bc qt time ed perl ntp kernel-devel ntpdate libcurl libcurl-devel awk uname tar sty read which dirname id ulimit ping gcc-c glibc.i686

安装SAP BI要求的功能:
yum -y install libstdc .i686 install libstdc .x86_64 compat-libstdc -33.i686 compat-libstdc -33.x86_64 glibc.i686 glibc.x86_64 libX11.i686 libX11.x86_64 libXext.i686 libXext.x86_64 expat.i686 expat.x86_64 libgcc.i686 libgcc.x86_64 libXcursor.i686 libXcursor.x86_64 libXrender.i686 libXrender.x86_64 libXfixes.i686 libXfixes.x86_64 libxcb.i686 libxcb.x86_64 libXau.i686 libXau.x86_64 libXext-devel

然后执行一次yum更新:
yum –y update
yum –y upgrade


给RHEL6.8配置可用的yum源
注意:不要用最新版的RHEL,因为centos的更新发布比RHEL慢,如果用最新版的RHEL、则使用yum源的时候会找不到合适的版本。
操作步骤如下:
(关键点:卸载rhel自带的yum包的时候要注意忽略依赖关系、否则卸载不掉;安装yum的时候要注意全部一起安装,否则依赖关系没完没了)。

下载CENTOS6.8的yum安装包:
打开http://mirrors.163.com/centos/6.8/os/x86_64/Packages/,【CTRL F】搜索下面这些包,然后下载,然后上传到Linux。
yum
yum-metadata
yum-plugin-fastestmirror
yum-updateonboot
yum-utils

安装的时候如果提示有其他依赖再下载就是了。
然后执行下面的命令安装CENTOS的YUM工具:
rpm -qa |grep yum
rpm -qa|grep yum|xargs rpm -e --nodeps
rpm -ivh yum*

vi /etc/yum.repos.d/CentOS-Base.repo
粘贴下面的内容进去(然后wq保存,之后就能不注册redhat而使用centos的yum源了):
[base]
name=CentOS-$6.8 - Base - 163.com
#mirrorlist=http://mirrorlist.centos.org/?release=$6.8&arch=$basearch&repo=os
baseurl=http://mirrors.163.com/centos/6.8/os/$basearch/
gpgcheck=1
gpgkey=http://mirrors.163.com/centos/RPM-GPG-KEY-CentOS-6


#released updates
[updates]
name=CentOS-$6.8 - Updates - 163.com
#mirrorlist=http://mirrorlist.centos.org/?release=$6.8&arch=$basearch&repo=updates
baseurl=http://mirrors.163.com/centos/6.8/updates/$basearch/
gpgcheck=1
gpgkey=http://mirrors.163.com/centos/RPM-GPG-KEY-CentOS-6


#additional packages that may be useful
[extras]
name=CentOS-$6.8 - Extras - 163.com
#mirrorlist=http://mirrorlist.centos.org/?release=$6.8&arch=$basearch&repo=extras
baseurl=http://mirrors.163.com/centos/6.8/extras/$basearch/
gpgcheck=1
gpgkey=http://mirrors.163.com/centos/RPM-GPG-KEY-CentOS-6


#additional packages that extend functionality of existing packages
[centosplus]
name=CentOS-$6.8 - Plus - 163.com
baseurl=http://mirrors.163.com/centos/6.8/centosplus/$basearch/
gpgcheck=1
enabled=0
gpgkey=http://mirrors.163.com/centos/RPM-GPG-KEY-CentOS-6

参考:
http://sanwen8.cn/p/2a3DPxF.html
http://mirrors.163.com/centos/6.8/os/x86_64/Packages/
http://blog.sina.com.cn/s/blog_4ab15f5f0102w2y5.html


分区规划:
名称
作用
大小
/swap
缓存,一般为内存的两倍
64GB
/boot
如果用的是RHEL,安装时建立此分区;如不是RHEL,不需要
4GB
/
类似于Windows的C盘(安装Linux和常用软件)
100GB
/ourdata或/opt
数据盘(数据库、我们的程序等)
剩余所有空间

rhel安装过程中的注意事项:
时区:北京/上海,
语言:勾选英语、简体中文、繁体中文。
启用网络,设置好hostname;
选择带GNOME桌面安装,勾选【开发调试】、【向下兼容】三个软件包复选框。
设置root用户密码。
创建一个用户(例如:biconst)、设置密码并勾选“设置为管理员复选框”。


一定不要忘记配置hosts文件,否则会有很多意想不到的问题:
编辑hosts文件
127.0.0.1                 sapbiprd
192.168.1.199                sapbiprd
192.168.1.199         sapbiprd.domain.com
192.168.1.100         sapbwprd
192.168.1.200         sapeccprd


安装MariaDB

使用中国电信的mariadb yum源
创建本机的repo(在/etc/yum.repos.d/下)
vim /etc/yum.repos.d/MariaDB.repo
内容如下:
[mariadb]
name = MariaDB
baseurl = http://mirrors.ctyun.cn/MariaDB/mariadb-10.1.13/yum/centos6-amd64/
gpgkey = http://mirrors.ctyun.cn/MariaDB/PublicKey
gpgcheck=1

先安装两个依赖
yum clean all
yum -y install jemalloc galera
卸载MySQL
rpm –qa|grep mysql
rpm –e mysql-libs-5.1.73-7.el6.x86_64 –nodeps
安装mariadb
yum install MariaDB-server MariaDB-client

yum 安装会自动创建mysql 用户和用户组
Yum安装会自动创建 /etc/my.cnf 以及/etc/my.cnf.d 文件架(并存放 server.conf client.conf tokudb.conf 等文件)

默认的rpm路径
basedir =/usr/bin
datadir=/var/lib/mysql
.h=/usr/include/mysql
plung=/usr/lib64/mysql
share=/usr/share/mysql

修改my.cnf文件
service mysql stop

注意:虽然是mariadb,但是mysql的命令是通用的!!

数据库文件存储在数据专用分区/ourdata
cp -rf /var/lib/mysql/*  /ourdata/sapbi/mariadb
chown -R mysql:mysql /ourdata/sapbi/mariadb
rm -rf /var/lib/mysql

修改配置文件/etc/my.cnf.d/mysql-clients.cnf,重点是[client],其他的可以参考
先用dd命令清空该文件,然后复制下面的内容到里面,参数根据需要修改!

[client]
port        = 3306
socket      = /ourdata/sapbi/mariadb/mysql.sock

修改配置文件/etc/my.cnf.d/server.cnf,这里的性能参数来自my-large.ini文件
先用dd命令清空该文件,然后复制下面的内容到里面,参数根据需要修改!

[mysqld]
port            = 3306
datadir         =/ourdata/sapbi/mariadb
socket          =/ourdata/sapbi/mariadb/mysql.sock
skip-external-locking
key_buffer_size = 256M
max_allowed_packet = 64M
table_open_cache = 256
sort_buffer_size = 1M
read_buffer_size = 1M
read_rnd_buffer_size = 4M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size= 16M
thread_concurrency = 8
log-bin=mysql-bin
binlog_format=mixed
server-id   = 1
lower_case_table_names = 0

character-set-server = utf8

log-bin=mysql-bin
binlog_format=mixed
server-id   = 1
expire_logs_days = 10

default_storage_engine = InnoDB
innodb_data_home_dir = /ourdata/sapbi/mariadb
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = /ourdata/sapbi/mariadb
innodb_buffer_pool_size = 256M
innodb_log_file_size = 64M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50

初始化数据
chown –R mysql:mysql /ourdata/sapbi/mariadb
mysql_install_db --defaults-file=/etc/my.cnf --datadir=/ourdata/sapbi/mariadb --user=mysql

启动服务
service mysql start

设置ROOT密码
mysqladmin -u root password "8888888"

登陆mysql
mysql -uroot -p

授权root远程登录
#root可从任何IP登陆,注意修改密码:\\\\\'888888\\\\\'
mysql>GRANT ALL PRIVILEGES ON *.* TO \\\\\'root\\\\\'@\\\\\'%\\\\\' IDENTIFIED BY \\\\\'888888\\\\\' WITH GRANT OPTION;

#root可从指定IP登陆,注意修改密码:\\\\\'888888\\\\\'、IP:\\\\\'192.168.1.188\\\\\'
mysql>GRANT ALL PRIVILEGES ON *.* TO \\\\\'root\\\\\'@\\\\\'192.168.1.188\\\\\' IDENTIFIED BY \\\\\'888888\\\\\' WITH GRANT OPTION;
mysql>FLUSH RIVILEGES

注意:mariadb安装完之后,root用户默认是没有密码的,执行mysql_secure_installation设置密码的时候直接敲回车跳过即可。

systemctl start mariadb ==> 启动mariadb
systemctl enable mariadb ==> 开机自启动
mysql_secure_installation ==> 设置 root密码等相关
mysql -uroot -p123456 ==> 测试登录!
Remove anonymous users? [Y/n] <– 是否删除匿名用户,回车
Disallow root login remotely? [Y/n] <–是否禁止root远程登录,回车,
Remove test database and access to it? [Y/n] <– 是否删除test数据库,回车
Reload privilege tables now? [Y/n] <– 是否重新加载权限表,回车
#修改root密码
SET PASSWORD FOR \\\\\'root\\\\\'@\\\\\'localhost\\\\\' = PASSWORD(\\\\\'password1\\\\\');
SET PASSWORD FOR \\\\\'root\\\\\'@\\\\\'127.0.0.1\\\\\' = PASSWORD(\\\\\'password1\\\\\');
#删除匿名用户
delete from user where user=\\\\\'\\\\\';

设置mariadb开机启动
chkconfig mysql on
service mysql stop
reboot


Yum方式安装MySQL(如果网络不行,不要尝试,成功不了!)
# 下载mysql源安装包
shell> wget http://dev.mysql.com/get/mysql57-community-release-el7-8.noarch.rpm
# 安装mysql源
shell> yum localinstall mysql57-community-release-el7-8.noarch.rpm
检查mysql源是否安装成功
shell> yum repolist enabled | grep "mysql.*-community.*"

安装MySQL
shell> yum install mysql-community-server

启动MySQL服务
shell> systemctl start mysqld

查看MySQL的启动状态
shell> systemctl status mysqld

开机启动
shell> systemctl enable mysqld
shell> systemctl daemon-reload

修改root默认密码
mysql安装完成之后,在/var/log/mysqld.log文件中给root生成了一个默认密码。通过下面的方式找到root默认密码,然后登录mysql进行修改:
shell> grep \\\\\'temporary password\\\\\' /var/log/mysqld.log
shell> mysql -uroot -p
mysql> ALTER USER \\\\\'root\\\\\'@\\\\\'localhost\\\\\' IDENTIFIED BY \\\\\'MyNewPass4!\\\\\';

添加远程登录用户
默认只允许root帐户在本地登录,如果要在其它机器上连接mysql,必须修改root允许远程连接,或者添加一个允许远程连接的帐户,为了安全起见,我添加一个新的帐户:
mysql> GRANT ALL PRIVILEGES ON *.* TO \\\\\'yangxin\\\\\'@\\\\\'%\\\\\' IDENTIFIED BY \\\\\'Yangxin0917!\\\\\' WITH GRANT OPTION;


linux加入ad域:linux 加入AD域


千言万语,有一点非常重要,必须要关闭selinux,否则mysql没办法启动!

开启iptables,关闭selinux
配置iptables
以下配置的端口根据实际情况配置,注意数据库、SSH80tomcat的操作端口必须配置。
yum方式安装iptables
# yuminstall iptables-services
编辑防火墙配置文件
vi/etc/sysconfig/iptables
添加下面三句话到默认的22端口这条规则的下面
-A INPUT-p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 3306 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 8080 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 8443 -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 8005 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 6400 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 6410 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 6405 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 2638 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 5801 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 5901 -j ACCEPT
-A INPUT-p tcp -m state --state NEW -m tcp --dport 6001 -j ACCEPT
重启防火墙:
# /etc/init.d/iptables restart
必须要关闭系统自带的防火墙!!!(就因为这个问题,排查了一下午的错误,血与泪的教训啊,泥煤的MySQL
 
简单的说,linux系统自带的SElinux是个垃圾,没法用,会导致MySQL等很多服务无缘无故启动不了,我们用iptables即可!!!
1. 永久关闭Selinux有效
  修改 /etc/selinux/config 文件中的 SELINUX="" disabled ,然后重启。
2. 即时生效(重启后无效)
  setenforce 0

安装VNC

yum install tigervnc-server tigervnc

vim /etc/sysconfig/vncservers
VNCSERVERS="1:root"
VNCSERVERARGS[1]="-geometry 1024x768 -alwaysshared -depth 24"

执行vncserver

vncpasswd 设置root用户的密码

编辑/root/.vnc/xstartup文件

chkconfig vncserver on

VNC的启动和重启:
# /etc/init.d/vncserver restart
注:有时候上面的命令启动会报错,直接运行就可以:
# vncserver
注:关闭具体的vncserver命令:vncserver -kill :1 vncserver -kill :2

注意:用VNC客户端连接服务器的时候最好选择版本高一点的vnc viewer,否则可能出现未知错误!


取消RHEL的注册提醒

yum list all | grep subscription
上面显示安装了几个与注册有关的包,卸掉这些包然后世界就清净了。
yum remove subscription-manager
顺带在去除rhn-setup-gnome,这下就连管理里面都没有可以注册的选项了。
RPM方式清理:
1、检查已安装组件(共3个)
# rpm -qa | grep subscription-manager
2、卸载查出的组件
# rpm –e subscription-manager-firstboot subscription-manager-gnome subscription-manager
3、检查已安装组件(共7个)
# rpm –qa | grep rhn
4、卸载查出的组件
# rpm –e rhn-check rhn-setup rhnlib rhnsd yum-rhn-plugin rhn-setup-gnome rhn-client-tools


安装BI4.2支持的MySQL版本:
MySQL 5.6 X64 FOR RHEL.

http://dev.mysql.com/get/Downloads/MySQL-5.6/MySQL-5.6.34-1.el6.x86_64.rpm-bundle.tar

mkdir /ourdata/sapbi/mysql/bin-logs

rpm -e mysql-libs* --nodeps
rpm -ivh MySQL-server*
rpm -ivh MySQL-client*
rpm -ivh MySQL-shared-5.6*
rpm -ivh MySQL-devel*

查询刚才生成的随机密码
ls -a | grep mysql

用安装时随机生成的密码登录MySQL,注意密码和-p之间不要有空格!
mysql -u root -p随机密码
 
修改root用户密码
SET PASSWORD FOR \\\\\'root\\\\\'@\\\\\'localhost\\\\\' =PASSWORD(\\\\\'MyNewPassword\\\\\');
 
修改my.cnf
输入下面的内容:
(ps,里面的socket          = /var/lib/mysql/mysql.sock这个之所以没有放在其他目录,是因为放在其他目录的话mysql命令会报错,估计程序设计得bug或者是其他地方还有优先级更高的配置!)
 
[client]
port                = 3306
socket                = /var/lib/mysql/mysql.sock
 
[mysqld]
port                = 3306
socket                = /var/lib/mysql/mysql.sock
datadir =        /ourdata/sapbi/mysql
skip-external-locking
key_buffer_size = 32M
max_allowed_packet = 1M
table_open_cache = 128
sort_buffer_size = 768K
net_buffer_length = 8K
read_buffer_size = 768K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M
thread_cache_size = 16
query_cache_size = 16M
tmp_table_size = 32M
character_set_server = utf8
init_connect = SET NAMES utf8
 
#skip-networking
max_connections = 500
max_connect_errors = 100
open_files_limit = 65535
 
log-bin=/ourdata/sapbi/mysql/log-bins/mysql-bin
binlog_format=mixed
server-id        = 1
expire_logs_days = 3
 
default_storage_engine = InnoDB
innodb_data_home_dir = /ourdata/sapbi/mysql
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = /ourdata/sapbi/mysql
innodb_buffer_pool_size = 256M
innodb_additional_mem_pool_size = 4M
innodb_log_file_size = 64M
innodb_log_buffer_size = 16M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 120
 
[mysqldump]
quick
max_allowed_packet = 4096M
socket          = /var/lib/mysql/mysql.sock
 
[mysql]
socket          = /var/lib/mysql/mysql.sock
no-auto-rehash
default-character-set = utf8
 
[myisamchk]
socket          = /var/lib/mysql/mysql.sock
key_buffer_size = 64M
sort_buffer_size = 2M
read_buffer = 4M
write_buffer = 4M
 
[mysqlhotcopy]
socket          = /var/lib/mysql/mysql.sock
interactive-timeout
权限设置:
cd/ourdata/sapbi
chown -R mysql:mysql mysql/
启动MySQL
service mysqld start
如果需要重新初始化:
mysql_install_db --defaults-file=/usr/my.cnf--datadir=/ourdata/sapbi/mysql --user=mysql
添加远程登录用户
默认只允许root帐户在本地登录,如果要在其它机器上连接mysql,必须修改root允许远程连接,或者添加一个允许远程连接的帐户,为了安全起见,我添加一个新的帐户:
mysql> GRANT ALL PRIVILEGES ON *.* TO\\\\\'yangxin\\\\\'@\\\\\'%\\\\\' IDENTIFIED BY \\\\\'Yangxin0917!\\\\\' WITH GRANT OPTION;
FLUSH PRIVILEGES;

ps.用MySQL需人为先创建好数据库
mysql -u root -pPASSWD
create database bi_cms;
create database bi_audit;


安装完毕后以root用户登录,切换到BI安装目录下,分别启动tomcat和servers,然后设置windows的hosts文件就能访问了。
也就是说,安装完毕后默认并没有启动服务,要人工启动后才可以访问
cd /ourdata/sapbi/biapp/sap_bobj
./tomcatstartup.sh
./startservers


默认文件夹:
SAP BI 4.2笔记(基于linux)


必须要修改ulimit值,正确的做法:
vim /etc/security/limits.d/90-nproc.conf
* soft nproc 10240
* hard nproc 16384
* soft nofile 10240
* hard nofile 65536
* soft stack 10240

如果不修改这个值,会出现错误:-bash: fork: retry: Resource temporarily unavailable错误

修改完后要停止服务,重启系统。


mysql的log-bins由于文件非常多,不建议使用默认的设置,放在其他目录mkdir -p /ourdata/sapbi/mysql-log-bins
chown -R mysql:mysql /ourdata/sapbi/mysql-log-bins

vi /usr/my.cnf[mysqld]
log-bin=/ourdata/sapbi/mysql-log-bins/mysql-bin

service mysql stop
service mysql start


安装过程中一定要勾选安装svn,否则后面没办法做跨系统迁移(CMC --> 升级管理 -->迁移)


常见错误代码查询:
http://help.sap.com/businessobje ... n/html/topic15.html
FWM 01001 - FWM 01014[size=13.3333px]In this section:


注意:如果第一次升级之后发现有异常,则再分次同步几次,例如账号单独同步一次、文件夹结构重新同步一次、连接信息重新同步一次,基本上大多数问题都能解决。

此外,由于更换了系统,对应的RFC配置、连接之类的也要做修改!


错误信息:Illegel url to the viewer的解决办法
关闭数据库,停止服务,重启服务器和服务即可。


使用普通账号登录:
Universe generation failed for resource id "ATePiypxtPJLkveqe_qlwFo". (Error: INF )
或者看不到报表目录。Dear Amit,Issue has been resolved. As we are using only one common connection between BO and BW. So I deleted the BO Dev Connection and I have moved the BO QA connection to BO dev and its working fine now. Thanks for your support.
真实原因为BI报表在不同的系统迁移后,报表都迁移过来了,用户组和用户也迁移过来了,但是具体的目录结构以及IDT对应的权限却没有迁移过来。所以要在CMC中分别给文件夹和OLAP连接做一次授权。以下截图为OLAP连接的权限配置,报表目录也同样需要在新系统里面重新授予一次权限,看来BI的这个“升级管理”做的并不完善。也可能是别人理解的升级管理是指从一个DEV系统到PRD这样的,不包括对等系统之间的迁移。
SAP BI 4.2笔记(基于linux)SAP BI 4.2笔记(基于linux)SAP BI 4.2笔记(基于linux)

SAP BI 4.2笔记(基于linux)


Hi,
After doing small research we found that this issues casuing because
After doing migration from Dev to QA. we will login into CMC
In genereal we change the server number, client, server name
but we did an change server type also , I mean when I click on server type it gives me an option of SERVER or GROUP
As per my company standards we need to select GROUP and filled all other prompts and then saved it
SO after doing changes, when I execute the report we are getting this error.
but if I keep "SERVER" as server type then report working fine.
Now I want to know what we need to if I want to use GROUP as server type?

OK, So this Thread is related to your other thread here: IDT Connection issue


Hi S J
I faced the same issue when I try to refresh the WEBI Reports of BEX Query using BICS Connection in BI LaunchPad. So I went to the Source File and mapped with the same BEX Query by
Data Access -> Tools -> Change Source and run the Report\\\'s. it worked for me.

--Raji. S


打开报表提示:
ERR_WIS_30253 - Your Security profile does not include permissions....

后台检查对应的文件夹、文件的对应的用户组的权限,最好采用继承的方式,修改权限后可能要重启一下服务,有时候由于缓存等原因,修改了不会立刻生效。


访问某些报表提示下面的错误:
com.businessobjects.sdk.core.server.CommunicationException$UnexpectedServerException: FatalException occured. The cause was : com.crystaldecisions.enterprise.ocaframework.OCAFrameworkException$AllServicesDown: 无法在 CMS newbi:6400 和类型为 webiserver 服务为 null 的群集 @newbi:6400 中找到服务器。所有此类服务器可能已关机或被管理员禁用。 (FWM 01014) (Error: INF )

原因:对应的java服务不堪重负,登录CMC将对应的Java服务克隆几份出来,做到“负载均衡”就好。

例如,上面提示:无法在 CMS newbi:6400 和类型为 webiserver 服务为 null 的群集 @newbi:6400 中找到服务器。

好,那么我们登录CMC,管理服务器:
当然,并不是克隆越多越好,要根据服务器的配置量力而行!!
SAP BI 4.2笔记(基于linux)
SAP BI 4.2笔记(基于linux)
SAP BI 4.2笔记(基于linux)
SAP BI 4.2笔记(基于linux)
应该经常监控服务器,发现异常的时候进行分析,要么修改配置、服务,要么重启服务甚至服务器,要么考虑增加服务器配置等。

SAP BI 4.2笔记(基于linux)

ERR_WIS_30270:
\u003Cinput type=\"hidden\" name=\"BENCH_ERROR\" value=\"Error Number :  - Error Description : com.businessobjects.sdk.core.server.CommunicationException$UnexpectedServerException: 调用“getPages”API 时出现内部错误。(错误:ERR_WIS_30270)\"\u003E


原因1:
   这里说明导致这个错误的很隐蔽的原因,在网上搜索此错误得到的几乎都是在找服务器或客户端的问题,但有一种BO连接的底层数据仓库变更也会导致此错误,情景如下:
  在Webi中创建两个变量A和B,A变量处理与字段ZA对映的维度,B变量处理A变量,当数据仓库中字段ZA被删除或者名称更改后,再次刷新报表时在Webi中就会弹出如上错误提示,此种情况如果按照错误内容搜索解决方案,很难找到对口的解决方法。
  所以在改数据仓库中的表和字段时要考虑到这种影响,报表出现这种错误时先排查掉这种简单但很隐蔽的原因。

原因2:
在报表发布到web intellience中报“调用 answerPrompts API时出现内部错误。(错误:ERR_WIS_30270)”的错误,其他报表都很正常,在百度搜了下,也没搜到结果。最后还是在google搜到了相关的一些信息。也没有提出真正的解决方案,我感觉是在加过滤条件的时候出的错,就一个一个的去查,结果发现,在报表中我们包含了日报,月报,年报,汇总。在4个报表中都包含了相同条件的查询为“交易类型”。日报,月报,年报中将交易类型都设为了可选,而在汇总中没有设置可选,所以在查看的时候,全部刷新就报错了。将汇总的也设置为可选后就解决了。



用Universe Design Tool客户端连接服务器是报错:
[repo_proxy 13] SessionFacade::openSessionLogon with user info has failed(Transport error: Communication failure.(FWM 00001)
(hr=#0x80042a01)
用WEBI胖客户端登录报错:未找到服务器或者服务器已经关闭。

参考:
Transport error: Communication failure.(FWM 00001)
Cause
The client could not talk to the Server. Possible causes of the problem are:
• The server may be down.
• There may have been a network communication problem.
• The request my have timed out.

Action
Verify that the server is up, that network communication is working correctly,
and check if a request time out has been set. If one has been set, lengthen
the amount of time before the request times out.

Transport error: Insufficient resources.(FWM 00002)
Cause
The Client and Server don’t have a communication channel over which they
can communicate.
Action
If Clientor Server sideuses SSL,please makesurethatbothsidesareusing
SSL.

Kerberos target name %1 is unknown. Please contact your system
administrator to make sure it’s set up properly.(FWM 00003)
Cause
The target account or SPN was not recognized
Action
Verify that the target account exists. Verify that the target SPN exists

Failed to contact the Active Directory server. (FWM 00004)
Cause
The Active Directory Server is not reachable
Action
Turn on logging, find the server name, and make sure that it is reachable.
The Active Directory Authentication plugin could not authenticate at this time.
Please try again. If the problem persists, please contact your technical support
department.

(FWM 00005)
Cause
Old alias format is detected.
Action
Update AD plugin from CMC (Central Management Console) AD plugin
screen.
Above are list of SAP Business Objects Error Messages from Error FWM 00001 to FWM 00005 received while performing certain operation against SAP Business Objects Business Intelligence Suite or related products.

What are SAP Business Objects Error Messages?
There are many different types of error messages received while using SAP Business Objects Business Intelligence Suite which include Administration (ADM) Errors,
Administration Wizard (ADW) Errors, BI Platform Servers (FWB) Errors , BIP Framework Middleware (FWM) Errors , Security (USR) Errors, Crystal Reports Errors, Dashboard and Analytics (EPM) Errors, Data Access Errors, Document and Universe Exchange Errors, Enterprise Application Errors, GUI Errors, Import Wizard (IWZ) Errors, List of Values Errors, SAP Live Office (LO) Errors, Metadata Bridges and Universe Builder (MDB) Errors, Publishing (FBE) Errors, Process Tracker (PT) Errors, SAP Query as a Web Service (QWS) Errors, Report Conversion Tool (RCT) Errors, Setup Errors , Translation Manager (UTM) Errors, Universe Errors, Voyager Errors, Web Intelligence Errors, HTTP errors.
Hope this was helpful.


error-fwm-00001-transport-error-communication-failure还有一种原因:
检查服务器的防火墙,先尝试关闭一下防火墙,看能不能连上。


service iptables stop

然后重新尝试连接,果然秒秒钟连上!!


在解决各种错误之前,先安装客户端工具,打开所有Universe等,检查IP地址、数据库名称等信息:SAP BI 4.2笔记(基于linux)

SAP BI 4.2笔记(基于linux)


允许MySQL的root用户远程登录:
Grant all privileges on *.* to \'root\'@\'%\' identified by \'kdm001\' with grant option;
上面这条命令中的kdm001是mysql的root用户的密码。
此外,这条命令执行两次!!

远程登录数据库测试:
mysql -u root -p -h 192.168.1.105


com.businessobjects.mds.securedconnection.internal.StatusSecuredConnectionException: Unable to retrieve the connection from the repository. Check if the connection exists in the repository and if you have the necessary rights. (IDT 15025) (Error: INF )
解决办法:用客户端IDT工具编辑链接为新的链接。


查询以前年度报表是发生错误:
发生以下数据库错误:(CS) "DBDriver failed to load : /ourdata/sapbi/biapp/sap_bobj/enterprise_xi40/dataAccess/connectionServer/drivers/lib64/libdbd_wmssql.so (libodbc.so: cannot open shared object file: No such file or directory)" 。有关此错误的信息,请参阅 SAP 支持门户中的 SAP 知识库文章 2054721。(IES 10901) (Error: INF )

原因:系统迁移之后对应的IDT连接没有更新。
方法:更新对应的IDT连接即可。

通过这个错误,我们知道BI和其他数据库的连接引擎在
/ourdata/sapbi/biapp/sap_bobj/enterprise_xi40/dataAccess/connectionServer/drivers/下面下面的java文件夹下的jar包应该是jdbc连接方式的jar包,lib64下的so包应该是odbc方式下的宝宝。


centos 下mysql的odbc连接配置(感谢原作者):Centos下安装并配置ODBC连接MySQL


错误:对不起,升级管理应用程序无法处理您的请求。
服务器中的错误为: Unable to retrieve the root LCM folder. Please check if you have sufficient rights to perform promotion management.

分析:服务器一直在使用,没有做过什么过分的操作,突然之间就这样了。

yahoo搜索了一下:
https://archive.sap.com/discussions/thread/3509399
https://launchpad.support.sap.com/#/notes/0002067506

In the CMC in folders you should have "All Folders" - this folder should map to "Public Folders" in the BILaunchpad.
SAP BI 4.2笔记(基于linux)

As you can see in both my screenshots, you should have a folder called LCM and in there a folder called Promotion Jobs.
The LCM folder should NOT be deletable, but we\'ve seen occasions where that does happen and also, if moved into another sub-folder, this can cause problems.
Recreating the LCM folder and subfolder is NOT going to fix the issue since you need them to have a specific CUID.
I don\'t know how to fix this off the top of my head - so please open a support incident and we\'ll gladly help you get this fixed. (If note 1916832 isn\'t the right one to fix this issue.)

根据网友的说法,是因为移动、删除或者重名了了文件夹目录下的LCM文件夹,我好像真的这个干过,BI安装完之后不是在根目录下生成几个文件夹嘛,我觉得目录有点乱就新建了一个文件夹、把这几个文件夹拖到下面去了!!

那么,解决方法就简单了,再把这些个文件夹放回根目录吧,为了不引起其他问题!!
我当时为了美观就新建了个文件夹把这些默认的问价移动到里面,现在再移动回根目录!
SAP BI 4.2笔记(基于linux)


svn端口  3690



配置IDT链接:
用IDT登录BI服务器,修改链接为MySQL的ODBC驱动的形式、用户和密码换为新的。
注意:是修改,不是删除原来的新建,因为有很多Universe已经在用已有的链接,如果你新建一个链接、干掉原来的,那就得一个一个去修改这些universe,非常麻烦!!!!!!

所以,修改现有IDT链接的属性即可。

然后,linux安装mysql-odbc-connector和unixODBC等包包。
yum install unixODBC unixODBC-devel libtool-ltdl libtool-ltdl-devel
yum install mysql-connector-odbc
具体的一些操作可以参考附件中的文章,感谢原作者!
linux下配置ODBC连接MySql
然后运行一下报表,提示驱动找不到:
发生以下数据库错误:(CS) "DBDriver failed to load : /sap_bobj/enterprise_xi40/dataAccess/connectionServer/drivers/lib64/libdbd_ux32odbc3.so (libodbc.so.1: cannot open shared object file: No such file or directory)" 。有关此错误的信息,请参阅 SAP 支持门户中的 SAP 知识库文章 2054721。(IES 10901) (Error: INF )


那么,我们find一下libdbd_ux32odbc3.so
find / -name libdbd_ux32odbc3.so
显示该文件在/sap_bobj/enterprise_xi40/dataAccess/connectionServer/drivers/lib64/libdbd_ux32odbc3.so
没问题,这个报错有点奇怪!
再看看libodbc.so
发现在三个地方都有该文件:
/usr/lib64/libodbc.so
/sap_bobj/enterprise_xi40/linux_x86/odbc/7.1.5/lib/libodbc.so
/sap_bobj/enterprise_xi40/linux_x64/odbc/7.1.5/lib/libodbc.so

那么我们赋值一份到
/sap_bobj/enterprise_xi40/dataAccess/connectionServer/drivers/lib64/下面吧
cp/sap_bobj/enterprise_xi40/linux_x64/odbc/7.1.5/lib/libodbc.so  /sap_bobj/enterprise_xi40/dataAccess/connectionServer/drivers/lib64/
cp /sap_bobj/enterprise_xi40/dataAccess/connectionServer/drivers/lib64/libodbc.so/sap_bobj/enterprise_xi40/dataAccess/connectionServer/drivers/lib64/libodbc.so.1

再刷新报表,又报错说找不到libCRicu26.so
同样的方式
find / -name libCRicu26.so
cp一份该文件到报错的目录下。

继续报错:libodbcinst.so不存在
同样的手段处理。


非root 用户用root权限执行程序的设置方法

非root 用户用root权限执行程序的设置方法:

假设需要执行的程序是 controller_test.用root用户设置步骤如下:

1, 设置所属用户与属组为  root
[root@localhost ~]# chown root.root controller_test
2,  对controller_test加入user的设置为s ,表示任何调用 controller_test程序的用户,拥有拥有者的所有权限。
[root@localhost ~]# chmod u+s controller_test

注意: 非root 用户需要对  controller_test 具有可执行权限。

注意,如果chmod u+s设置成功,则该文件背景颜色会变成红色!!非root用户运行该文件不需要理睬输出的错误信息!!


jetty9修改端口号:
编辑/ourdata/jetty/start.ini
找到
## Connector port to listen on
#jetty.http.port=8080
取消注释,修改为
jetty.http.port=50000

service jetty restart


SAP BI4.2 的linux ODBC配置文件位置

/data/sap_bobj/enterprise_xi40
两个文件:odbcinst.ini和odbc.ini
具体的配置参考:/data/sap_bobj/odbc_dd_7_1_5_sample.ini


关于SAP BI安装目录下几百GB的“PlatformSearchData”:
https://archive.sap.com/discussions/thread/3590296
https://archive.sap.com/discussions/thread/3500300

it suggested to login to CMC -> Platform Search Application and stop the indexing and click on Save and Close.

1640934 - How to safely use Platform Search Service in BI 4.0 without overloading the server?


linux下SQLSERVER ODBC配置
http://blog.csdn.net/lixiaohuiok111/article/details/7755318


523 80错误:
Hi All,

As weird as it is, the bash_profile needed to be re-sourced since since LD_LIBRARY_PATH and other important variables were empty.

After doing a source command to the bash_profile and restarting the BOBJ server, the reports successfully refreshes and the error is no more.

By the way, the database error message 523 80 which actually means:

- 523 "[DataDirect][ODBC lib]"

- 80 "Specified driver could not be loaded"

Thanks and best regards,

Ron

https://archive.sap.com/discussions/thread/3461444


发表评论

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

目前评论:7   其中:访客  7   博主  0

    • ag

      比htop更炫的top工具:
      https://github.com/MrRio/vtop

      yum install npm
      npm install -g vtop
      vtop

      • ag

        yum -y install epel-release
        yum -y install htop

        • ag

          网易centos 6最新的目录为:http://mirrors.163.com/centos/6/
          yum源设置的时候请注意.

          • ag

            https://www.slideshare.net/infovillesolutions/sap-bi-42sp02serveronsuselinux

            • ag

              https://docs.bmc.com/docs/display/public/BABSM8100/Installing+SAP+BusinessObjects+BI+4.0+or+SAP+BusinessObjects+BI+4.1

              • ag

                https://blogs.sap.com/2013/11/06/installing-sap-bi-41-sp01-on-red-hat-enterprise-linux-6x-step-by-step/

                • ag

                  SAP BI4.2需要的依赖包:
                  yum install compat-libstdc++-33-3.2.3-69.el6.i686
                  yum install compat-libstdc++-33.i686
                  yum install compat-libstdc++-33-3.x86_x64
                  yum install glibc.i686
                  yum install libstdc++.i686
                  yum install libX11-1.3-2.el6.i686