-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
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.
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.
-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'.
-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.
projects / anna.git / blobdiff