1 / 21

CORBA: Distributed Object Technologies

Explore the history, goals, and components of CORBA, including CORBA RMI, CORBA services, and the distributed whiteboard example. Understand how to use the IDL to map CORBA interfaces to different programming languages.

dgoodsell
Download Presentation

CORBA: Distributed Object Technologies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Organizational Communications and Distributed Object Technologies Lecture 13: CORBA Master of Information System Management

  2. CORBA Chapter 20 Coulouris text Master of Information System Management

  3. Today’s Topics • CORBA History and goals • CORBA RMI • CORBA services • The Distributed Whiteboard Revisited Master of Information System Management

  4. CORBA History and Goals • Object Management Group Formed in 1989 • Goals: -- OOP on distributed systems -- heterogeneous hardware -- heterogeneous OS -- different programming languages Master of Information System Management

  5. History and Goals • OMG Introduced the Object Request Broker (ORB) • The role of the ORB is to help a client find an object, activate the object if necessary, and call a method on the object. • Common Object Request Broker Architecture (CORBA) agreed to by a group of companies in 1991 • CORBA 2.0 specification released in 1996 Master of Information System Management

  6. History and Goals • CORBA 2.0 specification defined standards for different implementations of CORBA to communicate with one another • These standards are called the General Inter-ORB protocol (GIOP) and may run over various transports • GIOP over TCP/IP is called the Internet Inter-ORB Protocol Master of Information System Management

  7. CORBA RMI • Main components -- An Interface Definition language (IDL) that promotes the use of different programming languages, stubs are generated in the client’s language and skeletons are generated in the server’s language -- An architecture -- GIOP defines an external data representation (CDR) as well as message formats and message types -- Message types include request and reply as well as location requests, errors, and request cancellations Master of Information System Management

  8. CORBA Services • A set of generic services that can be used for distributed application -- Naming Service (location by name) -- Trading Service (location by attribute - directory service) -- Event Service -- Security Service (authentication, ACL’s, auditing, non- repudiation) -- Transaction Service (begin, commit, rollback a series of RMI calls using the Two Phase Commit Protocol) -- Persistent Object Service (POS) Master of Information System Management

  9. The Distributed Whiteboard Example in CORBA Master of Information System Management

  10. IDL Interfaces Shape and ShapeList struct Rectangle{ // no class in IDL 1 long width; long height; long x; long y; } ; struct GraphicalObject { 2 string type; Rectangle enclosing; boolean isFilled; }; interface Shape { 3 long getVersion() ; GraphicalObject getAllState() ; // returns state of the GraphicalObject }; typedef sequence <Shape, 100> All; // All is a 100 element array 4 interface ShapeList { 5 exception FullException{ }; 6 Shape newShape(in GraphicalObject g) raises (FullException); 7 All allShapes(); // returns sequence of remote object references 8 long getVersion() ; // parameters are in, out, or both }; // parameters may be primitive, struct or array and // are passed by value // parameters whose type is an IDL interface // is passed by remote reference Master of Information System Management

  11. The “idltojava” tool • Run idltojava on the above interface. • The command idlj is found in j2sdk1.4.2\bin. • The Java 2 Platform, Standard Edition, v1.4, provides an Object Request Broker (ORB) runtime component. • The JDK documentation states that its Java ORB has not been tested with ORB’s written in other languages. • JDK 1.4 provides an Orb class with a pluggable architecture. Master of Information System Management

  12. From IDL to Your Language of Choice The OMG specifies a mapping from IDL to several different programming languages, including Java, C, C++, Lisp, Python, Smalltalk, COBOL, and Ada. When mapped, statements in the OMG IDL are translated to corresponding statements in the programming language of choice. From JDK Documentation The IDL and the IDL compiler give CORBA its interoperability. IDL IDL Compiler Proxy Quiz: How does this compare with Web Services? Master of Information System Management

  13. Java Interface ShapeList Generated by idltojava from CORBA Interface ShapeList public interface ShapeList extends org.omg.CORBA.Object { Shape newShape(GraphicalObject g) throws ShapeListPackage.FullException; Shape[] allShapes(); int getVersion(); } Master of Information System Management

  14. ShapeListServant.java Written by a Java Developer import org.omg.CORBA.*; class ShapeListServant extends _ShapeListImplBase { ORB theOrb; private Shape theList[]; private int version; private static int n=0; public ShapeListServant(ORB orb){ theOrb = orb; // initialize the other instance variables } public Shape newShape(GraphicalObject g) throws ShapeListPackage.FullException { 1 version++; Shape s = new ShapeServant( g, version); if(n >=100) throw new ShapeListPackage.FullException(); theList[n++] = s; 2 theOrb.connect(s); return s; } public Shape[] allShapes(){ ... } public int getVersion() { ... } } Note how it talks to the CORBA Object Request Broker. Master of Information System Management

  15. ShapeListServer.java import org.omg.CosNaming.*; import org.omg.CosNaming.NamingContextPackage.*; import org.omg.CORBA.*; public class ShapeListServer { public static void main(String args[]) { try{ ORB orb = ORB.init(args, null); 1 ShapeListServant shapeRef = new ShapeListServant(orb); 2 orb.connect(shapeRef); 3 org.omg.CORBA.Object objRef = orb.resolve_initial_references("NameService"); 4 NamingContext ncRef = NamingContextHelper.narrow(objRef); NameComponent nc = new NameComponent("ShapeList", ""); 5 NameComponent path[] = {nc}; 6 ncRef.rebind(path, shapeRef); 7 java.lang.Object sync = new java.lang.Object(); synchronized (sync) { sync.wait();} } catch (Exception e) { ... } } } Note the call on rebind. Master of Information System Management

  16. ShapeListClient.java import org.omg.CosNaming.*; import org.omg.CosNaming.NamingContextPackage.*; import org.omg.CORBA.*; public class ShapeListClient{ public static void main(String args[]) { try{ ORB orb = ORB.init(args, null); 1 org.omg.CORBA.Object objRef = orb.resolve_initial_references("NameService"); NamingContext ncRef = NamingContextHelper.narrow(objRef); NameComponent nc = new NameComponent("ShapeList", ""); NameComponent path [] = { nc }; ShapeList shapeListRef = ShapeListHelper.narrow(ncRef.resolve(path)); 2 Shape[] sList = shapeListRef.allShapes(); 3 GraphicalObject g = sList[0].getAllState(); 4 } catch(org.omg.CORBA.SystemException e) {...} } Note the use of Java interfaces and classes that were generated by idltojava. These are not dynamic calls. The compiler sees the interfaces and classes. Master of Information System Management

  17. server client implementation interface repository repository skeleton object adapter Request ORB client proxy Servant ORB program for A core A core Reply or dynamic invocation or dynamic skeleton CORBA Architecture (1) CORBA allows for static and dynamic invocation. Applications may invoke operations on target objects with or without having compile-time knowledge of the remote object interface. (The client is a lot easier to read when it makes static calls.) Master of Information System Management

  18. server client implementation interface repository repository skeleton object adapter Request ORB client proxy Servant ORB program for A core A core Reply or dynamic invocation or dynamic skeleton CORBA Architecture (2) The Implementation Repository contains information that allows the ORB to locate and activate implementations of objects. The implementation repository : 1. Maintain a registry of known servers. 2. Record which server is currently running, and which port and host it uses. 3. Starts servers on demand if they are registered with the Implementation Repository.From [http://www.dre.vanderbilt.edu/~schmidt/DOC_ROOT/TAO/ docs/implrepo/paper.html] Master of Information System Management

  19. server client implementation interface repository repository skeleton object adapter Request ORB client proxy Servant ORB program for A core A core Reply or dynamic invocation or dynamic skeleton CORBA Architecture (3) Dynamic CORBA applications require a means of obtaining type information at run time. This is the function of the Interface Repository. Master of Information System Management

  20. Naming Graph in CORBA Naming Service initial naming context initial naming context initial naming context XX B ShapeList V P C T D E S R Q U CORBA provides a registry service and a directory service. Quiz: How does a registry differ from a directory? Quiz: How is this different from the rmiregistry? Master of Information System Management

  21. My Summary Master of Information System Management

More Related