WebSphere: Getting Started With WebSphere Application Server

3y ago
25 Views
2 Downloads
1.31 MB
119 Pages
Last View : Today
Last Download : 2m ago
Upload by : Cannon Runnels
Transcription

WebSphere Application Server Getting Started with WebSphereApplication ServerVersion 4.0SC09-4581-01

WebSphere Application Server Getting Started with WebSphereApplication ServerVersion 4.0SC09-4581-01

NoteBefore 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 Contractwith IBM Corp.

ContentsFigures .Tables.About this book . . . . .Who should read this book . .Document organization . . .Related information . . . . .Conventions used in this book .How to send your comments . . . . . . . v. vii. . . . . . . ix. ix. ix. x. x. xiiChapter 1. Introducing the IBM WebSpherefamily . . . . . . . . . . . . .IBM and e-business . . . . . . . . .The WebSphere family: providing e-businesssolutions . . . . . . . . . . . .WebSphere Application Server: differenteditions for different customer needs . .Which edition should you use? . . . .WebSphere Edge Server . . . . . .WebSphere Studio . . . . . . . .VisualAge for Java . . . . . . . .How do I get more information aboutWebSphere Application Server? . . . . .Installers and system administrators . .Application developers and systemarchitects . . . . . . . . . . .Chapter 2. Distributed computing andWebSphere Application Server . . . .Three-tiered client/server computing. . .Transactions: ensuring data consistency andpermanence in a distributed environment .Security: ensuring authorized use only . . 1. 1. 2.23467. 8. 8. 9. 11. 11. 12. 14Chapter 3. Overview of componenttechnology . . . . . . . . . . . . 17Objects . . . . . . . . . . . . . . 17Building objects through composition . . 18Interface versus implementation . . . . 18Classes . . . . . . . . . . . . . 19Inheritance . . . . . . . . . . . 19Polymorphism . . . . . . . . . . 19Components . . . . . . . . . . . . 20 Copyright IBM Corp. 1999, 2001Component models and related technologiesJava 2 Platform Enterprise Edition(J2EE ) . . . . . . . . . . .JavaBeans components . . . . . .Enterprise beans . . . . . . . .Applets and servlets . . . . . . .JavaServer Pages . . . . . . . .CORBA . . . . . . . . . . .Microsoft COM . . . . . . . . .21.21232426282930Chapter 4. Adapting business models toWebSphere Application Server . . . . . 33Component technology . . . . . . . . 33Common software approach . . . . . . 34Software availability . . . . . . . . . 34Software reuse . . . . . . . . . . . 34Dividing up software development tasks . . 35Tool sets . . . . . . . . . . . . . 35Scalability . . . . . . . . . . . . . 36Open standards and investment protection. . 36Chapter 5. Introduction to WebSphereApplication Server, Advanced Edition . .What is the difference between the threeversions of the Advanced Application Server?.Introduction to the Advanced ApplicationServer . . . . . . . . . . . . . .The Advanced Application Serverenvironment . . . . . . . . . . .Application model . . . . . . . . .WebSphere Programming ModelExtensions . . . . . . . . . . .The administration model in AdvancedApplication Server . . . . . . . . . .Administration tools . . . . . . . .The extensible markup language (XML) . . .Services used by the Advanced ApplicationServer . . . . . . . . . . . . . .Naming service . . . . . . . . . .Transaction service . . . . . . . . .Security service . . . . . . . . . .Workload management service . . . . .Development environment . . . . . . .Documentation . . . . . . . . . . .37373838404141434344444545454646iii

