Was 5.1 To 6.1 Updated

© 2008 IBM Corporation

IBM Websphere Software

Websphere Application Serverv5.1 to v6.1 Migration

Subrahmanyam Thuraga, PMPAdvisory IT SpecialistIBM India

| 12 Oct 2008 | Karapakkam, Chennai |


WAS 5.1 - 6.1 Migration © 2008 IBM Corporation2

Agenda

Review of v5.1 Architecture & v6.x Architecture (Delta that impacts Migration) v5.1 to v6.1 Migration Roadmap

– Topology Changes (Profiles, Node & Node Agent, Edge Components)

– Java 5

– Server Settings Migration, Migration Wizard & Commands

– Changes in Supported versions of components & Third Party Products

– API migration

v6.x New Concepts (Optional for core 5.1 to 6.1 migration)– Integrated TPV

– SDO, JSF, SIP Servlets, JSR 168 Portlets

– Installation factory

– WAS 6.1 Feature Packs

– EJB 3.0 Feature Pack

– Web Services Feature Pack

– Web 2.0 Feature Pack WAS 7.0!



Agenda

Review of v5.1 Architecture & v6.x Architecture (Delta that impacts Migration)

v5.1 to v6.1 Migration Roadmap– Topology Changes (Profiles, Node & Node Agent, Edge Components)

– Java 5



– API migration










Unifying WebSphere Application Server Code

The process of unifying the code and processes across z/OS, iSeries and distributed platforms that has spanned several releases is now completed in V6.1

V5.0 V5.0.X V5.1 V6.0

Common Security ModelParts 1 & 2

Common Samples

Z/OS becomes fully CTS compliant

CommonAdmin Model

Single Code base for PME

Common Service for PME

Common processes around a single code base

WebSphere Application Server V6.X: Common processes around a single code base

Common source code management Common build libraries Automated functional test case reuse Compliance Test Suite reuse Common Customer Support

Common Test Automation

V6.1



WebSphere Application Server Function Evolution

V5.04Q2003

V5.12Q2004

V6.0.X4Q2004

V6.12Q2006

V4.0.X2001

…

•J2EE 1.2 support•Configuration data in database•Support for Web Services

•J2EE 1.2, 1.3 support•JDK 1.3 support•Web Services based on Apache engine

•Configuration data in XML files•Packaging simplification•Network Deployment Cell for clustering and scalability•Built-in messaging engine based on WebSphere MQ

•Merging of z/OS and distributed code base

•J2EE 1.2, 1.3 support•JDK 1.4 support•Web Services based on JSR 101/109 on IBM engine•Support for JSF

•J2EE 1.2, 1.3, 1.4 support•Web Services based on J2EE 1.4 •WS-Security and Basic profile support•Common data model, SDO•Inclusion of PME for all packaging

•High Availability Manager•Java-based Messaging engine •Mixed version cell support for V5.0.X and V6

•J2EE 1.2, 1.3, 1.4 support•JDK 5.0 support•Portlet support•Session Initiation Protocol (SIP) support•WS-Notification, WS-Business Activity and WS-Resource Framework, WS-I BSP support•Virtual Member Manager

•OSGi based architecture•Consumability and ease of use enhancements•Serviceability enhancements

Potential functions:

•SOA core includes support for Service Component Architecture, Business Objects, Common Event Infrastructure

•WS-*

•J2EE 1.5 (JEE 5)



WAS Deprecation Policy

If a feature is listed here as deprecated, IBM intends to remove this capability in a future release of the product. Generally, IBM will not remove a feature until at least two major releases or three full years (whichever is longer) after the release in which it is deprecated.

– For example, features that were deprecated in WebSphere Application Server Version 5.0, Version 5.0.1, or Version 5.0.2 will not be removed from the product until after Version 6.0 because both Version 5.0.x and Version 5.1.x are considered to be major releases.

– In rare cases, it might become necessary to remove features sooner; such cases are indicated clearly and explicitly in the descriptions of these deprecated features in this article.

– http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/welcome_nd.html (Deprecated and removed features list)

– Features deprecated in Version 6.1 – Features deprecated in Version 6.0.2 – Features deprecated in Version 6.0 – Features deprecated in Version 5.1.1 – Features deprecated in Version 5.1 – Features deprecated in Version 5.0.2 – Features deprecated in Version 5.0.1 – Features deprecated in Version 5.0

V5.0.X

V5.1.X

V6.0.X

•New API introduced•Deprecated but still supported•Deprecated but still supported•V5.0.X APIs may be removedV6.1



Key Point(s)

V5

Deployment Manager

(1/platform)

V5

Application Server IBM HTTP Server

Web server plug-ins (1/platform)

V5

Application Client (1/platform)

V5

Data Direct JDBC Drivers

(Windows Only)

V5

Application Server Toolkit

(Windows, Linux)

V6

+ + +

Four CDs consolidated into 1 CD Components are packaged to allow for

incremental installation. Install only what you need

V6

1/platform



V6 Basic Architecture

MessagingEngine

Em

bedded HT

TP

Server

Em

bedded HT

TP

Server

Web Container

Servlets JSPs

EJB Container

EJBs

ApplicationDatabases

ApplicationDatabasesApplicationData

ApplicationData

XML Configuration

Files

XML Configuration

Files

HTTP Server Plug-

in

HTTP Server Plug-

in

HTTP Server

Application ServerApplication Server

Plug-in Configuration File

Plug-in Configuration File

Dynamic CacheDynamic Cache Name ServerName Server SecuritySecurity

…… …… ….….

Web ServicesEngine

Data ReplicationData Replication JMXJMX Transaction.Transaction.



Administering the Server

Messaging Engine

Messaging Engine

Em

bedded H

TT

P

Server

Em

bedded H

TT

P

Server

WebContainer

EJBContainer

XML Configuration

Files

XML Configuration

