X-Git-Url: https://git.teslayout.com/public/public/public/?p=anna.git;a=blobdiff_plain;f=example%2Fdiameter%2Flauncher%2Fdeployments%2Fst-client%2FREADME;h=73b32c2e440234d7da74c509cbf163460bb5f96e;hp=8730f6ed3235a9e202fa280bc40e650b92436e30;hb=e215832ffe9c51e08ce23d2eb0aaa2ecfecd6d85;hpb=5f502d03da4ab544b8c28fe19d02726fc61b9a8a diff --git a/example/diameter/launcher/deployments/st-client/README b/example/diameter/launcher/deployments/st-client/README index 8730f6e..73b32c2 100644 --- a/example/diameter/launcher/deployments/st-client/README +++ b/example/diameter/launcher/deployments/st-client/README @@ -1,35 +1,46 @@ ABOUT CONTENT ------------- -Template for xml messages (message.dtd), dictionaries (dictionary.dtd) and services (services.dtd) -are informative, not actually required by process. They are located at './DTDs'. Stacks are available -at './stacks'. There are also some stuff (hex/xml examples, etc.) which could be useful. +Template for xml messages (message.dtd), dictionaries (dictionary.dtd) +and services (services.dtd) are informative, not actually required by +process. They are located at './DTDs'. Stacks are available at './stacks'. +There are also some stuff (hex/xml examples, etc.) which could be useful. -Execute './configure.sh' and follow the intructions to clone the ADML instance into the needed amount -for system testing. +You could adapt your 'services' configuration using stuff from dynamic +directories if you are going to execute their tests, for example, from +'dynlibs/gx/00001/services' you will get the corresponding services +template and CER file for the test case messages CCR-I and CCR-T. If +not, dynamic programming will fail because the appropiate service is +not configured before starting ADML instances. + +Execute './configure.sh' and follow the intructions to clone the ADML +instance into the needed amount for system testing. STARTING THE PROCESS -------------------- -After configuring the ADML execution context, a new script has been created: 'run.sh'. -This script will run all the cloned ADML instances within ADMLS directory. Also, an -'./operation.sh' script will broadcast the operation provided through every cloned -instance. For example, if you provide 'test|ttps|5', the speed of 5 test cases per -second will be set on every ADML instance. Imagine you have N instances, and then +After configuring the ADML execution context, a new script has been +created: 'run.sh'. This script will run all the cloned ADML instances +within ADMLS directory. Also, an './operation.sh' script will broadcast +the operation provided through every cloned instance. For example, if +you provide 'test|ttps|5', the speed of 5 test cases per second will +be set on every ADML instance. Imagine you have N instances, and then you actually are establishing a total 5*N speed rate over the servers. TESTING PROCEDURE ----------------- -Firstly you shall program the test cases by mean script './program.sh'. For example: +Firstly you shall program the test cases by mean script './program.sh'. +For example: ./program.sh st_examples/DynamicQualification -Using option '-s', the testing will start after programming, with the desired rate -selected on configuration stage. +Using option '-s', the testing will start after programming, with the +desired rate selected on configuration stage. -Don't forget to populate whatever data you need on the tested system, because this -work is not done here. +Don't forget to populate whatever data you need on the tested system, +because this work is not done here. OPERATION --------- -Management interface for lite version is based on SIGUSR2 signal caugh. Use './operation.sh' -script within a specific instance directory to send any operation to the process. Ask for -help with that script to see all the operations supported. +Management interface for lite version is based on SIGUSR2 signal caugh. +Use './operation.sh' script within a specific instance directory to send +any operation to the process. Ask for help with that script to see all +the operations supported.