Migrating applications from WebSphere for z/OS V4 and V3.5 to V5 / [Tamas Vilaghy ... et al.].

Format:

Book

Contributor:

Vilaghy, Tamas.

International Business Machines Corporation. International Technical Support Organization.

Series:

IBM redbooks.

IBM redbooks

Language:

English

Subjects (All):

Web site development.

Application software--Development.

Application software.

WebSphere.

z/OS.

Physical Description:

xiv, 336 p. : ill.

Edition:

1st ed.

Place of Publication:

[S.l.] : IBM, International Technical Support Organization, 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 Infrastructure migration

Chapter 1. Migration strategy

1.1 Introduction

1.2 Development environment migration

1.3 Application migration

1.4 Preparing for runtime migration

1.5 Runtime migration

1.6 Migration scenarios

1.6.1 Monoplex scenario

1.6.2 Sysplex scenario

Chapter 2. WebSphere V5 Network Deployment

2.1 Base Application Server node

2.1.1 HFS structure of the base application node

2.1.2 Creating and administering the Base Application Server node

2.1.3 Multiple Base Application Server nodes

2.1.4 Multiple servers in a Base Application Server node

2.1.5 Limitations of the Base Application Server

2.1.6 TCP/IP port numbers and conflicts

2.2 Moving to Network Deployment cells

2.2.1 Deployment Manager

2.2.2 HFS structure of the Deployment Manager

2.2.3 Nodes and Node Agents

2.2.4 Federating a Base Application Server node

2.2.5 Pros and cons for base server or Network Deployment

2.3 Network Deployment in sysplex

2.3.1 Multiple cells in sysplex

2.3.2 Clustering servers

Chapter 3. Rolling out Version 5 in sysplex

3.1 WebSphere for z/0S V4.0.1 and V5 coexistence

3.2 Planning for WebSphere V5 for z/OS

3.2.1 HFS structure

3.2.2 Naming standards

3.2.3 Target infrastructure

3.3 Building Base Application Servers

3.3.1 Your first base server

3.3.2 Configuring an Integral JMS Provider

3.3.3 Building additional base servers

3.4 How to federate in a sysplex

3.4.1 Creating the Deployment Manager node

3.4.2 Federation

3.4.3 Deployment Manager console

3.4.4 Starting and stopping servers

3.5 Clustering

3.6 DB2 configuration

Chapter 4. System management.

4.1 WebSphere Administrative Consoles

4.1.1 Version 4.0.1 Administrative Console GUI

4.1.2 Version 5.0 Administrative Console GUI

4.1.3 Common Administrative Actions

4.2 WebSphere configuration objects

4.3 wsadmin primer

4.3.1 Background on BSF, JMX, and WebSphere scripting

4.3.2 wsadmin command syntax and usage

4.3.3 WebSphere objects available to scripts

4.3.4 Script Launcher

4.3.5 Properties used by scripting

4.3.6 Profiles

4.3.7 Using templates

4.3.8 Modifying attributes

4.4 Migration mapping

4.4.1 Migration steps

4.4.2 Classification of scripts

4.4.3 wsadmin V5.0

4.5 Migrating from SMAPI

Part 2 Application migration

Chapter 5. Application rollout in the sysplex

5.1 Migration paths to production

5.2 Phased rollout

5.3 The rollout environment

5.3.1 Version 4.0.1 production

5.3.2 Unit test

5.3.3 Acceptance test

5.3.4 System test

5.3.5 Performance test

5.4 Non-disruptive rollout to production

5.4.1 Using a Web server to redirect requests

5.4.2 Change management

5.4.3 Using relative references for portable applications

5.5 Operational considerations

5.5.1 The SMEUI interactive user interface

5.5.2 The SMAPI script interface

5.6 Application testing environments

5.6.1 Phased cut-over

5.7 Example: rolling out Trade2

5.7.1 Converting the Trade2 EAR

5.7.2 Importing into WebSphere Studio

5.7.3 Setting up the unit test environment

5.7.4 Unit testing the Trade2 application in WebSphere Studio

5.7.5 Exporting the EAR

