Patterns : self-service application solutions using WebSphere for z/OS V5 / Franck Injey ... [et al.].

Format:

Book

Author/Creator:

Injey, Franck.

Contributor:

Safari Tech Books Online.

Series:

IBM redbooks.

IBM redbooks

Language:

English

Subjects (All):

Client/server computing.

WebSphere.

Physical Description:

1 online resource (380 p.)

Edition:

1st ed.

Place of Publication:

San Jose : IBM, c2003.

Language Note:

English

Contents:

Front cover

Contents

Notices

Trademarks

Preface

The team that wrote this redbook

Become a published author

Comments welcome

Part 1 Self-Service patterns

Chapter 1. Patterns for e-business

1.1 Overview

1.2 The Patterns for e-business layered asset model

1.3 How to use the Patterns for e-business

1.3.1 Business, Integration, or Composite pattern, or a custom design

1.3.2 Selecting Application patterns

1.3.3 Review Runtime patterns

1.3.4 Review Product mappings

1.3.5 Review guidelines and related links

1.4 Summary

Chapter 2. The Self-Service Business pattern

2.1 Self-Service applications

2.2 Self-Service application patterns

2.3 Application patterns used in this book

Chapter 3. Runtime pattern

3.1 An introduction to the node types

3.1.1 Web application server node

3.1.2 User node

3.1.3 Public Key Infrastructure (PKI)

3.1.4 Domain Name System (DNS) node

3.1.5 Protocol firewall node

3.1.6 Domain firewall node

3.1.7 Directory and security services node

3.1.8 Database server node

3.1.9 Existing applications and data node

3.1.10 Web server redirector node

3.1.11 Application server node

3.2 Runtime patterns for Stand-Alone Single Channel

3.2.1 Basic Runtime pattern - Stand-Alone Single Channel

3.2.2 Runtime pattern: Variation 1

3.2.3 Runtime pattern: Other variations

3.3 Runtime patterns for Directly Integrated Single Channel

3.3.1 Basic Runtime pattern - Directly Integrated Single Channel

3.3.2 Runtime pattern: Variation 1

3.3.3 Runtime pattern: Other variations

Chapter 4. Product mappings

4.1 Overview

4.2 IBM WebSphere Application Server for z/OS V5

4.3 IBM CICS TS

4.4 IBM IMS

4.5 IBM WebSphere MQ

4.6 Product mappings for Stand-Alone Single Channel.

4.7 Product mappings for Directly Integrated Single Channel

4.8 Security considerations

Part 2 Guidelines

Chapter 5. WebSphere Application Server for z/OS V5

5.1 WebSphere Application Server for z/OS V5

5.2 Base configuration

5.2.1 HFS structure of the base application node

5.2.2 Creating and administering the base Application Server node

5.2.3 Multiple base Application Server nodes

5.2.4 Multiple servers in a base Application Server node

5.2.5 Limitations of the base Application Server

5.3 Moving to Network Deployment cells

5.3.1 The Deployment Manager

5.3.2 HFS structure of the Deployment Manager

5.3.3 Nodes and node agents

5.3.4 Federating a base Application Server node

5.3.5 Differences - base Application Server node and Network Deployment system

5.4 Network deployment in a sysplex

5.4.1 Multiple cells in a sysplex

5.4.2 Clustering servers

Chapter 6. J2EE connectors

6.1 J2EE connector architecture

6.1.1 J2EE Connector Architecture overview

6.2 CICS Transaction gateway V5.01

6.3 IMS Connector for Java

Chapter 7. J2EE 1.3 and WebSphere V5 security concepts

7.1 Overview

7.1.1 Security server topology

7.1.2 Terminology used for J2EE security

7.1.3 User registries

7.1.4 Global security

7.2 J2EE container-based security

7.2.1 Role-based authorization

7.2.2 Web container authentication and authorization

7.2.3 EJB container authentication and authorization

7.2.4 Propagation

7.3 Resource authentication

7.4 Security interoperability using IIOP

7.4.1 Identity assertion

7.5 Additional capabilities

7.5.1 Single Sign-On (SSO)

7.5.2 Java 2 security

7.5.3 JAAS

7.5.4 Additional programmatic login/logout capabilities

7.5.5 Cryptographic application and data security

Part 3 Technical scenarios.

Chapter 8. Patterns Development Kit Lite (PDK Lite)

8.1 Patterns Development Kit Lite (PDK Lite) overview

8.1.1 Patterns Development Kit Lite

