2 options
WebSphere J2EE application development for the IBM @ server iSeries server / [Bob Maatta ... et al.].
- Format:
- Book
- Series:
- IBM redbooks.
- IBM redbooks
- Language:
- English
- Subjects (All):
- Application software--Development.
- Application software.
- Java (Computer program language).
- Web site development--Computer programs.
- Web site development.
- WebSphere.
- Physical Description:
- xiv, 440 p. : ill.
- Edition:
- 1st ed.
- Place of Publication:
- [Research Triangle Park, NC] : IBM, International Technical Support Organization, 2002.
- Language Note:
- English
- Contents:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Special notice
- Comments welcome
- Chapter 1. Introduction to J2EE
- 1.1 Java 2 Enterprise Edition (J2EE)
- 1.1.1 J2EE platform technologies
- 1.1.2 J2EE 1.2 required standard extension APIs
- 1.1.3 J2EE package levels in WebSphere
- 1.2 J2EE containers
- 1.3 J2EE components
- 1.3.1 Client-side components
- 1.3.2 Server-side components: Servlets
- 1.3.3 JavaServer Pages: Separating presentation logic
- 1.3.4 Server-side components: EJBs
- 1.4 J2EE services
- 1.4.1 Java Naming Directory Interface
- 1.4.2 Java Database Connectivity
- 1.4.3 Security
- 1.4.4 Transactions (JTA and JTS)
- 1.4.5 JavaBean Activation Framework (JAF)
- 1.5 J2EE communication
- 1.5.1 Remote method invocation (RMI/IIOP)
- 1.5.2 Java Messaging Service
- 1.5.3 JavaMail
- 1.6 J2EE packaging and deployment
- 1.6.1 J2EE deployment descriptor
- 1.7 J2EE platform roles
- 1.8 J2EE additional resources
- Chapter 2. Servlet and JSP development using VisualAge for Java
- 2.1 Servlet support in WebSphere Advanced Edition 4.0
- 2.1.1 IBM development environments for WebSphere applications
- 2.2 Introduction to servlets
- 2.2.1 Simple servlet example
- 2.3 Setting up VisualAge for Java to develop and test servlets
- 2.3.1 Loading the required features
- 2.3.2 Using the WebSphere Test Environment
- 2.3.3 Testing the servlet under VisualAge for Java Enterprise Edition 4.0
- 2.3.4 Exporting class files to a JAR file
- 2.4 Using JDBC to access an iSeries database
- 2.4.1 The architecture of the sample application
- 2.4.2 JDBCCatalogSupport class
- 2.4.3 JDBCItemCatalog class
- 2.4.4 Testing the application in the scrapbook
- 2.4.5 ItemServlet class
- 2.4.6 Running the ItemServlet inside VisualAge for Java.
- 2.4.7 Exporting the servlet from VisualAge for Java
- 2.5 Database connection pools
- 2.5.1 DataSource version
- 2.5.2 Running the ItemPoolServlet inside VisualAge for Java
- 2.5.3 Exporting the ItemPoolServlet servlet from VisualAge for Java
- 2.6 JSP support in WebSphere Version 4.0
- 2.6.1 JSP life cycle
- 2.6.2 JSP design
- 2.6.3 JSP servlet interface example
- 2.6.4 Running the CallJSP servlet inside VisualAge for Java
- 2.6.5 Exporting the CallJSP servlet from VisualAge for Java
- 2.7 Session management
- 2.7.1 Session tracking solutions
- 2.7.2 HttpSession interface
- 2.7.3 ItemSessionServlet example
- 2.7.4 Running the ItemSessionServlet servlet inside VisualAge for Java
- 2.7.5 Exporting the ItemSessionServlet from VisualAge for Java
- Chapter 3. WebSphere V4.0 assembly and deployment tools
- 3.1 WebSphere 4.0 application packaging overview
- 3.2 Application Assembly Tool overview
- 3.3 Application packaging and deploying scenario
- 3.3.1 Packaging MyHelloWorldServlet
- 3.3.2 Installing the MyHello Web module under the Single Server
- 3.3.3 Packaging ItemServlet
- 3.3.4 Installing the ItemServlet Web module on the Single Server
- 3.3.5 Running ItemServlet from an HTML file
- 3.3.6 Packaging ItemPoolServlet
- 3.3.7 Installing the ItemPool Web module on the Single Server
- 3.3.8 Packaging and deploying CallJSP
- 3.3.9 Packaging and deploying ItemSessionServlet
- 3.3.10 Installing the OrderEntry application on Advanced Edition
- 3.3.11 Packaging the MyHelloWorldApp enterprise application
- 3.3.12 Installing the MyHelloWorldApp application on Advanced Edition
- 3.3.13 Testing the MyHelloWorldApp application
- 3.3.14 Packaging the OrderEntryApp enterprise application
- 3.3.15 Installing the OrderEntryApp application on Advanced Edition
- 3.3.16 Testing the OrderEntryApp application.
- Chapter 4. Introduction to WebSphere Studio Application Developer
- 4.1 WebSphere Studio Application Developer overview
- 4.2 Getting started with Application Developer
- 4.2.1 Navigating in Application Developer
- 4.2.2 Importing resources
- 4.2.3 Customizing Application Developer
- 4.3 Working with Java code
- 4.3.1 Adding new methods
- 4.3.2 Compiling Java code
- 4.3.3 Running the Java code
- 4.3.4 Exporting the Java code
- 4.4 Conclusion
- Chapter 5. Building Java servlets and JSPs with WebSphere Studio Application Developer
- 5.1 Migrating code from VisualAge for Java
- 5.2 Migrating the OrderEntry WAR file
- 5.2.1 Importing a WAR file
- 5.2.2 Building the project and modifying the project's properties
- 5.2.3 Exploring the enterprise application structure in Application Developer
- 5.2.4 Testing the servlets
- 5.3 Developing a new application with Application Developer
- 5.3.1 New OrderEntry application logic
- 5.3.2 Building the application
- 5.3.3 Building the OrderEntry application with Application Developer
- 5.4 Conclusion
- Chapter 6. Introduction to Enterprise JavaBeans
- 6.1 The Enterprise JavaBeans specification
- 6.2 Enterprise JavaBeans architecture definition
- 6.3 How EJB technology fits into the Java architecture
- 6.4 Why EJB is important
- 6.5 Leveraging Java and EJB technology
- 6.6 EJB architectural overview
- 6.6.1 The EJB server
- 6.6.2 Types of components
- 6.6.3 Component content
- 6.7 EJB roles
- 6.7.1 Enterprise JavaBean provider
- 6.7.2 Application assembler
- 6.7.3 Application deployer
- 6.7.4 Server provider
- 6.7.5 Container provider
- 6.8 Using EJB technology on the iSeries server
- 6.8.1 Overview of Java for the iSeries server
- 6.8.2 EJB technology on the iSeries server
- 6.9 EJB interoperability with other distributed architectures
- 6.9.1 CORBA.
- 6.9.2 Component Object Model (COM)
- 6.9.3 IBM WebSphere Business Components
- 6.10 Conclusion
- Chapter 7. Overview of the OrderEntry application
- 7.1 The ABC Company
- 7.2 The ABC Company database
- 7.3 A customer transaction
- 7.4 Application flow
- 7.5 Customer transaction flow
- 7.6 Database table structure
- 7.7 OrderEntry application database layout
- 7.8 Database terminology
- Chapter 8. iSeries EJB application development scenario
- 8.1 OrderEntry application architecture with objects
- 8.2 Business data: Entity Enterprise JavaBeans
- 8.2.1 Database access: Using a connection pool
- 8.2.2 Persistence: Container or bean managed
- 8.2.3 Container-managed persistence
- 8.2.4 Bean-managed persistence
- 8.3 Business processes: Session Enterprise JavaBeans
- 8.3.1 Three-tier versus two-tier architecture
- 8.3.2 Stateless or stateful beans
- 8.3.3 Order Entry example
- 8.3.4 Stateless session bean: OrderPlacement
- 8.3.5 Stateful session bean: OrderEntryClerk
- 8.4 Conclusion
- Chapter 9. Developing EJBs with Application Developer
- 9.1 Bottom-up mapping
- 9.1.1 Creating an EJB project
- 9.1.2 Importing a schema
- 9.1.3 Creating the entity EJB from the imported schema
- 9.1.4 Defining getter methods as read-only
- 9.1.5 Deploying the Stock bean in the WebSphere Test Environment
- 9.2 Top-down mapping
- 9.2.1 Adding methods to the Stock bean
- 9.2.2 Mapping the Stock bean
- 9.2.3 Deploying the stock bean and testing
- 9.3 Meet-in-the-middle mapping
- 9.3.1 Creating the stock enterprise bean
- 9.3.2 Adding the methods
- 9.3.3 Mapping the stock bean
- 9.3.4 Deploying and testing the enterprise bean
- 9.4 Developing a bean-managed persistence (BMP) entity bean
- 9.4.1 Testing the BMP bean
- 9.5 Conclusion
- Chapter 10. Building Java applications with Enterprise JavaBeans.
- 10.1 Developing the HelloWorld EJB application
- 10.1.1 Creating the HelloWorld bean in Application Developer
- 10.1.2 Creating a servlet that uses the EJB
- 10.1.3 Creating a Java client application that uses the EJB
- 10.2 Building Java applications with Application Developer
- 10.2.1 The ItemsDb class
- 10.2.2 Using the ItemsDb class
- 10.3 Building servlets
- 10.4 Migration from EJB version 1.0 to version 1.1
- 10.5 Installing the OrderEntry application on the server
- 10.5.1 Generating the OrderEntry enterprise application
- 10.5.2 Deploying
- 10.6 Conclusion
- Chapter 11. Interfacing to legacy applications
- 11.1 Interfacing to legacy applications
- 11.2 Modifying the RPG application
- 11.2.1 Processing the submitted order
- 11.3 Enhancing the Java application
- 11.3.1 Changing the CartServlet servlet
- 11.3.2 Changing the ItemsDb class
- 11.3.3 Changing the OrderPlacement session bean
- 11.4 Using data queues to interface to legacy applications
- 11.4.1 Interfacing to data queues from EJBs
- 11.4.2 The writeDataQueue method
- 11.5 Using MQSeries to interface to legacy applications
- 11.5.1 The MQCon class
- 11.5.2 Including MQSeries in the OrderEntry application
- 11.5.3 Changing the ItemsDb class
- 11.5.4 Changing the OrderPlacement session bean
- 11.6 Using XML to interact with applications
- 11.6.1 Using XML
- 11.7 Conclusion
- Chapter 12. The Command package
- 12.1 The IBM Framework for e-business
- 12.2 Distributed Java applications
- 12.3 The Command package
- 12.3.1 The Command interface
- 12.3.2 Facilities for creating commands
- 12.4 Creating a command
- 12.4.1 Benefits of the Command package framework
- 12.4.2 Using the EJBCommandTarget class
- 12.4.3 Creating the GetCustomerCmdEJB command
- 12.4.4 Using the GetCustomerCmdEJB command
- 12.5 Creating your own command targets.
- 12.5.1 Constructing the GetCustomerCmd command and its target.
- Notes:
- "May 2002."
- "This edition applies to Version 4, Release 0, of WebSphere Application Server Advanced Edition for iSeries, Program number 5733-WA4, and Version 4, Release 0, of WebSphere Application Server Advanced single server edition for iSeries, Program number 5733-WS4, for use with the OS/400 V5R1"--T.p. verso.
- "SG24-6559-00."
- Includes bibliographical references (p. 427-428) and index.
- OCLC:
- 939263409
The Penn Libraries is committed to describing library materials using current, accurate, and responsible language. If you discover outdated or inaccurate language, please fill out this feedback form to report it and suggest alternative language.