Three Architectures Comparisons for HLA computing RTI

BY: Zeeshan Rafi([email protected])

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

(JDK). There is an increasing need to decrease
Distributed simulation has become an rapidly
defense budget will do control.
Growing Department of Defense (DOD). In this
That promises to significantly reduce the
article, we shall compare the three different
acquisition and analysis Cost. Simple design for
architectures Support for distributed computing
distributed simulation enhance the re-DOD
HLA, and CORB A, RMI. This is similar to the
various Simulation modeling efforts. Distributed
structure of each base; there are profound
to each of the three architectures computing
differences that might affect Distributed
execution, provides many of the problems
application developer or administrator
distributed the simulation model. Each has a
Simulation exercises.
base effect the structure of his architectural
vision of the world. This article compares the
characteristics of these three Particular
INTRODUCTION focuses on the key technology of their
Impact of distributed simulation. Naturally,
The propose and performance of a distributed
so to cover all aspects of the architecture is
simulation model Has become rapidly growing
impossible Also discussed the salient
Department of Department of Defense(DOD).In
features of each paper. In the next section,
recent years, DOD has invested Critical
we will discuss the core Elements of
resources distributed infrastructure High-level
distributed architecture. 5 and Part 3
simulation of model lemesi . Geçerli focus
Pioneer ede(HLA) defense architecture
I touched the main features HLA, CORBA,
modeling Simulation and office and of In RMI, respectively, and followed
sulfoxide(DMSO)U.S. Department of Energy ( by a brief discussion Comparison of Section6.
Protection, 1998).Human HLA ,most benefits of In Section7, will Ornerier. A results and was
the previous two Efforts of the DOD: Distributed followed by Comparison of Section6. In
Interactive Simulation(DE) And aggregate level 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 of the simulation of I have looked up to fit in the
supported for interoperability with you federation RTI HLA. There I'm in the United
everything you will need to work with others of States (5 federated federation rules 5 and rate
all. rules Department of Defense, 1996a, 1998):
Code of Federal Regulations Federation
3. HLA
(1) Is assumed to have the form of law FOM
High priority to efforts in the Department of Defense
For the development of modeling and simulation
OMT.
(DOD) Level, coercive. High a common technology (2) All expressions the object must be federated
Standard technical architecture for the simulation of It is not and RTI.I
all DOD. It is an important feature consists Elements, (3) during federation of 1 FOM, all exchange
interface specifications and design rulesTo provide the data must go through the RTI.
a common framework for identifying with
Design of the system architecture. HLA is due (4) During the execution of the Federation, all
Processes that have been included government, federates shall interact with one
industry, and academia. HLA has been accepted RTI and interfaces according to the
as a draft standard IEEE Are supported by the specifications.
standard of interoperability of simulation
(5) Between the attributes of the federation
Organization (SISO). HLA is applicable to a wide
execution Can be owned by the federate is only
range of functional areas ranging from training
one instance of an object Time that I was given.
to the acquisition of systems analysis. HLA is
also applicable to simulations of the purely
constructive Federation rules
Representation of software to man-in-loop
simulation to interface to the system and live. (6) The linkage must have a law in the form of
Envision a coalition of design principles HLA SOM OMT.
Simulation consists of modular components
clearly defined functions and interfaces. There (7) Can be used as an attribute update reflected
is a federation Specific combination of rates
federation object model Set and run-time SOM their appropriate data send / receive.
infrastructure (FOM), the federate Service (RTI).
(8) You can now transfer accept Federated Rate
Federate simulation includes U Simulation, live
Property SO Misbased on its ownership in.
player interface. There is RTI I distributed the
(9) You can vary depending on the work
operating system for the federation. Specific
condition They offer the appropriate attribute
the simulation functions are separated
update Their SOM.
intentionally I have generic support.
(10) I would to be able to manage the federated
3.1 HLA Rules local time Data exchange with them to be
coordinated, other members of the Federation.

