To configure EnduroX you have to finish several steps.

In this chapter will be descirbed typical GNU/Linux system configuration required for EnduroX. Server Posix queue paramters must be set-up:

Typical configuration would look like (normally you can put this in /etc/rc.local):

# Mount the /dev/mqueue
mkdir /dev/mqueue
mount -t mqueue none /dev/mqueue
echo 32000 > /proc/sys/fs/mqueue/msg_max
echo 10000 > /proc/sys/fs/mqueue/msgsize_max
echo 10000 > /proc/sys/fs/mqueue/queues_max

Which means:

See [MQ_OVERVIEW] for more details about Posix queues on GNU/Linux.

Also do not remember to update EnduroX environment variables to reflect these settings. Variabales like:

See [EX_ENV] for more configuration flags.

Update also should be done to system security configuration. I.e. update to /etc/security/limits.conf is required, following lines must be added:

*               soft    msgqueue        -1
*               hard    msgqueue        -1

EnduroX depends lot of Environment variables. See manpage of ex_env ([EX_ENV]) to see all paramters that must be setup. There is also sample configuration provided. Normally it is expected that seperate shell script file is setup containing all paramters. Then to load the environment, login with EnduroX user in, and run following command in your app dir, for example:

$ cd /endurox/app/conf
$ . setapp

Vital part of EnduroX is ndrxdconfig.xml config. Full path to it is configured in NDRX_CONFIG environment variable. To see how to setup see manpage of it [NDRXCONFIG].

Environment variable NDRX_DEBUG_CONF contains full path to debug file. See [DEBUGCONF] for more details about debug.conf setup.

To start the EnduroX application, login with EnduroX instance user, and issue following command xadmin start, for example:

$ xadmin start -y
ndrxd PID (from PID file): 25037
exec tpevsrv -k 0myWI5nu -i 14 -e /tmp/TPEVSRV -r --  :
        process id=26793 ... Started.
exec tpbridge -k 0myWI5nu -i 101 -e /tmp/BRIDGE002 -r -- -n2 -r -i 0.0.0.0 -p 4433 -tP -z30 :
        process id=26794 ... Started.
exec tpbridge -k 0myWI5nu -i 102 -e /tmp/BRIDGE012 -r -- -n12 -r -i 10.10.10.2 -p 14433 -tA -z30 :
        process id=26795 ... Started.
Startup finished. 3 processes started.

To see all commands available by xadmin (xa) see manpage of it [XADMIN].

EnduroX is capable to continue with out restart in case if ndrxd local ATMI monitor is crashed or contains invalid data structures for some reason. In this case administrator can do following:

To setup cluster see you have to setup bridge ATMI processes on each of the machines. See [TPBRIDGE] documentation to have understanding of clustering. Sample setup of cluster node which activetly connects to Node 2 and waits call from Node 12 could look like:

<?xml version="1.0" ?>
<endurox>
        <appconfig>
                <sanity>10</sanity>
                <brrefresh>6</brrefresh>
                <restart_min>1</restart_min>
                <restart_step>1</restart_step>
                <restart_max>5</restart_max>
                <restart_to_check>20</restart_to_check>
        </appconfig>
        <defaults>
                <min>1</min>
                <max>2</max>
                <autokill>1</autokill>
                <respawn>1<respawn>
                <start_max>2</start_max>
                <pingtime>1</pingtime>
                <ping_max>4</ping_max>
                <end_max>3</end_max>
                <killtime>1</killtime>
        </defaults>
        <servers>
                <!-- Connect to cluster node 2, we will wait for call -->
                <server name="tpbridge">
                        <max>1</max>
                        <srvid>101</srvid>
                        <sysopt>-e /tmp/BRIDGE002 -r</sysopt>
                        <appopt>-n2 -r -i 0.0.0.0 -p 4433 -tP -z30</appopt>
                </server>
                <!-- Connect to cluster node 12, we try to connect activetly to it -->
                <server name="tpbridge">
                        <max>1</max>
                        <srvid>102</srvid>
                        <sysopt>-e /tmp/BRIDGE012 -r</sysopt>
                        <appopt>-n12 -r -i 195.122.24.13 -p 14433 -tA -z30</appopt>
                </server>
        </servers>
</endurox>