WebSphere version 5 application development handbook / [Ueli Wahli ... et al.].

Format:

Book

Contributor:

Wahli, Ueli.

International Business Machines Corporation. International Technical Support Organization.

Series:

IBM redbooks.

IBM redbooks

Language:

English

Subjects (All):

Application software--Development.

Application software.

Web site development.

WebSphere.

Physical Description:

xxviii, 700 p. : ill.

Edition:

1st ed.

Place of Publication:

[S.l.] : IBM, International Technical Support Organization, c2003.

Language Note:

English

System Details:

text file

Summary:

This IBM Redbooks publication provides detailed information on how to develop J2EE-compliant Web applications for WebSphere Application Server Version 5 using WebSphere Studio Application Developer Version 5.1 as an integrated development environment. Also covered are a variety of application development tools from IBM and Open Source. The target audience for this book includes the entire application development team, especially architects and developers. It also includes developers with experience of earlier versions of the WebSphere products, who are looking to migrate to Version 5. This book is organized in four main parts: - Introduction—covering the J2EE programming model, the development process, and software configuration management - Requirements, analysis, architecture, and design—covering the early phases of a project, using Rational XDE - Implementation—covering the coding of business logic, presentation, and Web services, using Application Developer - Debugging, unit testing, deployment, and measurements—covering the test and production phases of a project, using Application Developer, Application Server, and Open Source tools Throughout the book, we refer to PiggyBank, a sample J2EE application we create step-by-step to illustrate the use of the tools, concepts, and principles of the application development process. Please note that the additional material referenced in the text is not available from IBM.

Contents:

Front cover

Contents

Notices

Trademarks

Preface

The team that wrote this redbook

Become a published author

Comments welcome

Part 1 Introduction

Chapter 1. Introduction

Target audience of this redbook

Content of this redbook

Objectives

Context

What this redbook is not

Complementary readings

Content overview

PiggyBank

The case

Web interface

Teller interface

Technical environment

Products

Instructions

IBM products

Open Source products

DB2 Universal Database

WebSphere Application Server

WebSphere Studio Application Developer

Eclipse

WebSphere Studio product family

Rational XDE

Rational ClearCase

Struts

Log4J

Ant

JUnit

Cactus

JMeter

Concurrent Versions System

Chapter 2. J2EE programming model

J2EE platform

J2EE clients

Web clients

Hyper Text Transfer Protocol (HTTP)

Hyper-Text Markup Language (HTML)

eXtensible Markup Language (XML)

JavaScript and document object model (DOM)

Multipurpose Internet Mail Extensions (MIME)

Application clients

Web services

J2EE roles

J2EE application model and components

J2EE application model

Components

Servlets

Filters

Life cycle events

JavaServer Pages (JSPs)

Enterprise JavaBeans (EJBs)

Container-managed relationships (CMR)

EJB query language (EJB QL)

Local and remote interfaces

J2EE packaging

Containers

Web container

EJB container

JCA container

Application client container

Applet container

J2EE services

Java Naming and Directory Interface (JNDI)

Java Database Connectivity (JDBC)

Java Transaction API (JTA) and Java Transaction Service (JTS)

Isolation level

Java Messaging Service (JMS)

J2EE benefits

WebSphere versions

WebSphere Application Server architecture.

Node

Configuration repository

Application Server

Web server and Web server plug-in

Embedded HTTP server

Virtual hosts

Administrative Console and application

Admin service

Scripting client

JMS server

Name server

Security service

Web services engine

Summary

Chapter 3. Development process

The need for a process

Waterfall model

An iterated process

The need for architecture

Rational Unified Process

Four phases of a software development project

eXtreme Programming

Values

Practices

Phases

Project roles

Unified Modeling Language

Static diagrams

Dynamic diagrams

Development using frameworks

Starting with a framework

What is a framework?

Frameworks drawbacks

Framework adoption

Frameworks used for PiggyBank

Chapter 4. Software configuration management

Introduction

Resource management

Managing versions with CVS

Using CVS

Working with a project

Caveats

Using CVS with Application Developer

Creating a repository

Connecting to a repository

Retrieving a project from the repository

Registering a project with the repository

Committing updates

Retrieving updates

Creating a version

Merging conflicts

Version management with Rational ClearCase LT

Using ClearCase

Using ClearCase with Application Developer

Creating the Versioned Object Base

Creating the view

Registering a project with ClearCase

Editing a file

File management operations

Retrieving a project from the view

