Sterling B2B Integrator与SAP交互 - 02 安装配置

系统组成：

1. 服务器OS及硬件：

　　OS: Red Hat Enterprise Linux Server release 6.6

　　Hardware: Virtual Machine, x86_64，2 core, 8GB RAM, 100GB HDD

2. 软件：

　　Java JDK 1.7.0 update 26

　　IBM DB2 Database V9.7

　　Sterling B2B Integrator 5.2.4

　　继续装插件

　　SAP Suite Adapter for JCo 3.x - 连接SAP系统

　　Oracle Database 11g Release 2 JDBC Drivers - 连接Oracle

3. 修改OS系统参数

修改参数 - 在Linux系统用户可打开文件的最大数

[root@sterling ~]# vi /etc/security/limits.conf
#*               soft    core
#*               hard    rss
#@student        hard    nproc
#@faculty        soft    nproc
#@faculty        hard    nproc
#ftp             hard    nproc
#@student        -       maxlogins       

 * hard nofile
 * soft nofile
 * hard memlock
 * soft memlock
 * hard nproc
 * soft nproc
 * hard stack
 * soft stack 

# End of file

数据库参数

[sapadm02@sterling ~]$ ipcs -l

------ Shared Memory Limits --------
max number of segments =
max seg size (kbytes) =
max total shared memory (kbytes) =
min seg size (bytes) = 

------ Semaphore Limits --------
max number of arrays =
max semaphores per array =
max semaphores system wide =
max ops per semop call =
semaphore max value = 

------ Messages: Limits --------
max queues system wide =
max size of message (bytes) =
default max size of queue (bytes) = 

内核参数

[sapadm02@sterling ~]$ cat /etc/sysctl.conf
# Kernel sysctl configuration file for Red Hat Linux
#
# For binary values,  is disabled,  is enabled.  See sysctl() and
# sysctl.conf() for more details.

# Controls IP packet forwarding
net.ipv4.ip_forward = 

# Controls source route verification
net.ipv4.conf.default.rp_filter = 

# Do not accept source routing
net.ipv4.conf.default.accept_source_route = 

# Controls the System Request debugging functionality of the kernel
kernel.sysrq = 

# Controls whether core dumps will append the PID to the core filename.
# Useful for debugging multi-threaded applications.
kernel.core_uses_pid = 

# Controls the use of TCP syncookies
net.ipv4.tcp_syncookies = 

# Disable netfilter on bridges.
net.bridge.bridge-nf-call-ip6tables =
net.bridge.bridge-nf-call-iptables =
net.bridge.bridge-nf-call-arptables = 

# Controls the default maxmimum size of a mesage queue
kernel.msgmnb = 

# Controls the maximum size of a message, in bytes
kernel.msgmax = 

# Controls the maximum shared segment size, in bytes
kernel.shmmax = 

# Controls the maximum number of shared memory segments, in pages
kernel.shmall =
kernel.shmall =
kernel.shmmni =
kernel.shmmax =
kernel.sem =
kernel.msgmni =
kernel.msgmax =
kernel.msgmnb = 

默认内核参数对照表

Oracle驱动参数 - 设置数据库连接

[sapadm02@sterling ~]$ cat /opt/app/gis/install/properties/jdbc_customer.properties.in
## PROPERTY_FILE_NAME
## jdbc_customer.properties.in (for initialization)
## jdbc_customer.properties (for operations)

## PROPERTY_FILE_DESCRIPTION
## The jdbc_customer.properties file has the same settings as the jdbc.properties file. This allows
## you to separate your customized database pool information (in jdbc_customer.properties) from the
## pool information provided by Application (in jdbc.properties). This arrangement
## has the following benefits:
## * During an upgrade, you can copy your jdbc_customer.properties.in file instead of cutting
##   and pasting your changes out of jdbc.properties.
## * The application can make changes to the jdbc.properties file during a patch (if
##   necessary) without changing a database pool that you added.
## For information about the properties in the jdbc_customer.properties file, refer to
## the documentation for the jdbc.properties file.

## DATABASE_SUPPORT: N

## Adding Database Pools
## You can use the jdbc_customer.properties file to add a new database pool to the application
## environment.  You can add this pool without having to restart the application, which lets
## you continue running business processes.
## To dynamically add a new database pool, do the following:
## . Create the new pool in jdbc_customer.properties.
## . Refresh the JDBC properties by doing one of the following:
##    * Click the Refresh JDBC Pools button on the JDBC Monitor page.
##    * Go the the [install_dir]/install/bin directory (UNIX/Linux) or the
##      [install_dir]\install\bin directory (Windows) and run the following command:
##      opscmd.sh/opscmd.cmd -cREFRESHJDBC -nnode1
## . Use the Database Usage page to confirm that you have added the pool.

TVCSHTestPool.driver=oracle.jdbc.OracleDriver
TVCSHTestPool.url=jdbc:oracle:thin:@192.168.72.109::TDB
TVCSHTestPool.user=IPRTVCSH_T
TVCSHTestPool.password=password
TVCSHTestPool.catalog=TDB
TVCSHTestPool.type=remote
TVCSHTestPool.testOnReserve=true
TVCSHTestPool.testOnReserveQuery=select 'x' from dual
TVCSHTestPool.testOnReserveInterval=
TVCSHTestPool.max8177RetryCount=
TVCSHTestPool.dbvendor=oracle
TVCSHTestPool.buffersize=n
TVCSHTestPool.maxsize=
TVCSHTestPool.initsize=
TVCSHTestPool.behaviour=
TVCSHTestPool.lifespan=
TVCSHTestPool.idletimeout=
TVCSHTestPool.housekeepinginterval=
TVCSHTestPool.storedProcClassName=com.sterlingcommerce.woodstock.util.frame.jdbc.OracleNoAppStoredProcQuery
TVCSHTestPool.varDataClassName=com.sterlingcommerce.woodstock.util.frame.jdbc.OracleVarData
TVCSHTestPool.factory=com.sterlingcommerce.woodstock.util.frame.jdbc.ConnectionFactory