LogicApp Configuration

LogicApp Configuration

The core of an N2IWF deployment is a configured N2SVCD LogicApp instance.

The base of an example N2IWF LogicApp configuration might include:

<application name="N2IWF-Logic" module="LogicApp">
    ...
    <config>
        <services>
            <service module="LhoScpApp::LhoScpLuaService"
                     libs="../../n2scp/apps/lho_scp/lib"
                     script_dir="../../n2iwf/lua/svc/"
                     lua_lib_path="../lua/lib/?.lua;../../n2iwf/lua/lib/?.lua;../../n2iwf/lua/svc/scp/?.lua;../../n2scp/lua/lib/?.lua;../../n2cug/lua/lib/?.lua">
                <triggers>
                    <trigger script_key="iwf_svc"/>
                </triggers>
                ...
            </service>
        </services>
        ...
    </config>
</application>

The following points are relevant to LogicApp configuration for N2IWF:

Lua Library Path

For the lua_lib_path parameter in the LogicApp service, the following guidelines apply:

Compiled Lua

Any Lua libraries, both supplied by N-Squared and custom, may be pre-compiled by using the Lua compiler utility. If this is done, ensure that the lua_lib_path is updated to reflect the appropriate file suffix as generated by the compiler.