Chapter 6. WebSphere Application ServerEnterprise Edition . . . . . . . .Why use Enterprise Application Server? .Low-level services used in EnterpriseApplication Server products. . . . . .Distributed Computing Environment(DCE) . . . . . . . . . . . .Common Object Request BrokerArchitecture (CORBA) . . . . . .Component Object Model (COM) . . .Other tools available with the EnterpriseApplication Server . . . . . . . . . 47. 47. 48. 48. 49. 50iv. . . 61. . . 61. . . 62.67. 67.68686969. 70. 71. 50Chapter 7. Introduction to EnterpriseEdition services . . . . . . . . . . 53CORBA support. . . . . . . . . . . 53WebSphere to WebSphere CORBAscenarios . . . . . . . . . . . . 53WebSphere to third-party CORBAapplications . . . . . . . . . . . 55JMS Listener . . . . . . . . . . . . 56Business Rule Beans . . . . . . . . . 56Internationalization Service . . . . . . . 57WorkArea . . . . . . . . . . . . . 58Chapter 8. Introduction to TXSeriesTXSeries CICS . . . . . . . .Basic CICS concepts . . . . .The CICS application programminginterface . . . . . . . . .Relational database support . . .Queue services . . . . . . .Intersystem communication . . .CICS SNA support . . . . . .Communicating with users . . .CICS Transaction Gateway . . .CICS administration . . . . .TXSeries Encina . . . . . . . .Encina Monitor . . . . . . .The Recoverable Queueing Service (RQS)The Structured File Server (SFS) . . .The Peer-to-Peer Communications (PPC)Services . . . . . . . . . . .The DE-Light Gateway . . . . . .The Encina Toolkit . . . . . . . .Encina . . . . . . . . . . .Encina tools available only on Windowsplatforms . . . . . . . . . . .Interoperability with WebSphere ApplicationServer Advanced Edition. . . . . . .62636364656565656666Chapter 9. Sample topologies andconfigurations . . . . . . . . . . .Client topologies . . . . . . . . . .Thick client . . . . . . . . . . .Thin client . . . . . . . . . . .Thinner client . . . . . . . . . .Server topologies . . . . . . . . . .Distributed servers . . . . . . . . .Cloned servers . . . . . . . . . .Consolidated servers . . . . . . . .Advanced Single Server Edition topology . .Advanced Application Server topologies . .Simple configuration . . . . . . . .DMZ configuration . . . . . . . .TXSeries configurations . . . . . . . .A simple CICS configuration . . . . .A simple CICS configuration within a DCEcell . . . . . . . . . . . . . .A simple Encina Monitor cell configurationAppendix. The library for WebSphereApplication Server . . . . . . .7373737475757576777778787980808182. 85Notices . . . . . . . . . . . . . 95Trademarks and service marks . . . . . . 97IndexWebSphere: Getting Started with WebSphere Application Server. 101

Figures1.2.3.4.5.6.7.8.9.10.11.Three-tiered client/server architectureBeans make it possible to programvisually. . . . . . . . . . . .EJB architecture . . . . . . . . .An applet-based business solutionA servlet-based business solutionClients and servers communicate byusing an ORB . . . . . . . . .The components of the AdvancedApplication Server environment . . .Architecture of Encina . . . . . . .Interoperability between Javaapplications and Encina/Encina servers . . . . . . . . . . . .A thick client has a local user interfaceand remote business logic . . . . .A thin client has an applet user interfaceand remote business logic . . . . . Copyright IBM Corp. 1999, .A thinner client used with a servletA cluster of distributed serversconnected to resource managers . . .Physical consolidation of the middle andback-end tiers . . . . . . . . .A simple Advanced Single ServerEdition configuration . . . . . . .Simple Advanced Application Serverconfiguration . . . . . . . . . .DMZ configuration in the AdvancedApplication Server . . . . . . . .A simple distributed configuration usingCICS in a non-DCE cell environment . .A distributed configuration using CICSin a DCE cell environment . . . . .A simple Encina Monitor configuration75767778798081828374v

viWebSphere: Getting Started with WebSphere Application Server

Tables1.2.Conventions used in this book . . . . xSelecting a WebSphere Application Serveredition . . . . . . . . . . . . 3 Copyright IBM Corp. 1999, 20013.4.Components of Encina . . . . . . 69The library for WebSphere ApplicationServer . . . . . . . . . . . . 85vii

viiiWebSphere: Getting Started with WebSphere Application Server

