N2SVCD Configuration

The n2svcd binary is installed into /usr/share/n2svcd/bin/n2svcd and executes as an init.d process. The process starts up and runs continously.

At startup, the n2svcd binary reads its static configuration from its configuration file which defaults to /etc/n2svcd/n2svcd.xml.

The /etc/n2svcd/n2svcd.xml file defines the configuration for all of the installed Applications. Example Applications are:

Example n2svcd.xml

The following is an example /etc/n2svcd/n2svcd.xml configuration file with three Applications configured.

<?xml version="1.0" encoding="utf-8"?>
    <syslog enabled="1" ident="n2svcd"/>

    <application name="Manage" module="ManageApp">

    <application name="SIGTRAN" module="SigtranApp">
        <parameter name="opc" value="4112"/>
        <parameter name="ossn" value="10"/>
          <connection name="Loopback" type="loopback"/>
          <connection name="telco-slc01" type="sua" sg_dpc="2058">
          <route pc="4112" connection="Loopback"/>
          <route pc="2058" connection="telco-slc01"/>

    <application name="Tester" module="TesterApp">
        <parameter name="json_host" value=""/>
        <parameter name="json_port" value="9009"/>


The following top-level elements/attributes are supported.

Attribute Type Description
syslog Object Container for Syslog configuration.
See below for details.
statsd Object Container for StatsD statistics relay configuration.
See below for details.
applications Array Container for one or more Applications.
.application Object A configured Application running within the Service Daemon.
See below for details, as well as the separate per-Application class configuration on other pages.
virtuals Array Container for one or more user-defined Virtual Application translations.
.virtual Object A user-defined Virtual Application used for load-sharing or failover.
See below for more details.

For further details, see the specific N2SVCD Configuration sub-topics for each Application.

Syslog Configuration

The syslog top-level configuration Object defines the configuration for writing to the Linux Syslog. By default, Syslog writing is disabled. Only messages of level NOTICE, WARNING and ERROR will ever be written to the Syslog. DEBUG, DUMP and SPAM is never written to the Syslog.

The syslog configuration object supports the following attributes:

Attribute Type Description
enabled Integer Set this to 1 to enable writing to the Linux Syslog, 0 to disable.
(Default = 0, do not write to the Linux Syslog).
ident String The application Ident value written to every Syslog record.
(Default = Main Program name, typically n2svcd).
pid Integer Specify 1 to include PID in Syslog records, 0 to exclude PID.
(Default = 1, include PID in Syslog records).

STATSD Configuration

The statsd top-level configuration Object is used to define a destination for the delivery of statistics counters. By default, statistics counter values are only stored in memory and will be lost when n2svcd is restarted. If you wish to maintain a permanent record of statistics counters then you must set up a STATSD server and configure it here.

The statsd configuration object supports the following attributes:

Attribute Type Description
host String IPv4 Host Name or A.B.C.D IPv4 Address for UDP StatsD host.
(Default = Do not notify statistics to an external agent).
port Integer Port number for UDP StatsD daemon.
(Default = 8125).
prefix String Common prefix for UDP StatsD notifications.
The generating Application Name will also form part of the statistics counter name.
(Default = n2svcd.).

Application Configuration

The applications.application configuration object is used to define Real Applications. These Real Applications perform all of the work within n2svcd.

Each application object has its own class-specific configuration structure which is described in the separate, dedicated configuration page for that Application. However, there are some common attributes for each Application, as described here.

Attribute Type Description
name String [Required] A unique name for this application instance.
module String [Required] Value defines which Application class will be loaded.
include Array Array of library class paths to pre-load when instantiating the Application class.
.lib String [Required] Relative or Absolute directory path in which the Application class is found.
parameters Array Array of parameter configuration to configure the Application.
.parameter Object A parameter to be passed to the Application at configuration time.
.name String [Required] Name of the Application parameter.
See per-Application class documentation.
.value String The parameter configuration value which will be passed to all Application instances, unless overridded using a per-instance value-<idx> override.
.value-<idx> String A parameter value specific to a single instance of a repeated Application.
The first application override value key is value-1.
See notes below concerning Repeated Applications.
repeat Integer Number of instances of this Application to construct.
(Default = 1).