Files


Admin consoleAdmin

console

C:\> wsadmin

Web-basedadministrative console

wsadmincommand-line client

RMI/IIOP

HTTP(S)Admin

MBeansAdmin

MBeans

Web Services Engine

Web Services Engine

Adm

in. Service

Adm

in. Service

SOAP/HTTP



Accessing Server Resources

Web browserHTTP(S)

ApplicationDatabases

ApplicationDatabasesApplicationData

ApplicationData

Messaging Engine

Messaging Engine

Em

bedded H

TT

P

Server

Em

bedded H

TT

P

Server

WebContainer

EJBContainer


Web Services Engine

Web Services Engine

Servlets/JSPsServlets/JSPs EJBsEJBs

Java client

Web Servicesclient

RMI/IIOP SOAP/JMS

SOAP/HTTP(S)

JMS Client



Version 6 Packaging

WebSphere Application Server Network DeploymentWebSphere Application Server Network Deployment

WebSphere Application Serverand

WebSphere Application Server Express (up to 2 CPUs)

WebSphere Application Serverand

WebSphere Application Server Express (up to 2 CPUs)

Web-based AdminWeb-based Admin Web ServicesWeb Services

EJB ContainerEJB Container MessagingMessaging

ClusteringClustering Node AgentNode Agent Deployment ManagerDeployment Manager

Web ContainerWeb Container JDKJDK

PMEsPMEs

Web Services GatewayWeb Services Gateway



WebSphere Application Server V6 Express & Base

node1

server1server1

adminconsoleadminconsole

profile1



WebSphere Application Server V6 Network Deployment

dmgrNode

dmgrdmgr


dmgrCell dmgr profile

node1

server1server1

nodeagent1nodeagent1

server1server1

samplesNode

samplesProfile

profile1

Port 9060

Port 9080


Port 2809



Content Express Application Server Network Deployment

Core Application Server Standalone Node Standalone NodeDeployment Manager,

Standalone Node,Managed Node

Web Server plug-ins Yes Yes Yes

Application Client (not on zLinux) Yes Yes Yes

Data Direct JDBC drivers 1 Yes Yes Yes

Development and Deployment Tools 2Rational Web Developer

ASTK

Rational Application Developer *Trial*ASTK

Rational Application Developer *Trial*ASTK

Database included in the package DB2 Express 1

(Dev. Use only)DB2 Express 1

(Dev. Use only)DB2 Enterprise Server

Edge Components No No Yes

IBM Tivoli Directory Server (LDAP server) No No Yes

Tivoli Access Manager Server No No Yes

Production Ready Applications IBM Business Solutions 2 None None

Windows platform only 1

Windows and Linux/Intel platforms only 2

Version 6 Packaging Content



Tool Stack Positioning Rational Application Developer (RAD) and Web Developer provide the first class IBM development experience, with focus on the graphical construction of applications

AST is focused at a more basic (textual) level than RAD, but provides support to create & deploy WebSphere Application Server applications

AST is included with V6.1

Both Rational and AST are based on Eclipse base and a new open source Eclipse project called WTP (Web Tools Platform)

Rational Application Developer and Web DeveloperUML modeling & visualization,Graphical application constructionComponent test automation & mgmtCode analysis, complexity & correctnessApplication trace & profiling

WebSphere Application Server Toolkit (AST)WebSphere Application Server application creation,

assembly, deployment & unit test support

Eclipse: Base & WTPBasic framework, Web Tools, Models & Wizards



Single Server Topology



Agenda



– Java 5



– API migration










Installation Options

WebSphereProductBinaries

WebSphereProfile+

1 2

3

Install Image

Install

WebSphereProfile

Create Profile

OR

V6.1 NodeV6.1

Node Agent

V6.1 Deployment

Manager

OR

OR

V6.1 Node Agent

V6.1 Node

V6.1 Deployment

Manager

V6.1Application

Server

V6.1Application

ServerDefault Profile

Install product binariesand option to install WebSphere Samples

Optionally create a default WebSphere ProfileA. Deployment ManagerB. Stand-alone Single Application Server C. Cell (DMgr and managed node)D. Custom Profile (Managed Node)

Create profiles afterinstallation

Server

A

B

C

D



Installing WebSphere Application Server v6 - Express

Each profile has a similar set of directories and files. But each set is unique for each profile

Each profile shares a common set of WAS v6 product binaries



WebSphere Profiles WebSphere Application Server V6.1 files are divided into two categories

– Core product files– Application binaries for WebSphere Application Server; these are shared across all profiles

– User files– Customizations, including configuration files, installed applications, resource adapters, properties, log files

Profiles are collections of related user files– A profile defines a WebSphere runtime environment

– Profiles share product binaries

– A profile can optionally be created at install time

– Additional profiles can be added later

A profile is an ‘instance’ of a WebSphere Application Server configuration– A profile contains its own set of scripts, its own environment, its own repository, and its own node

agent. Many profiles can be created off of a single install. All profiles on the same system may share the same runtime binaries

– Only have to apply maintenance once to update all of the profiles Easily created using the Profile Management Tool At least one profile per physical machine / LPAR

+WebSphere Application Server V6.1

Product Binaries

WebSphereV6.1 Profile =

Complete WebSphere Application Server V6.1

Installation



Application Server

Deployment Manager

Custom ProfileV6.1

Application Server

V6.1 Deployment

Manager

V6.1 Node

V6.1 NodeAgent

Cell Template

V6.1 NodeAgent

V6.1 Application

Server

V6.1 Deployment

Manager

V6.1 Node

NewV6.1

Profile Management Tool: Profile Templates



Impact on Server Commands WebSphere commands (like startServer, stopServer) are now “profile” aware

– There is a “-profileName” option on many WebSphere v6 commands

– Or issue the commands from <profile_home>/bin

– Setupcmdline from <profile_home>/bin

