Design and Performance Evaluation of a Service-Oriented HLA RTI on the Grid - Grid Computing: Infrastructure, Service, and Applications - page 456

is translated to a method invocation of the corresponding module
class that will take over the processing work. For example, a getCallbacks
Grid service invocation of the LIS is translated to a CallbackModule.
getCallbacks Java method invocation that will scan the callback queues
and return the available callbacks as a list.

18.4.3 Federation Management Service

The FMS is a grid service related to the HLA federation management
service group. The FMFS dei nes a createResource operation invoked by the
RTI index service to create an FMRI for a new federation. The FMIS dei nes
some operations corresponding to the HLA federation management service
group such as joinFederationExecution and resignFederationExecution. It
also dei nes operations for fetching some information kept in FMRIs. When
a federation is created, a new FMRI will be created and it is the FMRI's
responsibility to create a new DMRI, OOMRI, TMRI, and DDMRI for the
new federation. The FMRI operates as a federation-wide registry. It keeps
the EPRs of the DMRI, OOMRI, TMRI, and DDMRI created for the federa-
tion. It also keeps the EPRs of federates' LRIs for the federation. It gener-
ates federate handles for new joining federates. When a federate resigns
from the federation, it is responsible to notify the whole federation about
this resign for the deletion of any information related to the federate.

18.4.4 Declaration Management Service

The DMS is a grid service related to the HLA Declaration Management
service group. The DMFS dei nes a createResource operation invoked by
the FMRI to create a DMRI for a new federation. The DMIS dei nes some
operations corresponding to the HLA declaration management service
group such as publishInteractionClass and subscribeInteractionClass. It
also dei nes operations for fetching some information kept in DMRIs. The
DMRI keeps the subscription and publication information of all federates
in the federation. When a DMRI is created and initialized, it reads the
federation execution data (FED) in HLA 1.3 or FOM document data (FDD)
in HLA 1516 i le and generates handles for the interaction classes, interac-
tion class parameters, object classes, and object class attributes dei ned in
the federation. All these handles are kept in the DMRI and the DMIS
dei nes operations for fetching the handle information. Since these federa-
tion object model (FOM) [1] data are centralized in the DMRI, the DMIS
can dei ne some operations to enable dynamic change of the FOM which
is not supported in most of the traditional RTIs. For example, the DMIS
can dei ne an addObjectClass operation for adding a new object class in
the federation. Similar to the HLA evolved modular FOMs approach [30],
the DMIS can dei ne some operations to enable a FOM module to be
dynamically added to or deleted from the federation FOM.