8.2.1 Tasks that must be performed before installation
Before installing the HADB server, execute the following tasks as a superuser:
-
Check the prerequisite libraries and user commands#
-
Set up an HADB administrators group.
-
Set up the HADB administrator.
-
Set up an OS user who belongs to the HADB administrators group.
-
Create a directory for storing the server directory.
-
Change the settings of the directory for storing the server directory.
-
Create the directories for storing communication-information files.
-
Modify the access privileges to syslog.
- #
-
This can be performed by a general user (an OS user without administrator privileges) instead of a superuser.
- Organization of this subsection
(1) Checking the prerequisite libraries and user commands
Make sure that the libraries and user commands necessary for the HADB server to operate correctly are installed in the OS.
- ▪ Check method
-
Execute the OS's yum command to check the packages installed in the OS. The following shows the command to be executed.
yum list installed
After checking the execution results of the preceding command, if all the packages listed in the following two tables are installed, the necessary libraries and user commands have been installed in the OS.
Table 8‒1: List of packages to check (checking the prerequisite libraries) No.
Package name and version to check
Prerequisite library for the HADB server included in the package
1
glibc (2.12 or later)
libc.so.6
2
librt.so.1
3
libm.so.6
4
libpthread.so.0
5
ld-linux-x86-64.so.2 (loader for execution)
6
libdl.so.2
7
libaio (0.3.107 or later)
libaio.so.1
8
openssl (1.0.0 or later)
libcrypto.so.10
9
zlib (1.2.3 or later)
libz.so.1
10
libuuid (2.17.2 or later)
libuuid.so.1
11
None
linux-vdso.so.1#
- #
-
Because this library is a virtual shared library provided by kernels, you do not need to check whether the package exists.
Table 8‒2: List of packages to check (checking the prerequisite user commands) No.
Package name and version to check
User commands prerequisite for the HADB server contained in packages
1
gdb (7.2 or later)
gcore
2
gstack
If any package is not installed, install it in the OS. For details about how to install packages, see the OS documentation. You need to install the packages as a superuser.
- Note
-
The following shows an example of executing the command to check whether a specific package has been installed.
- Example
-
Check whether package libaio has been installed.
yum list installed | grep libaio
If package libaio is displayed in the execution result, package libaio has been installed. If package libaio is not displayed in the execution result, package libaio has not been installed.
(2) Setting up an HADB administrators group
Set up an HADB-only group (HADB administrators group) under the server machine's OS. Use the operating system's groupadd command to set up an HADB administrators group.
By setting up an HADB administrators group, you can restrict access to the files in the directories used to run the HADB server (server directory and DB directory) so that only OS users in the HADB administrators group can access them. This enhances the level of security.
- ■ HADB administrators group setup example
-
Set up adbgroup as an HADB administrators group under the server machine's OS.
groupadd adbgroup
You can also use an existing group that has been set up under the OS as an HADB administrators group.
(3) Setting up the HADB administrator
Once you have set up an HADB administrators group, set up the OS user who will manage the HADB server (HADB administrator) under the server machine's OS. Use the operating system's useradd command to set up the HADB administrator. Use a maximum of 32 bytes for the name of the HADB administrator.
An HADB administrator is a special user who is set up in the OS. The HADB administrator has the privileges needed to execute all HADB commands, and is the owner of files in the server directory and the DB directory. The OS user who is set up as the HADB administrator will be recognized as such by the HADB server when the HADB server is installed.
When you set the user name of the HADB administrator in the OS, you can also set up an HADB administrators group in the primary group to which the HADB administrator belongs. This gives the HADB administrator owner-level access privileges to the various types of files and directories on the HADB server, and prevents other OS users from being able to overwrite data.
Once you have set up the user name of the HADB administrator in the OS, you must set up the administrator's password. Use the operating system's passwd command to set up a password.
- ■ HADB administrator setup example
-
Set up adbmanager as the HADB administrator under the server machine's OS. When you do this, also set the HADB administrators group (adbgroup) as the primary group.
useradd -g adbgroup adbmanager
(4) Setting up the OS user who belongs to the HADB administrators group
Once you have set up the HADB administrator, we recommend that you set up the OS user who will manage the HADB server (OS user who belongs to the HADB administrators group). You set up this user separately from the HADB administrator under the server machine's OS.
The OS user who belongs to the HADB administrators group is given the privileges needed to execute HADB commands (excluding some commands). This OS user can also access the files in the server directory and the DB directory owned by the HADB administrator. Setting up the OS user who belongs to the HADB administrators group allows an OS user other than the HADB administrator to execute HADB commands, making HADB server operations more convenient.
Use the operating system's useradd command to set up the OS user who belongs to the HADB administrators group. Use a maximum of 32 bytes for the name of this OS user. Also, when you set up this user's user name under the OS, set the HADB administrators group as the primary group.
Once you have set up the user name of the OS user who belongs to the HADB administrators group under the OS, you must set a password. To do so, use the operating system's passwd command.
- ■ Example of setting an OS user who belongs to the HADB administrators group
-
Set up adbgroupuser01 as the OS user who belongs to the HADB administrators group under the server machine's OS. When you do so, also set the HADB administrators group (adbgroup) as the primary group.
useradd -g adbgroup adbgroupuser01
- Note
-
For details about the HADB commands that an OS user who belongs to the HADB administrators group can execute, see List of commands under List of Commands and Common Rules in the manual HADB Command Reference.
(5) Creating a directory for storing the server directory
Create a directory for storing the server directory, which is required to install the HADB server, as a superuser. Use the mkdir OS command to create a directory for storing the server directory.
Specify /HADB as the path name of the directory for storing the server directory.
- ■ Example of creating a directory for storing the server directory
-
The following shows how to create /HADB as a directory for storing the server directory.
mkdir /HADB
(6) Changing the settings of the directory for storing the server directory
After creating a directory for storing the server directory (/HADB), make the following changes to the settings as a superuser:
-
Changing the owner and group of the directory for storing the server directory (/HADB)
Change the owner of the directory to the HADB administrator (adbmanager). Also, change the group of the directory to the HADB administrators group (adbgroup). To change the owner and group of the directory, use the chown OS command.
-
Assigning write permission to the directory for storing the server directory (/HADB)
Assign write permission to the directory so that the HADB administrator (adbmanager) can write data to the directory. To assign write permission to the directory, use the chmod OS command.
- ■ Example of changing the settings of the directory for storing the server directory
-
The following shows how to change the owner and group of the directory for storing the server directory (/HADB) and assign write permission to the directory.
chown adbmanager:adbgroup /HADB chmod 755 /HADB
(7) Creating the directories for storing communication-information files
Create the directories for storing communication-information files needed to operate the HADB server. Use the operating system's mkdir command to create these directories.
The directories for storing communication-information files vary depending on the version of the OS of the server machine on which the HADB server is installed.
-
If the server machine's OS is Red Hat Enterprise Linux Server 6 (64-bit x86_64)
-
If the server machine's OS is Red Hat Enterprise Linux Server 7 (64-bit x86_64)
(a) Red Hat Enterprise Linux Server 6
The following table shows the path names of the directories for storing communication-information files and the access privileges that are assigned.
|
No. |
Path name of the directory to be created |
Owner |
Access privilege |
|---|---|---|---|
|
1 |
/dev/HADB/pth |
Superuser |
777 |
|
2 |
/lib/udev/devices/HADB/pth |
- ▪ Example of creating the directories for storing communication-information files
-
Create directories (/dev/HADB/pth and /lib/udev/devices/HADB/pth) for storing communication-information files. When you do so, assign 777 as the access privilege.
mkdir -p -v -m 777 /dev/HADB/pth mkdir -p -v -m 777 /lib/udev/devices/HADB/pth
(b) Red Hat Enterprise Linux Server 7
The following table shows the path names of the directories for storing communication-information files and the access privileges that are assigned.
|
No. |
Path name of the directory to be created |
Owner |
Access privilege |
|---|---|---|---|
|
1 |
/dev/HADB/pth |
Superuser |
777 |
In addition, you must create the following settings file.
|
No. |
Settings file to be created |
Owner |
Access privilege |
|---|---|---|---|
|
1 |
/etc/tmpfiles.d/dev-HADB-pth.conf |
Superuser |
644 (default) |
The following shows the information to be entered in the settings file (dev-HADB-pth.conf).
# Type Path Mode UID GID Age Argument d /dev/HADB/pth 0777 root root - -
- ▪ Example of creating a directory for storing communication-information files
-
Create the directory (/dev/HADB/pth) for storing communication-information files. When you do so, assign 777 as the access privilege.
mkdir -p -v -m 777 /dev/HADB/pth
- ▪ Example of creating a settings file
-
Create the settings file (dev-HADB-pth.conf).
Execute the following OS command.
vi /etc/tmpfiles.d/dev-HADB-pth.conf
After executing the vi command, press the I key. Then, enter the following information.
# Type Path Mode UID GID Age Argument d /dev/HADB/pth 0777 root root - -
When you finish entering the information, press the Esc key. Then, enter the following command, and then press the Enter key.
:wq
(8) Modifying the syslog access privilege
Modify the access privilege to syslog, to which HADB server messages are output. You can use the operating system's chmod command to modify this privilege.
Modifying the access privilege to syslog allows you to acquire syslog when you use the adbinfoget command to acquire troubleshooting information.
The following table shows the default path name of syslog and the access privilege that is assigned.
|
No. |
Default path name for syslog |
Owner |
Access privilege |
|---|---|---|---|
|
1 |
/var/log/messages# |
Superuser |
604 |
- #
-
If you have changed syslog, to which HADB server messages are output, to a destination other than /var/log/messages, assign the access privilege to syslog at the modified destination.
- ■ Example of modifying the syslog access privilege
-
This example changes the syslog access privilege (/var/log/messages) to 604.
chmod 604 /var/log/messages