DOCSLIB.ORG

Getting Started with Websphere Application Server

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Getting Started with Websphere Application Server WebSphere® Application Server Getting Started with WebSphere Application Server Ve r s i o n 4 .0 SC09-4581-01 WebSphere® Application Server Getting Started with WebSphere Application Server Ve r s i o n 4 .0 SC09-4581-01 Note Before using this information and the product it supports, be sure to read the general information under “Notices” on page 95. Second Edition (June 2001) This edition replaces SC09-4581-00. Order publications through your IBM representative or through the IBM branch office serving your locality. © Copyright International Business Machines Corporation 1999, 2001. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures..............v Component models and related technologies 21 Java 2™ Platform Enterprise Edition Tables..............vii (J2EE™) ............21 JavaBeans components .......23 About this book ..........ix Enterprise beans .........24 Who should read this book .......ix Applets and servlets ........26 Document organization ........ix JavaServer Pages .........28 Relatedinformation..........x CORBA ............29 Conventions used in this book ......x MicrosoftCOM..........30 How to send your comments ......xii Chapter 4. Adapting business models to Chapter 1. Introducing the IBM WebSphere WebSphere Application Server .....33 family..............1 Component technology ........33 IBMande-business..........1 Common software approach ......34 The WebSphere family: providing e-business Software availability .........34 solutions.............2 Softwarereuse...........34 WebSphere Application Server: different Dividing up software development tasks . 35 editions for different customer needs . 2 Toolsets.............35 Which edition should you use? .....3 Scalability.............36 WebSphere Edge Server .......4 Open standards and investment protection. 36 WebSphere Studio .........6 VisualAgeforJava.........7 Chapter 5. Introduction to WebSphere How do I get more information about Application Server, Advanced Edition . 37 WebSphere Application Server? ......8 What is the difference between the three Installers and system administrators . 8 versions of the Advanced Application Server?. 37 Application developers and system Introduction to the Advanced Application architects ............9 Server..............38 The Advanced Application Server Chapter 2. Distributed computing and environment...........38 WebSphere Application Server .....11 Application model .........40 Three-tiered client/server computing....11 WebSphere Programming Model Transactions: ensuring data consistency and Extensions...........41 permanence in a distributed environment . 12 The administration model in Advanced Security: ensuring authorized use only . 14 Application Server ..........41 Administration tools ........43 Chapter 3. Overview of component The extensible markup language (XML). 43 technology ............17 Services used by the Advanced Application Objects..............17 Server..............44 Building objects through composition . 18 Naming service ..........44 Interface versus implementation ....18 Transaction service .........45 Classes.............19 Security service ..........45 Inheritance ...........19 Workload management service .....45 Polymorphism..........19 Developmentenvironment.......46 Components ............20 Documentation...........46 © Copyright IBM Corp. 1999, 2001 iii Chapter 6. WebSphere Application Server The Recoverable Queueing Service (RQS) 67 Enterprise Edition .........47 The Structured File Server (SFS) ....67 Why use Enterprise Application Server? . 47 The Peer-to-Peer Communications (PPC) Low-level services used in Enterprise Services ............68 Application Server products.......48 TheDE-LightGateway.......68 Distributed Computing Environment TheEncinaToolkit.........69 (DCE) .............48 Encina++ ............69 Common Object Request Broker Encina tools available only on Windows Architecture (CORBA) .......49 platforms............70 Component Object Model (COM) ....50 Interoperability with WebSphere Application Other tools available with the Enterprise Server Advanced Edition........71 Application Server ..........50 Chapter 9. Sample topologies and Chapter 7. Introduction to Enterprise configurations...........73 Edition services ..........53 Client topologies ..........73 CORBA support...........53 Thick client ...........73 WebSphere to WebSphere CORBA Thin client ...........74 scenarios............53 Thinner client ..........75 WebSphere to third-party CORBA Server topologies ..........75 applications ...........55 Distributed servers .........75 JMS Listener ............56 Cloned servers ..........76 BusinessRuleBeans.........56 Consolidated servers ........77 InternationalizationService.......57 Advanced Single Server Edition topology . 77 WorkArea.............58 Advanced Application Server topologies . 78 Simpleconfiguration........78 Chapter 8. Introduction to TXSeries . 61 DMZconfiguration........79 TXSeries CICS ...........61 TXSeries configurations ........80 BasicCICSconcepts........62 AsimpleCICSconfiguration.....80 The CICS application programming A simple CICS configuration within a DCE interface ............62 cell ..............81 Relational database support ......63 A simple Encina Monitor cell configuration 82 Queue services ..........63 Intersystem communication ......64 Appendix. The library for WebSphere CICS SNA support .........65 ApplicationServer.........85 Communicating with users ......65 CICS Transaction Gateway ......65 Notices.............95 CICS administration ........65 Trademarks and service marks ......97 TXSeries Encina ...........66 EncinaMonitor..........66 Index .............101 iv WebSphere: Getting Started with WebSphere Application Server Figures 1. Three-tiered client/server architecture 12 12. A thinner client used with a servlet 75 2. Beans make it possible to program 13. A cluster of distributed servers visually............23 connected to resource managers . 76 3. EJB architecture .........24 14. Physical consolidation of the middle and 4. An applet-based business solution 27 back-end tiers .........77 5. A servlet-based business solution 28 15. A simple Advanced Single Server 6. Clients and servers communicate by Edition configuration .......78 usinganORB.........30 16. Simple Advanced Application Server 7. The components of the Advanced configuration..........79 Application Server environment . 39 17. DMZ configuration in the Advanced 8. Architecture of Encina .......66 Application Server ........80 9. Interoperability between Java 18. A simple distributed configuration using applications and Encina/Encina++ CICS in a non-DCE cell environment . 81 servers ............71 19. A distributed configuration using CICS 10. A thick client has a local user interface in a DCE cell environment .....82 andremotebusinesslogic.....74 20. A simple Encina Monitor configuration 83 11. A thin client has an applet user interface andremotebusinesslogic.....74 © Copyright IBM Corp. 1999, 2001 v vi WebSphere: Getting Started with WebSphere Application Server Tables 1. Conventions used in this book ....x 3. Components of Encina++ ......69 2. Selecting a WebSphere Application Server 4. The library for WebSphere Application edition ............3 Server............85 © Copyright IBM Corp. 1999, 2001 vii viii WebSphere: Getting Started with WebSphere Application Server About this book This document is intended to help you get started using IBM® WebSphere™ Application Server and familiarize you with the components that make up this product. Although this book focuses on the WebSphere Application Server Enterprise Edition, it also contains information on the WebSphere Application Server Advanced Edition. Who should read this book This document is intended for use by installers, system administrators, developers, system architects, and other information technology professionals who want to gain an understanding of WebSphere Application Server. A minimal level of familiarity with distributed computing and Web computing is assumed. Document organization This document has the following organization: v “Chapter 1. Introducing the IBM WebSphere family” on page 1 provides a high-level introduction to the IBM e-business strategy and how the WebSphere Application Server and associated products implement this strategy. v “Chapter 2. Distributed computing and WebSphere Application Server” on page 11 describes distributed computing, transactions, and security. v “Chapter 3. Overview of component technology” on page 17 describes the various component models and related technologies used in WebSphere Application Server. v “Chapter 4. Adapting business models to WebSphere Application Server” on page 33 discusses the value that WebSphere Application Server offers to an organization. v “Chapter 5. Introduction to WebSphere Application Server, Advanced Edition” on page 37 describes the main components and concepts of the Advanced Application Server and its three versions: – WebSphere Application Server, Advanced Edition (AE) – WebSphere Application Server, Advanced Single Server Edition (AEs) – WebSphere Application Server, Advanced Developer Edition (AEd) The chapter’s primary focus is WebSphere Application Server, Advanced Edition. © Copyright IBM Corp. 1999, 2001 ix v “Chapter 6. WebSphere Application Server Enterprise Edition” on page 47 introduces the Enterprise Application Server and associated concepts. v “Chapter 7. Introduction to Enterprise Edition services”
Load more

