Information Technology Reference
In-Depth Information
depending on the used protocol (ACL, HTTP or WebSocket). Additionally, it has
to handle the corresponding message performatives [8] in any possible interface
combination. That means in fact the implementation of a cross-technological mes-
sage tracking and routing mechanism (handling messages going in and out of each
type of interface). To simplify the operation of the WebGateway-agent we limit the
range of performatives to FIPA-Inform and FIPA-Request, which is sucient for
the invocation of Web services.
2.2 Service Registration
Referring to the FIPA specification underlying
, agents have to register
their services at the Directory Facilitator (DF). In order to publish such an agent
service as a RESTful Web service, a second registration at the Web Service Reg-
istry (see Figure 2) has to be executed. This second registration differs from the
one conforming to the FIPA specifications. In addition to the standard registra-
tion parameters (service name, service type, etc.), it is necessary to submit the
representation of the related REST resource. This representation could, in fact,
be any media type that is supported by the Jetty Web server but in our case, we
have designed resource representations to be based on Java Server Pages 6 (JSP)
together with supplementary source files as it is known from ordinary Web site
development.
Mulan
#$
" $
!
!
"
"
!
!
Fig. 2. Service Registration and Message Decoupling
After service registration on the agent side, the WebGateway-agent comes
into play. It treats the agent service as a REST resource and assigns an address
in the form of an URI to it. In addition, platforms and agents are also treated as
REST resources and are assigned URIs. The composition schema of addresses is
depicted in Figure 3 in terms of a 4-level naming hierarchy and the corresponding
URI parts:
6 Java Server Page (JSP): http://www.oracle.com/technetwork/java/javaee/jsp
Search WWH ::




Custom Search