If no profile is used, the default profile is assumed– Only one default profile can exist

Examples: – startServer server1 -profileName Node1

– startManager -profileName DMgr

– stopServer server1 assumes default profile



J2SE 5.0

Major Features of Interest– Compile-time type safety with Generics

– Auto-boxing of primitives

– Annotations

– Type-safe Enumerated Types

– Concurrency utilities

– JMX

Toleration Mode– WebSphere Application Server v6.x remains J2EE 1.4

New VM Code Base for IBM-provided JVMs

Much Improved Performance



Generics

Example:Example: Using a Collection in JDK 1.4.2

Example:Example: Using a Collection in JDK 5.0– Notice that the element coming out of the array does not require a cast

– This example also illustrates autoboxing and auto-unboxing

LinkedList intList = new LinkedList();intList.add( new Integer(1) );Integer iObj = (Integer) intList.getFirst();int iPrim = iObj.intValue();

LinkedList<Integer> intList = new LinkedList<Integer>();

intList.add( 1 );int iPrim = intList.getFirst();



Autoboxing and Enhanced For Loop Syntax

Example:Example: Navigating a Collection in JDK 1.4

Example:Example: Navigating a Collection in JDK 5.0

ArrayList list = new ArrayList();// Fill the ArrayList with values here...int sum = 0;for(Iterator i = list.iterator(); i.hasNext(); ){ Integer value = (Integer)i.next(); sum += value.intValue();}

ArrayList<Integer> list = new ArrayList<Integer>();// Fill the ArrayList with values here...int sum = 0;for(Integer i : list ) sum += i;



Java now natively supports enumerated types that:– Are typesafe and robust

– Offer namespace support

– Provide meaningful printed values

– Can have associated fields and methods, implement interfaces, and more

Example:Example: Using a simple enum

Enumerations

enum Day { SUNDAY, MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY }System.out.println( “That goodness it’s ” + Day.FRIDAY );



There are three major categories of annotation types– Marker annotations have no variables – they simply appear, identified by name, with no other information supplied

– Example:Example:

– Single-value annotations are like markers, but they only have one value, so a special syntax can be used


– Full annotations have multiple data members