Recommended publications
  • Distributed Objects in C
    Rochester Institute of Technology RIT Scholar Works Theses 2006 Distributed Objects in C# Xiaoyun Xie Follow this and additional works at: https://scholarworks.rit.edu/theses Recommended Citation Xie, Xiaoyun, "Distributed Objects in C#" (2006). Thesis. Rochester Institute of Technology. Accessed from This Master's Project is brought to you for free and open access by RIT Scholar Works. It has been accepted for inclusion in Theses by an authorized administrator of RIT Scholar Works. For more information, please contact [email protected]. Rochester Institute of Technology Department of Computer Science Master of Science Project Distributed Objects System in C# Submitted By: Xie, Xiaoyun (Sherry) Date: February 2004 Chairman: Dr. Axel T. Schreiner Reader: Dr. Hans-Peter Bischof Observer: Dr. James Heliotis 2 ABSTRACT Today more and more programs run over a collection of autonomous computers linked by a network and are designed to produce an integrated computing facility. Java Distributed Objects (JDO) proposed by Dr. Axel T. Schreiner [1] builds an infrastructure which allows distributed program components to communicate over a network in a transparent, reliable, efficient, and generic way. JDO was originally intended as a teaching device to assess design parameters for distributed objects. This project focuses on porting JDO, which is implemented in Java on Sun’s JDK, to C# on Microsoft’s .NET. On one hand, it builds an infrastructure in C# that simplifies the construction of distributed programs by hiding the distributed nature of remote objects. On the other hand, it generates insights into the differences between two platforms, namely, Java on Sun and C# on .NET, in the distributed objects area.
    [Show full text]
  • Reflective Remote Method Invocation
    Loyola University Chicago Loyola eCommons Computer Science: Faculty Publications and Other Works Faculty Publications 1998 Reflective Remote Method Invocation George K. Thiruvathukal Loyola University Chicago, [email protected] Lovely S. Thomas Andy T. Korczynski Follow this and additional works at: https://ecommons.luc.edu/cs_facpubs Part of the Programming Languages and Compilers Commons Recommended Citation G. Thiruvathukal, L. Thomas, and A. Korczynski, “Reflective Remote Method Invocation,” in ACM Java Grande, 1998. This Conference Proceeding is brought to you for free and open access by the Faculty Publications at Loyola eCommons. It has been accepted for inclusion in Computer Science: Faculty Publications and Other Works by an authorized administrator of Loyola eCommons. For more information, please contact [email protected]. This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 License. Copyright © 1998 George K. Thiruvathukal, Lovely S. Thomas, and A. Korczynski Reflective Remote Method Invocation G. K. Thiruvathukal1 Tools of Computing LLC and Argonne National Laboratory Chicago, Illinois, U.S.A. L. S. Thomas2 Illinois Institute of Technology, Chicago, Illinois, U.S.A. A. T. Korczynski3 Illinois Institute of Technology, Chicago, Illinois, U.S.A. Abstract Remote Method Invocation (RMI) is available in the current Java language design and implementation, providing the much-needed capability of allowing objects running in different Java processes to collaborate using a variation on the popular Remote Procedure Call (RPC). Although RMI provides features which are desirable for high-performance distributed computing, its design and implementation are deficient in key areas of importance to the high-performance computing community in general.
    [Show full text]
  • Websphere Product Family: Overview and Architecture
    Front cover WebSphere Product Family Overview and Architecture Discover the WebSphere family Take an in-depth look at key products Compare capabilities Carla Sadtler Gennaro Cuomo John Ganci Marc Haberkorn Carol Jones Peter Kovari Kevin Griffith Dildar Marhas Rob Will ibm.com/redbooks International Technical Support Organization WebSphere Product Family Overview and Architecture February 2005 SG24-6963-02 Note: Before using this information and the product it supports, read the information in “Notices” on page xv. Third Edition (February 2005) This edition applies to the WebSphere family. © Copyright International Business Machines Corporation 2004, 2005. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . xv Trademarks . xvi Preface . xvii The team that wrote this redbook. xvii Become a published author . xix Comments welcome. xix Summary of changes . xxi February 2005, Third Edition . xxi Chapter 1. IBM WebSphere product overview . xxiii 1.1 WebSphere overview . xxiv 1.2 WebSphere family . xxv 1.3 IBM WebSphere Application Servers . xxvi 1.3.1 WebSphere Application Server V6 for distributed platforms . xxviii 1.3.2 WebSphere Application Server V5.1. xxxi 1.3.3 WebSphere Extended Deployment V5.1 . xxxiii 1.4 IBM software development platform . xxxv 1.4.1 Application development for WebSphere Application Server V6 . xxxvi 1.4.2 WebSphere Studio and Rational Developer . .xxxvii 1.5 IBM WebSphere Business Integration products . .xliii 1.5.1 Integration servers . xlv 1.5.2 Product overview. xlvi 1.5.3 WebSphere Business Integration Server Foundation . xlvi 1.5.4 WebSphere Business Integration Server .
    [Show full text]
  • Remote Procedure Call (RPC)
    Remote Procedure Call (RPC) RPC – RMI - Web Services 1 Complexity of the distributed applications . The programming of distributed applications is difficult. In addition to the usual tasks, programmers who build clients and servers must deal with the complex issues of communication. Although many of the needed functions are supplied by a standard API such as the socket interface, the socket calls require the programmer to specify many low level details as names ,addresses,protocols and ports. Moreover, asinchronous communications models are complex to implement. Distributed implementations tend to use the same standard API (e.g.,the socket interface). As a consequence most of the detailed code found in one program is replicated in others RPC – RMI - Web Services 2 . For example, all client programs that use a connection oriented transport must create a socket, specify the server’s endpoint address, open a connection to the server, send requests,receive responses and close the connection when interaction is complete. Tools (software that generates all or part of a computer program) have been created to construct clients and servers. Tools cannot eliminate all programming: a programmer must supply the code that perform the computation for the particular service. However, a tool can handle the communication details. As a result the code contains fever bugs. RPC – RMI - Web Services 3 . RPC = Remote Procedure Call . The basic model has been proposed by Birrell e Nelson in 1984. The essence of this technique is to allow programs on different machines to interact using simple procedure call/return semantics, just as if the two programs were in the same computer .
    [Show full text]
  • A Comparative Evaluation of .Net Remoting and JAVA RMI Taneem Ibrahim University of Arkansas, Fayetteville
    Inquiry: The University of Arkansas Undergraduate Research Journal Volume 5 Article 12 Fall 2004 A Comparative Evaluation of .net Remoting and JAVA RMI Taneem Ibrahim University of Arkansas, Fayetteville Follow this and additional works at: http://scholarworks.uark.edu/inquiry Part of the Computer and Systems Architecture Commons Recommended Citation Ibrahim, Taneem (2004) "A Comparative Evaluation of .net Remoting and JAVA RMI," Inquiry: The University of Arkansas Undergraduate Research Journal: Vol. 5 , Article 12. Available at: http://scholarworks.uark.edu/inquiry/vol5/iss1/12 This Article is brought to you for free and open access by ScholarWorks@UARK. It has been accepted for inclusion in Inquiry: The nivU ersity of Arkansas Undergraduate Research Journal by an authorized editor of ScholarWorks@UARK. For more information, please contact [email protected], [email protected]. Ibrahim: A Comparative Evaluation of .net Remoting and JAVA RMI 86 INQUIRY Volume 5 2004 A COMPARATIVE EVALUATION OF .NET REMOTING ANDJAVARMI By: Taneem Ibrahim Department of Computer Science and Computer Engineering Faculty Mentor: Dr. Amy Apon Department of Computer Science and Computer Engineering Abstract: Introduction: Distributed application technologies such as A distributed system is a collection of loosely coupled Micrososoft.NEJRemoting, and Java Remote Method Invocation processors interconnected by a communication network [8]. (RMI) have evolved over many years to keep up with the From tbe point view of a specific processor in a distributed constantly increasing requirements of the enterprise. In the system, the rest of the processors and their respective resources broadest sense, a distributed application is one in which the are remote, whereas its own resources are local.
    [Show full text]
  • Distributed Objects
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by UCL Discovery Distributed Objects Wolfgang Emmerich Neil Roodyn Dept. of Computer Science Cognitech Ltd University College London City Cloisters, 188-194 Old Street London WC1E 6BT,UK London EC1V 9FR, UK [email protected] [email protected] ABSTRACT be addressed. In addition, any distributed application must This tutorial motivates the need for, and discusses the prin- be tolerant of failures, such as temporarily unreachable com- ciples of object-oriented distribution middleware. We will ponents or network time-outs. Dealing with these issues at give an overview how these principles are supported by the the network operating system layer is overly complicated for major incarnations of object-oriented middleware, the Ob- an application engineer. ject Management Group’s Common Object Request Broker Distribution middleware is layered between network operat- Architecture (CORBA), Microsoft’s Distributed Component ing systems and distributed applications in order to bridge Object Model (DCOM) and Java’s Remote Method Invoca- this gap. Middleware provides the application designer with tion (RMI). We will discuss common design problems that a higher-level of abstraction. Middleware systems imple- occur when building applications using distributed objects ment this higher level of abstraction based on primitives that and present techniques for their solution. are provided by network operating systems. While doing so 1 INTRODUCTION they hide the complexity of using a network operating sys- In a number of domains, such as the financial and telecom- tem from application designers. The idea of middleware is munications sector, applications have to be adapted to evolv- not new.
    [Show full text]
  • Distributed Objects
    Introduction to Distributed Objects The idea of distributed objects is an extension of the concept of remote procedure calls. In a remote procedure call system (Sun RPC, DCE RPC, Java RMI), code is executed remotely via a remote procedure call. The unit of distribution is the procedure / function /method (used as synonyms). So the client has to import a client stub (either manually as in RPC or automatically as in RMI) to allow it to connect to the server offering the remote procedure. Object as Distribution Unit In a system for distributed objects, the unit of distribution is the object. That is, a client imports a ”something” (in Java’s JINI system, it’s called a proxy) which allows the client access to the remote object as if it were part of the original client program (as with RPC and RMI, sort of transparently). A client actually imports a Java class and this becomes part of the set of classes available on the client machine. So, for example, the client can define subclasses of this imported class, overload methods, etc. In addition, distributed object systems provide additional services, like a discovery service that allows clients to locate the objects they need, security services, reliability services, etc. Distributed object technologies: 1. DCOM (Distributed Common Object Model), developed by Microsoft, but also available on other platforms. Built on top of DCE’s RPC, interacts with COM. 2. CORBA (Common Object Request Broker Architecture), defined by the Object Management Group, an industry consortium. CORBA is available for most major operating systems 3. JINI (“Genie,” JINI is not initials — a joke; JINI actually doesn’t stand for anything.) JINI is developed on top of Java.
    [Show full text]
  • Distributed Object Based Systems
    Distributed Systems Distributed Object-Based Systems Björn Franke University of Edinburgh, 2015 OVERVIEW • Basic Concepts • Middleware Technologies • CORBA • DCOM • .NET Remote Procedure Calls/Windows Communication Foundation • Google gRPC BASIC CONCEPTS REMOTE PROCEDURE CALLS (RPC) BASIC CONCEPTS REMOTE PROCEDURE CALLS (RPC) BASIC CONCEPTS MARSHALLING/UNMARSHALLING MIDDLEWARE TECHNOLOGIES HIGH-LEVEL VIEW MIDDLEWARE TECHNOLOGIES SLIGHTLY MORE DETAIL • High-level abstractions & API • Heterogeneity Hidden • Transparent Distribution • General purpose services e.g. directory/naming CORBA COMMON OBJECT REQUEST BROKER ARCHITECTURE • Industry-defined standard for distributed objects • Enables collaboration between systems on different operating systems, programming languages, and computing hardware • Interface definition language (IDL) to specify object interfaces. CORBA then specifies a mapping from IDL to a specific implementation language. • Central: Object request brokers (ORBs) • Application initialises ORB, and accesses an internal Object Adapter, which maintains things like reference counting, object (and reference) instantiation policies, and object lifetime policies. • Object Adapter is used to register instances of the generated code classes (result of compiling the user IDL code, which translates interface definitions into an OS- and language-specific class base for use by the user application). CORBA GLOBAL ARCHITECTURE • The Object Request Broker (ORB) forms the core of any CORBA distributed system. • Horizontal facilities consist
    [Show full text]
  • Distributed Computing Paradigms Distributed Application Paradigms
    Distributed Computing Paradigms Distributed Application Paradigms level of abstraction high object space network services, object request broker, mobile agent remote procedure call, remote method invocation client-server message passing low The Message Passing Paradigm Message passing is the most fundamental paradigm for distributed applications. A process sends a message representing a request. The message is delivered to a receiver, which processes the request, and sends a message in response. In turn, the reply may trigger a further request, which leads to a subsequent reply, and so forth. Process A Process B a message Me ssage passing The Message Passing Paradigm The basic operations required to support the basic message passing paradigm are send, and receive. For connection-oriented communication, the operations connect and disconnect are also required. With the abstraction provided by this model, the interconnected processes perform input and output to each other, in a manner similar to file I/O. The I/O operations encapsulate the detail of network communication at the operating-system level. The socket application programming interface is based on this paradigm. http://java.sun.com/products/jdk/1.2/docs/api/index.html http://www.sockets.com/ The Client-Server Paradigm Perhaps the best known paradigm for network applications, the client-server model assigns asymmetric roles to two collaborating processes. One process, the server, plays the role of a service provider which waits passively for the arrival of requests. The other, the client, issues specific requests to the server and awaits its response. service request a client process a server process Server host a service Client host ..
    [Show full text]
  • Distributed Computing Paradigms
    Distributed Computing Paradigms Mei-Ling Liu Distributed Computing Paradigms, 5/8/2007 M. Liu 1 Paradigms for Distributed Applications Paradigm means “a pattern, example, or model.” In the study of any subject of great complexity, it is useful to identify the basic patterns or models, and classify the detail according to these models. This paper aims to present a classification of the paradigms for distributed applications. Characteristics that distinguish distributed applications from conventional applications which run on a single machine. These characteristics are: w Interprocess communication: A distributed application require the participation of two or more independent entities (processes). To do so, the processes must have the ability to exchange data among themselves. w Event synchronization: In a distributed application, the sending and receiving of data among the participants of a distributed application must be synchronized. Distributed Computing Paradigms, 5/8/2007 M. Liu 2 Abstractions Arguably the most fundamental concept in computer science, abstraction is the idea of detail hiding. To quote David J. Barnes1: We often use abstraction when it is not necessary to know the exact details of how something works or is represented, because we can still make use of it in its simplified form. Getting involved with the detail often tends to obscure what we are trying to understand, rather than illuminate it … Abstraction plays a very important role in programming because we often want to model, in software, simplified versions of things that exist in the real world … without having to build the real things. In software engineering, abstraction is realized with the provision of tools or facilities which allow software to be built without the developer having to be cognizant of some of the underlying complexities.
    [Show full text]
  • Distributed Object Systems
    Distributed Systems Distributed Object-Based Systems Björn Franke University of Edinburgh, 2016 OVERVIEW • Basic Concepts • Middleware Technologies • Apache Ignite (see coursework lecture) • CORBA • DCOM • .NET Remote Procedure Calls/Windows Communication Foundation • Google gRPC BASIC CONCEPTS REMOTE PROCEDURE CALLS (RPC) BASIC CONCEPTS REMOTE PROCEDURE CALLS (RPC) BASIC CONCEPTS MARSHALLING/UNMARSHALLING MIDDLEWARE TECHNOLOGIES HIGH-LEVEL VIEW MIDDLEWARE TECHNOLOGIES SLIGHTLY MORE DETAIL • High-level abstractions & API • Heterogeneity Hidden • Transparent Distribution • General purpose services e.g. directory/naming CORBA COMMON OBJECT REQUEST BROKER ARCHITECTURE • Industry-defined standard for distributed objects • Enables collaboration between systems on different operating systems, programming languages, and computing hardware • Interface definition language (IDL) to specify object interfaces. CORBA then specifies a mapping from IDL to a specific implementation language. • Central: Object request brokers (ORBs) • Application initialises ORB, and accesses an internal Object Adapter, which maintains things like reference counting, object (and reference) instantiation policies, and object lifetime policies. • Object Adapter is used to register instances of the generated code classes (result of compiling the user IDL code, which translates interface definitions into an OS- and language-specific class base for use by the user application). CORBA GLOBAL ARCHITECTURE • The Object Request Broker (ORB) forms the core of any CORBA distributed
    [Show full text]
  • Portable Serialization of CORBA Objects: a Reflective Approach Marc-Olivier Killijian Juan-Carlos Ruiz Jean-Charles Fabre LAAS-CNRS LAAS-CNRS LAAS-CNRS 7, Av
    Portable Serialization of CORBA Objects: a Reflective Approach Marc-Olivier Killijian Juan-Carlos Ruiz Jean-Charles Fabre LAAS-CNRS LAAS-CNRS LAAS-CNRS 7, Av. du Colonel Roche 7, Av. du Colonel Roche 7, Av. du Colonel Roche 31077 Toulouse Cedex 4 (France) 31077 Toulouse Cedex 4 (France) 31077 Toulouse Cedex 4 (France) +33.5.61.33.62.41 +33.5.61.33.69.09 +33.5.61.33.62.36 [email protected] [email protected] [email protected] ABSTRACT resulting from different programming languages. We use in this paper the terms portable and language (and platform) The objective of this work is to define, implement and independent interchangeably. illustrate a portable serialization technique for CORBA objects. We propose an approach based on reflection: through Serialization in a homogeneous environment has been studied open compilers facilities the internal state of CORBA objects quite extensively, e.g. in [1] [2]. This is not the case of is obtained and transformed into a language independent serialization in heterogeneous environments where works like format using CORBA mechanisms. This state can be restored [3] [4] focus on platform interoperability but not on language and used by objects developed using different languages and portability. Our objective in this work is to provide facilities running on different software platforms. A tool was developed to serialize and de-serialize CORBA objects in a portable and applied to a Chat application as a case study. The format. We introduce an abstract model of object state so that a proposed technique is used to exchange state information serialized state is interoperable and portable.
    [Show full text]