This preview shows page 1-2-3-4-5-6-7-8-57-58-59-60-61-62-63-64-115-116-117-118-119-120-121-122 out of 122 pages.
Enterprise Computing and InteroperabilityOverview of PresentationWhat is Enterprise Computing?Role of an Object Request Broker (ORB)Interface Definition Language, IDLORB and High Level View of RequestsCORBA Components and InterfacesInterfacesClient SideObject Implementation SideDynamic Invocation Interface (DII)Request ComponentsRepositories: Interface and ImplementationThree Types of ORBsSlide 15Three Types of ImplementationsSlide 17System Design with CORBASlide 19Slide 20IDL: Modules and InterfacesIDL: Basic TypesIDL: Complex TypesIDL: Complex Types (cont.)IDL Example: GUIIDL Example: ServerObject Management ArchitectureCORBAservicesNaming ServiceNaming GraphCosNamingModuleEvent ServiceEvent Service Design PrinciplesPush ModelPull ModelEvent ChannelsEvent Channels (cont.)Typed Event CommunicationTypedPushConsumerTyped Event ExampleTyped Event Example (cont.)Class DiagramComponent Diagram: Source FilesComponent Diagram: ExecutablesCollaboration DiagramDeployment Diagram (degenerate)Design ConsiderationsReferencesConcluding RemarksInteroperability StrategiesArchitectural Alternatives & FrameworkJava Client to Legacy App via RDBSORB Integration of Java Client and Legacy ApplicationJava Client with Wrapper to Legacy ApplicationOne COTS and One Legacy Application to Java ClientsADAM: User PerspectiveCase Study: The ADAM EnvironmentCharacterizing ADAM Software ProfileADAM: Current Software ArchitectureClient Requirements and FunctionalitiesSlide 61ADAM: Target Software ArchitectureWrapper Requirements and FunctionalitiesADAM: Client/Wrapper ComponentsADAM: Java to C++ WrapperCommunication Requirements and FunctionalitiesADAM: Socket CommunicationsTwinPeaks Requirements and FunctionalitiesADAM: TwinPeaks ArchitectureStatus of TwinPeaks EffortSlide 71Assessment of TwinPeaks ProductSlide 73Slide 74Slide 75Slide 76Slide 77Slide 78Slide 79Slide 80Concluding Remarks and DiscussionSlide 82Java Beans and Enterprise Java BeansChanging PerspectivesComponentsOverviewJava BeansSlide 88What are Enterprise Java Beans ?Designer and Developer Roles in Enterprise Java Beans (EJB)EJB Roles & DeploymentUtilizing EJB TechnologyThe EJB ArchitectureEJB ContainerEnterprise Java APIsEnterprise Java Beans Session BeansEnterprise Java Beans Entity BeansModel for Persistence Passivation/ActivationStateless vs. Stateful Session BeansEntity Bean PersistenceDeploying EJBsWho’s Announced EJB Support?Typical Development and Deployment ScenarioEJB Component-Based ArchitectureClient-Server Component ModelTwo-Tier, Three-Tier, Four-Tier Example ArchitecturesWombat SecuritiesFour-Tier Architecture ExampleNocturnal Aviation, Inc.Three-Tier ExampleSanta Cruz WidgetsSanta Cruz Widgets (2-tier)Architecture ComparisonsFurther API ComparisonsSummary & Key MessagesEJB RoadmapWhat Is the Java Blend Product?JavaBlend ApplicationsJava Blend ComponentsJava Blend Runtime ArchitectureJava Blend Software and Enterprise JavaBeans TechnologyConcluding Remarks Enterprise Computing/InteroperabilityECIC-1.1CSE298 CSE300CSE300Enterprise Computing and InteroperabilityProf. Steven A. DemurjianComputer Science & Engineering DepartmentThe University of Connecticut191 Auditorium Road, Box U-155Storrs, CT [email protected]://www.engr.uconn.edu/~steve(860) 486 - 4818† Special Thanks to Prof. Alex Shvartsman and Scott Craig for providing portions of this material.ECIC-1.2CSE298 CSE300CSE300Overview of PresentationOverview of PresentationWhat is Enterprise Computing?What is Enterprise Computing?Interoperability and CORBAInteroperability and CORBAPrimerKey Concepts and IdeasSystem Design with CORBA/IDLInteroperability StrategiesInteroperability StrategiesGeneral ApproachesJava-Based WrapperSecurity Issues for Enterprise ComputingSecurity Issues for Enterprise ComputingWhat are Key Issues re. Security for EC?How are Legacy/COTS Handled?Concluding RemarksConcluding RemarksECIC-1.3CSE298 CSE300CSE300What is Enterprise Computing?What is Enterprise Computing?Today’s and Tomorrows Applications are System Today’s and Tomorrows Applications are System of Systemsof SystemsFacilitate Interactions/Information ExchangeLeverage Existing Information, Resources, and Applications in New EnvironmentInteroperability Key IssueStrive for New/Innovative Application Usage in Strive for New/Innovative Application Usage in Distributed Environment - For Example …Distributed Environment - For Example …Expand to Multi-User CapabilitiesIncorporate Modern GUI Introduce Useful FunctionalityUpgrade to Web-Based AccessECIC-1.4CSE298 CSE300CSE300ClientApplicationObjectImplementationORBRole of an Object Request Broker (ORB)Role of an Object Request Broker (ORB)ORB Provides the Underlying Infrastructure for ORB Provides the Underlying Infrastructure for Supporting Interoperating Software Systems Supporting Interoperating Software Systems (Applications) Composed of Distributed Objects(Applications) Composed of Distributed ObjectsORB Provides the Basic Request DeliveryORB Provides Interface DefinitionsLocation is Transparent to the Caller and Object Location is Transparent to the Caller and Object ImplementationImplementationCaller and the Object Implementation Can be in the Caller and the Object Implementation Can be in the Same Process thru Opposite Sides of the WorldSame Process thru Opposite Sides of the WorldORB Manages Local Location and OptimizationORB Manages Local Location and OptimizationECIC-1.5CSE298 CSE300CSE300Interface Definition Language, IDLInterface Definition Language, IDLKey Component of CORBA Is the Interface Key Component of CORBA Is the Interface Definition Language, IDLDefinition Language, IDLMapping is Available in C, C++, Java, Ada, Etc. IDL Is Independent of Any Language/CompilerMultiple InheritancePublic Interface OrientedNot for ImplementationPrimary Support for Interoperability Between Primary Support for Interoperability Between Static and Dynamic Request MechanismsStatic and Dynamic Request MechanismsECIC-1.6CSE298 CSE300CSE300ClientApplicationObjectImplementationORBObject reference Object dispatcherIDL BoundaryObject CallIDL BoundaryMethods and DataRequestORB and High Level View of RequestsORB and High Level View of RequestsThe Request Consists ofThe Request Consists ofTarget ObjectOperation (Method)ParametersRequest Context (Optional)ECIC-1.7CSE298 CSE300CSE300ObjectAdapterORB CoreOne interfaceOne
View Full Document
Unlocking...