3 Template for xml messages (message.dtd), dictionaries (dictionary.dtd)
4 and services (services.dtd) are informative, not actually required by
5 process. They are located at './DTDs'. Stacks are available at './stacks'.
6 There are also some stuff (hex/xml examples, etc.) which could be useful.
8 You could adapt your 'services' configuration using stuff from dynamic
9 directories if you are going to execute their tests, for example, from
10 'dynlibs/gx/00001/services' you will get the corresponding services
11 template and CER file for the test case messages CCR-I and CCR-T. If
12 not, dynamic programming will fail because the appropiate service is
13 not configured before starting ADML instances.
15 Execute './configure.sh' and follow the intructions to clone the ADML
16 instance into the needed amount for system testing.
20 After configuring the ADML execution context, a new script has been
21 created: 'run.sh'. This script will run all the cloned ADML instances
22 within ADMLS directory. Also, an './operation.sh' script will broadcast
23 the operation provided through every cloned instance. For example, if
24 you provide 'test|ttps|5', the speed of 5 test cases per second will
25 be set on every ADML instance. Imagine you have N instances, and then
26 you actually are establishing a total 5*N speed rate over the servers.
30 Firstly you shall program the test cases by mean script './program.sh'.
32 ./program.sh st_examples/DynamicQualification
34 Using option '-s', the testing will start after programming, with the
35 desired rate selected on configuration stage.
37 Don't forget to populate whatever data you need on the tested system,
38 because this work is not done here.
42 Management interface for lite version is based on SIGUSR2 signal caugh.
43 Use './operation.sh' script within a specific instance directory to send
44 any operation to the process. Ask for help with that script to see all
45 the operations supported.