N2SVCD Configuration - TesterApp

Tester Application Configuration

The N2SVCD Tester Application is the primary access point for agents wishing to execute tests. The Tester Application has two primary interactions:

• Perform JSON interactions with clients wishing to perform and monitor tests.
• Execute tests by interacting with other protocol gateways.

See the N2SVCD Overview for more information on how the Tester Application interacts with other components.

The following configuration is used to create a Tester Application instance. In the usual case, you will only ever require a single Tester instance. Even if your Tester Installation is intended to interact with a number of different "environments under test" (e.g. Production, Model), you can run tests against multiple different environments via a single Tester Application instance.

<?xml version="1.0" encoding="utf-8"?>
<n2svcd>
  ...
  <applications>
    ...
    <application name="Tester" module="TesterApp">
      <include><lib>../apps/tester/lib</lib></include>
      <parameters>
        <parameter name="json_host" value="10.42.2.154"/>
        <parameter name="json_port" value="9009"/>
        <parameter name="default_sigtran_app_name" value="SIGTRAN"/>
        <parameter name="default_pi_app_name" value="PI-SMF01"/>
        <parameter name="default_osd_app_name" value="OSD-SLC01"/>
        <parameter name="default_db_app_name_smf" value="DB-SMF01"/>
      </parameters>
    </application>
    ...
  </application>
  ...
</n2svcd>

The application element attributes for a Tester Application instance are:

Attribute	Type	Description
name	String	[Required] A unique name for this application instance.
module	String	[Required] TesterApp
include.lib	String	[Required] ../apps/tester/lib
parameters	Array	Array of name = value Parameters for this Application instance.
.json_host	String	IPv4 Host Name or A.B.C.D IPv4 Bind Address on which to create a JSON RPC server. (Default = 0.0.0.0).
.json_port	Integer	IPv4 Bind Port Number on which to create a JSON RPC server. (Default = 9009).
.default_sigtran_app_name	String	Name of a SIGTRAN Application instance to use for sending TCAP BEGIN (InitialDP and AssistRequestInstruction) operations. (Default = SIGTRAN Application Name must be specified in each test definition).
.default_pi_app_name	String	Name of a PI Application instance to use for sending Oracle OCNCC PI requests. (Default = PI Application Name must be specified in each test definition).
.default_osd_app_name	String	Name of a OSD Application instance to use for sending Oracle OCNCC OSD requests. (Default = OSD Application Name must be specified in each test definition).
.default_diameter_app_name	String	Name of a DIAMETER Application instance to use for sending DIAMETER requests. (Default = DIAMETER Application Name must be specified in each test definition).
.default_db_app_name_smf	String	Name of a DB Application instance for performing lookups against the Oracle OCNCC SMF. (Default = SMF DB Application Name must be specified in each test definition).

Default Application Names

Note: The "default__app_name" parameters are not typically required to be specified. Usually, the IN Tester Graphical User Interface will be configured to explicitly specify its preferred protocol gateways for each individual test.

In fact, in a multi-environment installation, specifying "default__app_name" parameters is not recommended. It is highly desirable that the user running the test should expressly indicate their target environment. Default protocol gateway instances are not desirable in such a case.

Instead, you should configure "environments" within the IN Tester Graphical User Interface.