The first component of the definition of the HLA 3.2 HLA Interface Specification
is the HLA Rules that describe the esponsibilities
The second component of the definition of HLA modify, and Send and receive objects interact
Standard for interface specification to federate with the sample.
dialogue Object data management services have been
RTI (Ministry of Defense of us, 1998). This is the evaluated I offer a distribution management
definition How to access the services of RTI. services. Federated use the services of property
Interface specification management For example, I want to transfer
Are offered in (MI) Application Programming ownership of the attribute. This feature is
Interface CORBA IDL, C + +, Ada95, in many Modeling supports the federation of
ways, including Of Java. Service interface cooperatives. Use the services of Time
specifications are six basic RTI. Management for the federate In order to
Group: Federation Management, Declaration coordinate pre-logical, maintenance
Management, Object management, real estate
3.3 HLA Object Model Template
management, time Management and data
distribution management. Remember The third component of the definition of HLA
Interface Specification "interface" is not object Is a common way for that (OMT) Model
associated with this Language, as described in Template Prescribe the information contained
section 2. within the object of HLA
Federate make use of the services of directors Federation and the United States each
of the Federation Create Delete, dynamic simulation model (Defense, 1996a, 1996b), and.
control, and change Execution of the OMT language interface HLA. Object model
federation. HLA specification for In order to describes a set of shared objects Interaction
avoid the single, participated in the software federation, or attributes of simulation these
system Execution of federated, to a federation objects, the level of detail of the object and its
of more than what You can prevent that Represent the real world, including the space
participate in a single software system and Time resolution. HLA OMT method, which
The Independent Union of the execution of provides a general Concrete framework of the
multiple. Current RTI However, some object model Please refer to the manual.
applications necessarily support I want to set Encouragement simulation OMT
this property. Federation management services, Interoperability and simulation again.
including, Restart checkpoint control, pause, There are two types of object model of the HLA,
resume, and function.
Federated use the services of a management Simulation and federated object model objects
declaration declared their intention to publish (FOMS) Model (solid). Two types of models
and subscribe to appeal Interaction with the have been described I method was used OMT.
attribute. you need to call the federate FOM, which contains all of the information that
Declaration Management services that are pre- has been, shared Need for (interaction of the
recorded Object instance, the attribute value is parameter object, and attributes) I was given
updated, for example Effect of the declaration, the Union. SOM, which contains all of the
send interaction The federation, if you are federal government (Parameter objects,
independent of management. In order to deal attributes, interaction and information)
with the federate, using the Object Visible to all other federates in the federation
Management Service Delete object, record,
and Reflect on the information from other, defined in C + +, IDL Rather than
federates Unity. implementation. In CORBA applications,
The attribute name is part of the state of the Are compiled into one of the subsequent code,
object. Is the object that dispatched the case of IDL is first written Supported languages.
changes in the interaction also objected up, I Elements defined in IDL is as follows:
might cause a change in state. A Then use the generated, implemented in
Parameter information related to the languages that I Code as a basis. Module: IDL
interaction Receiver provided object by sending has four key elements Interface attributes,
object (s).By providing a new instance of the operations, and.
federated update rate, qualification Bundle more than one module is the name
the value of the attribute to change the space and Interface. Interface is a set of
attributes and properties to reflect attributes, Operation that corresponds to the
a new instance of the attribute with a value of object. Mon interface Seen as a contract to
Attribute. Approach to interoperability through implement a defined Operations such as how to
HLA Ability to subscribe to and publish and support the same In order to provide the
attributes Interaction. Discovered through this appropriate type, and the signature and return
cooperation FOM. Is significantly different from Accessory methods that correspond to the
the interaction of the local object attributes. Interface I might define an
for remote interaction, the latter is only inheritance hierarchy. All objects
possible if, I subscribe to the receipt of an must have a method that implements the
attribute change. interface corresponding to the operations and
attributes of the interface Such as those of all
4. CORBA
interfaces that are inherited in the same way.
CORBA is a non-commercial venture by Object Multiple has been supported interface
Consortium Management Group (OMG), more inheritance, can not be inherited from the
than 800 Members of management was interface of the two interface has
established in 1989 (object Group, 1998; Haki or attributes of the same name for the
and Orfali, 1998). It is the oldest and I was operation. CORBA We specifies that it is
probably the most mature of the three possible to have only one object interface 2.0.
architectures we please consider in this paper. However, to support CORBA 3.0 proposal has
CORBA is very large, Collection of protocol been made multiple interfaces.
specifications and complex, and the inner these Correspond to instance variables, attributes,
short paper, we can almost touch Earl Is used to represent the data. Attributes are
Prominent feature. the basic types of either Object reference type,
or has been constructed. Basic possible
Int primitive data types and normal (long, type
4.1 CORBA interface language is short type float, double, type Boolean, etc.).
Constructed types almost Correspond to those
available in, C + +. Struct can be been defined
CORBA interface language program Interface
using the type def. Corresponds to the
Definition Language (IDL). The IDL syntax is as
sequence Variable-length array. Finally, for each
follows. Essentially, except for the interface
type of use I represent all the required data. It is
strong and what represents the data in a Conceptual entity of ORB stuff in fact, the client
flexible way, it is self describing. and the server object is configured by software
Be used to call methods on an object reference Are present in both the client and server
you can be placed on the object. IDL is not machines. What Client request object, the
specified, it is a property in many cases, the message goes to the first ORB His machine.
implementation of accessor methods, it will be Client ORB set ORB to communicate with the
used instead Provides direct access to instance server. Server ORB, it returns a reference to an
variables. Moment Attributes are read-only or object of interest to pass to the customer
read and identify Written. returns the ORB Client. This is transparent to
The process corresponds to the process, the program, it does not mean each
are defined to retu method name, signature participating applications to CORBA objects
and Types. A transaction is defined as an ORB software is installed on the machine where
independent Whether INOUT IN, or OUT, I must not exist.
according to the argument, from the calling
object that was passed to the object called Both static and dynamic tools for CORBA
Call the object, called object or both. Server that provides remote object. Static
CORBA CORBA is a language-independent way method each contains a "stub" of the client and
can be implemented either by the server and the server the actual object on the server
the client without the languages that are interface. Server stub you will be referred to as
supported, and I can work together a "frame" in many cases. Bolt connection of the
but I know each other's language. More object, ORB will generate a machine and
importantly, the There is no need to check any generally, this IDL, the modeler is - it's not
participant under the assumption CORBA necessarily writing a call to the ORB. To
CORBA applications in other languages implement a distributed object in this way, one
the client and the server. The following begins with the class of IDL Skeleton code only
languages are currently supported Java C, C + +, while the server is used, will only be used to
Smalltalk, Ada, and COBOL are. Definition stub code Client. But please do not need the
Interface of a class is an important element of stubs and skeletons in the same language, so
this instead standing in the language. that all communication takes place via,
ORB. For example, an object in C + + may
be a server Java IDL client stubs, you
2.4 CORBA Object Manager created yourself. Importantly,
any addition, customers have to make a
There is a CORBA Object Request Object
Manager Broker (ORB). The ORB allows objects
server Assumptions about other languages.
to send, Whether or not to receive the object,
the message they are a local or remote. All 3.4 CORBA Naming Service
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 It does not require the use of static each
methods of the intent. client stub I wanted to be a special code for
the remote object Created before the remote
object can be compiled was obtained. Support the four that are included in the
CORBA is providing dynamic invocation RMI Separated by JDK1.l, sparse
In order to avoid the need for (DII) stub distribution of packages and to identify the
interface that has been precompiled. remote object (via a "marker" interface),
Remote object is "discovered" for the first Distance to throw an exception when
time using the DII client is one of several recording a distant subject;
mechanisms. In addition, the interface Performance of remote objects and remote
Customers to determine the object so as to waste services Collection. RMI is an object-
obtain you want to invoke a method. oriented remote Procedure Call (RPC). As
Information about how to (After the the name implies, this is included
exception is thrown, and the type argument Invoke a method on a remote object. RMI is
list, return) was obtained. Outgoing sent a designed to In order to minimize the
request to create if you call this method on difference when using the normal (local)
the remote object. distant objects. RMI is a Java-based Java
platform independence strains.
Requirements for the implementation of the
Create an interface repository that contains RMI You, if you have a client or server
the server Dynamic interfaces can be application simple
accessed from the client. Moment
the interface can be scanned in order to find 5.1 RMI interface language
the repository class it has been fascinated by
the client. Interface, including tanks
In contrast to the HLA and CORBA or RMI object
was exposed to the object's IDL.
is not defined Implement a separate interface
CORBA client and server, the execution of a
language. On the contrary, Java RMI is using its
single Local area communication network
own syntax interface Own language object
(LAN), more or less Automatic. ORB on
interface (1997 Java soft, Farley, 1997).
each machine software because usually
Significantly, which simplifies the design of the
considered to explore all the other spheres
application, since two languages instead of one,
on the LAN Transparent for each customer. programming? Appears as, by inheriting from
CORBA Provides the ability to the Java remote interface java. rmi. Remote
communicate with the ball on the interface, a "marker" interface
using the Internet Inter-ORB Protocol what method is applied, it should not
different LAN (IIOP), TCP / IP is extended. the only compiler serves as an identifier. All
methods you need to throw even though they
are defined in the remote interface
5. RMI
or one of its subclasses of java.

