Transport mechanism, in particular, is like a chameleon because it adapts to each situation, by transparently choosing the best available protocol. Java RMI, event-notification, HTTP, and IIOP are currently used, but more protocols can be easily added via the MTP and IMTP JADE interfaces. Most of the interaction protocols defined by FIPA are already available and can be instantiated after defining the application-dependent behaviour of each state of the protocol.
In the inter-platform scenario, interaction among agents is achieved by the Agent Communication Channel (ACC), which is physically distributed across all the containers of the platform. In fact, each container can be launched with one or more message transport protocols (MTPs) and the entire platform is able to internally route the messages and select the best MTP (which might be even on a different container) for each situation. The following MTPs are currently available for JADE:
CORBA IIOP MTP based on standard Sun ORB provided with the JDK. (the default installation)
CORBA IIOP MTP based on ORBACUS .
JADE provides a Java interface both for implementing new ad-hoc IMTP and MTP. An alternative IMTP, for example, has been implemented for JADE integrated with LEAP in order to provide inter-container communication in wireless environments, where RMI is not available.
Inter-platform communication, i.e. communication between agents living on different platforms, is based on modules called MTP (Message Transport Protocol).
Such modules are able to marshal/un-marshal and transmit ACL messages according to the FIPA specifications. In this way JADE agents are able to communicate with
agents living on remote platforms regardless of whether these are other JADE platforms or different platforms (possibly developed with a different programming language) provided that they are FIPA compliant. FIPA specifies how to transfer ACL messages over three well known transport protocols: HTTP, IIOP (the transport protocol defined in CORBA) and SMTP.
JADE provides suitable MTPs for HTTP and IIOP only.
Znalezione MTP dla Jade w sieci:
This add-on includes a modified version of the JADE HTTP MTP (version 3.3) allowing usage of different message envelope encodings(currently the bit-efficient Envelope Codec). The CASCOM Message Gateway for using the MTP in private and unreliable wireless networks, e.g in 3G-networks.
A JADE MTP (Message Transport Protocol) based upon Jabber, an Instant Messaging (IM) protocol designed to sustain lengthy bidirectional communications among entities on the Internet.
It uses Apache CXF for sending and receiving SOAP messages.
FIPA Mailbox for JADE
The package allows agents on platforms which are ->
-> behind firewalls
-> on devices with non-fixed IP addresses
-> moving between different networks
intermittently connected to the public internet
To communicate with normal platforms in a transparent way to both the sender and the receiver.
The package works using an "access point" which consists of a Java Servlet running on a publicly available host (i.e. one outside the firewall) which “wraps” a standard JADE MTP (such as the HTTP MTP). The client platform then uses the fipa mailbox mtp to send and receive (by polling the servlet) messages via the server which in turn uses the wrapped MTP.
MTP (Message Transport Protocol) implementation based on JMS (Java Messaging Service)
Szczegółowe informacje na temat wymienionych wyżej MTP znajdują się na: