A PEtALS domain. Each member share its data and communicate with other members. This tag is related to the PEtALS network. When declared, this tag defines the UDP multicast channel whom PEtALS nodes broacast messages to synchronize their data. If not declared, the nodes use dedicated connections by TCP unicast channels. If you want to use a large number of nodes, it can be interesting to define this tag to avoid huge dedicated TCP connections. Note that some networks forbids UDP multicast messages.Do not declare this tag in 'standalone' domain mode. The JNDI directory shared among the PEtALS domain. If not declared, the internal PEtALS JNDI directory is used. If you want to connect the PEtALS domain to an external JNDI directory, specify the the JNDI parameters. Refer to JNDI specifications for more details. A PEtALS subdomain. PEtALS nodes can expose their services into 'public' or 'private' area. 'public' services are reachable by the entire PEtALS domain whereas 'private' service are reachable only by members of the same subdomain. Not used in 'standalone' domain mode. Three domain mode are available. The 'standalone' mode allows an unique node within the domain. In this mode the domain is lighten by getting ride of the Network, Joram and Dream services. The 'dynamic' mode allows any no/de connecting to the PEtALS network to join the domain. In multicast network, you just have to define your local node in the topology. In unicast network, you must specify additionally the nodes that would be your coordinators; at least one of these node must run when you launch your local node. The 'static' domain accepts only the nodes defined in the topology. Each node of the domain must have the same topology definition. Set to true if the hosts running the PEtALS sub-domain are timed-synchronized (using NTP for example). Default value is false. Define a PEtALS node. It contains the definition of security, management and communication resources. Define the IP address or host name of the container. Define the user to be used for JMX and Joram clients. Define the password to be used for JMX and Joram clients. Define the port to listen for PEtALS network messages. In multicast network, the messages are only responses whereas in unicast network, it can be any messages. Do not declare this tag in 'standalone' domain mode. Define the JMX required ports. Define the Transport required port. Do not declare this tag in 'standalone' domain mode. The PEtALS topology. It contains information about the resources and configurations required by your PEtALS nodes. PEtALS node local setting are defined independently in the file 'server.properties'