TPM Agent startup/shutdown

TPM Agent Environment Configuration

After completing the application.yml file settings, configure the TPM Agent environment in the following order.

1.1. Set the maximum size of the core dump file

ulimit -c unlimited

1.2. Set TPM Agent environment variables

. set.sh

set.sh script content

export TPMAGENT_HOME={TPM_Agent_Home_Path}
export PATH=$TPMAGENT_HOME:$PATH
export LD_LIBRARY_PATH=$TPMAGENT_HOME:$LD_LIBRARY_PATH
export BOOT_WITH_AUTO_DOWN_CLEAN=true
export ENABLE_DEBUG=false
export ENABLE_GC_LOG=false
export JAVA_MIN_HEAP_SIZE=300m
export JAVA_MAX_HEAP_SIZE=300m

Note

The above script is a template that provides the basic settings for the binary execution PATH, TPM Agent library path LD_LIBRARY_PATH, and environment variables. The users can modify the script directly according to the usersr environment and then run the TPM Agent.

Arguments	Description
{TPM_Agent_Home_Path}	Directory path where the compressed file "java_tpmagent_dist_{version}.tar.gz" is extracted.

1.3. Tibero environment variable settings

export TB_HOME={Monitoring_DB_Path}
export TB_SID={Monitoring_DB_SID}
export LD_LIBRARY_PATH=$TB_HOME/lib:$TB_HOME/client/lib
export PATH=$PATH:$TB_HOME/bin:$TB_HOME/client/bin

Arguments	Description
{Monitoring_DB_Path}	Enter the path to the monitoring database
{Monitoring_DB_SID}	Enter the SID of the monitoring database

---

Start, stop, and other commands

The tpmctl.sh command is as follows, and the users can check the usage in the terminal with the help command.

Command	Description
./tpmctl.sh [-p port] up	Starts the TPM Agent. The -p option allows the users to specify JVM debug ports. By default, it searches for available ports, but if no available ports are found in the current environment, the users can manually specify a port using this option.
./tpmctl.sh down	Stop the TPM Agent
./tpmctl.sh help	Display TPM Agent help
./tpmctl.sh version	TPM Agent version output
./tpmctl.sh libversion	Output the list of build patches for the TPM Stat library used by the TPM Agent and the list of patches for Tibero.

---

libJNITpmStat.so library

This library is required for Java TPM Agent to use libtpmstat.so.

Note

tpSince it must be used with tpmagent.jar, extract the distributed compressed file, copy the libJNITpmStat.so file corresponding to the OS version the users want to run to the same directory as tpmagent.jar under the lib directory.

Caution

If the version of the libtpmstat.so library used by the libJNITpmStat.so file does not match the current Tibero binary version, errors such as SIGSEGV will occur, and the process will not run. The types of error-related files generated vary by JVM vendor, but files such as core, jitdump, and javacore may be created. Therefore, the users must verify the version of the libtpmstat.so library when these files are generated.

---

Important notes when rebooting Tibero

After Tibero Down, TPM Agent Down is required to immediately perform Tibero Boot. This is because the Tibero Shared Memory referenced by TPM Agent must be released.

Caution

To release the Tibero Shared Memory referenced by the TPM Agent, Tibero Down must be detected, and the detection interval is the same as the data collection interval. Therefore, if the data collection interval is set to a long duration or the TPM Agent itself becomes slow, the detection of Tibero Down may be delayed, resulting in a delay in the timing when Tibero Down can be performed and Tibero Boot can be initiated.

To prevent the delay in detecting Tibero Down and the subsequent delay in the time when Tibero Boot becomes possible, perform TPM Agent Down and then Tibero Boot.