This section explains the tasks required before installing BDCEP.
Configure the /etc/hosts file so that network name resolution is enabled for the CEP Server host name (*1). Note the following when registering the host name:
When registering the CEP Server host name as "127.0.0.1" (CEP Server loopback address), always first describe the IP address setting used when gaining access from outside the CEP Server.
Alternatively, do not set the host name of the CEP Server for "127.0.0.1".
*1: The HOSTNAME parameter setting in the /etc/sysconfig/network file.
Example
Example of setting /etc/hosts
Below is an example of setting the host name "cepsv1" for "127.0.0.1". In this example, the IP address setting used when gaining access from outside the CEP Server is "10.10.10.10".
10.10.10.10 cepsv1
127.0.0.1 cepsv1 localhost.localdomain localhost
Check that the port numbers to be used by BDCEP are available for use. The port numbers used by BDCEP are shown below. Use firewall or operating system settings to ensure the relevant port can be used.
Port number | Description |
|---|---|
80 | Port number used by the input adapter (SOAP adapter or HTTP adapter) to receive input events. |
81 | Port number used internally by BDCEP. |
102 | |
389 | |
636 | |
2000 | |
2465 | |
3279 | |
4433 | |
5432 | |
6666 | |
8002 | |
8009 | |
8080 | |
8686 | |
8909 | |
8919 | |
9700 | |
10550 | |
10555 | |
12000 | |
12001 | |
12200 | |
12210 | |
12220 | |
12230 | |
13000 | |
23600-23602 | |
23700-23710 | |
28080 | |
28090-28100 | |
28686-28696 | |
anyPort | Port number used by the input adapter known as the socket adapter to receive input events. Use this by setting one unused port number between 5001 and 32767 for each CEP engine, and by setting a maximum of five for the entire CEP Server. Setting the port numbers to be used is done in CEP engine setup after installation. Port number 9600 is set in the CEP engine created at initial setup. |
Check that the disks have sufficient free capacity. Refer to "4.2.3 Resources Required at Installation" for information on the required disk capacity.
If there is a shortage of free disk capacity, extend the size.
Create a specific user and group to execute the CEP engine. Each of the processes of the CEP engine run with the user and group permissions created here.
Example
Operation example of creating the engine execution user and group using the user name "isbdcep" and the group name "isbdcep"
$ su - <ENTER>
# /usr/sbin/groupadd isbdcep<ENTER>
# /usr/sbin/useradd -g isbdcep isbdcep<ENTER>
Note
The user creation method depends upon the management policy of the system. Always check with the system administrator.
Up to 8 characters can be specified for the user name and the group name.
Kernel parameters must be tuned in advance when operating BDCEP.
Edit /etc/sysctl.conf to change the values of the target kernel parameters to suitable values, according to the parameter "type".
If the type is "Maximum":
If the value already set (initial value or previously set value) is greater than the value shown in the table, it need not be changed. If it is smaller than the value in the table, change it to the value in the table.
If the type is "Additional"
Add the value shown in the table to the value that is already set (initial value or previously set value). Check the system maximum values before adding this value and, if adding that value would exceed the system maximum value, set the system maximum value.
The current kernel parameters can be verified using "/sbin/sysctl -a".
After making the changes, execute "/sbin/sysctl -p /etc/sysctl.conf" or reboot the OS.
Refer to the documentation for the operating system for information on how to change the kernel parameters.
Below are the kernel parameters to be set.
Shared memory
Parameter | Description | Value to be set | Type |
|---|---|---|---|
kernel.shmmax | Maximum size in shared memory | 57413492 | Maximum |
kernel.shmmni | Maximum number of shared memory segments | 41 | Additional |
Semaphore
For semaphore settings, set the values for each parameter in the following format:
kernel.sem = SEMMSL SEMMNS SEMOPM SEMMNI
Parameter | Description | Value to be set | Type |
|---|---|---|---|
SEMMSL | Maximum number of semaphores for each semaphore identifier | 512 | Maximum |
SEMMNS | Number of semaphores for the system as a whole | 5763 | Additional |
SEMOPM | Maximum number of operators for each semaphore call | 50 | Maximum |
SEMMNI | Number of semaphore operators for the system as a whole | 1143 | Additional |
Message queue
Parameter | Description | Value to be set | Type |
|---|---|---|---|
kernel.msgmax | Maximum message size | 16384 | Maximum |
kernel.msgmnb | Maximum number of bytes of messages in the message queue | 32768 | Maximum |
kernel.msgmni | Maximum number of message queue IDs | 526 | Additional |
When operating BDCEP, adjust the user limitations for the number of processes (threads) that can be executed.
Edit "/etc/security/limits.conf" and change the number of processes (threads) that the user can execute to an appropriate value.
For BDCEP, set the number of processes (threads) the engine execution user can execute to "2048" or higher. Add "2048" to the already specified value (the initial or previously specified value).
The number of processes (threads) that the engine execution user can execute can be checked with the following command as a superuser.
# /bin/su -c 'ulimit -u' engineExecutionUser <ENTER>
Reboot the OS after changing the value.
Refer to the OS manual for information on how to change the value.
Example
Example for setting /etc/security/limits.conf
This is an example for specifying the number of processes (threads) an engine execution user can execute. In this example, the value is set by adding "2048" to the default value of "1024".
isbdcep soft nproc 3072The following shared memory file is generated while BDCEP is running (XXX is the user name, YYY is the process ID):
/tmp/hsperfdata_XXX/YYY
If the tmpwatch shell script is registered in cron, the shared memory file is deleted by the tmpwatch shell script. This may cause problems during product operations.
To avoid this, modify the /etc/cron.daily/tmpwatch shell script so that shared memory files are not the targets of deletion by tmpwatch.
Example
Example of modified /etc/cron.daily/tmpwatch shell script
Precede the '/usr/sbin/tmpwatch XXX /tmp' line with the lines in the example below (XXX is in hours):
for f in `echo /tmp/hsperfdata_*/*` ; do
/bin/touch $f > /dev/null 2>&1
done
If the FJSVsmee64 and FJSVsclr64 packages were installed using a Fujitsu product other than BDCEP (such as Systemwalker Centric Manager), perform the following procedure:
Check the installation of the FJSVsmee64 and FJSVsclr64 packages.
Check if the FJSVsmee64 and FJSVsclr64 packages have been installed. If so, check the version of each package using the following commands:
# rpm -q -i FJSVsmee64 | grep Version <ENTER>
# rpm -q -i FJSVsclr64 | grep Version <ENTER>
If the packages have been installed, the version information will be displayed. If nothing is displayed, the packages have not been installed, so the following steps are not required. Skip to "4.3.2 Installation Procedure".
Note
If the installed version is more recent than the version provided by BDCEP, you must perform the procedure explained in "4.3.3.2 Reinstalling FJSVsmee64 and FJSVsclr64 Packages" after installing BDCEP.
Information
The versions of FJSVsmee64 and FJSVsclr64 bundled with this version of BDCEP are as follows:
FJSVsmee64 4.1.2
FJSVsclr64 2.0.7
Stop all Fujitsu products. Refer to the manual provided with each product for information on how to stop the product.
Uninstall the FJSVsmee64 and FJSVsclr64 packages.
# rpm -e FJSVsmee64 <ENTER>
# rpm -e FJSVsclr64 <ENTER>