5.7.6 Deploying the EAR to the acceptance test monoplex

5.7.7 Acceptance testing in WebSphere for z/OS V5

5.7.8 Redeploying the EAR to the sysplex

5.7.9 Testing Trade2 on the sysplex

5.8 Making the URL point to the V5 sysplex

Chapter 6. Application migration from Version 3.5

6.1 Introduction.

6.2 Packaging and assembling

6.2.1 Web applications (WAR files)

6.2.2 Building enterprise applications (EAR files)

6.3 Deployment procedures

6.4 Security

6.5 ASCII/EBCDIC considerations

6.6 Connectors

6.7 JDBC/SQLJ

6.8 Plug-in

6.9 Migration tools

Chapter 7. Application migration from Version 4

7.1 Overview

7.1.1 Issues

7.2 Migration tools

7.2.1 Importing into WebSphere Studio Application Developer V5

7.2.2 Application Assembly Tool

7.2.3 ejbdeploy

7.2.4 390fy

7.2.5 Class API Checker Tool

7.2.6 Converting the Trade2 EAR to J2EE 1.3 using the AAT

7.2.7 Migrating a J2EE 1.2 EAR file to J2EE 1.3 using WSAD

7.3 Remapping CMPs

7.4 Migration verification

7.4.1 Configuring a DB2 client alias for the database

7.4.2 Defining the data source

7.4.3 Setting the data source properties

7.4.4 Testing from WebSphere Studio

7.5 J2EE component levels

7.6 Resources

7.7 Packaging and assembling

7.8 Security

7.9 Connectors

7.10 ASCII/EBCDIC

7.11 JDBC/SQLJ

7.11.1 db2sqljjdbc.properties

7.11.2 Loading external modules

7.11.3 Accessing DB2 Version 6 data

7.12 JMS

7.13 Transactions

7.14 Deployment descriptors

7.15 The WebSphere Plug-in

7.16 Classloader

7.16.1 MANIFEST classpath

7.16.2 Loading executables

7.17 The deployment process

7.17.1 The Deployment Manager GUI

7.18 Java clients

Chapter 8. Development tool migration

8.1 Migrating between versions of WebSphere Studio

8.2 WebSphere Studio migration documentation

8.3 WebSphere Studio fix packs and interim fixes

8.4 Migrating from VisualAge for Java

8.5 Applications using CCF, J2C and EAB

Chapter 9. Application migration security aspects

9.1 Application migration security aspect checklist

9.2 Application migration strategies.

9.3 Migrating IBM HTTP Server thread-level-based security

9.3.1 Affected environments

9.3.2 What causes this problem?

9.3.3 How can you make it work again?

9.4 Migrating WebSphere Application Server thread-level-based security

9.4.1 Affected environments

9.4.2 What is causing this problem?

9.4.3 How can you make it work again?

9.5 Solution strategies for thread-level-based security problems

9.5.1 Affected environments

9.5.2 Hypothetical historical application scenarios

9.5.3 Scenario 1: Multiple restricted methods to access OS resources

9.5.4 Scenario 2: Restrict the caller by using programmatic security

9.5.5 Scenario 3: Separate Application Server as access engine

9.5.6 Scenario 4: Java2 security and JAAS for access control

9.6 Security aspects when migrating CCF connectors

9.6.1 Affected environments

9.6.2 What is causing this problem?

9.6.3 How can you make it work again?

9.7 Security aspects when migrating J2C connectors

9.7.1 Affected environments

9.7.2 What is causing this problem?

9.7.3 How can you make it work again?

9.8 Migrating SOMDOBJS to EJBROLE

9.8.1 Using SOMDOBJS with WebSphere simple configuration option

9.8.2 Migrating from SOMDOBJS to Web container, EJBROLE profiles

Part 3 Appendixes

Appendix A. Additional material

Locating the Web material

Using the Web material

System requirements for downloading the Web material

How to use the Web material

Abbreviations and acronyms

Related publications

IBM Redbooks

Other publications

Online resources

How to get IBM Redbooks

Help from IBM

Index

Back cover.

Notes:

"November 2003."

Includes bibliographical references and index.

OCLC:

137342256