DESCRIPTION

ndrxconfig.xml holds the application domain configuration. It describes the ATMI servers that need to be started. Counts of the, how much to start. Also, it describes sanity times i.e. period after which system sanity checks should be made. Also, it describes time frames in which ATMI server should start or stop. Internal server ping can be configured here too.

PARAMETERS

VARIABLE SUBSTITUTION

Several parameters in the ndrxconfig.xml file are processed via substitution engine. Engine processes puts the environment variables or special functions in the place-holders. Placeholder is defined as ${ENV_VARIABLE} for environment variables and ${FUNC=[PARAMETER]} for functions. The value can be escaped with \${some_value}.

Functions are processed in case if statement in brackets contains equal sign =. As the sign is not allowed for environment variables, Enduro/X uses it to distinguish between env variable and function.

Following FUNC (functions) are defined:

dec Decrypt base64 string in PARAMETER and replace the placeholder with the value. To get encrypted value, it is possible to use exencrypt(8) tool.

DATA DEPENDENT ROUTING

Enduro/X supports data dependent routing. There are three components which are required for routing:

When all above is defined, the routing will be activated, when client (or servers code) would issue:

Also affects any other Enduro/X APIs which internally uses tpcall/tpacall. Such as tpenqueue(3), tpdequeue(3), tpbegin(3), etc. but it is not recommended to configure routing for Enduro/X system servers or services (or at least with out advice from Mavimax).

Routing criterions by it self operate with three data types: LONG, DOUBLE and STRING.

Syntax for ROUTE_RANGES is following: <min_value_1>-<max_value_1>:<group_code_1>,…, <min_value_N>-<max_value_N>:<group_code_N>. Additional syntax is supported, such as:

Ranges value are validated and processed as indicated by field typ. LONG is limited to:

^[+-]?([0-9])+$

DOUBLE type value shall be expressed as:

^[-+]?(([0-9]*[.]?[0-9]+([ed][-+]?[0-9]+)?))$

For DOUBLE decimal separator is .. Also to check that equality is checked with precision of 0.000001.

STRING values may contain any printable character including newline.

When processes is perform routing, first matched range is used to extract the group code. If range is not found or buffer type does not match with service for which routing is defined TPESYSTEM error is returned to caller. Range matching is performed form left to right order. Range include the range min/max values. When range is defined for STRING type, values are compared by strcmp() function.

Examples of valid routing configuration:

<?xml version="1.0" ?>
<endurox>
...

    <services>
            <defaults routing="RT1"/>
            <service svcnm="DEBITSVC" />
            <service svcnm="CREDIT" routing="RT2" />
            <defaults routing="RT3" />
            <service svcnm="TXHANDLER" />
    </services>
    <routing>

        <route routing="RT1">
            <field>T_LONG_FLD</field>
            <ranges>MIN-4:GRP1,100-200:GRP4,300:GRP6,1000-22100:GRP5,*:*</ranges>
            <buftype>UBF</buftype>
        </route>

        <route routing="RT2">
            <field>T_STRING_FLD</field>
            <ranges>
                    MIN-'AAA':GRP1
                    ,'AAB' - AAC:'GRP4'
                    ,'HELLO\'' - HELLO5:*
                    ,'Z' - MAX:GRP6
            </ranges>
            <buftype>UBF</buftype>
        </route>

        <!-- cast value from string to double -->
        <route routing="RT3">
            <field>T_STRING_FLD</field>
            <ranges>
                    MIN - -1.1:GRP1
                    ,-1 - 44:'GRP4'
                    ,'44.1' - 123.15:*
                    ,*:*
            </ranges>
            <buftype>UBF</buftype>
            <fieldtype>DOUBLE</fieldtype>
        </route>
    <routing>
...
</endurox>


Note that *DDR* settings can be changed on they fly with *xadmin reload*, but
changes are deferred to certain amount of time. See 'DDRRELOAD'.

COMMAND LINE ARGUMENT ESCAPE

Process command line arguments normally may contain spaces or tables in their values. As Enduro/X processes need to prepare arguments for exec, at the prepare phase clear distinguishing must be made between multiple arguments and argument values. Thus Enduro/X employs a parser to split CLI strings into arguments. Blocks with spaces or tabs inside must be quoted. The logic is similar to the way how shall perform quote processing.

The following rules apply:

Samples:

Example 1:
CLI Value: someproc 'HELLO\' WORLD' X"some value \'"X

Process would receive arguments:
1. someproc
2. HELLO' WORLD
3. Xsome value \'X

