Operating systems have service management subsystems that support starting and stopping services when the host operating system
is booted and shut down. StreamBase supports the Linux service management subsystem using
This page assumes familiarity with
systemd concepts and general architecture; sudo access is required to install new services.
systemd unit file is shipped in
<product-installation-location>/distrib/tibco/dtm/services/linux/tibco-ep.service. This file defines a service named
tibco-ep that can manage a single node. Multiple nodes can also be started on a single machine by installing multiple copies of the shipped unit file, each with
a different name.
systemd file as follows. These instructions install the service with the default name and configure a service to manage a single
Install into the required
systemddirectory using the default service name. Run this command in one line; the example below wraps to the next line for clarity:
sudo cp <product-installation-location>/distrib/tibco/dtm/services/ linux/tibco-ep.service /usr/lib/systemd/system
Do not use a symbolic link to install the file;
systemddoes not fully support symbolic links.
systemdmanager configuration to detect the newly installed service.
sudo systemctl daemon-reload
Enable the service so Linux can automatically manage it.
sudo systemctl enable tibco-ep
Manually start the service.
sudo systemctl start tibco-ep
Multiple nodes can be installed on the same machine by installing multiple copies of the unit file with different names. Run
the following to install another service named
my-application on the same machine:
sudo cp <product-installation-location>/distrib/tibco/dtm/services/linux/ tibco-ep.service /usr/lib/systemd/system/my-application.service sudo systemctl daemon-reload sudo systemctl enable my-application sudo systemctl start my-application
systemd file supports configuration using the
systemd environment configuration variables. You can change these configuration values directly in the
systemd file after it is installed.
||Java installation.||Yes. Default value is
||Absolute path to application archive to install on node.||No. Node will be installed without an application.|
||Absolute path to product installation.||Yes. Default value is
||Node name.||Yes. Default value is
||Absolute path to node deploy configuration to configure node during installation.||No. Node will be installed using default configuration.|
||Absolute path to the run directory where nodes will be installed.||Yes. Default value is
||Absolute path to substitution variable file.||No. No substitution variables will be specified during node install.|
In addition to these supported configuration variables, you can specify standard
systemd configuration values in unit file overrides using
systemctl edit. See the
systemd documentation for complete details on the unit file supported configuration variables.
The shipped unit file has these behaviors for managing services using
start — install node if not installed and start the node.
stop — stop and quiesce the node.
reload — not supported. Use standard node configuration mechanisms to change node configuration.
The Restart=on-failure configuration is enabled. When a node fails, it is automatically restarted after taking these actions:
Creating a snapshot of the failed node.
Removing the node.
Re-installing the node.
All user data stored in a failed node is lost. TIBCO recommends replicating your data to another node as needed.
Use these steps to completely remove an installed service. These steps use the default shipped service name,
Stop the service.
sudo systemctl stop tibco-ep
Remove the service from management by the operating system.
sudo systemctl disable tibco-ep
sudo rm /usr/lib/systemd/system/tibco-ep.service
Remove any configuration overrides.
sudo rm -rf /etc/systemd/system/tibco-ep.service.d
systemdmanager to update its configuration.
sudo systemctl daemon-reload
Reset all failed messages.
sudo systemctl reset-failed