Removing a view

Part 2 Requirements, analysis, and design

Chapter 5. Requirements

Requirements gathering

Techniques for requirements gathering

Best practices for requirements gathering

Use case modeling

Template for use cases.

PiggyBank use cases

Display balance

Transfer money

Cash check

Organizing your use cases

Creating PiggyBank use case diagrams

Activity diagrams

Creating the display balance activity diagram

PiggyBank prototype

Prototype process

Types of prototypes

Benefits of prototyping

PiggyBank user interface

Welcome page

Login

Main menu

Display accounts

Transfer

Logout

Teller application

Chapter 6. Analysis

Analysis model

Analysis stereotypes

Creating the analysis model in Rational XDE

Finding classes

Defining the domain model

Describing the domain model in Rational XDE

Adding classes

Adding attributes

Adding relationships

Realizing the use cases

Boundary and controller classes

Adding the collaboration instance

Creating the sequence diagram

Using packages

Completing the sequence diagram

Adding notes to the diagram

Collaboration class diagram

Sequence diagram

Chapter 7. Architecture

What is software architecture?

Architectural views

Runtime architecture

Application architecture

Presentation layer

Standalone client

Web client

Servlet - Model 1

MVC - Model 2

Business layer

Session facade

Business delegate

Transfer object

Integration layer

Data access object

Architecture by tiers

Chapter 8. Design

Moving from analysis to design

Design model structure

Design layers

Design subsystems

Realization package

Creating the design model in Rational XDE

Preferences

Creating the design model

Creating the design model structure

PiggyBank design

Design procedure

Integration layer design

Create a subsystem.

Create classes

Create method

Create relationships

Business layer design

Domain model

Create domain model classes

Create session facade classes

Business delegate interface definitions

Business delegate EJB implementation design

Presentation layer design

ApplicationInitServlet

BaseServlet

BaseAction

Common elements design

PiggyBank log wrapper

Designing the log wrapper

PiggyBank home factory

Designing the home factory

Packaging the application

Defining components

Enterprise application packaging

Deployment diagram

Part 3 Implementation

Chapter 9. Considerations

Application Developer guidelines

Workspace

.Workspace structure

Utility project

Project structure

Source code formatting

Application Developer preferences

Checkstyle

Application logging

Requirements for a logging framework

Logging implementation

Automation opportunities

Using JNDI

Obtaining an InitialContext

Local and global JNDI namespaces

Caching

Coding for performance

General performance tips

Database connection pooling

Using System.out

String concatenation

JSP and servlet performance tips

Storing objects in HTTP sessions

Using HTTP sessions in JSPs

Servlet multi-threading

EJB performance tips

Accessing EJBs from client code

Transaction isolation levels

Managing application versions

Specifying the application name

Partitioning Web applications in the URI namespace

Partitioning using virtual hosts

Partitioning using the Web application context root

Partitioning EJBs in the JNDI namespace

Partitioning access to database and other resources

Security

Application-managed security

Container-managed security.

Reactive or proactive security

Chapter 10. Code generation

Code generation

Log wrapper code generation

Creating the Java modeling project

Using the copy procedure

Using the move procedure

Synchronizing the model and code

Reverse engineering (Java)

Create the reference model

Use the reference model

Extend the log wrapper

PiggyBank EJB generation

Creating the EJB modeling project

Chapter 11. Business logic

PiggyBank business layer

Preparing Application Developer

Import required projects

Implementing the components

Implementing the framework project

Creating the Java project

Tailoring the logging implementation

Creating the packages

Creating the classes

Creating the IPiggyBankBusinessDelegate interface

Creating the BusinessDelegateFactory

Implementing the business delegate project

Creating the PiggyBankEJBDelegateImpl

Creating the PiggyBankEJBDelegateFactory

Creating an enterprise application for the EJBs

Creating an EAR project with an EJB module

Preparing the WebSphere test environment

Server project

WebSphere Version 5.0.2 server

Adding the enterprise application to the server

Configuring the server with a data source

Define an authentication alias

Define a data source

Setting the server class path

Enabling security for the server

Disable security for now

Utility projects

Adding a utility project to an enterprise application

Module dependency

Implementing the EJB project

Project properties

Reviewing the model

Creating the transfer objects

Creating the CMP entity beans

Create the Customer entity bean

Create the CmpEntityAdapter.

Create the Account entity bean.

Notes:

"December 2003."

Includes bibliographical references and index.

OCLC:

63540289