Repeating Real Applications

The repeat attribute is a mechanism by which load-sharing can be easily configured when running n2svcd in multi-process mode on suitable hardware.

An application configured with repeat will result in the creation of multiple Real Application instances, each with a name formed by appending :1, :2, etc. onto the given name. The given name will then be instantiated as a Virtual Application which maps to all of the multiple Real Applications.

e.g. When configured with name = Scripter and repeat = 2 then the following will be created:

To configure separate parameters.parameter values for different repeated application instances, use the value-<idx> syntax.

The following example configuration creates three instances of RealApp1 with port numbers 4601, 4602, 4603 respectively.

    <application name="RealApp1" repeat="3">
        <parameter name="PortNumber" value="4601">

Note that if n2svcd is running in the default single-process mode then there will be no performance gain by creating multiple Application instances.

Applications which need exclusive access to a single resource (such as a single local server port number) are not obvious candidates for multiple instances.

Virtual Application Configuration

Virtual Applications are the mechanism by which one Application Name can translate at run-time into multiple Real Application instances. This offers a mechanism for load-sharing and redundancy.

As described above, the repeat attribute on the application configuration object is the simplest way to construct a Virtual Application for load-sharing across two identical instances. The parameter per-instance value override mechanism should support most common configuration cases.

However, if that configuration mechanism does not provide sufficient configuration flexibility for your purposes (or if you wish to make the Virtual Application mechanism more explicit) then you may manually configure explicit Virtual Applications using the virtuals configuration Array.

    <virtual name="VirtualApp">
        <application name="RealApp1" promoted="1"/>
        <application name="RealApp2" promoted="0"/>

    <application name="RealApp1">

    <application name="RealApp2">

Each virtual configuration Object supports the following attributes:

Attribute Type Description
name String [Required] Name for your Virtual Application. Must not conflict with any other defined Real or Virtual Application name.
applications Array Array of Real Applications.
.application Object Entry for a Real Application translation for the Virtual Application.
.name String [Required] Name of the Real Application. Must be a configured Application name.
.standby Integer Set this to 1 to indicate that this Application is consided a Standby within the configured applications. This means that even when the Application reports itself with Status higher than STATUS_STANDBY, the maximum Status used when translating a Virtual Application Handle will be STATUS_STANDBY.
.promoted Non-Negative Integer Setting this to value greater than 0 indicates that this Application should always be promoted when translating a Virtual Application Handle across two Applications which otherwise have the same current Status.
(Default = 0).

Handle Translation and Application Status

Both the "Repeated Real Applications" and "Virtual Application Configuration" provide a mechanism by which a single Application Handle is created, which at run-time is translated to exactly one Real Application (for the purpose of load-sharing and/or failover).

The key attribute for translating an Application Handle into a Real Application is the Availability Status of the available Real Applications, which is as follows:

Each Application implements its own logic to determine and update its status in real-time.

When translating a Handle into a Real Application, the following logic is used:

  1. The Application with the highest current Application Status is always used.
  2. Any Application marked standby has is capped at STATUS_STANDBY for this tranlation.
  3. Any Application marked fallback has is capped at STATUS_FALLBACK for this tranlation.
  4. For Applications with the same Status, the highest promoted Application is always used.
  5. For Applications with the same Status and promoted value, Round-Robin is performed.

Note that the "Repeated Real Applications" convenience mechanism does not support the configuration of standby, fallback or promoted attributes. These are only available through the "Virtual Application Configuration" mechanism.

Note that when using standby or fallback flags with Virtual Application translation, the web-based ManageApp will show the full working status of the Real Application (e.g. STATUS_AVAILABLE, STATUS_BUSY) and not the "capped" status that a Virtual Applicaiton translation may decide to apply.