About this bookThis document is intended to help you get started using IBM WebSphere Application Server and familiarize you with the components that make upthis product. Although this book focuses on the WebSphere Application ServerEnterprise Edition, it also contains information on the WebSphere ApplicationServer Advanced Edition.Who should read this bookThis document is intended for use by installers, system administrators,developers, system architects, and other information technology professionalswho want to gain an understanding of WebSphere Application Server. Aminimal level of familiarity with distributed computing and Web computingis assumed.Document organizationThis document has the following organization:v “Chapter 1. Introducing the IBM WebSphere family” on page 1 provides ahigh-level introduction to the IBM e-business strategy and how theWebSphere Application Server and associated products implement thisstrategy.v “Chapter 2. Distributed computing and WebSphere Application Server” onpage 11 describes distributed computing, transactions, and security.v “Chapter 3. Overview of component technology” on page 17 describes thevarious component models and related technologies used in WebSphereApplication Server.v “Chapter 4. Adapting business models to WebSphere Application Server” onpage 33 discusses the value that WebSphere Application Server offers to anorganization.v “Chapter 5. Introduction to WebSphere Application Server, AdvancedEdition” on page 37 describes the main components and concepts of theAdvanced 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, AdvancedEdition. Copyright IBM Corp. 1999, 2001ix

v “Chapter 6. WebSphere Application Server Enterprise Edition” on page 47introduces the Enterprise Application Server and associated concepts.v “Chapter 7. Introduction to Enterprise Edition services” on page 53describes the functionality provided by the Enterprise Edition services.v “Chapter 8. Introduction to TXSeries” on page 61 provides more detailedinformation on TXSeries .v “Chapter 9. Sample topologies and configurations” on page 73 discussesexamples of WebSphere Application Server system configurations.v “Appendix. The library for WebSphere Application Server” on page 85provides a complete list of the documentation available with WebSphereApplication Server.Related informationFor further information on the topics and software discussed in this manual,see the following documents:v Building Business Solutions with WebSpherev CICS Application Programming Guidev Enterprise Edition InfoCentervvvvTXSeries Planning and Installation GuideWriting Encina ApplicationsWriting Encina Applications on Windows SystemsWriting Enterprise Beans in WebSphereConventions used in this bookWebSphere Application Server Enterprise Edition documentation uses thefollowing typographical and keying conventions.Table 1. Conventions used in this bookConventionMeaningBoldIndicates command names. When referring to graphical user interfaces(GUIs), bold also indicates menus, menu items, labels, and buttons.MonospaceIndicates text you must enter at a command prompt and values you mustuse literally, such as commands, functions, and resource definition attributesand their values. Monospace also indicates screen text and code examples.ItalicsIndicates variable values you must provide (for example, you supply thename of a file for fileName). Italics also indicates emphasis and the titles ofbooks.Ctrl-xWhere x is the name of a key, indicates a control-character sequence. Forexample, Ctrl-c means hold down the Ctrl key while you press the c key.xWebSphere: Getting Started with WebSphere Application Server

Table 1. Conventions used in this book (continued)ConventionMeaningReturnRefers to the key labeled with the word Return, the word Enter, or the leftarrow.%Represents the UNIX command-shell prompt for a command that does notrequire root privileges.#Represents the UNIX command-shell prompt for a command that requiresroot privileges.C:\ Represents the Windows NT command prompt. When used to describe a menu, shows a series of menu selections. Forexample, “Click File New” means “From the File menu, click the Newcommand.” When used to describe a tree view, shows a series of folder or objectexpansions. For example, “Expand Management Zones Sample Cell andWork Group Zone Configuration” means:1. Expand the Management Zones folder2. Expand the management zone named Sample Cell and Work Group Zone3. Expand the Configurations folderNote: An object in a view can be expanded when there is a plus sign ( )beside that object. After an object is expanded, the plus sign is replaced by aminus sign (-). Expands a tree structure to show more objects. To expand, click the plus sign( ) beside any object.-Collapses a branch of a tree structure to remove from view the objectscontained in that branch. To collapse the branch of a tree structure, click theminus sign (-) beside the object at the head of the branch.Entering commandsWhen instructed to “enter” or “issue” a command, type the command andthen press Return. For example, the instruction “Enter the ls command”means type ls at a command prompt and then press Return.[]Enclose optional items in syntax descriptions.{}Enclose lists from which you must choose an item in syntax descriptions. Separates items in a list of choices enclosed in braces ({ }) in syntaxdescriptions.Ellipses in syntax descriptions indicate that you can repeat the precedingitem one or more times. Ellipses in examples indicate that information wasomitted from the example for the sake of brevity.INIn function descriptions, indicates parameters whose values are used to passdata to the function. These parameters are not used to return modified datato the calling routine. (Do not include the IN declaration in your code.)About this bookxi