@SuppressWarnings(value={“unchecked”})public void nonGenericsMethod() { List stringList = new ArrayList(); stringList.add(“foo”); // causes warning}

Annotations

@FullAnnotation( var1=“data value 1”,var2=“data value 2”,var3=“data value 3” )

@Deprecated public void deprecatedMethod() {…}



J2SE 5.0 - IBM Innovations

Just-In-Time (JIT) Compiler Technology enhancements– Multiple levels of optimization– Asynchronous compilation

Garbage collector improvements– Sub-pooling for large SMP machines greatly improves application throughput– Type-accurate, parallel collector

Virtual Machine (VM) technologies – JVM Shared Classes improve startup time and footprint– Profiling and debugging

– Full-speed debug; hot-code replacement

Much Improved Performance…



Memory Management / Garbage Collection How the IBM J9 Generational and Sun/HP Garbage Collectors Work

IBM J9:-Xmn (-Xmns/-Xmnx)Sun:-XX:NewSize=nn-XX:MaxNewSize=nn-Xmn<size>

Sun JVM Only:-XX:MaxPermSize=nn

• Minor Collection – takes place only in the young generation, normally done through direct copying very efficient• Major Collection – takes place in the old generation and uses the normal mark and sweep algorithm

Nursery/Young Generation Old Generation Permanent Space

JVM Heap

IBM J9:-Xmo (-Xmos/-Xmox)Sun:-XX:NewRatio=n



The New Just In Time Compiler

JIT behavior can be changed using JIT options– Specify optimization levels, view a compile listing, exclude certain methods from compilation, limit

methods eligible to be compiled

Allows for full speed debug – very powerful in combination with hot code replace– Run in debug mode with the JIT enabled and replace class definitions on the fly without having to

restart the server

IBM JIT Features – 5.0IBM JIT Features – 5.0– Uses a separate thread for compiling

– Methods are queued for compile

– Maintains a separate stack for Java

– Can recompile methods at 5 opt levels

– Cooperatively suspended for GC

– JIT compiles at no-opt with -Xdebug

IBM JIT Features – 1.4.2IBM JIT Features – 1.4.2– Compiles on the Java threads

– Methods are compiled on demand

– Uses the native stack for Java

– Uses only one optimization strategy

– Asynchronously suspended for GC

– JIT is disabled with -Xdebug



Improved performance with J2SE 5– Java Virtual Machine (JVM) enhancements– New memory allocation and garbage collection

schemes– Reduced lock contention for improved ORB scalability

Improved Web Container performance and scalability

– Asynchronous IO (AIO)– Code path improvements– Caching enhancements– Improved HTTP session replication– JSP engine improvements

EJB improvements – Code path improvements– Light weight Entity Bean– Higher performance access intent settings– Optimizations to persistence manager– Read-only beans

Improved Web services performance– Improved deserialization– Web services caching– Other web services improvements

In-process messaging– Code path improvements– Can use the file system as message store

rather than a relational database

Improved Dynamic Fragment Caching– DMap caching improvements

Miscellaneous performance improvements

– Finer grain authentication optimizations for data sources

Startup Time and Memory Footprint improvements (With IBM JDK)

– Sharing of classes across JVM’s– Class cache in shared memory for faster

startup time

Performance Gains… performance report to be made available after GA



Agenda



– Java 5



– API migration










Application Migration

V6.X supports J2EE 1.4 – Implicitly supports J2EE 1.2 and J2EE 1.3

J2EE 1.4 supports incremental upgrade– Modules within an application can be J2EE 1.2, 1.3 or 1.4

V6.X in general is very compatible with prior WAS versions– Many V4.X applications run unchanged

– Most V5.0, V5.1 applications run unchanged



Runtime migration tools

Automated migration tools provided–Wizard, WASPreUpgrade, WASPostUpgrade

–Copy existing configurations between versions

–Distributed – –Migration Wizard–Or use commands directly

–zOS Customization support – creates customized jobs–iSeries

–Use commands directly



Migrating WAS Configurations – Tools

WASPreUpgrade– Saves applications and configuration data from a previous installation of WAS to a backup directory.

WASPostUpgrade– Restores applications and configuration data from a WAS backup directory created by

WASPreUpgrade.

Migration wizard– migration.bat

– GUI front end for WASPreUpgrade and WASPostUpgrade

convertScriptCompatibility– Changes the WAS/ND v6 Deployment Manager from a node that supports backward compatibility v5.x

admin scripts to a node that supports only v6

clientUpgrade– Upgrades Application Clients



Migrating a WebSphere V4 or V5 Standalone Node

1. Stop all v4 / v5 application server processes If v4.x AE, Administrative Server must be started

2. Install WAS v6 and create a standalone node profile Express and Base installations create a “default” profile

3. Execute WASPreUpgrade * Creates a backup of v4 / v5 configuration data

Analyze WASPreUpgrade.<dateTimeStamp>.log for any errors

4. Execute WASPostUpgrade * Copies and transforms backup of v4 / v5 configuration data created by WASPreUpgrade

Analyze WASPostUpgrade.<dateTimeStamp>.log for any errors

5. Start v6 processes and test

*Migration Wizard could be used to complete this step



Migrating a WAS v5 Standalone Node to WAS v6

WAS v5 WASPreUpgrade

Server Configuration Applications Resources

Backup Files

3

WASPostUpgrade

4

wasprofile

2

WAS v6 App

Server

Migrated WAS v6

App Server

log

log

1Stop Node

5Start Node



Migrating a Version 5 Deployment Manager

1. Stop V5 Deployment Manager

2. Install WAS v6 – ND and create a Deployment Manager profile

3. Execute WASPreUpgrade * Creates a backup of v5 Deployment Manager configuration data

Analyze WASPreUpgrade.<dateTimeStamp>.log for any errors

4. Execute WASPostUpgrade * Copies and transforms backup of v5 Deployment Manager configuration data created by

WASPreUpgrade

Analyze WASPostUpgrade.<dateTimeStamp>.log for any errors

5. Start V6 Deployment Manager

*Migration Wizard could be used to complete this step



Migrating a Version 5 Managed Node

1. Start v6 Deployment Manager

2. Stop v5 application servers and node agent

3. Install WAS v6 – ND and create a Custom profile Do not federate the node at this time

4. Use the Migration Wizard to migrate the v5 managed node to the v6 managed node Migration Wizard will automatically federate node

5. Start v6 node agent

6. Start v6 application servers

7. Test



Migrating a WAS/ND v5 Cell to a WAS/ND v6 Cell

Migration Steps

1. Install WAS/ND v6 on the WAS/ND v5 DMgr node and create DMgr profile

2. Execute WASPreUpgrade and WASPostUpgrade on each WAS/ND v5 DMgr node

3. Start the WAS/ND v6 DMgr node

4. Install WAS/ND v6 on each WAS/ND v5 Managed node and create a Custom profile

5. Execute Migration Wizard against each WAS/ND v5 Managed node

6. Each migrated node will be automatically federated by Migration Wizard

Node CNode B

WAS v5 Application

Server

WAS v5 Application

Server

WAS v5 Application

Server

WAS v5 Application

Server

WAS/ND v5 Cell

WAS/ND v5 DMgr

Node A




Migration Steps







Node CNode B

WAS v5 Application

Server

WAS v5 Application

Server

WAS v5 Application

Server

WAS v5 Application

Server

WAS/ND v5 Cell

WAS/ND v5 DMgr

Node A

WAS/ND v6 DMgr




Migration Steps







Node CNode B

WAS v5 Application

Server

WAS v5 Application

Server

WAS v5 Application

Server

WAS v5 Application

Server

WAS/ND v5 Cell

WAS/ND v5 DMgr

Node A

WAS/ND v6 DMgr

Mig

rate




Migration Steps







Node CNode B

WAS v5 Application

Server

WAS v5 Application

Server

WAS v5 Application

Server

WAS v5 Application

Server

WAS/ND v5 Cell

WAS/ND v5 DMgr

Node A

WAS/ND v6 DMgr




Migration Steps




4. Install WAS/ND v6 on each WAS/ND v5 Managed node and create a Managed node profile



Node CNode B

WAS v6 Application

Server

WAS v6 Application

Server

WAS v6 Application

Server

WAS v6 Application

Server

WAS/ND v5 Cell

WAS/ND v5 DMgr

Node A

WAS/ND v6 DMgr

WAS v5 Application

Server

WAS v5 Application

Server

WAS v5 Application

Server

WAS v5 Application

Server




Migration Steps







Node CNode B

WAS v6 Application

Server

WAS v6 Application

Server

WAS v6 Application

Server

WAS v6 Application

Server

WAS/ND v5 Cell

WAS/ND v5 DMgr

Node A

WAS/ND v6 DMgr

WAS v5 Application

Server

WAS v5 Application

Server

WAS v5 Application

Server

WAS v5 Application

Server

Mig

rate

Mig

rate

Mig

rate

Mig

rate




Migration Steps







Node CNode B

WAS v6 Application

Server

WAS v6 Application

Server

WAS v6 Application

Server

WAS v6 Application

Server

WAS/ND v5 Cell

WAS/ND v5 DMgr

Node A

WAS/ND v6 DMgr

WAS v5 Application

Server

WAS v5 Application

Server

WAS v5 Application

Server

WAS v5 Application

Server

Fed

erat

e

Fe

de

rate

Fe

de

rate

Fede

rate




Node CNode B

WAS v6 Application

Server

WAS v6 Application

Server

WAS v6 Application

Server

WAS v6 Application

Server

WAS/ND v6 Cell

Migration Steps







WAS/ND v5 DMgr

Node A

WAS/ND v6 DMgr

WAS v5 Application

Server

WAS v5 Application

Server

WAS v5 Application

Server

WAS v5 Application

Server

Fully Migrated



WASPreUpgrade Syntax & Examples Syntax

– WASPreUpgrade <backupDirectory> <currentWebSphereDirectory>

Examples– WASPreUpgrade C:\WAS51\backups\DMgr C:\WAS51\DMgr

– WASPreUpgrade C:\WAS51\backups\AppServer C:\WAS51\AppServer

Note: See InfoCenter for full syntax.

WASPostUpgrade Syntax & Examples Syntax

– WASPostUpgrade <backupDirectory>

Examples– WASPostUpgrade C:\WAS51\backups\DMgr

– WASPostUpgrade C:\WAS51\backups\AppServer

Note: See InfoCenter for full syntax.



Script Compatibility

Migrated WAS v4 node– wscp based…

– Re-implement using wsadmin objects

Migrated WAS v5 node– wsadmin based…

– May require some rework with regards to JMS

WAS v6 mixed node cells– WAS v6 mixed node cell operates in compatibility mode

– WAS v5 scripts will work on v5 managed nodes



Migrating Web Server Configurations - Overview

Web Server and Plug-in migration is a manual process– There are no migration tools

The Web Server should be installed first followed by the appropriate Plug-in– This sequence allows the plug-in install process to automatically update httpd.conf. Otherwise, the

httpd.conf will have to be updated manually

v6 Plug-ins can route to both WAS v5 and WAS v6



IBM Rational Application Developer



Agenda



– Java 5



– API migration









WAS 5.1 - 6.1 Migration © 2008 IBM Corporation

Look out for these code changes

Migrating to Java 2 Standard Edition (J2SE) 5

Migrating Web application components from WebSphere Application Server Version 5.x

Adjusting exception handling for EJB wrappered applications migrating from version 5 to version 6

Migrating applications to use data sources of the current J2EE Connector Architecture (JCA)

General considerations for migrating from Version 5 embedded messaging

Interoperating Security with previous product versions




Decide whether to take advantage of new J2SE 5 capabilities in your applications

Determine whether to use the default JIT mode Compile J2SE 5 applications to run on older Java virtual

machine levels by setting the compiler modes (specify '-source' and '-target' modes)

Address incompatibilities in previously compiled J2SE 1.4 based applications

– Variables named 'enum.

– Ambiguous references to classes with base names of 'Proxy,' 'Queue,' or 'Formatter.'

Start the transition from deprecated JVMDI and JVMPI functions to JVMTI

Update your use of the Java command line interface (use -agentlib / -agentpath /-javaagent )

Update ANT tasks – If you have created ANT tasks based on the idltojava ANT task shipped with prior versions of this product, you will need to ensure that it passes

the proper parameters for J2SE 5 as it does for J2SE 1.4, to ensure the stubs/ties and skeletons it generates are compatible to earlier product releases.




Version 4 Version 5 Version 6

Default Content-Type text or html text or html charset=<default_encoding>

none

Append Charset on getWriter if the property does not exist on Content-Type

text or html text or html text/xml;

Example: response.setCharacterEncoding("UTF-8"); response.setContentType("text/xml"); response.getWriter();

charset=UTF-8

Remove charset from the Content-Type property if the setContentType property is called after getWriter with a ";charset=" portion

text or html text or html text or html

Example: setContentType("text/html;charset=ISO-8859-7"); getWriter(); setContentType("text/xml;charset=UTF-8");

JSP migration might be a concern if your application references JSP page implementation classes in unnamed packagesJSP migration might be a concern if your application references JSP page implementation classes in unnamed packages



Adjusting exception handling for EJB wrappered applications migrating from version 5 to version 6 it is no longer possible to directly use

java.lang.Exception or java.lang.Throwable types.

– The JAX-RPC version 1.1 specification states: “a service specific exception declared in a remote method signature must be a checked exception. It must extend java.lang.Exception either directly or indirectly but it must not be a RuntimeException.”

Procedure:– Modify your applications that use service specific exceptions.

– Modify all of the exception handling in the enterprise beans that use it.

– See http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tejb_migrwrap.html




Migrate your applications that use Version 4 data sources, or data sources (WebSphere Application Server V4), to use data sources that support more advanced connection management features, such as connection sharing.

Procedure:– Convert a 2.2 Web module to a 2.3 Web module

– Convert a 1.1 EJB module to a 2.1 EJB module (or later)

– Add the EJB modules and Web modules to an EAR file

– Install the Application on WebSphere Application Server



General considerations for migrating from Version 5 embedded messaging You do not need to change Version 5 JMS applications

You do not need to change Version 5 JMS resource definitions

You do not need to change version 5 client JMS resource definitions

You should replace MDB listener ports with JMS activation specifications

A Version 5 JMS server is converted to a Version 6 application server

The wildcard syntax is converted automatically for interoperation between

Version 5 and Version 6

Configuration scripts for WebSphere Application Server Version 5

Embedded Messaging should not be run, and fail if they are run

Use “WebSphere message migration” utility– http://<yourhostname>:9080/MessageMigrationUtility



Migration of message fields

JMS Message Header fieldsJMS Message Header fieldsHeader field name State after migration

JMSMessageID Unchanged

JMSCorrelationID Unchanged

JMSDeliveryMode Unchanged

JMSPriority Unchanged

JMSTimestamp Unchanged

JMSExpiration Unchanged

JMSRedelivered Can be reset as a result of the migration process.

JMSType Unchanged

JMSDestination The name of the destination is unaltered. Other properties of the destination are mapped to their WebSphere Application Server Version 6 equivalents, where possible.

JMSReplyTo The name of the reply destination is unaltered, and assumed to exist on the WebSphere Application Server Version 6 bus to which the messages are being migrated. Note: •References to temporary queues or topics are migrated in the same way as for permanent reply destinations. It will not be possible to send reply messages to these destinations because they will not exist in the WebSphere Application Server Version 6 bus. •Topic reply-to destinations are assumed to be topics within the default topic space, which must exist for the reply message to be sent.



JMSX properties

JMSX property name State after migration

JMSXUserID Unchanged

JMSXAppID Unchanged

JMSXDeliveryCount Can be reset as a result of the migration process.

JMSXGroupID Unchanged

JMSXGroupSeq Unchanged

JMSXProducerTXID Not supported by service integration bus.

JMSXConsumerTXID Not supported by service integration bus.

JMSXRcvTimestamp Not supported by service integration bus.

JMSXState Not supported by service integration bus.




The current release of the Application Server distinguishes the identities of the user who acts as an administrator, managing the Application Server environment, from the identity of the user that is used for authenticating between servers.

Interoperability is achieved only when the Lightweight Third Party Authentication (LTPA) authentication mechanism and a distributed user registry is used such as Lightweight Directory Access Protocol (LDAP) or a distributed Custom user registry.

SWAM is deprecated in WebSphere Application Server. Version 6.1 and will be

removed in a future release. You need to Configure (reconfigure) WebSphere Application Server

Version 6.1 with the same distributed user registry, Re-Configure the LTPA authentication mechanism & Add certificates



Agenda



– Java 5



– API migration










Fine Grain Application Update

Application EARModule1.jar

a/b/File1c/d/File2

Module2.ware/f/File1g/h/File2

Module3.jar i/j/File1k/l/File2

Partial Application ZIP

/Module1.jar/a/b/File1/Module2.war/m/n/File3/Module3.jar JAR file

After Update

a/b/File1 in Module1.jar of the EAR is replaced m/n/File3 is added to Module2.war in EAR file Module3.jar in the EAR is entirely replaced

Final Application EARModule1.jar

a/b/File1c/d/File2

Module2.ware/f/File1g/h/File2

m/n/File3Module3.jar

r/s/File4 t/u/File5

r/s/File4t/u/File5



File Deletions

In a partial application, file deletion is specified using a special meta-data file– META-INF/ibm-partialapp-delete.props

– Can be at Application Scope or Module Scope

Application EARModule1.jar

a/b/File1a/b/File2e/f/File1

Module2.war i/j/File1k/l/File2

Partial Application ZIP

/Module1.jar/META-INF/ibm-partialapp-delete.props

Application EAR(final)

Module1.jare/f/File1

Module2.war i/j/File1k/l/File2a/b/File*



AST & Enhanced EAR Same look and feel as IBM Rational Application Developer



The Problem

1. Full install of GA: Select features and provide other install-time input2. Install refresh pack (if needed)3. Install fix packs (if needed)4. Install one or more interim fixes (if needed)5. Create and configure App Servers and other artifacts6. Deploy applications

Installing and configuring WAS usually requires many steps:

Typically need to iterate over these steps to Typically need to iterate over these steps to achieve desired end result – not a pure linear achieve desired end result – not a pure linear process!process!

V6.0

V6.0.2

V6.0.2.5

iFix “A” and “B”A

B

JDK 1.4.2 SR3

wsadmin script

J2EE app



Command Line

Invocation Tool

Single package containingV6.0

V6.0.2

V6.0.2.5

J2EE Applications

Configuration archive

Automated, customized WAS install package

Installation Factory Capabilities

Processing

Engine

V6.0

V6.0.2

V6.0.2.5JDK 1.4.2 SR3

Build Definition

XML

iFix “A” & “B”

AB

JDK 1.4.2 SR3

iFix “A” and “B”

3rd-party Scripts

J2EE Applications

Configuration Archive

3rd-party Scripts

C:\>ifcli

Composition

Tool (GUI)

Create



Using a CIP to Update an InstallSystem Level After CIP Installation

V6.0.2.5

JDK 1.4.2 SR3


V6.0

V6.0.1

V6.0.1.2

V6.0.1.2

iFix “A”+

JDK 1.4.2

SR1

V6.0+

New

Scratch

Install

Update Existing

InstallationsExisting WAS Installations

Install CIP

Final System Level

Single package containing

V6.0

V6.0.2

V6.0.2.5

JDK 1.4.2 SR3


…

Install…Automated, customized WAS install package



Value-Add Programming Support

Service Data Objects (SDO)– Enables unified data access and representation across heterogeneous

data stores (JSR 235)

JavaServer Faces (JSF) 1.0– User interface framework for development of Java based Web

applications

Programming Model Extensions (PMEs)– APIs that extend the J2EE programming model, for solving complex

business problems



Service Data Objects

DataBaseDataBase

DataBaseDataBase

……

Access APIsAccess APIs

Data APIsData APIs

Metadata Access APIsMetadata Access APIs

Metadata APIsMetadata APIs


Data APIsData APIs




Data APIsData APIs



EJBMediator

CustomMediator

JDBCMediator

SDO CoreAPIs

ClientClient

Unified data representation & retrieval across heterogeneous data sources

FileFile



Set of functions pre-built for reuse within Web User Interfaces

Some Examples include:– DatePicker

– DataGrid

– Graph

– Input

– Menu

– TabbedPanel

– TimePicker

– Tree

– More …

Consumability: IBM JSF Widget Library Included



Programming Model ExtensionsCore extensions included in all WebSphere versions

– WebSphere Business Integration Server Foundation extensions

•Last Participant Support

•Internationalization Service

•WorkArea Service

•ActivitySession Service

•Extended JTA Support

•Startup Beans

•Asynchronous Beans

•Scheduler Service

•Object Pools

•Calendar

•Dynamic Query

•DistributedMap

•Application Profiling

Newly added

•CommonJ Work Manager •CommonJ Timer Manager



Session Initiation Protocol (SIP) Servlets The next generation of applications are being built on SIP

– Chat/Instant messaging

– VoIP is built using SIP

– Video conferencing, video over IP

– Collaborative applications

– Entertainment/Gaming JSR 116 SIP Servlets provide SIP support

– Provided by the first truly converged container

– Servlets can share a single application session across protocols

– HTTP Servlets and Portlets can create SIP messages and tie state together with a single application session

ConvergedServlet

Container

HTTP Servlets

SIP Servlets

Portlets

Shared application session



Supports JSR 168 Portlet programming model– Makes portlet programming model available in all WAS-based

servers

Tools support includes– Wizards to create

– Portlet Projects– Portlets

– Editor to manage the portlet deployment descriptor (portlet.xml)

– Ability to import portlet WAR file

Limited aggregation through JSP tag library– Proprietary interface

– Provides migration for aggregating servlets

Remote request dispatch support not provided

The portlet project creation wizard will create an empty portlet for you and add it to the project

Portlet Support



System Management - What is New Mixed cell support

– Enables phased migration for WebSphere Application Server v5

Configuration archiving– Allows you to create a complete or partial archive of an existing configuration that can

be used to create new configurations

WebSphere profiles– Used to define one or more runtime server instances, while utilizing a single instance

of installation libraries

Generic servers– A non-WebSphere server or process that is administered as an application server

instance

External Web servers– Defined as managed or unmanaged servers, providing additional capabilities for

administration and management of plug-in configurations

Node Groups– Enables grouping of nodes in a cell with different capabilities (e.g., containment of

distributed systems and z/OS)



Application Management – What is New

Enhanced EAR files– Developed using Rational Application Developer or the Application

Server Toolkit

– Contains bindings and server configuration settings

Fine grained application update– Enables small delta to applications without performing a full application

update and restart

WebSphere Rapid Deployment– Support for developers to use annotation based programming

– Moving toward automation of application development and deployment



Government Standards

Latest Common Criteria EAL 4 certification– Governance for security standards across applications

IPv6 – Interoperability between IPv4 and IPv6 clients

– Rounding out compliance in z/Series and i/Series

9.67.128.1

Client

TCP / UDP

IPv6-only Node

IPv6

Client

TCP / UDP

IPv4-only Node

IPv4

Server (0::0)

TCP / UDP

IPv4

Dual Mode Node

IPv6

IPv6 Packets

IPv4 Packets

::FFFF:9.67.128.1

2001:0DB8::1

2001:0DB8::1



Application Server Toolkit V6.1

Eclipse 3.1 Web Tools Platform (WTP) 1.0

– J2EE tools

– XML tools

– Web tools

– Web Service tools

– RDB Tools Test and performance tools Graphical editor framework Eclipse modeling framework (EMF) JDK 1.4.2 (also supports 5.0)

WebSphere additions:– WebSphere Rapid Deployment

– Graphical deployment descriptors

– IBM Web Services tools

– Automation Toolkit for WebSphere for writing and testing wsadmin Jython scripts

– EJB deployment support

– WebSphere server integration

– SIP Servlet (JSR 116) support

– Portlet (JSR 168) support



The WS Admin scripting commands that map to actions on the admin console are logged and/or JMX notifications emitted in the Jython language

Consumability: Command Console Assist



Web Services Evolution… ?

JAX-RPC (JSR-101) 1.0 New standard API for

programming Web services in Java

JSR-109 1.0 New J2EE deployment model for

Java Web services

SAAJ 1.1

WS-Security Extensions added

WS-I Basic Profile 1.0 Profile compliance

UDDI4J version 2.0 (client)

Apache Soap 2.3 enhancements

The engine is a new high performance SOAP engine supporting both HTTP and JMS

JAX-RPC (JSR-101) 1.1 Additional type support xsd:list Fault support Name collision rules New APIs for creating Services isUserInRole() JSR-109 – WSEE 1.1 Moved to J2EE 1.4 schema types Migration of web services client DD

moving to appropriate container DDs Handlers support for EJBs Service endpoint interface (SEI) is a

peer to LI/RISAAJ 1.2 APIs for manipulating SOAP XML

messages WS-Security WSS 1.0WS-I Basic Profile 1.1 Attachments supportWS-TX AT (Atomic Transactions) JAXR support UDDI v3 support Includes both the registry

implementation and the client API library

WS-BA (Business Activity) Compensation framework for

loosely coupled transactionsWS-I BSP (Basic Security Profile) Interoperability over the wire (i.e.

WebSphere client with .NET svr.) Tightening of specificationWS-N (Notification) Publish/Subscribe modelWS – Security enhancementsPerformance Enhancements SAAJ changes (send XML docs. w/

attachments) SOAP/JMS New and faster parser (Banshee

instead of B2B)

SOAP/JMS Enhancements Caching enhancements

Text message enhancementsWS-RF (Resource Framework) Stateful web service resourcesWS-Addressing Endpoint ref. support for WS-Res.

WAS V5.0.2/5.1 WAS V6.0 WAS V6.1



Agenda



– Java 5



– API migration










Goal: Ease Application Serving Management Burden

88

IBM Solution– Dynamic start of app server components

– Simplified administration of web services

– Straightforward configuration of integrated messaging capabilities

You want to…

• Invoke key runtime provisioning of applications to meet business demands

• Improve infrastructure management efficiency, reducing resources/skills

Enabling fast, efficient development of critical applcations and services

Enabling fast, efficient development of critical applcations and services



Easing Application Serving Management Burden WebSphere Application Server v7 Provides Key Runtime Provisioning Capabilities

Dynamic start of app server components based on application needs Reduces the runtime footprint – less memory required Can significantly reduce startup times

HA ManagerSecurity

SIP ContainerWeb ServicesEJB ContainerWeb Container

V6.1 Server

Infrastructure…

V7 Server

Dynamically

Activated!!

All

Activated

HA ManagerSecurity

SIP ContainerWeb ServicesEJB ContainerWeb Container

Infrastructure…



Goal: Capitalize on Intelligent App Server Management

IBM Solution– Flexible, “loosely coupled” application server management

– Introduction of admin agents – enabling asynchronous agent execution

– Expanded multi-node remote management

– Improved support of development/unit testing/QA environments

90

You want to…

• Reduce SOA infrastructure administrative overhead

• Provide remote management for expanded topologies

Node A

Admin scripts

Serverconfiguration

Node Aconfiguration

Cell config

Admin consoleAppServer

AdminAgent

Intelligent management features ease admin. open new opportunities

Intelligent management features ease admin. open new opportunities



Capitalizing on Intelligent App Server Management WebSphere Application Server v7 Allows Flexible Management of Branch Organizations

JobManager

Dmgr

Dmgr

Dmgr

Dmgr

AdminAgent

Dmgr

AdminAgent

JobManager

Supports high latency remote branch servers Supports geographically separated data centers



Capitalizing on Intelligent App Server Management WebSphere Application Server v7 Addresses the Server Farm Dilemma with New Ideas

Loosely coupled Job Manager

Local node “Autonomy” unlike ND topology

Loose federation – Not “slave” to Deployment Manager

Develop/Unit Test/QA scenarios

AdminNode

WAS NDCell

JobManager

AdminAgent

BaseNode

BaseNode

BaseNode



Capitalizing on Intelligent App Server Management WebSphere Application Server v7 Overcomes Challenges of Existing Base Management

WebSphere Application ServerV5 & V6 Base Product Architecture

Node A

Admin scripts

Serverconfiguration

Node Aconfiguration

Cell config


Node Agent NOT included in Base product

Admin logic hosted in the same JVM as application server and customer applications.

Current Base Management



Capitalizing on Intelligent App Server Management WebSphere Application Server v7 Overcomes Challenges of Existing Base Management (cont.)

WebSphere Application ServerV7 Base Product Architecture

Node A

Admin scripts

Serverconfiguration

Node Aconfiguration

Cell config


Admin Agent included in Base product

AdminAgent

New Flexible Management Option



Easing Application Serving Management Burden WebSphere Application Server v7 Properties File Based Configuration Utility Reduces Manual Effort

Properties File

Processing Utility

Processing Command Options:

Properties File(s)

Property_name = “foo”

Scope = Server

Name = “server1”

MaximumHeapSize= 1024

ORB_LISTENER_ADDRESS_PORT = 9001

# ---------------------------

# comment line

# ---------------------------

extract

apply

delete

WebSphere

Configuration Repository



Using Technology Innovation to Meet Evolving Needs WebSphere Application Server v7 Expands Support through Business Level Applications

Expanding the notion of “Application” beyond J2EE

Extensible deployment logic framework Supports more than Application Server deployment

target runtimes– for example: Proxy Server, Web Server, CE, files, etc.

Full lifecycle management of applications– Install, distribute, activate, monitor, update, remove

BLA1

EJB Module Web

Module

BLA3

CICS Transaction

DB2 Database

Portlet Module

JAX-WS Web Service

Module

BLA2

WAR

J2EE Enterprise

App

JAREAR

Axis2 PAR

Business Logic

Configuration

Composition



Using Technology Innovation to Meet Evolving Needs WebSphere Application Server v7 Offers Enhanced Kerberos Support

WebSphereApplication

Server

Kerberos KDC

Kerberos z/OS KDC

WebSphereApplicationServer/zOS

DB2

RACFLDAP

Browser clients withdesktop single sign-on

SPNEGO token over HTTP/S

Java clients With desktop single sign-on

Kerberos SSO

Kerberos cross domain trust

Kerberos SSO

Kerberos SSO

RACFUser Registry

LDAPUser Registry

Kerberos tokenover RMI/IIOP, Web Services

Broader implementation of Kerberos delivers improved interoperability with other applications and environments



WebSphere Premium Support

Sell Premium Support to help your customers:

Upgrade with confidence.– A manufacturing company uses Premium Support to confidently apply new functionality and

product versions to their environment, which is one of the largest WebSphere deployments. The company benefits from weekly conference calls with a Premium Support Manager to plan and perform the product upgrade.

Configure new functionality such as multiple security realms, flexible management, or business-level applications.

– A transportation company uses Premium Support to guide them through product version upgrades. The company has a highly-skilled technical team that strives to use the most up-to-date products and functionality. Premium Support provides the company’s technical team with migration plans, opportunities to join product updates with IBM’s leading Lotus Developers, and fast turnaround for complex PMRs.

Optimize system operations.– An IT service provider uses Premium Support to ensure that their business application and

network management services achieve their customer’s expectations. The company benefits from skill sharing activities, reactive support, and on-site support from technical specialists.

Identifying potential Premium Support customers



WebSphere Application Server Library

Product documentation in HTML and PDF format– http://www.ibm.com/software/webservers/appserv/was/library/

– Information Center and Resource links

– Tutorials and demos– Samples Gallery– Technical Information– Service and Support– Education– Redbooks



IBM Education Assistant

On demand software education web site– http://www.ibm.com/software/info/education/assistant/

– Narrated presentations

– Show Me Demonstrations

– Tutorials – Configurations for:– WebSphere Application Server v6– WebSphere Application Sever v5– Rational Application Developer v6



www.ibm.com/developerworks/websphere/zones/was/

Recommended reading for WebSphere Application Server

Redbooks for WebSphere Application Server V6

Was 5.1 To 6.1 Updated

Technology

Transcript of Was 5.1 To 6.1 Updated