23.03.2017 Views

wilamowski-b-m-irwin-j-d-industrial-communication-systems-2011

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Industrial Agent Technology 16-5<br />

issue directives to the subordinate agents of the holon. Thus, it may broker and/or supervise the interactions<br />

between the subholons of that holon. The outbound interface of a mediator implements the interaction<br />

of the holon with the rest of the agent society. The mediator can plan and negotiate for the holon on the<br />

basis of the common plans and goals of its underlying agents.<br />

All this three kinds of federation architectures permit to coordinate the system activity via facilitation<br />

as a means of reducing overheads, ensuring stability, and providing scalability (cf. [6]).<br />

16.2.7 How Agents Can Be Implemented<br />

In order to implement communities of agents, several layers need to be realized. The lowest layers are<br />

the network and <strong>communication</strong> layers that allow agents to abstract from their exact physical location<br />

and to exchange messages. On the next level, the actual agent infrastructure needs to be provided, which<br />

means that usually a number of different agent types need to be provided (the actual agents, broker<br />

agents, white and yellow pages, etc.) as well as ontologies and agent life-cycle management services.<br />

These first layers can be seen as syntactical layers in the sense that they do not reflect the actual intelligence<br />

of the system—they just provide the necessary foundation for a MAS to function. Especially for<br />

these “syntactical” layers, a significant number of commercial and academic agent construction tools<br />

are available, providing a variety of services and agent models, the differences reflecting the philosophy<br />

and the target problems envisioned by the platform developers. A reference for a broad number of<br />

agent construction tools can be found on the AgentBuilder Web site (http://www.agentbuilder.com/<br />

AgentTools) and in [28].<br />

Java Agent DEvelopment Framework (JADE; cf. [27]) is perhaps the best-known FIPA (cf. [29])<br />

compliant platform to develop agent-based solutions. It provides the mandatory components defined by<br />

FIPA to manage the agent’s infrastructure, which are the agent <strong>communication</strong> channel (ACC), the agent<br />

management system (AMS), and the directory facilitator (DF). The AMS agent provides white pages and<br />

agent life-cycle management services, maintaining a directory of agent identifiers and states, and the<br />

DF provides yellow pages services and the capability of federation within other DFs on other existing<br />

platforms. The <strong>communication</strong> among agents is done via message passing. The messages are encoded<br />

using the FIPA-ACL and their content is formatted according to the FIPA-SL (Semantic Language), both<br />

specified by FIPA. Ontologies should be used to support a common understanding of the concepts of<br />

their knowledge domain, passed in the messages’ content. Ontologies can be designed using a knowledge<br />

representation tool, such as Protégé (see http://protege.stanford.edu/), and then translated into<br />

Java classes according to the JADE guidelines that follow the FIPA Ontology Service Recommendations<br />

specifications (cf. [29]).<br />

JADE also provides a set of graphical tools that allows supervising the status of agents and supporting<br />

the debugging phase which are usually quite complex tasks in distributed <strong>systems</strong>. Figure 16.1 illustrates<br />

FIGURE 16.1<br />

Graphical user interfaces of the Remote Monitoring and Sniffer agents.<br />

© <strong>2011</strong> by Taylor and Francis Group, LLC

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!