Ease of use for ADML System Test configuration

diff --git a/dynamic/launcher/gx/00001/services/cerGx.xml b/dynamic/launcher/gx/00001/services/cerGx.xml
new file mode 100644 (file)
index 0000000..6e55b0a
--- /dev/null
+++ b/dynamic/launcher/gx/00001/services/cerGx.xml
@@ -0,0 +1,14 @@
+<message version="1" name="CER" application-id="0" hop-by-hop-id="1" end-by-end-id="120858368">
+   <avp name="Origin-Host" data="esmdx0900.gxrel10plusrealm.com"/>
+   <avp name="Origin-Realm" data="gxrel10plusrealm.com"/>
+   <avp name="Host-IP-Address" data="1|10.1.27.231"/>
+   <avp name="Vendor-Id" data="0"/>
+   <avp name="Product-Name" data="SAPC"/>
+   <avp name="Supported-Vendor-Id" data="10415"/>
+   <avp name="Supported-Vendor-Id" data="193"/>
+   <avp name="Firmware-Revision" data="1"/>
+   <avp name="Vendor-Specific-Application-Id">
+      <avp name="Vendor-Id" data="10415"/>
+      <avp name="Auth-Application-Id" data="16777238"/>
+   </avp>
+</message>

diff --git a/dynamic/launcher/gx/00001/services/services.msk b/dynamic/launcher/gx/00001/services/services.msk
new file mode 100644 (file)
index 0000000..11728cc
--- /dev/null
+++ b/dynamic/launcher/gx/00001/services/services.msk
@@ -0,0 +1,9 @@
+<services>
+  <!-- Stacks -->
+  <stack id="16777238" dictionary="dictionaryGx.xml" ignoreFlagsOnValidation="yes"/>
+  <stack id="0" dictionary="dictionaryBase.xml"/>
+
+  <!-- Nodes -->
+  <node originHost="esmdx0900.gxrel10plusrealm.com" applicationId="16777238" entity="ebs511dvipt:3868" cer="cerGx.xml" entityServerSessions="__CLIENT_CONNECTIONS__"/>
+</services>
+

diff --git a/example/diameter/launcher/DEPLOY.sh b/example/diameter/launcher/DEPLOY.sh
index 72604a8..ce1c91a 100755 (executable)
--- a/example/diameter/launcher/DEPLOY.sh
+++ b/example/diameter/launcher/DEPLOY.sh
@@ -210,6 +210,7 @@ do
   cp $dir/$dynlib_variant/*.so $DPATH/dynlibs/$dir
   cp $dir/*.xml $DPATH/dynlibs/$dir 2>/dev/null
   cp $dir/dynamic.suffix $DPATH/dynlibs/$dir 2>/dev/null
+  cp -r $dir/services $DPATH/dynlibs/$dir 2>/dev/null
 done
 cd - >/dev/null
 cp ./resources/scripts/select_dynlib.sh $DPATH/dynlibs/select.sh

diff --git a/example/diameter/launcher/deployments/st-client/README b/example/diameter/launcher/deployments/st-client/README
index 8730f6e..73b32c2 100644 (file)
--- 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.