Three Architectures Comparisons for HLA computing RTI

BY: Zeeshan Rafi(zeeshan.rafi@uog.edu.pk)

Abstract (RMI), Sun Java Development Kit software, from

Distributed simulation has become an rapidly
Growing Department of Defense (DOD). In this
article, we shall compare the three different
architectures Support for distributed computing
HLA, and CORB A, RMI. This is similar to the
structure of each base; there are profound
differences that might affect Distributed
application developer or administrator
Simulation exercises.
INTRODUCTION
The propose and performance of a distributed
simulation model Has become rapidly growing
Department of Department of Defense(DOD).In
recent years, DOD has invested Critical
resources distributed infrastructure High-level
simulation of model lemesi . Geçerli focus
Pioneer ede(HLA) defense architecture
modeling Simulation and office
sulfoxide(DMSO)U.S. Department of Energy (
Protection, 1998).Human HLA ,most benefits of
the previous two Efforts of the DOD: Distributed
Interactive Simulation(DE) And aggregate level
(JDK). There is an increasing need to decrease
defense budget will do control.
That promises to significantly reduce the
acquisition and analysis Cost. Simple design for
distributed simulation enhance the re-DOD
various Simulation modeling efforts. Distributed
to each of the three architectures computing
execution, provides many of the problems
distributed the simulation model. Each has a
base effect the structure of his architectural
vision of the world. This article compares the
characteristics of these three Particular
focuses on the key technology of their
Impact of distributed simulation. Naturally,
so to cover all aspects of the architecture is
impossible Also discussed the salient
features of each paper. In the next section,
we will discuss the core Elements of
distributed architecture. 5 and Part 3
I touched the main features HLA, CORBA,
and of In RMI, respectively, and followed
by a brief discussion Comparison of Section6.
In Section7, will Ornerier. A results and was
followed by Comparison of Section6. In
Section 7, will Conclusions and

simulation protocol standard Protocol(ALSP). recommendations.