8.2 Understanding the PDK Lite application

8.3 PDK use cases

8.3.1 Display Funds

8.3.2 Transfer Funds

8.4 Architectural overview model

8.5 System design overview

8.5.1 Component model

8.5.2 Object model

8.6 Design considerations

8.6.1 Validation of client input

8.6.2 Singleton factories

8.6.3 Model-view-controller implementation

8.6.4 Using the WebSphere Command Framework

8.6.5 Session EJB facade

8.6.6 Caching of EJB home references

8.6.7 Using two-phase commit

8.7 PDK development

8.7.1 Tools and APIs

8.7.2 PDK project structure

8.7.3 Team development

8.8 Installing the PDK Lite application

8.8.1 Creating the tables on DB2 for z/OS

8.8.2 Java Authentication and Authorization Services

8.9 JDBC configuration

8.9.1 WebSphere and DB2 on z/OS

8.9.2 WebSphere and DB2 on Linux for zSeries

8.9.3 WebSphere on Linux for zSeries and DB2 on z/OS

Chapter 9. Stand-Alone scenario

9.1 Architectural overview model

9.2 z/OS option

9.3 Linux for zSeries option

Chapter 10. Web services scenario

10.1 Architectural overview model

10.2 System design overview

10.2.1 Component model

10.2.2 Object model

10.3 Low level design considerations

10.3.1 Application pattern

10.3.2 Transmission pattern

10.3.3 SOAP messaging mechanism and synchronous pattern

10.3.4 Message structure

10.4 Runtime configuration

10.4.1 Single and two-tier runtime environments

10.4.2 Configuring Web service requester

10.4.3 Configuring a Web service provider

Chapter 11. J2EE Connector Architecture scenarios

11.1 Architectural overview model

11.2 System design overview

11.2.1 Component model

11.2.2 Object model.

11.3 Low level design considerations

11.3.1 Connection management

11.3.2 Creating the input and output record

11.3.3 Data conversion

11.3.4 Executing the enterprise application

11.3.5 Transaction management

11.3.6 Security

11.4 Application development using J2EE Connectors

11.4.1 Installing the J2EE Connector resource adapter

11.4.2 Create a session EJB

11.4.3 Testing the session EJB

11.5 CICS TS runtime configuration

11.5.1 Runtime configuration design

11.5.2 WebSphere Application Server configuration

11.5.3 CICS Transaction Server configuration

11.6 IMS TM runtime configuration

11.6.1 IMS Connect configuration

11.6.2 WebSphere Application Server configuration

Chapter 12. JMS scenario

12.1 Architectural overview model

12.1.1 Java Messaging Service (JMS) introduction

12.2 System design overview

12.2.1 Component model

12.2.2 Object model

12.3 Low level design considerations

12.3.1 Point-to-point messaging model

12.3.2 Message structure

12.3.3 JMS resource lookups using JNDI

12.3.4 Managing JMS resources

12.3.5 Synchronous vs. asynchronous

12.3.6 Message selectors

12.3.7 Message time to live

12.3.8 Persistent vs. non-persistent messages

12.3.9 Enterprise application design

12.3.10 Alternate publish/subscribe design

12.4 Advantage and disadvantages of JMS

12.5 Runtime configuration

12.5.1 Configuration of the queue sharing group

12.5.2 JNDI name spaces

12.5.3 Application Server tier configuration

12.5.4 Enterprise Server tier configuration

Part 4 Appendixes

Appendix A. WebSphere configuration

z/OS

HFS structure

was.env

control.jvm.options

servant.jvm.options

resources.xml

Linux for zSeries

Appendix B. Configuring a queue sharing group in WebSphere MQ

Set up the DB2 environment to support MQ shared queue.

Create the storage group - CSQ45CSG

Create the database - CSQ45CDB

Create the tablespaces

Create the DB2 tables and associated indexes - CSQ45CTB

Bind the DB2 plans - CSQ45BPL

Grant execute authority - CSQ45GEX

Set up the CFRM policy with the MQ structures

Add the MQ data sharing group entry to the DB2 table

Update the ZPARM

Define the shared queues between the two MQ subsystems

Appendix C. Additional material

Locating the Web material

Using the Web material

System requirements for downloading the Web material

How to use the Web material

Glossary

Related publications

IBM Redbooks

Other publications

Online resources

How to get IBM Redbooks

Help from IBM

Index

Back cover.

Notes:

Bibliographic Level Mode of Issuance: Monograph

OCLC:

137342263