Example 1:
CLI Value: someproc HELLO \ 'SOMETHING

Process would receive arguments:
1. someproc
2. HELLO
3.
4. SOMETHING

Above applies to CLT_COMMAND_LINE, ATMI_SERVER_SYSTEM_OPTIONS and ATMI_SERVER_APPLICATION_OPTIONS.

XML INCLUDE

ndrxconfig.xml supports entity substitution, thus effectively, portions of XMLs may be included from other files.

For example having ndrxconfig.xml:

<?xml version="1.0" ?>
<!DOCTYPE doc [
<!ENTITY defaults SYSTEM "ndrxconfig.xml.defaults">
]>
<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;

    <servers>
    </servers>
</endurox>

and

ndrxconfig.xml.defaults:

    <defaults>
        <min>1</min>
        <max>2</max>
    </defaults>

would make final config for ndrxd(8) and cpmsrv(8) 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>
    </defaults>

    <servers>
    </servers>
</endurox>

EXAMPLE

Sample configuration:

<?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>
        <start_max>2</start_max>
        <pingtime>1</pingtime>
        <ping_max>4</ping_max>
        <end_max>3</end_max>
        <killtime>1</killtime>
        <envs group="JAVAENV">
            <env name="_JAVA_OPTIONS">-Xmx1g</env>
        </envs>
    </defaults>
    <servers>
        <server name="tpevsrv">
            <srvid>14</srvid>
            <min>1</min>
            <max>1</max>
            <cctag>RM1</cctag>
            <env>${NDRX_HOME}/tpevsrv_env</env>
            <sysopt>-e /tmp/TPEVSRV -r</sysopt>
        </server>
        <server name="tpbridge">
            <max>1</max>
            <srvid>100</srvid>
            <sysopt>-e /tmp/BRIDGE -r</sysopt>
            <appopt>-n2 -r -i 0.0.0.0 -p 4433 -tA</appopt>
        </server>
        <server name="jserver2">
            <max>1</max>
            <srvid>200</srvid>
            <sysopt>-e /tmp/BRIDGE -r</sysopt>
            <envs>
                <usegroup>JAVAENV</usegroup>
                <env name="NDRX_RTGRP">GRP4</env>
                <env name="CLASSPATH">${CLASSPATH}:${NDRX_APPHOME}/libs/${NDRX_SVPROCNAME}.jar</env>
                <env name="CLASSPATH">${NDRX_APPHOME}/libs/somelib.jar</env>
            </envs>
            <cmdline>java</cmdline>
        </server>
        <server name="cpmsrv">
            <cctag>RM2</cctag>
            <srvid>9999</srvid>
            <sysopt>-e /tmp/cpmsrv.log -r -- -k3 -i1</sysopt>
        </server>
    </servers>
    <clients>
        <client cmdline="testbinary -t ${NDRX_CLTTAG} -s ${NDRX_CLTSUBSECT}" autostart="Y" cctag="RM4">
            <exec tag="TAG1" subsect="SUBSECTION1" log="${APP_LOG}/testbin1-1.log" cctag="RM5"/>
            <exec tag="TAG2" subsect="SUBSECTION2" log="${APP_LOG}/testbin1-2.log"/>
        </client>
        <client cmdline="testenv.sh" env="environment.override1" log="env1.log">
            <exec tag="TESTENV" autostart="Y"/>
        </client>
    </clients>
    <services>
            <defaults trantime="600" />
            <service svcnm="SERVICE1" prio="50" routing="RT1"     autotran="Y"  />
            <defaults autotran="Y" />
            <service svcnm="SERVICE2" prio="50" routing="RT2"     trantime="600" />
    </services>
    <routing>
        <route routing="RT1">
            <field>T_LONG_FLD</field>
            <ranges>MIN-4:GRP1,100-300:GRP4,1000-22100:GRP5,*:*</ranges>
            <buftype>UBF</buftype>
        </route>

        <route routing="RT2">
            <field>T_STRING_FLD</field>
            <ranges>MIN-AAA:GRP1,'AAB'-'AAD':'GRP4',*:*</ranges>
            <buftype>UBF</buftype>
        </route>

    </routing>
</endurox>

BUGS

Report bugs to support@mavimax.com

SEE ALSO

xadmin(8), ndrxd(8), ndrxconfig.xml(5), ndrxdebug.conf(5), ex_envover(5), exencrypt(8) exsinglesv(8)

COPYING

© Mavimax, Ltd