X-Git-Url: https://git.teslayout.com/public/public/public/?a=blobdiff_plain;f=example%2Fdiameter%2Flauncher%2Fdeployments%2Fbasic%2FREADME;h=e3a561676f0acb5afff46ce73b0abea6ad2222d5;hb=ea1b80f8fd0c1b806460f98f4e4cf433698857d9;hp=38250640419e72b56c805c77380479bb8cf7562a;hpb=7bf36f6cec41494071f07699184d8230ccd8cb41;p=anna.git

diff --git a/example/diameter/launcher/deployments/basic/README b/example/diameter/launcher/deployments/basic/README
index 3825064..e3a5616 100644
--- a/example/diameter/launcher/deployments/basic/README
+++ b/example/diameter/launcher/deployments/basic/README
@@ -1,35 +1,31 @@
 ABOUT CONTENT
 -------------
-Template for xml messages (message.dtd) and dictionaries (dictionary.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 './stack_examples'. There are also some stuff (hex/xml examples, etc.) which could be useful.
 
 Firstly you have to configure this directory in order to choose the type of launcher which will
 be preconfigured for your basic needs: client, server, balancer (proxy) and dummy process (this
 last is used for code/encode and does not launch any communication interface).
 
 If you are going to launch different processes, we recommend to clone this whole directory into
-another one (call it 'ADL-client', 'ADL-server_2', 'Diameter_proxy', or whatever you want), and
+another one (call it 'ADML-client', 'ADML-server_2', 'Diameter_proxy', or whatever you want), and
 then configure it again.
 
 Execute './configure.sh' and follow the intructions. You can call this several times, but the
 last configuration will be the one which prevails.
 
-Additional helpers/scripts could be found at './resources' directory.
-
 STARTING THE PROCESS
 --------------------
-After configuring the ADL execution context, a new script has been created: 'run.sh'.
-You can manually edit such script adding parameters as '-trace debug' to get complete traces,
-or adapt the communication endpoints for your environment.
+After configuring the ADML execution context, a new script has been created: 'run.sh'.
+You can manually edit such script adding parameters as '--trace debug' to get complete traces,
+or adapt the communication endpoints for your environment editing 'services.xml'.
 
 Launch the executable process without arguments to see a complete command-line help.
-Don't be scared. There are plenty of possibilities but the 'run.sh' script has been prepared
-for the type of launcher you wanted.
+Don't be scared. There are plenty of possibilities but the 'run.sh' script and 'services.xml'
+have been prepared for the type of launcher you wanted.
 
 OPERATION
 ---------
 Management interface for lite version is based on SIGUSR2 signal caugh. Use './operation.sh'
-script to send any operation to the process. Ask for help with that script to see all the
-operations supported.
-
+script to send any operation to the process. Check 'HELP.md' for more information.