Various efforts have been made In order to 2.1 BASIC ELEMENTS OF DISTRIBUTED
provide distributed computing, commercial
sector. Two there is are cent effort of common ARCHITECTURES
objects the most appropriate The Object
The basic elements of distributed
Management Request Broker (CORBA), And
Architecture to focus attention on three basic
Group (OMG), Remote Method Invocation
elements, we interface language of the
object: a distributed architecture Name Manager Object to communicate with the
objects and services manager. In addition, machine through it all.
let’s deal with topics such as programming
languages, etc. Operating system support,
In fact, may be the physical location of the
and hardware, and Network protocol is
object manager both the client and the server
being used. It is important for the language
or server location, completely independent of
interface of the object they need to support
the client and server machines. One
distributed applications Abstract level than the
Architecture has been well designed; the
normal communication Practice. Must be
physical location should be independent of the
minimal object Premise of the implementation
object manager Application designer. Naming
of another object Can contain other objects, the
service mechanism the server can be used to
method of the later method Machine. Method
inform customers about the object access.
and the class define the contrast Contract for an
Can be in the range of implementation, these
object that implements the interface, and
services Simple list to the data-based complex
not only provides a list of methods. Thus, the
objects. There is a customer to be able to
interface Ideal too l to ensure interoperability
explore the service, the object will discover the
between Distributed object .In order to get the
need for various methods of the signature of
language, CORBA and HLA to explain the
the argument, from one and object reference,
approach to distributed objects, each
so you can call its methods Object.
another interface feature Language practice. On
the other hand, RMI Thus, using the Java
language and language-specific approach You may need to be delayed until run time,
Interface to the interface specification. This is hard-coded the application. You can extend the
quite its implies lot of design issues, limit distributed architecture Neutral (HLA, CORBA)
Have been deployed in other languages, in RMI or linguistic (RMI). Languages pacific one The
objects, you will be able to cope. Using the key distributed approach assumes that is greater
elements required to implement the interface. than or equal to about Object - in fact, all the
features of the language.
Containing a combination of several virtual live,
In addition, the drawback that can be applied to
exercise, because the mechanism underlying
legacy systems Different, incompatible language
the constructive simulation, there are basically
.Language-specific. In order to provide an
the following three types, the simulation is that
approach to this heritage, including hard
Different. Object Manager is responsible for the
Programs. Architecture neutral, can be built
object Reference to the object to be
into the language Legacy applications written in
instantiated to the requesting client
any language that is supported by despite the
Necessary and maneuvering object request
difficult transition programming a month Effort.
different machines. You can become indifferent
There are more opportunities for important it
to objects Performed by invoking methods
may not have interoperability between
specific to the fact that to obtain the local
different programs. I was developed using the
Because of the remote control code or code to
distributed computing in mind. However, due to
hide the object manager Details are displayed.
the coupling, it should be provided for each
Conceptually, the backbone of the Object
language actually have to get it from, is
supported for interoperability with you
everything you will need to work with others of
all.
3. HLA
High priority to efforts in the Department of Defense
For the development of modeling and simulation
(DOD) Level, coercive. High a common technology
Standard technical architecture for the simulation of
all DOD. It is an important feature consists Elements,
interface specifications and design rulesTo provide
a common framework for identifying with
Design of the system architecture. HLA is due
Processes that have been included government,
industry, and academia. HLA has been accepted
as a draft standard IEEE Are supported by the
standard of interoperability of simulation
Organization (SISO). HLA is applicable to a wide
range of functional areas ranging from training
to the acquisition of systems analysis. HLA is
also applicable to simulations of the purely
constructive
Representation of software to man-in-loop
simulation to interface to the system and live.
Envision a coalition of design principles HLA
Simulation consists of modular components
clearly defined functions and interfaces. There
is a federation Specific combination of
federation object model Set and run-time
infrastructure (FOM), the federate Service (RTI).
Federate simulation includes U Simulation, live
player interface. There is RTI I distributed the
operating system for the federation. Specific
the simulation functions are separated
intentionally I have generic support.
3.1 HLA Rules
The first component of the definition of the HLA
is the HLA Rules that describe the esponsibilities
of the simulation of I have looked up to fit in the
federation RTI HLA. There I'm in the United
States (5 federated federation rules 5 and rate
rules Department of Defense, 1996a, 1998):
Code of Federal Regulations Federation
(1) Is assumed to have the form of law FOM
OMT.
(2) All expressions the object must be federated
It is not and RTI.I
(3) during federation of 1 FOM, all exchange
the data must go through the RTI.
(4) During the execution of the Federation, all
federates shall interact with one
RTI and interfaces according to the
specifications.
(5) Between the attributes of the federation
execution Can be owned by the federate is only
one instance of an object Time that I was given.
Federation rules
(6) The linkage must have a law in the form of
SOM OMT.
(7) Can be used as an attribute update reflected
rates
SOM their appropriate data send / receive.
(8) You can now transfer accept Federated Rate
Property SO Misbased on its ownership in.
(9) You can vary depending on the work
condition They offer the appropriate attribute
update Their SOM.
(10) I would to be able to manage the federated
local time Data exchange with them to be
coordinated, other members of the Federation.
3.2 HLA Interface Specification
The second component of the definition of HLA
Standard for interface specification to federate
dialogue
RTI (Ministry of Defense of us, 1998). This is the
definition How to access the services of RTI.
Interface specification
Are offered in (MI) Application Programming
Interface CORBA IDL, C + +, Ada95, in many
ways, including Of Java. Service interface
specifications are six basic RTI.
Group: Federation Management, Declaration
Management, Object management, real estate
management, time Management and data
distribution management. Remember
Interface Specification "interface" is not
associated with this Language, as described in
section 2.
Federate make use of the services of directors
of the Federation Create Delete, dynamic
control, and change Execution of the
federation. HLA specification for In order to
avoid the single, participated in the software
system Execution of federated, to a federation
of more than what You can prevent that
participate in a single software system
The Independent Union of the execution of
multiple. Current RTI However, some
applications necessarily support I want to set
this property. Federation management services,
including, Restart checkpoint control, pause,
resume, and function.
Federated use the services of a management
declaration declared their intention to publish
and subscribe to appeal Interaction with the
attribute. you need to call the federate
Declaration Management services that are pre-
recorded Object instance, the attribute value is
updated, for example Effect of the declaration,
send interaction The federation, if you are
independent of management. In order to deal
with the federate, using the Object
Management Service Delete object, record,
modify, and Send and receive objects interact
with the sample.
Object data management services have been
evaluated I offer a distribution management
services. Federated use the services of property
management For example, I want to transfer
ownership of the attribute. This feature is
Modeling supports the federation of
cooperatives. Use the services of Time
Management for the federate In order to
coordinate pre-logical, maintenance
3.3 HLA Object Model Template
The third component of the definition of HLA
object Is a common way for that (OMT) Model
Template Prescribe the information contained
within the object of HLA
Federation and the United States each
simulation model (Defense, 1996a, 1996b), and.
OMT language interface HLA. Object model
describes a set of shared objects Interaction
federation, or attributes of simulation these
objects, the level of detail of the object and its
Represent the real world, including the space
and Time resolution. HLA OMT method, which
provides a general Concrete framework of the
object model Please refer to the manual.
Encouragement simulation OMT
Interoperability and simulation again.
There are two types of object model of the HLA,
Simulation and federated object model objects
(FOMS) Model (solid). Two types of models
have been described I method was used OMT.
FOM, which contains all of the information that
has been, shared Need for (interaction of the
parameter object, and attributes) I was given
the Union. SOM, which contains all of the
federal government (Parameter objects,
attributes, interaction and information)
Visible to all other federates in the federation
and Reflect on the information from other,
federates Unity.
The attribute name is part of the state of the
object. Is the object that dispatched the case of
changes in the interaction also objected up, I
might cause a change in state. A
Parameter information related to the
interaction Receiver provided object by sending
object (s).By providing a new instance of the
federated update rate, qualification
the value of the attribute to change the
attributes and properties to reflect
a new instance of the attribute with a value of
Attribute. Approach to interoperability through
HLA Ability to subscribe to and publish and
attributes Interaction. Discovered through this
cooperation FOM. Is significantly different from
the interaction of the local object
for remote interaction, the latter is only
possible if, I subscribe to the receipt of an
attribute change.
4. CORBA
CORBA is a non-commercial venture by Object
Consortium Management Group (OMG), more
than 800 Members of management was
established in 1989 (object Group, 1998; Haki
and Orfali, 1998). It is the oldest and I was
probably the most mature of the three
architectures we please consider in this paper.
CORBA is very large, Collection of protocol
specifications and complex, and the inner these
short paper, we can almost touch
Prominent feature.
4.1 CORBA interface language
CORBA interface language program Interface
Definition Language (IDL). The IDL syntax is as
follows. Essentially, except for the interface
defined in C + +, IDL Rather than
implementation. In CORBA applications,
Are compiled into one of the subsequent code,
IDL is first written Supported languages.
Elements defined in IDL is as follows:
Then use the generated, implemented in
languages that I Code as a basis. Module: IDL
has four key elements Interface attributes,
operations, and.
Bundle more than one module is the name
space and Interface. Interface is a set of
attributes, Operation that corresponds to the
object. Mon interface Seen as a contract to
implement a defined Operations such as how to
support the same In order to provide the
appropriate type, and the signature and return
Accessory methods that correspond to the
attributes. Interface I might define an
inheritance hierarchy. All objects
must have a method that implements the
interface corresponding to the operations and
attributes of the interface Such as those of all
interfaces that are inherited in the same way.
Multiple has been supported interface
inheritance, can not be inherited from the
interface of the two interface has
or attributes of the same name for the
operation. CORBA We specifies that it is
possible to have only one object interface 2.0.
However, to support CORBA 3.0 proposal has
been made multiple interfaces.
Correspond to instance variables, attributes,
Earl Is used to represent the data. Attributes are
the basic types of either Object reference type,
or has been constructed. Basic possible
Int primitive data types and normal (long, type
is short type float, double, type Boolean, etc.).
Constructed types almost Correspond to those
available in, C + +. Struct can be been defined
using the type def. Corresponds to the
sequence Variable-length array. Finally, for each
type of use I represent all the required data. It is
strong and what represents the data in a
flexible way, it is self describing.
Be used to call methods on an object reference
you can be placed on the object. IDL is not
specified, it is a property in many cases, the
implementation of accessor methods, it will be
used instead Provides direct access to instance
variables. Moment Attributes are read-only or
read and identify Written.
The process corresponds to the process,
are defined to retu method name, signature
and Types. A transaction is defined as an
independent Whether INOUT IN, or OUT,
according to the argument, from the calling
object that was passed to the object called
Call the object, called object or both.
CORBA CORBA is a language-independent way
can be implemented either by the server and
the client without the languages that are
supported, and I can work together
but I know each other's language. More
importantly, the There is no need to check any
participant under the assumption CORBA
CORBA applications in other languages
the client and the server. The following
languages are currently supported Java C, C + +,
Smalltalk, Ada, and COBOL are. Definition
Interface of a class is an important element of
this instead standing in the language.
2.4 CORBA Object Manager
There is a CORBA Object Request Object
Manager Broker (ORB). The ORB allows objects
to send, Whether or not to receive the object,
the message they are a local or remote. All
messages between the clients ORB should be
the server object. Typically, the Client requests
a reference to the object on the server I call the
methods of the intent.
Conceptual entity of ORB stuff in fact, the client
and the server object is configured by software
Are present in both the client and server
machines. What Client request object, the
message goes to the first ORB His machine.
Client ORB set ORB to communicate with the
server. Server ORB, it returns a reference to an
object of interest to pass to the customer
returns the ORB Client. This is transparent to
the program, it does not mean each
participating applications to CORBA objects
ORB software is installed on the machine where
I must not exist.
Both static and dynamic tools for CORBA
Server that provides remote object. Static
method each contains a "stub" of the client and
the server the actual object on the server
interface. Server stub you will be referred to as
a "frame" in many cases. Bolt connection of the
object, ORB will generate a machine and
generally, this IDL, the modeler is - it's not
necessarily writing a call to the ORB. To
implement a distributed object in this way, one
begins with the class of IDL Skeleton code only
while the server is used, will only be used to
stub code Client. But please do not need the
stubs and skeletons in the same language, so
that all communication takes place via,
ORB. For example, an object in C + + may
be a server Java IDL client stubs, you
created yourself. Importantly,
any addition, customers have to make a
server Assumptions about other languages.
3.4 CORBA Naming Service
It does not require the use of static each
client stub I wanted to be a special code for
the remote object Created before the remote
object can be compiled was obtained.
CORBA is providing dynamic invocation
In order to avoid the need for (DII) stub
interface that has been precompiled.
Remote object is "discovered" for the first
time using the DII client is one of several
mechanisms. In addition, the interface
Customers to determine the object so as to
obtain you want to invoke a method.
Information about how to (After the
exception is thrown, and the type argument
list, return) was obtained. Outgoing sent a
request to create if you call this method on
the remote object.
Create an interface repository that contains
the server Dynamic interfaces can be
accessed from the client. Moment
the interface can be scanned in order to find
the repository class it has been fascinated by
the client. Interface, including tanks
was exposed to the object's IDL.
CORBA client and server, the execution of a
single Local area communication network
(LAN), more or less Automatic. ORB on
each machine software because usually
considered to explore all the other spheres
on the LAN Transparent for each customer.
CORBA Provides the ability to
communicate with the ball on the
using the Internet Inter-ORB Protocol
different LAN (IIOP), TCP / IP is extended.
5. RMI
Start of Java Development Kit 1.1 (JDK
1.1), Contains a remote Java programming
language as part of the standard Java method
invocation (RMI) Library (Java soft, 1997).
Support the four that are included in the
RMI Separated by JDK1.l, sparse
distribution of packages and to identify the
remote object (via a "marker" interface),
Distance to throw an exception when
recording a distant subject;
Performance of remote objects and remote
waste services Collection. RMI is an object-
oriented remote Procedure Call (RPC). As
the name implies, this is included
Invoke a method on a remote object. RMI is
designed to In order to minimize the
difference when using the normal (local)
distant objects. RMI is a Java-based Java
platform independence strains.
Requirements for the implementation of the
RMI You, if you have a client or server
application simple
5.1 RMI interface language
In contrast to the HLA and CORBA or RMI object
is not defined Implement a separate interface
language. On the contrary, Java RMI is using its
own syntax interface Own language object
interface (1997 Java soft, Farley, 1997).
Significantly, which simplifies the design of the
application, since two languages instead of one,
programming? Appears as, by inheriting from
the Java remote interface java. rmi. Remote
interface, a "marker" interface
what method is applied, it should not
the only compiler serves as an identifier. All
methods you need to throw even though they
are defined in the remote interface
or one of its subclasses of java.
5.2 Object Manager
Approach to the implementation of the RMI
remote object basically the same way, such as
CORBA. Each remote Can be compiled
separately, the interface, the client-side stub
and server-side skeleton. User from the
beginning in the development java.rmi.server.
Unicast Remote Object is likely to be lower the
service provides for the remote object Point-to-
point basis. Remote object, the general will the
bottom of the application and hope Unicast
Remote Object Remote interface. And an
instance of the remote object Depending on the
class name using the java.rmi. Naming class in
uniform, we are using a similar system Of
Resource Locator (URL) "name RMI: / / host:
name / object port number."
An important aspect of the Security Manager of
the RMI. When you work with a remote object
contains a potential security Risk that requires
an instance of the RMI One is used to apply the
java.rmi.RM1SecurityManager Security policy.
Responsible for RMISecurityManager when
How to determine whether a local call
Protection for remote and unstable or
Operation. If you do not have an example of
when RMISecurity Manager After you
configures the local machine may only Class
Loaded into the application. It is when
RMISecurityManager Remote operation of all
the other very limited is disabled. However, the
programmer ca defines him instead, the
security manager.
6 COMPARISONS
There are three differences between the
Approaches. Deal of both HLA and CORBA
perhaps the oldest practices in different
languages. The basic approach in order to
provide support for CORBA Communication
layer is compatible with CORJ3A Legacy
applications. CORBA is, it supports a maximum
Can be applied language binding layer,
Appropriate language and optionally you can
work with any CORBA client. Despite HLA If
responsibility for the Java -1, C + +, and Ada
interoperability between federate in different
languages RTI is placed on the practice. This
burden will be added In HLA federation,
implemented in multiple languages
there is no burden of any kind imposed in
contrast to CORBA Regardless of cross-language
compatibility. RMI is an asset Java-based
technology is mainly cross-language All. No Java
program should interoperate
JNI and CORBA interfaces out of the common as
not exist. Nature of Java is cross-platform
capabilities we are increasing the number of
significant platform you can run a distributed
application. General led CORBA and RMI
Applications have been particularly targeted by
HLA I distributed the simulation. As a result,
have HLA Rather than infrastructure; I aimed
directly we are supported by a simulation
model using the rules of Federation.
Specialized services for simulation, and time,
Management. Since the concept of simulation
with each the simulated time, this service is
essential to properly HLA federation function.
Distribution in, but May not be able to even the
idea of CORBA and RMI applications Since the
time that is simulated, it would not make sense
for any of the following This architecture
features such as içerecek.HLA Very strict rules
of legal restrictions are imposed, more
federated RMI and CORBA. For example, all
possible the use of RMI and CORBA Java clients
Communicate with a remote object. Indeed, the
limit CORBA objects, including the ability of
non-CORBA, in some cases, you may require
such a possibility. It offers a subscription service
publishing and HLA, between objects, we do not
support direct communication
Make the RMI and CORBA. Communication
between the the last object in the distance in
one of two possible architectures
is the fact that, quite complex and fascinating
As a result, to enable communication between
objects within less than normal.
The concept of transfer of ownership of the
object of HLA Unique ability of the three
architectures. This ability of certain types of
modeling is a powerful tool Simulation. For
example, people in the model airplane
implementation of the dynamics of the missile
that can carry also, start using the model
provided. Aircraft Start the model, the missile
can have on it Property is transferred to the
missile model. In Instantiated object and RMI
CORBA, by the server each time the server
belongs. Both CORBA and RMI to use a special
communication Protocol for network
transmission. Use the TCPDP RMI,
CORBA is defined, and, on the other hand, the
most common Internet protocols,
Built on top of Internet Inter-ORB Protocol
(IIOP) that Is TCP / IP. On the other hand, HLA is
specified Not a protocol, I leave the choice to
the practice of RTI.
It is unfortunate because it may interfere with
interoperability, that it The RTI applications
from different vendors. In earlier versions, but
did not specify the protocol in the same way
and the CORBA 1.0 ORB implementation
experienced a shortage of such fully
Interoperability. Unique advantage over the
other two RMI Security architecture. As
described above, the RMI Security Manager can
provide malicious code is not available when I
want to access local resources. These are the
class of the JDK You can apply a digital
signature, encryption, and be opened and used
for the transmission of confidential information
I confirm the identity of the sender.
7. CONCLUSIONS
A similar approach RMI HLA, CORBA and
That the distribution is enabled, the computer,
nearly A similar mechanism for the three major
components Naming objects, interface
language, and the Object Manager Service.
Built-in simulation models for situations such as
written in different languages, HLA provides
more mainly due to the correct orientation of
the other two, I offer a service simulation,
simulation-related. If the old Including the
database, perhaps, CORBA Best choice for the
implementation of the service layer
Distributed database information for their
clients. For example the application of RMI, very
new for example, due to an excellent choice
from a close relationship Advantage of Java
language and applications Object-oriented
language.
REFERENCES
Farley, Jim (1997) Java Distributed Computing,
O’Reilly, Cambridge, MA. Java soft, Inc. (1997)
Remote Method Invocation Specification.
Object Management Group (1998) The Common Object
Request Broker: Architecture and Specijkation.
Orfali, Robert and Dan Harkey (1998) Client/Server
Programming with Java and CORBA, John Wiley and
Sons, Inc., New York, NY.US Department of Defense
(1996) High Level Architecture
Object Model Template, IEEE P1516.2.
US Department of Defense (1998) High Level
Architecture IntegaceSpeczjication, Version 1.3 of
IEEE P1516.1, M&S HLA - Federate I/F Spec, DRAFT
1 of 20 April1998.
US Department of Defense (1996) High Level
ArchitectureGlossary.