Table 1. Conventions used in this book (continued)ConventionMeaningOUTIn function descriptions, indicates parameters whose values are used toreturn modified data to the calling routine. These parameters are not used topass data to the function. (Do not include the OUT declaration in your code.)INOUTIn function descriptions, indicates parameters whose values are passed to thefunction, modified by the function, and returned to the calling routine. Theseparameters serve as both IN and OUT parameters. (Do not include theINOUT declaration in your code.) CICSIndicates the full pathname where the CICS product is installed; for example,C:\opt\cics on Windows NT or /opt/cics on Solaris. If the environmentvariable named CICS is set to the product pathname, you can use theexamples exactly as shown; otherwise, you must replace all instances of CICS with the CICS product pathname.CICS on Open SystemsRefers collectively to the CICS products for all supported UNIX platforms.TXSeries CICSRefers collectively to the CICS for AIX, CICS for Solaris, and CICS forWindows NT products.CICSRefers generically to the CICS on Open Systems and CICS for Windows NTproducts. References to a specific version of a CICS on Open Systemsproduct are used to highlight differences between CICS on Open Systemsproducts. Other CICS products in the CICS Family are distinguished by theiroperating system (for example, CICS for OS/2 or IBM mainframe-based CICSfor the ESA, MVS, and VSE platforms).How to send your commentsYour feedback is important in helping to provide the most accurate andhighest quality information. If you have any comments about this book or anyother WebSphere Application Server Enterprise Edition documentation, sendyour comments by e-mail to wasdoc@us.ibm.com. Be sure to include the nameof the book, the document number of the book, the version of WebSphereApplication Server Enterprise Edition, and, if applicable, the specific locationof the information you are commenting on (for example, a page number ortable number).xiiWebSphere: Getting Started with WebSphere Application Server

Chapter 1. Introducing the IBM WebSphere familyThis chapter examines the IBM approach to e-business and discusses how theproducts in the WebSphere family provide solutions to your e-businesschallenges. It also looks at some of the other tools available with theWebSphere family and how they fit into IBM’s overall approach. The finalsection of this chapter provides guidance on where to get more informationabout WebSphere family products.IBM and e-businessThe popularity of the World Wide Web (the Web) among both individuals andbusinesses has grown rapidly. Although individuals use the Web for manydifferent purposes, businesses use the Web primarily to provide products,services, and information to their customers, suppliers, strategic partners, andemployees.When the first businesses moved onto the Web, it was enough for them toprovide a few static Web pages that listed products and services for sale andprovided a telephone number or address to order those products and services.Businesses that provided information services (such as software companies)were among the first to enter this new frontier, and they often madeinformation and software products available for downloading.As new technologies were developed, static Web pages were no longersufficient. In response, businesses built active Web sites where customerscould order products directly, customers and suppliers could communicatewith the business, and employees could communicate with each other.While the Web side of many businesses was changing rapidly, non-Webbusiness information systems also went through major changes as applicationdevelopment spread into distributed systems from mainframe systems. TheOpen Group’s Distributed Computing Environment (DCE) and the ObjectManagement Group’s (OMG) Common Object Request Broker Architecture(CORBA) were two major technologies that provided the infrastructure forthese types of systems.Until recently, Web and non-Web business information systems remainedlargely detached from one another. The IBM e-business initiative and theWebSphere family have changed that. WebSphere enables businesses tointegrate their Web-based systems with their non-Web systems, producing asingle enterprise-wide business system. Copyright IBM Corp. 1999, 20011

