DOCSLIB.ORG

Websphere Product Family: Overview and Architecture

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read 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 . lii 1.5.5 WebSphere InterChange Server. liii 1.5.6 WebSphere MQ . lv 1.5.7 WebSphere Business Integration Message Broker . lvi 1.5.8 WebSphere Business Integration Adapters . .lviii 1.5.9 WebSphere Business Integration Toolset. lix 1.5.10 WebSphere MQ Workflow. lxii 1.5.11 WebSphere Business Integration Connect . lxv 1.5.12 WebSphere Data Interchange. lxvi 1.5.13 WebSphere Business Integration Monitor. lxvi 1.5.14 WebSphere Business Integration Modeler . lxvii 1.6 IBM WebSphere Commerce . .lxviii 1.7 IBM WebSphere Portal for Multiplatforms . lxx © Copyright IBM Corp. 2004, 2005. All rights reserved. iii Chapter 2. WebSphere Application Server V5 architecture . lxxv 2.1 Server architecture . .lxxvi 2.1.1 Express configuration . .lxxvi 2.1.2 Base configuration . lxxvii 2.1.3 Network Deployment configuration . lxxviii 2.2 Cells, nodes and servers. .lxxix 2.3 Servers . .lxxxi 2.3.1 Application server . .lxxxi 2.3.2 JMS server . .lxxxi 2.3.3 Clusters . lxxxii 2.4 Containers . .lxxxiv 2.4.1 Web container . lxxxv 2.4.2 EJB container . .lxxxvi 2.4.3 Client application container . .lxxxvi 2.5 Application server services . lxxxvii 2.5.1 JCA services . lxxxviii 2.5.2 Transaction service . lxxxviii 2.5.3 Dynamic caching. .lxxxix 2.5.4 Message listener service. xc 2.5.5 Object Request Broker service . xc 2.5.6 Name service . xci 2.5.7 PMI service . xciii 2.5.8 Security service. xciv 2.5.9 Admin service . xciv 2.6 Virtual hosts. xciv 2.7 Session management . xcv 2.7.1 Session persistence . xcvi 2.8 Web services. xcviii 2.8.1 IBM WebSphere UDDI Registry . c 2.8.2 Web Services Gateway. ci 2.9 Security . ciii 2.9.1 User registry . cv 2.9.2 Authentication . cvi 2.9.3 Authorization . cvii 2.9.4 Security components. cviii 2.9.5 Security flows . cix 2.10 Resource providers . cx 2.10.1 JDBC resources . cxi 2.10.2 JavaMail . cxiii 2.10.3 JCA resource adapters . cxiv 2.10.4 URL providers . cxiv 2.10.5 JMS providers . cxv 2.10.6 Resource environment providers . .cxvii iv WebSphere Product Family Overview and Architecture 2.11 Administration . .cxvii 2.11.1 Administration tools. cxviii 2.11.2 Configuration repository . cxix 2.11.3 Centralized administration. cxix 2.12 The flow of an application . cxxi 2.13 Developing and deploying applications . cxxiii Chapter 3. IBM WebSphere Extended Deployment . .cxxvii 3.1 Introduction . cxxviii 3.2 An adaptable IT infrastructure . cxxix 3.3 Dynamic operations. cxxx 3.3.1 Resource sharing . cxxxi 3.3.2 Application service levels . .cxxxii 3.3.3 Performance requirements . ..
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]
  • Current Affairs October 2019
    Current Affairs October 2019 Current Affairs October 2019 1st Oct, 2019 Chhattisgarh government to start five new schemes on Gandhi Jayanti Chhattisgarh government, under the leadership of Chief Minister Bhupesh Baghel is set to launch five new schemes on October 2 to mark the 150th birth anniversary of Mahatma Gandhi. The schemes are: Mukhyamantri Suposhan Abhiyaan (Chief Minister Nutrition Scheme), Mukhyamantri Haat Bazaar Clinic Yojana (Chief Minister Market Clinic Scheme), Mukhyamantri Shahariya slum Swasthya Yojana (Chief Minister Urban Slum Health Scheme), Universal PDS scheme Mukhyamantri ward Karyalaya (Chief Minister Ward Offices). In a first, rail passengers to be compensated for delays on board IRCTC's Tejas Express train Passengers of IRCTC's Delhi-Lucknow Tejas Express will be compensated in case of delays, the Railway subsidiary said on Tuesday, announcing a first of its kind offer from any national carrier. An amount of Rs 100 will be paid in case the delay is for over an hour and Rs 250 for delays of over two hours, the IRCTC said ahead of the launch of its first train. Rajnath Singh launches DefExpo 2020 website Defence Minister Rajnath Singh on Monday launched the website of the 11th edition of DefEXpo, which will be held in Lucknow in February next year, officials said. The event will be hosted from February 5-8. "The website, www.defexpo.gov.in, provides online services to exhibitors, besides hosting informative content about the product profile of DPSUs (Defence Public Sector Undertakings) and ordnance factories," a senior official said. President Kovind presents Vayoshreshtha Samman-2019 President Ram Nath Kovind today conferred the Vayoshreshtha Samman-2019 on the eminent senior citizens and institutions in New Delhi in recognition of their services towards the cause of the elderly persons.
    [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]
  • 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]
  • Download Conference Program (Pdf)
    The 16th International Web for All Conference San Francisco, 2019 http://www.w4a.info/2019/ #w4a2019 Endorsed by the IW3C2 International World Wide Web Conference Committee ISBN: 978-1-4503-6716-5 Foreword The International Web for All Conference (W4A) began in 2004 as a workshop to make the World Wide Web accessible for people with disabilities. Over the years the workshop has grown into the top conference for web accessibility research, attracting a diverse crowd from academia, industry, government, and nonprofits. W4A has become the venue for scientists, students, and practitioners from around the world to showcase their latest research, widen their perspectives through discussions with peers, and establish future research agendas. W4A is an influential conference that has a growing impact on the research community. According to the ACM Digital Library Bibliometric, people downloaded each of the W4A's 431 papers an average of 353 times and W4A papers were citation average of 4.64. These data confirm that W4A does not only provide excellent visibility to papers but also enables strong scientific impact. We have always embraced the potential of new technologies to provide an accessible user experience for everyone. No longer do we look at technology and its potential challenges for users, but we look for how it can be used to provide accessible experiences for all. In recognition of the emergence of this new age, the theme for the 16th International Web for All Conference is “Personalization – Personalizing the Web.” Personalization pervades all aspects of technology from home appliances to mobile phones, from shopping experiences to education.
    [Show full text]
  • IBM Puresystems Guidebook for IBM Business Partners
    March 2014 CLICK HERE to check for updates Your Roadmap to Success with IBM IBM Expert Integrated PureSystems Systems Business Partner Guide Edited by Jim Hoskins IBM PureSystems Business Partner Guide Other Titles of Interest More IBM Titles of Interest • IBM Power Systems Business Partner Guide • IBM Storage Business Partner Guide • IBM Smarter Workforce Business Partner Guide For more information, email us at [email protected]. IBM PureSystems Business Partner Guide Fifth Edition Your Roadmap to Success with IBM Expert Integrated Systems Edited by Jim Hoskins (version 5.0e) 605 Silverthorn Road Gulf Breeze, FL 32561 maxpress.com Notices Production Manager: Jacquie Wallace Cover Designer: Lauren Smith This publication is designed to provide accurate and authoritative information in regard to the subject matter covered. It is sold with the understanding that the publisher is not engaged in rendering professional services. If legal, accounting, medical, psychological, or any other expert assistance is required, the services of a competent professional person should be sought. ADAPTED FROM A DECLARATION OF PRIN- CIPLES OF A JOINT COMMITTEE OF THE AMERICAN BAR ASSOCIATION AND PUBLISHERS. Copyright 2014 by Maximum Press. All rights reserved. Published simultaneously in Canada. Reproduction or translation of any part of this work beyond that permitted by Section 107 or 108 of the 1976 United States Copyright Act without the permission of the copyright owner is unlawful. Requests for permission or further information should be addressed to the Permissions Department, Maximum Press. This ebook was sponsored by IBM. This ebook utilized information provided by IBM and other companies including publicly available data.
    [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]
  • Michael Jordan
    Michael Jordan For other people named Michael Jordan, see Michael Associated Press's list of athletes of the century. Jordan Jordan (disambiguation). is a two-time inductee into the Basketball Hall of Fame, having been enshrined in 2009 for his individual career, Michael Jeffrey Jordan (born February 17, 1963), also and again in 2010 as part of the group induction of the 1992 United States men’s Olympic basketball team (“The known by his initials, MJ,[1] is an American former pro- fessional basketball player. He is also a businessman, and Dream Team”). principal owner and chairman of the Charlotte Hornets. Jordan is also known for his product endorsements. He Jordan played 15 seasons in the National Basketball As- fueled the success of Nike’s Air Jordan sneakers, which sociation (NBA) for the Chicago Bulls and Washington were introduced in 1985 and remain popular today.[5] Wizards. His biography on the NBA website states: “By Jordan also starred in the 1996 feature film Space Jam as acclamation, Michael Jordan is the greatest basketball himself. In 2006, he became part-owner and head of bas- player of all time.”[2] Jordan was one of the most effec- ketball operations for the then-Charlotte Bobcats, buying tively marketed athletes of his generation and was con- controlling interest in 2010. In 2015, Jordan became the sidered instrumental in popularizing the NBA around the first NBA player in history to become a billionaire. world in the 1980s and 1990s.[3] After a three-season stint at the University of North Car- olina, where he was a member of the Tar Heels’ national 1 Early years championship team in 1982, Jordan joined the NBA’s Chicago Bulls in 1984.
    [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]