5.2 Object Manager

Start of Java Development Kit 1.1 (JDK
1.1), Contains a remote Java programming
language as part of the standard Java method Approach to the implementation of the RMI
invocation (RMI) Library (Java soft, 1997). remote object basically the same way, such as
CORBA. Each remote Can be compiled Appropriate language and optionally you can
separately, the interface, the client-side stub work with any CORBA client. Despite HLA If
and server-side skeleton. User from the responsibility for the Java -1, C + +, and Ada
beginning in the development java.rmi.server. interoperability between federate in different
Unicast Remote Object is likely to be lower the languages RTI is placed on the practice. This
service provides for the remote object Point-to- burden will be added In HLA federation,
point basis. Remote object, the general will the implemented in multiple languages
bottom of the application and hope Unicast there is no burden of any kind imposed in
Remote Object Remote interface. And an contrast to CORBA Regardless of cross-language
instance of the remote object Depending on the compatibility. RMI is an asset Java-based
class name using the java.rmi. Naming class in technology is mainly cross-language All. No Java
uniform, we are using a similar system Of program should interoperate
Resource Locator (URL) "name RMI: / / host: JNI and CORBA interfaces out of the common as
name / object port number." not exist. Nature of Java is cross-platform
An important aspect of the Security Manager of capabilities we are increasing the number of
the RMI. When you work with a remote object significant platform you can run a distributed
contains a potential security Risk that requires application. General led CORBA and RMI
an instance of the RMI One is used to apply the Applications have been particularly targeted by
java.rmi.RM1SecurityManager Security policy. HLA I distributed the simulation. As a result,
Responsible for RMISecurityManager when have HLA Rather than infrastructure; I aimed
How to determine whether a local call directly we are supported by a simulation
Protection for remote and unstable or model using the rules of Federation.
Operation. If you do not have an example of Specialized services for simulation, and time,
when RMISecurity Manager After you Management. Since the concept of simulation
configures the local machine may only Class with each the simulated time, this service is
Loaded into the application. It is when essential to properly HLA federation function.
RMISecurityManager Remote operation of all Distribution in, but May not be able to even the
the other very limited is disabled. However, the idea of CORBA and RMI applications Since the
programmer ca defines him instead, the time that is simulated, it would not make sense
security manager. for any of the following This architecture
features such as içerecek.HLA Very strict rules
6 COMPARISONS of legal restrictions are imposed, more
federated RMI and CORBA. For example, all
There are three differences between the possible the use of RMI and CORBA Java clients
Approaches. Deal of both HLA and CORBA Communicate with a remote object. Indeed, the
perhaps the oldest practices in different limit CORBA objects, including the ability of
languages. The basic approach in order to non-CORBA, in some cases, you may require
provide support for CORBA Communication such a possibility. It offers a subscription service
layer is compatible with CORJ3A Legacy publishing and HLA, between objects, we do not
applications. CORBA is, it supports a maximum support direct communication
Can be applied language binding layer, Make the RMI and CORBA. Communication
between the the last object in the distance in
one of two possible architectures for the transmission of confidential information
is the fact that, quite complex and fascinating I confirm the identity of the sender.
As a result, to enable communication between
objects within less than normal.
7. CONCLUSIONS

The concept of transfer of ownership of the

object of HLA Unique ability of the three A similar approach RMI HLA, CORBA and
architectures. This ability of certain types of That the distribution is enabled, the computer,
modeling is a powerful tool Simulation. For nearly A similar mechanism for the three major
example, people in the model airplane components Naming objects, interface
implementation of the dynamics of the missile language, and the Object Manager Service.
that can carry also, start using the model Built-in simulation models for situations such as
provided. Aircraft Start the model, the missile written in different languages, HLA provides
can have on it Property is transferred to the more mainly due to the correct orientation of
missile model. In Instantiated object and RMI the other two, I offer a service simulation,
CORBA, by the server each time the server simulation-related. If the old Including the
belongs. Both CORBA and RMI to use a special database, perhaps, CORBA Best choice for the
communication Protocol for network implementation of the service layer
transmission. Use the TCPDP RMI, Distributed database information for their
CORBA is defined, and, on the other hand, the clients. For example the application of RMI, very
most common Internet protocols, new for example, due to an excellent choice
Built on top of Internet Inter-ORB Protocol from a close relationship Advantage of Java
(IIOP) that Is TCP / IP. On the other hand, HLA is language and applications Object-oriented
specified Not a protocol, I leave the choice to language.
the practice of RTI. REFERENCES

Farley, Jim (1997) Java Distributed Computing,

O’Reilly, Cambridge, MA. Java soft, Inc. (1997)
It is unfortunate because it may interfere with
Remote Method Invocation Specification.
interoperability, that it The RTI applications
from different vendors. In earlier versions, but Object Management Group (1998) The Common Object
Request Broker: Architecture and Specijkation.
did not specify the protocol in the same way Orfali, Robert and Dan Harkey (1998) Client/Server
and the CORBA 1.0 ORB implementation
Programming with Java and CORBA, John Wiley and
experienced a shortage of such fully
Sons, Inc., New York, NY.US Department of Defense
Interoperability. Unique advantage over the (1996) High Level Architecture
other two RMI Security architecture. As
Object Model Template, IEEE P1516.2.
described above, the RMI Security Manager can US Department of Defense (1998) High Level
provide malicious code is not available when I Architecture IntegaceSpeczjication, Version 1.3 of
want to access local resources. These are the IEEE P1516.1, M&S HLA - Federate I/F Spec, DRAFT
1 of 20 April1998.
class of the JDK You can apply a digital
signature, encryption, and be opened and used US Department of Defense (1996) High Level
ArchitectureGlossary.