The WebSphere family: providing e-business solutionsThe IBM WebSphere family was designed to help users realize the promise ofe-business. It is a set of software products that helps customers develop andmanage high-performance Web sites and integrate those Web sites with newor existing non-Web business information systems. It focuses on the followinggeneral types of businesses:v Businesses that want to use the latest technologies to establish a powerfulWeb presence or upgrade their current Web presencev Businesses that want to develop distributed, enterprise-wide businesssystems and applicationsv Businesses that want to integrate their Web presence with their existingcomputer systems and applicationsThe WebSphere family consists of the WebSphere Application Server andother WebSphere family software that is tightly integrated with theWebSphere Application Server and enhances its performance.WebSphere Application Server is fully compliant with Sun Microsystem’sJava 2, Enterprise Edition (J2EE ) standard and supports other commonindustry standards such as CORBA, XA, secure sockets layer (SSL), Kerberos,Logical Unit (LU) 6.2, and lightweight directory access protocol (LDAP).WebSphere Application Server: different editions for different cu

examples of WebSphere Application Server system configurations. v “Appendix. The library for WebSphere Application Server” on page 85 provides a complete list of the documentation available with WebSphere Application Server. Related information For further information on the topics and software discussed in this manual, see the following .

Related Documents:

In the three volumes of the IBM WebSphere Portal V4.1 Handbook, we cover WebSphere Portal Enable and Extend. The IBM WebSphere Portal V4.1 Handbook will help you to understand the WebSphere Portal architecture, how to install and configure WebSphere Portal, how to administer portal pages using WebSphere Portal; it will also discuss the

IBM WebSphere Portal Version 5 Family Enable WebSphere Application Server IBM HTTP server WebSphere Portal Server Out-of-the-Box Portlets Collaboration Services API Portal Toolkit WebSphere Translation Server WebSphere Studio Site Developer Content Management Personalization Portal Document Manager

WebSphere 8. Welcome to the F5 Deployment Guide for IBM WebSphere. This document provides guidance for deploying the BIG-IP Local Traffic Manager (LTM) with IBM WebSphere 8. The BIG-IP system can optimize IBM WebSphere at many layers: in front of the IBM HTTP . Servers, between HTTP Servers and WebSphere Application Servers, or to eliminate .

Unit Objectives 2 This unit was designed to enable you to: Start a development project that implements WebSphere Commerce V7. Describe the Runtime architecture of WebSphere Commerce. Describe the development model for WebSphere Commerce. Explain the application of Struts in WebSphere Commerce. Describe the presentation layer for WebSphere Commerce by using both

Download and install WebSphere MQ 2. Configure WebSphere MQ 3. Install OEG Gateway . Oracle Enterprise Gateway 6 / 30 4. Configure Gateway to send messages to WebSphere MQ 5. Configure Gateway to listen for messages from WebSphere MQ queue 6. Test Setup 2. Setting up the WebSphere MQ environment

WebSphere Application Server WebSphere MQ Use the most appropriate protocol C .net Java C JMS COBOL Java Jacl JMS Jython Web-Sockets C# HTTP WebSphere Application Server is a fully compliant Java Enterprise Edition (JEE) application server. The Java Message Service (JMS) is the JEE application messaging protocol. WebSphere MQ provides a fully

Figure 2 WebSphere Manages the Middle Tier in a Three-Tier Model One of the WebSphere products, WebSphere Portal, manages a variety of enterprise applications and supports application development and delivery. In the Lean Retail WebSphere Solution, content development and document management functions of WebSphere Portal were tested.

Level 1 Pass Level 1 Merit Level 2 Pass Level 2 Merit Level 2 Distinction Learning Aim A: Investigate Media Products A.1P1 Identify media products, their purpose and audience, using limited examples from one or more sectors. A.1M1 Outline media products, their purpose and audience, using basic examples from one or more sectors. A.2P1