Was 5.1 To 6.1 Updated
Upcoming SlideShare
Loading in...5
×
 

Was 5.1 To 6.1 Updated

on

  • 2,674 views

 

Statistics

Views

Total Views
2,674
Views on SlideShare
2,666
Embed Views
8

Actions

Likes
1
Downloads
188
Comments
0

3 Embeds 8

http://www.slideshare.net 5
http://115.112.206.131 2
http://www.techgig.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Was 5.1 To 6.1 Updated Was 5.1 To 6.1 Updated Presentation Transcript

  • Websphere Application Server v5.1 to v6.1 Migration Subrahmanyam Thuraga, PMP Advisory IT Specialist IBM India | 12 Oct 2008 | Karapakkam, Chennai |
  • 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
      • 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!
  • 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 Model Parts 1 & 2 Common Samples Z/OS becomes fully CTS compliant Common Admin 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.0 4Q2003 V5.1 2Q2004 V6.0.X 4Q2004 V6.1 2Q2006 V4.0.X 2001 …
    • 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
    • New API introduced
    • Deprecated but still supported
    • Deprecated but still supported
    • V5.0.X APIs may be removed
    V5.0.X V5.1.X V6.0.X V6.1
  • Key Point(s)
    • Four CDs consolidated into 1 CD
    • Components are packaged to allow for incremental installation. Install only what you need
    + + + 1/platform V5 Deployment Manager (1/platform) WebSphere V5 Application Server IBM HTTP Server Web server plug-ins (1/platform) WebSphere V5 Application Client (1/platform) WebSphere V5 Data Direct JDBC Drivers (Windows Only) WebSphere V5 Application Server Toolkit (Windows, Linux) WebSphere V6 WebSphere V6 WebSphere
  • V6 Basic Architecture Messaging Engine Embedded HTTP Server Application Databases Application Data XML Configuration Files HTTP Server Plug-in HTTP Server Application Server Plug-in Configuration File Web Services Engine Web Container Servlets JSPs EJB Container EJBs Dynamic Cache Name Server Security … … … . Data Replication JMX Transaction.
  • Administering the Server Messaging Engine Embedded HTTP Server Web Container EJB Container XML Configuration Files Application Server Admin console C:> wsadmin Web-based administrative console wsadmin command-line client RMI/IIOP HTTP(S) Admin MBeans Web Services Engine Admin. Service SOAP/HTTP
  • Accessing Server Resources Web browser HTTP(S) Application Databases Application Data Messaging Engine Embedded HTTP Server Web Container EJB Container Application Server Web Services Engine Servlets/JSPs EJBs Java client Web Services client RMI/IIOP SOAP/JMS SOAP/HTTP(S) JMS Client
  • Version 6 Packaging WebSphere Application Server Network Deployment WebSphere Application Server and WebSphere Application Server Express (up to 2 CPUs) PMEs Web Services Gateway Web-based Admin Web Services EJB Container Messaging Clustering Node Agent Deployment Manager Web Container JDK
  • WebSphere Application Server V6 Express & Base server1 adminconsole node1 profile1
  • WebSphere Application Server V6 Network Deployment dmgrCell dmgr profile server1 samplesNode samplesProfile Port 9060 Port 9080 adminconsole Port 2809 dmgrNode dmgr adminconsole node1 server1 nodeagent1 profile1
  • Version 6 Packaging Content Windows platform only 1 Windows and Linux/Intel platforms only 2 Content Express Application Server Network Deployment Core Application Server Standalone Node Standalone Node Deployment 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 2 Rational 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
  • 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 Developer UML modeling & visualization, Graphical application construction Component test automation & mgmt Code analysis, complexity & correctness Application trace & profiling WebSphere Application Server Toolkit (AST) WebSphere Application Server application creation, assembly, deployment & unit test support Eclipse: Base & WTP Basic framework, Web Tools, Models & Wizards
  • Single Server Topology
  • 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!
  • Installation Options + 1 2 3 Install Create Profile OR OR OR V6.1 Node V6.1 Deployment Manager Default Profile Install product binaries and option to install WebSphere Samples
    • Optionally create a default WebSphere Profile
    • Deployment Manager
    • Stand-alone Single Application Server
    • Cell (DMgr and managed node)
    • Custom Profile (Managed Node)
    Create profiles after installation A B C D WebSphere Product Binaries WebSphere Profile Install Image WebSphere Profile V6.1 Node V6.1 Node Agent V6.1 Deployment Manager V6.1 Node Agent V6.1 Application Server V6.1 Application Server
  • 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 WebSphere V6.1 Profile = Complete WebSphere Application Server V6.1 Installation
  • Application Server Deployment Manager Custom Profile Cell Template New V6.1 Profile Management Tool: Profile Templates V6.1 Application Server V6.1 Deployment Manager V6.1 Node V6.1 NodeAgent V6.1 NodeAgent V6.1 Application Server V6.1 Deployment Manager V6.1 Node
  • 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: Using a Collection in JDK 1.4.2
    • 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: Navigating a Collection in JDK 1.4
    • 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: 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:
      • Single-value annotations are like markers, but they only have one value, so a special syntax can be used
        • Example:
      • Full annotations have multiple data members
        • Example:
    Annotations @SuppressWarnings(value={“unchecked”}) public void nonGenericsMethod() { List stringList = new ArrayList(); stringList.add(“foo”); // causes warning } @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
    JVM Heap IBM J9: -Xmo (-Xmos/-Xmox) Sun: -XX:NewRatio=n Nursery/Young Generation Old Generation Permanent Space
  • 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.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.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
    • 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!
  • 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
    • Stop all v4 / v5 application server processes
      • If v4.x AE, Administrative Server must be started
    • Install WAS v6 and create a standalone node profile
      • Express and Base installations create a “default” profile
    • Execute WASPreUpgrade *
      • Creates a backup of v4 / v5 configuration data
      • Analyze WASPreUpgrade.<dateTimeStamp>.log for any errors
    • Execute WASPostUpgrade *
      • Copies and transforms backup of v4 / v5 configuration data created by WASPreUpgrade
      • Analyze WASPostUpgrade.<dateTimeStamp>.log for any errors
    • 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 1 Stop Node 5 Start Node
  • Migrating a Version 5 Deployment Manager
    • Stop V5 Deployment Manager
    • Install WAS v6 – ND and create a Deployment Manager profile
    • Execute WASPreUpgrade *
      • Creates a backup of v5 Deployment Manager configuration data
      • Analyze WASPreUpgrade.<dateTimeStamp>.log for any errors
    • Execute WASPostUpgrade *
      • Copies and transforms backup of v5 Deployment Manager configuration data created by WASPreUpgrade
      • Analyze WASPostUpgrade.<dateTimeStamp>.log for any errors
    • Start V6 Deployment Manager
    * Migration Wizard could be used to complete this step
  • Migrating a Version 5 Managed Node
    • Start v6 Deployment Manager
    • Stop v5 application servers and node agent
    • Install WAS v6 – ND and create a Custom profile
      • Do not federate the node at this time
    • Use the Migration Wizard to migrate the v5 managed node to the v6 managed node
      • Migration Wizard will automatically federate node
    • Start v6 node agent
    • Start v6 application servers
    • Test
  • Migrating a WAS/ND v5 Cell to a WAS/ND v6 Cell
    • Migration Steps
    • Install WAS/ND v6 on the WAS/ND v5 DMgr node and create DMgr profile
    • Execute WASPreUpgrade and WASPostUpgrade on each WAS/ND v5 DMgr node
    • Start the WAS/ND v6 DMgr node
    • Install WAS/ND v6 on each WAS/ND v5 Managed node and create a Custom profile
    • Execute Migration Wizard against each WAS/ND v5 Managed node
    • Each migrated node will be automatically federated by Migration Wizard
    Node C Node 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
  • Migrating a WAS/ND v5 Cell to a WAS/ND v6 Cell
    • Migration Steps
    • Install WAS/ND v6 on the WAS/ND v5 DMgr node and create DMgr profile
    • Execute WASPreUpgrade and WASPostUpgrade on each WAS/ND v5 DMgr node
    • Start the WAS/ND v6 DMgr node
    • Install WAS/ND v6 on each WAS/ND v5 Managed node and create a Custom profile
    • Execute Migration Wizard against each WAS/ND v5 Managed node
    • Each migrated node will be automatically federated by Migration Wizard
    Node C Node 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
  • Migrating a WAS/ND v5 Cell to a WAS/ND v6 Cell
    • Migration Steps
    • Install WAS/ND v6 on the WAS/ND v5 DMgr node and create DMgr profile
    • Execute WASPreUpgrade and WASPostUpgrade on each WAS/ND v5 DMgr node
    • Start the WAS/ND v6 DMgr node
    • Install WAS/ND v6 on each WAS/ND v5 Managed node and create a Custom profile
    • Execute Migration Wizard against each WAS/ND v5 Managed node
    • Each migrated node will be automatically federated by Migration Wizard
    Node C Node 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 Migrate
  • Migrating a WAS/ND v5 Cell to a WAS/ND v6 Cell
    • Migration Steps
    • Install WAS/ND v6 on the WAS/ND v5 DMgr node and create DMgr profile
    • Execute WASPreUpgrade and WASPostUpgrade on each WAS/ND v5 DMgr node
    • Start the WAS/ND v6 DMgr node
    • Install WAS/ND v6 on each WAS/ND v5 Managed node and create a Custom profile
    • Execute Migration Wizard against each WAS/ND v5 Managed node
    • Each migrated node will be automatically federated by Migration Wizard
    Node C Node 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
  • Migrating a WAS/ND v5 Cell to a WAS/ND v6 Cell
    • Migration Steps
    • Install WAS/ND v6 on the WAS/ND v5 DMgr node and create DMgr profile
    • Execute WASPreUpgrade and WASPostUpgrade on each WAS/ND v5 DMgr node
    • Start the WAS/ND v6 DMgr node
    • Install WAS/ND v6 on each WAS/ND v5 Managed node and create a Managed node profile
    • Execute Migration Wizard against each WAS/ND v5 Managed node
    • Each migrated node will be automatically federated by Migration Wizard
    Node C Node 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
  • Migrating a WAS/ND v5 Cell to a WAS/ND v6 Cell
    • Migration Steps
    • Install WAS/ND v6 on the WAS/ND v5 DMgr node and create DMgr profile
    • Execute WASPreUpgrade and WASPostUpgrade on each WAS/ND v5 DMgr node
    • Start the WAS/ND v6 DMgr node
    • Install WAS/ND v6 on each WAS/ND v5 Managed node and create a Custom profile
    • Execute Migration Wizard against each WAS/ND v5 Managed node
    • Each migrated node will be automatically federated by Migration Wizard
    Node C Node 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 Migrate Migrate Migrate Migrate
  • Migrating a WAS/ND v5 Cell to a WAS/ND v6 Cell
    • Migration Steps
    • Install WAS/ND v6 on the WAS/ND v5 DMgr node and create DMgr profile
    • Execute WASPreUpgrade and WASPostUpgrade on each WAS/ND v5 DMgr node
    • Start the WAS/ND v6 DMgr node
    • Install WAS/ND v6 on each WAS/ND v5 Managed node and create a Custom profile
    • Execute Migration Wizard against each WAS/ND v5 Managed node
    • Each migrated node will be automatically federated by Migration Wizard
    Node C Node 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 Federate Federate Federate Federate
  • Migrating a WAS/ND v5 Cell to a WAS/ND v6 Cell WAS/ND v6 Cell
    • Migration Steps
    • Install WAS/ND v6 on the WAS/ND v5 DMgr node and create DMgr profile
    • Execute WASPreUpgrade and WASPostUpgrade on each WAS/ND v5 DMgr node
    • Start the WAS/ND v6 DMgr node
    • Install WAS/ND v6 on each WAS/ND v5 Managed node and create a Custom profile
    • Execute Migration Wizard against each WAS/ND v5 Managed node
    • Each migrated node will be automatically federated by Migration Wizard
    WAS/ND v5 DMgr Node A Fully Migrated Node C Node B WAS v6 Application Server WAS v6 Application Server WAS v6 Application Server WAS v6 Application Server WAS/ND v6 DMgr WAS v5 Application Server WAS v5 Application Server WAS v5 Application Server WAS v5 Application Server
  • WASPreUpgrade Syntax & Examples
    • Syntax
      • WASPreUpgrade <backupDirectory> <currentWebSphereDirectory>
    • Examples
      • WASPreUpgrade C:WAS51ackupsDMgr C:WAS51DMgr
      • WASPreUpgrade C:WAS51ackupsAppServer C:WAS51AppServer
    • Note: See InfoCenter for full syntax.
    WASPostUpgrade Syntax & Examples
    • Syntax
      • WASPostUpgrade <backupDirectory>
    • Examples
      • WASPostUpgrade C:WAS51ackupsDMgr
      • WASPostUpgrade C:WAS51ackupsAppServer
    • 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
    • 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!
  • 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
  • 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
  • Migrating to Java 2 Standard Edition (J2SE) 5
    • 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.
  • 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
  • Migrating Web application components from WebSphere Application Server Version 5.x JSP migration might be a concern if your application references JSP page implementation classes in unnamed packages       Example: setContentType(&quot;text/html;charset=ISO-8859-7&quot;); getWriter(); setContentType(&quot;text/xml;charset=UTF-8&quot;); text or html text or html text or html Remove charset from the Content-Type property if the setContentType property is called after getWriter with a &quot;;charset=&quot; portion charset=UTF-8     Example: response.setCharacterEncoding(&quot;UTF-8&quot;); response.setContentType(&quot;text/xml&quot;); response.getWriter(); text/xml; text or html text or html Append Charset on getWriter if the property does not exist on Content-Type none text or html charset=<default_encoding> text or html Default Content-Type Version 6 Version 5 Version 4  
  • 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
  • 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
  • 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
  • Migrating applications to use data sources of the current J2EE Connector Architecture (JCA)
    • 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
  • 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
  • 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 fields
    • 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.
    JMSReplyTo The name of the destination is unaltered. Other properties of the destination are mapped to their WebSphere Application Server Version 6 equivalents, where possible. JMSDestination Unchanged JMSType Can be reset as a result of the migration process. JMSRedelivered Unchanged JMSExpiration Unchanged JMSTimestamp Unchanged JMSPriority Unchanged JMSDeliveryMode Unchanged JMSCorrelationID Unchanged JMSMessageID State after migration Header field name
  • JMSX properties Not supported by service integration bus. JMSXState Not supported by service integration bus. JMSXRcvTimestamp Not supported by service integration bus. JMSXConsumerTXID Not supported by service integration bus. JMSXProducerTXID Unchanged JMSXGroupSeq Unchanged JMSXGroupID Can be reset as a result of the migration process. JMSXDeliveryCount Unchanged JMSXAppID Unchanged JMSXUserID State after migration JMSX property name
  • 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
  • Interoperating Security with previous product versions
    • 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
    • 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!
  • Fine Grain Application Update Application EAR Module1.jar a/b/File1 c/d/File2 Module2.war e/f/File1 g/h/File2 Module3.jar i/j/File1 k/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 EAR Module1.jar a/b/File1 c/d/File2 Module2.war e/f/File1 g/h/File2 m/n/File3 Module3.jar r/s/File4 t/u/File5 r/s/File4 t/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 EAR Module1.jar a/b/File1 a/b/File2 e/f/File1 Module2.war i/j/File1 k/l/File2 Partial Application ZIP /Module1.jar/META-INF/ ibm-partialapp-delete.props Application EAR (final) Module1.jar e/f/File1 Module2.war i/j/File1 k/l/File2 a/b/File*
  • AST & Enhanced EAR
    • Same look and feel as IBM Rational Application Developer
  • The Problem
    • Full install of GA : Select features and provide other install-time input
    • Install refresh pack (if needed)
    • Install fix packs (if needed)
    • Install one or more interim fixes (if needed)
    • Create and configure App Servers and other artifacts
    • Deploy applications
    Installing and configuring WAS usually requires many steps: Typically need to iterate over these steps to achieve desired end result – not a pure linear process! V6.0 V6.0.2 V6.0.2.5 iFix “A” and “B” JDK 1.4.2 SR3 wsadmin script J2EE app A B
  • Installation Factory Capabilities Command Line Invocation Tool
    • Single package containing
    • V6.0
    • V6.0.2
    • V6.0.2.5
    • J2EE Applications
    • Configuration archive
    Automated, customized WAS install package Processing Engine V6.0 V6.0.2 V6.0.2.5 JDK 1.4.2 SR3 Build Definition XML iFix “A” & “B”
    • JDK 1.4.2 SR3
    • iFix “A” and “B”
    • 3 rd -party Scripts
    J2EE Applications Configuration Archive 3 rd -party Scripts C:>ifcli Create A B Composition Tool (GUI)
  • Using a CIP to Update an Install
    • System Level After CIP Installation
      • V6.0.2.5
      • JDK 1.4.2 SR3
      • iFix “A” and “B”
    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 Installations … Install… Automated, customized WAS install package Existing WAS Installations Install CIP Final System Level
    • Single package containing
    • V6.0
    • V6.0.2
    • V6.0.2.5
    • JDK 1.4.2 SR3
    • iFix “A” and “B”
  • 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 Data Base Data Base EJB Mediator Custom Mediator JDBC Mediator SDO Core APIs Client Unified data representation & retrieval across heterogeneous data sources File … … Access APIs Data APIs Metadata Access APIs Metadata APIs Access APIs Data APIs Metadata Access APIs Metadata APIs Access APIs Data APIs Metadata Access APIs Metadata APIs
    • 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 Extensions
    • Core 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
    Converged Servlet 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
    Portlet Support The portlet project creation wizard will create an empty portlet for you and add it to the project
  • 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
  • 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
  • Consumability: Command Console Assist The WS Admin scripting commands that map to actions on the admin console are logged and/or JMX notifications emitted in the Jython language
  • 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/RI
    • SAAJ 1.2
    • APIs for manipulating SOAP XML messages
    • WS-Security
    • WSS 1.0
    • WS-I Basic Profile 1.1
    • Attachments support
    • WS-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 transactions
      • WS-I BSP (Basic Security Profile)
      • Interoperability over the wire (i.e. WebSphere client with .NET svr.)
      • Tightening of specification
      • WS-N (Notification)
      • Publish/Subscribe model
      • WS – Security enhancements
      • Performance 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 enhancements
      • WS-RF (Resource Framework)
      • Stateful web service resources
      • WS-Addressing
      • Endpoint ref. support for WS-Res.
    WAS V5.0.2/5.1 WAS V6.0 WAS V6.1
  • 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!
  • Goal: Ease Application Serving Management Burden
    • 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
  • 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 Manager Security SIP Container Web Services EJB Container Web Container V6.1 Server Infrastructure… V7 Server Dynamically Activated!! All Activated HA Manager Security SIP Container Web Services EJB Container Web 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
    • You want to…
    • Reduce SOA infrastructure administrative overhead
    • Provide remote management for expanded topologies
    Intelligent management features ease admin. open new opportunities Node A Admin scripts Server configuration Node A configuration Cell config Admin console App Server Admin Agent
  • Capitalizing on Intelligent App Server Management WebSphere Application Server v7 Allows Flexible Management of Branch Organizations
    • Supports high latency remote branch servers
    • Supports geographically separated data centers
    Job Manager Dmgr Dmgr Dmgr Dmgr Admin Agent Dmgr Admin Agent Job Manager
  • 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
    Admin Node WAS ND Cell Job Manager Admin Agent Base Node Base Node Base Node
  • Capitalizing on Intelligent App Server Management WebSphere Application Server v7 Overcomes Challenges of Existing Base Management WebSphere Application Server V5 & V6 Base Product Architecture Node A Admin scripts Admin console Node Agent NOT included in Base product Admin logic hosted in the same JVM as application server and customer applications. Current Base Management Server configuration Node A configuration Cell config App Server
  • Capitalizing on Intelligent App Server Management WebSphere Application Server v7 Overcomes Challenges of Existing Base Management ( cont .) New Flexible Management Option WebSphere Application Server V7 Base Product Architecture Node A Admin scripts Server configuration Node A configuration Cell config Admin console App Server Admin Agent included in Base product Admin Agent
  • 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 JAR EAR Axis2 PAR Business Logic Configuration Composition
  • Using Technology Innovation to Meet Evolving Needs WebSphere Application Server v7 Offers Enhanced Kerberos Support Broader implementation of Kerberos delivers improved interoperability with other applications and environments WebSphere Application Server Kerberos KDC Kerberos z/OS KDC WebSphere Application Server/zOS DB2 RACF LDAP Browser clients with desktop 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 RACF User Registry LDAP User Registry Kerberos token over RMI/IIOP, Web Services
  • 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