2.3.2 Registering HiRDB and option program products in the operating system

Executor: Superuser
Organization of this subsection
(1) OS registration method
(2) Specifying character encoding
(3) Using JP1/OmniBack II (HP-UX only)
(4) Using POSIX library version

(1) OS registration method

(a) HiRDB

The superuser executes the pdsetup command to register HiRDB into the OS. The pdsetup command copies the directories and files from the installation directory to the HiRDB directory. For a HiRDB/Parallel Server, execute the pdsetup command for each server machine.

To perform registration into the OS:

  1. Execute the pdsetup command.
  2. Check the termination status.
    If the termination status of the pdsetup command is not 0, an error may have occurred. See the message output to the syslog file, eliminate the cause of the error, and then re-register HiRDB into the OS.

For details about the pdsetup command, see the manual HiRDB Version 8 Command Reference.

Notes
  • The pdsetup command is located in the bin directory under the HiRDB installation directory.
  • If you execute the pdsetup command, the Inittab directory is automatically created in the conf directory under the HiRDB installation directory. This directory is used to back up the /etc/inittab file. If the /etc/inittab file is damaged during or after the execution of the pdsetup command, use this backup file to start the operating system.
  • Once you execute the pdsetup command, do not change the owner of the HiRDB directory using the chown OS command. If you do so, HiRDB may no longer start.
(b) Option program products

To install an option program product, you use the pdopsetup command to register the option program product with the OS. In the case of a HiRDB/Parallel Server, you must execute the pdopsetup command for each server machine. However, in the case of HiRDB LDAP Option or HiRDB Disaster Recovery Light Edition, execute as follows:

For HiRDB LDAP Option
On the server machine that contains the dictionary server, execute the pdopsetup command.
For HiRDB Disaster Recovery Light Edition
For HiRDB/Single Server, execute the command on the server machines at both the business site and the log applicable site.
For HiRDB/Parallel Server, execute the command on each server at both the business site and the log applicable site.

(2) Specifying character encoding

(a) Specification at the server

Use the -c option of the pdsetup command to specify the character encoding to be used in with HiRDB. Table 2-4 lists the character encoding that can be used with HiRDB.

Table 2-4 Character encoding supported by HiRDB

Character encodingOS
HP-UXSolarisAIX 5LLinux
Shift JIS Kanji encodingD[Figure]D[Figure]
EUC Chinese Kanji encoding[Figure][Figure][Figure][Figure]
Single-byte character encoding[Figure][Figure][Figure][Figure]
EUC Japanese Kanji encoding[Figure]D[Figure]D
Unicode (UTF-8)1[Figure][Figure][Figure][Figure]
D: Default character encoding that is assumed when the -c option is omitted from the pdsetup command
[Figure]: Character encoding supported by the OS
1 The Unicode set (UTF-8) cannot be used for versions prior to HiRDB Text Search Plug-in Version 02-02. Therefore, if you are using HiRDB in conjunction with a version of HiRDB Text Search Plug-in that is prior to 02-02, do not specify utf-8 in the -c option of the pdsetup command.
(b) Specification at the client

On the client side, specify the character encoding with the LANG or PDCLTLANG operand in the client environment definition as appropriate to the server's character encoding. The client environment definition is referenced during UAP creation or execution. For the client environment variables supported based on the server's available character encoding, see the manual HiRDB Version 8 UAP Development Guide.

(3) Using JP1/OmniBack II (HP-UX only)

To use JP1/OmniBack II, specify the -p option in the pdsetup command. For operation using JP1/OmniBack II, see the manual HiRDB Version 8 System Operation Guide.

Note that JP1/OmniBack II is not supported by a 64-bit-mode HiRDB.

(4) Using POSIX library version

If you are using the POSIX library version, specify the -l option in the pdsetup command. You need the POSIX library version to use the following facilities:

For details about Java stored procedures and Java stored functions, see the manual HiRDB Version 8 UAP Development Guide. For details about the Directory Server linkage facility, see the manual HiRDB Version 8 System Operation Guide. For details about the HiRDB External Data Access facility, see the manual HiRDB External Data Access Version 7 Description and User's Guide.

The Linux version supports Java stored procedures and Java stored functions without requiring any special setup.

1 The following versions of HiRDB support Java stored procedures and Java stored functions:
  • HP-UX version (32-bit mode POSIX library version) and HP-UX (IPF version)
  • Solaris version (32-bit mode POSIX library version)
  • AIX 5L version (32-bit mode POSIX library version)
  • Linux version (32-bit mode) and Linux version (EM64T)
2 The table below shows the OSs that support the Directory Server linkage facility. Note that HiRDB must be in the 32-bit mode.
  • HP-UX
  • Solaris 8
  • AIX 5L
3 The following operation systems can use the HiRDB External Data Access facility. This is the HiRDB/Parallel Server limited facility.
  • HP-UX (32-bit mode POSIX library version)
  • Solaris (32-bit mode POSIX library version)
  • AIX 5L (32-bit mode POSIX library version)
  • Linux (32-bit mode)