DOC PREVIEW
Berkeley COMPSCI 294 - Distributed Service Architectures

This preview shows page 1-2-14-15-29-30 out of 30 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 30 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Distributed Service ArchitecturesOutlineOverviewCORBAObject Interoperability – CORBA StyleCommunicationCORBA ORB ArchitectureCORBAservicesCORBAservices (continued)JINIJini – An OverviewKey ConceptsDiscoveryLookupDiscovery and LookupSlide 16Slide 17Slide 18PowerPoint PresentationSlide 20Slide 21LeasingRemote EventTransactionsOther issuesOther issues (continued)SummaryJini Surrogate ArchitectureCORBA Interoperable Object Reference (IOR)Binding of a persistent referenceDistributed Service ArchitecturesYitao [email protected]/19/2002OutlineOverviewCORBAJINISummaryOverviewHow different entities communicate with each other?How is a service discovered by client?How does the system adapt to faults?How is security addressed?Mobility? Scalability?CORBAThe OMG grew out of the object technology boom of the 1980s. Its founders were Data General, Hewlett-Packard, and Sun. Today some 800 (and growing) companies comprise the OMG. Together these companies have created and continue to create standards for object-oriented computingCORBA 1.0 (October 1991)CORBA 3.0 -- Pre-release Spring 1999, Commercial release late 1999Object Interoperability – CORBA StyleAll about Objects -Common Object Request Broker ArchitectureInterface defined in Interface Definition Language (IDL)A contract between objectsMarshaling/unmarshaling arguments and results.Independent of implementation. Heterogeneous language support, mapped to C, C++, Java, COBOL, Smalltalk, Ada, Lisp, Python etc.Objects live within server and are passed by referenceCommunicationORB1StubClientSkelObjectORB2StubClientSkelObjectIIOPOBR: Object Request BrokerCORBA ORB ArchitectureDII: Dynamic Invocation InterfaceDSI: Dynamic Skeleton InterfacePOA: Portable Object AdapterORB CoreClientDIIClient StubsORB InterfaceImpl SkeletonsDSIPOAObject ImplementationOBJ REFCORBAservicesOMG published 17 object servicesNaming ServiceAssociation of names to objectsLocate components by nameTrader Service – Object Yellow PageMatch services by type and propertiesConcurrency Control ServiceA lock manager for transaction or threadsCORBAservices (continued)Transaction Service2PC among recoverable components Flat or nested transactionsSecurity Serviceauthentication, access control, message protection, audit, non-repudiation, security managementJINIJini technology was publicly released on January 25, 1999.Current Release:Jini Technology Starter Kit v 1.2 (released 12/2001) http://developer.java.sun.com/developer/products/jini/Jini – An OverviewService centeredFulfillment of original Java vision – groups of devices exchanging data and code.The Jini vision: Networkanything, anytime, anywhere!Built on top of JavaN e t w o r k T r a n s p o r tO p e r a t i n g S y s t e mJ a v a T e c h n o l o g yJ i n i T e c h n o l o g yS e r v i c eA p p l i c a t i o nKey ConceptsDiscoveryLookupLeasingRemote EventsTransactionsDiscoveryProcess used to find communities on the network and join themEnable spontaneous Jini community-building= finding (and joining) lookup servicesProtocolsMulticast Request ProtocolMulticast Announcement ProtocolUnicast Discovery ProtocolLookupEnables a client to find a particular srvcMaintains a list of Service Items.Service Item = Downloadable proxy object + AttributesSearchable by object type, ID, or attributesServices join the lookup servicesClients download proxy objects and request service from themProxy: performs …Discovery and LookupJini Lookup ServiceJini ServiceJini ServiceDiscovery and LookupJini Lookup ServiceJini ServiceJini ServiceDiscovery and LookupJini Lookup ServiceJini ServiceJini ServiceProxy CodeProxy CodeDiscovery and LookupJini Lookup ServiceJini ServiceJini ServiceProxyAttributeAttributeAttributeProxyAttributeAttributeAttributeJini Lookup ServiceJini ServiceJini ServiceProxyAttributeAttributeAttributeProxyAttributeAttributeAttributePDAJini ClientDiscovery and LookupDiscovery and LookupJini Lookup ServiceJini ServiceJini ServiceProxy CodeProxyAttributeAttributeAttributeProxyAttributeAttributeAttributePDAJini ClientDiscovery and LookupJini Lookup ServiceJini ServiceJini ServiceProxy CodeProxyAttributeAttributeAttributeProxyAttributeAttributeAttributePDAJini ClientLeasingEnables Jini’s stable, self-healing, self-adapting nature.Acknowledges explicitly the fact that network is transientResources are allocated for a specific time period. If the resource is needed longer, the client must renew the lease, demonstrating its continued need.Remote EventProvide asynchronous notifications to Jini clients and servicesAdhere to Jini leasing so that event generation can survive the transient nature of clients on a network.TransactionsJini’s mechanism for allowing computations that may involve multiple services to reach a “safe” stateProtects against partial failureHelp address concurrency problemsOther issuesFault tolerance - Multiple lookup services in a community (also for load balancing)Mobility Discovery and lookup support spontaneous form of communities Leasing clears the system off any stale informationScalabilityLookup services are servicesSupporting multiple communitiesOther issues (continued)SecurityDistributed computing makes the issue tougherJini doesn’t provide additional security mechanismRelies on Java 2 securityBeing worked onSummaryCORBALow level primitives for distributed computingLanguage independentPass remote object by referencesNetwork transparentJiniFlexible framework for building complex distributed systemsLanguage-specific, OS independentPass remote object by value (instances)Network awareJini Surrogate ArchitectureCategory 1Category 2(MIDP, PersonalJava)Category 3 (J2ME CVM w/RMI Profile)Service NService 2Jini Lookup ServiceJini client #1Jini client #2Jini client #nPDATelephoneFaxPagerTV set-top boxVCRGateway ServiceProviderService 1InternetGateway ServerCORBA Interoperable Object Reference (IOR)Type Name (Repository ID)Protocol and Address DetailsObject Key (Adapter & Object Name)CORBA Interoperable Object Reference (IOR)Binding of a persistent


View Full Document

Berkeley COMPSCI 294 - Distributed Service Architectures

Documents in this Course
"Woo" MAC

"Woo" MAC

11 pages

Pangaea

Pangaea

14 pages

Load more
Download Distributed Service Architectures
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Distributed Service Architectures and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Distributed Service Architectures 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?