The first interoperability functionality allows MESIS agents to act as CORBA clients, for example, to control legacy network components via CORBA interfaces, to exploit services and facilities provided by any CORBA DPE (e.g., Transactions, Collection and Trader Object Services), and to invoke CORBA-compliant services at the application level.

MESIS DPE components can also become CORBA servers to offer their services to other entities. This enlarges the accessibility of a MESIS service to any existing client, independently of its technology (even non MA). For instance, a user can employ a standard Web browser interface (such as a CORBA client applet integrated in a standard HTML page) to invoke the Video on Demand service.

The third interoperability direction derives from the increasing number of MA systems recently proposed and already implemented. This number, on the one hand, declares the interests in the MA paradigm but, on the other hand, can endanger interoperability and could limit the industrial diffusion of MA applications.
MASIF proposes a standardization for agent and agent system names, and for agent system types and location. It defines two interfaces, MAFAgentSystem and MAFFinder, respectively for agent management and for agent tracking.

Agent management allows an external system to control agents belonging to a compliant MA platform: MASIF defines actions to suspend/resume/terminate agents and to move agents between MA systems provided that they have compatible agent types.

Agent tracking permits to locate agents and their services. Agents are registered with MAFFinders, that provide a global naming service for mobile agents because the CORBA name service is not suitable for entities mobile by nature like agents.

The implementation of the MESIS CORBABridge is based on VisiBroker. However, the module is portable without modification on any ORB compliant to the CORBA 2.2 specification. In fact, we have used only the portable functions provided by the Internet Inter-ORB Protocol and the Portable Object Adapter, to overcome potential incompatibility among different ORBs.