The backend processes are simple processes that are configured entirely using command-line arguments.
The backend processes do not provide special logging or process-management functionality themselves — they expect that their parent process will manage restarting the backend if necessary, and will capture
stderr to an appropriate logging mechanism. To help with logging, a
start-backend.sh script allows logging of backend output to a file, or (through a pipe) to a separate process.
You can start the backends:
The recommended way to start the backends is to configure Signalware’s process-management system to start the backend processes. The benefits of this approach are:
Signalware will automatically restart processes that fail unexpectedly.
The lifecycle of the backends is coupled with the lifecycle of Signalware as a whole, so separate backend startup/shutdown procedures are not needed.
The state of individual backends can be managed using Signalware’s process-management MML commands.
To configure a backend in this way, execute the
START-PROCESS MML commands using the Signalware MML tools (such as
CREATE-PROCESS:NAME="logical_name",CE="ce_name",UID=numeric_uid,GID=numeric_gid, EXEC="/path/to/backend/installation/start-backend.sh -logfile /path/to/logfile.txt -node ss7_node_name -lssn numeric_local_ssn -port numeric_local_port -verbose"; START-PROCESS:NAME="logical_name",CE="ce_name";
This example has been line-wrapped for readability; each command should be executed as a single line. Note that:
Once configured, the
CREATE-PROCESS command is persistent, and the backend will automatically be started whenever the Signalware instance is started.
In a multi-CE cluster, the
CREATE-PROCESS MML commands may be executed on any CE. Signalware arranges for the commands to be propagated to the correct CE for execution.
For more on the MML commands, please see the Signalware
Backends may be started manually (not using Signalware). This may be useful for manual testing, or when another tool provides process management.
In this case,
start-backend.sh may be run directly, with appropriate arguments.
Ensure restart, environment, name
The process starting the backend should: