Using systemd to Manage a TimesTen Service

3 Using systemd to Manage a TimesTen Service

Traditionally Linux systems used the System V init mechanism to coordinate system startup operations. More recently, Linux has moved to a new method based on the systemd daemon and its associated infrastructure. Although systemd is currently the standard for system startup coordination and for service management on Linux, the System V init mechanism is still supported.

It has always been possible to set a TimesTen instance's main daemon to start automatically on system startup. This is achieved by installing suitable System V init startup scripts. TimesTen provides the setuproot utility script for this purpose. On systems that support systemd, as an alternative to using the System V init mechanism, it is possible to configure a TimesTen instance's main daemon to run as a system service.

See "About Creating an Instance on Linux/UNIX" for the choices you can make if your Linux system supports both the System V init mechanism and systemd.

Note:

You can only use systemd in TimesTen Classic.

The chapter provides an overview of how systemd can be used for automatic management of the TimesTen daemon. It explains the importance of the systemd service unit configuration file as a mechanism for setting operating system limits for the TimesTen environment. The chapter details the process for creating and modifying an instance for automatic systemd management. It concludes with examples illustrating how to create and modify an instance for automatic systemd management.

See the Oracle TimesTen In-Memory Database Release Notes for information on the TimesTen Linux platforms that support systemd.

Topics: