Enterprise Application Development-Enterprise Applicatio Development-Lecture Handout, Exercises of Software Development

This lecture handout was provided by Sir Aabher Dutt at Indian Institute of Space Science and Technology for Enterprise Application Development course. It includes: Enterprise, Application, Development, Common, Object, Request, Broker, Architecture, Interface, Language

Typology: Exercises

2011/2012

Uploaded on 07/19/2012

pankti
pankti 🇮🇳

4.1

(8)

39 documents

1 / 4

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Enterprise Application Development
CORBA & ORBIX
Page 1 of 4
In Modern era of computation, distributed applications are highly used. For the
following scenarios, an application must be distributed
1. Data used by the application must be distributed
2. Computation is distributed
3. Users of the application are distributed
Distributed clients or users interact with each other through objects. They may face
many problems during interaction to web server e.g.; Different Plateform and more
than one server(Load balancing) etc.
To cope with these problems, there are many middleware introduced. CORBA is one of
them.
CORBA
CORBA is acronym for Common Object Request Broker Architecture.”It is a standard
defined by the Object Management Group(OMG) that enables software components
written in multiple computer languages and running on multiple computers to work
together (i.e., it supports multiple platforms)”*1+
According to CORBA specification, an ORB is mandatory to interact with objects. In
practice, the application simply initializes the ORB, and accesses an internal Object
Adapter, which maintains things like reference counting, object (and reference)
instantiation policies, and object lifetime policies. The Object Adapter is used to register
instances of the generated code classes. Generated code classes are the result of
compiling the user IDL code, which translates the high-level interface definition into an
OS- and language-specific class base for use by the user application. This step is
necessary in order to enforce CORBA semantics and provide a clean user process for
interfacing with the CORBA infrastructure.
interface definition language (IDL)
CORBA uses an interface definition language (IDL) to specify the interfaces which
objects present to the outer world. A CORBA implementation comes with a tool called
docsity.com
pf3
pf4

Partial preview of the text

Download Enterprise Application Development-Enterprise Applicatio Development-Lecture Handout and more Exercises Software Development in PDF only on Docsity!

Page 1 of 4

In Modern era of computation, distributed applications are highly used. For the following scenarios, an application must be distributed

  1. Data used by the application must be distributed
  2. Computation is distributed
  3. Users of the application are distributed

Distributed clients or users interact with each other through objects. They may face many problems during interaction to web server e.g.; Different Plateform and more than one server(Load balancing) etc. To cope with these problems, there are many middleware introduced. CORBA is one of them.

CORBA

CORBA is acronym for Common Object Request Broker Architecture .”It is a standard defined by the Object Management Group(OMG) that enables software components written in multiple computer languages and running on multiple computers to work together (i.e., it supports multiple platforms)”*1+ According to CORBA specification, an ORB is mandatory to interact with objects. In practice, the application simply initializes the ORB, and accesses an internal Object Adapter , which maintains things like reference counting, object (and reference) instantiation policies, and object lifetime policies. The Object Adapter is used to register instances of the generated code classes. Generated code classes are the result of compiling the user IDL code, which translates the high-level interface definition into an OS- and language-specific class base for use by the user application. This step is necessary in order to enforce CORBA semantics and provide a clean user process for interfacing with the CORBA infrastructure.

interface definition language (IDL)

CORBA uses an interface definition language (IDL) to specify the interfaces which objects present to the outer world. A CORBA implementation comes with a tool called

Page 2 of 4

an IDL compiler which converts the user's IDL code into some language-specific generated code. A traditional compiler then compiles the generated code to create the linkable-object files for the application. This diagram illustrates how the generated code is used within the CORBA infrastructure.

CORBA Component Model

CORBA Component Model (CCM) is an addition to the family of CORBA definitions. It was introduced with CORBA 3 and it describes a standard application framework for CORBA components. Though not dependent on "language independent Enterprise Java Beans (EJB)", it is a more general form of EJB, providing four component types instead of the two that EJB defines. It provides an abstraction of entities that can provide and accept services through well-defined named interfaces called ports.

ORBIX

Architecture

Orbix includes an Object Request Broker (ORB) that presents an abstraction layer that relieves the programmer of dealing with many of the complexities of network

Page 4 of 4

The following security standards are supported by the Orbix Security Service:

  1. Secure Sockets Layer /Transport Layer Security (SSL/TLS)
  2. CCITT X.509, which governs the form of security certificates based on public (asymmetric) key systems
  3. OMG Common Secure Interoperability specification, version 2 (CSIv2)
  4. Security Assertion Markup Language (SAML) HIGH AVAILABILITY OF ORBIX SERVICES THROUGH REPLICATION CLUSTERING One of the most powerful features in Orbix is its server clustering architecture. With server clustering, it is possible to group together multiple physical servers—each of which may be running on a different machine into a single logical server. To clients using the server, the appearance is that of a single server process, but the Orbix infrastructure distributes invocations across the set of server processes in the cluster.