Getting Started with WebSphere Application Server v8.5 Version to Version Migrations

(1)

An IBM Proof of Technology

Getting Started with WebSphere Application

Server v8.5 Version to Version Migrations

(2)

Agenda



_{Configuration Migration Overview}



_{Configuration Migration Tools}



_{Configuration Migration Type}



_{Configuration Migration Scenarios}

(3)

Runtime Environment



Most likely will need to support parallel

development



_{Migrate some test systems iteratively}

– Integration – System test – Performance – Pre-Production – Production



_{Use the same migration process throughout}

if possible

– Or at least before you do production migration… Assessment Planning Skills Production Review results Test Development Environment Code Migration Unit Test Runtime Environment Runtime Migration Test Systems Development Environment Runtime Environment 3

(4)

5

Configuration migration process

v6.x, v7.0 Profile

Create V8.x Profile _{WAS PostUpgrade} V8.x ProfileMigrated

WAS PreUpgrade _Backup Files

• Server Configuration

• Applications

• Resources

V8.x Profile

Migrating is the copying of a WebSphere Application Server configuration from a previous release of a product into a new release

(5)

Agenda



_{Configuration Migration Overview}



_{Configuration Migration Tools}



_{Configuration Migration Type}



_{Configuration Migration Scenarios}

(6)

Configuration migration tools

7



Migration wizard

‒ migrate an earlier supported version of WebSphere Application

Server to Version 8.x

‒ A graphical interface of migration tools, the WASPreUpgrade and

the WASPostUpgrade.



WASPreUpgrade tool

‒ Save the applications and configuration data from a previous

installation of WebSphere Application Server to a backup directory.



_{WASPostUpgrade tool}

‒ Restore the configuration data from a previous release.

‒ Reads the data from the backup directory where the

(7)

8

Benefits of using configuration migration tools



_{Assists administrators in moving their configuration when}

migrating

‒

_{Merges old configuration with new configuration}

‒

_{Provides deep functionality, e.g. “Lights-on” WAS migration}

‒

_{Especially useful for customers that have large topologies}

• Large telecom customer recently used the tool when migrating a 500+ JVM environment



Provides a framework for Stack product migration

‒

_{Already in use by Commerce, Portal, WPS and Virtual Enterprise}

(8)

Migration Wizard

9

1. Migration Wizard is included in the WebSphere Application Server’s

‘Customization Toolbox

’

‒ Installed as a feature when installing WebSphere Application Server

(9)

Migration Wizard detects WebSphere Application Servers

10 IBM Confidential



_{Automatically detects existing WebSphere Application Servers that exist on the}

(10)

Choose a Profile to Migrate

11 IBM Confidential



_{Choose the profile you want to migrate}

(11)

Disable the old Deployment manager?

12 IBM Confidential



_{You have the option to disable the source Dmgr after a successful migration}



_{If selected, the OLD Dmgr will be shutdown.}

(12)

Migration Output

13 IBM Confidential



_{Specify the migration output and trace directories}

(13)

Migrate to a new or existing Profile



_{Choose to migrate to a new profile or an existing profile that the System}

Administrator has already created.

‒ If migrating to a new profile, the wizard will prompt you for Profile information that will be used to create the new profile

(14)

Do you want to migrate applications?



_{You may choose to move the applications.}



_{This option does not ensure the applications will run on the target}

environment.



_{Recommend using the Application Migration Toolkit to migrate}

applications and ensure all breaking changes are resolved.

(15)

What to do about Port Conflicts

16 IBM Confidential



_{Guide the migration wizard on the appropriate action to take in the event}

of port conflicts during the migration.

(16)

Generate Migration Commands

17 IBM Confidential



_{Migration commands can be generated and used for subsequent ‘Command Line’}

(17)

Example of Generated Migration Commands

18 IBM Confidential

1. Backup of the profile (backupConfig.bat)

2. Execute the WAS pre upgrade command (WASPreUpgrade.bat)

3. Create the new profile (manageprofiles.bat -create -profileName AppSrv01)

4. Execute the WAS post upgrade command (WASPostUpgrade.bat)

(18)

Monitor the steps during the migration

19 IBM Confidential



_{As each step is completed successfully, the tabs representing the steps will have a}

green

check mark

1. Backup Source Profile, 2. Migrate from Source Profile 3. Create Target Profile

(19)

Migration Results

20 IBM Confidential



_{On the “Migration Results” screen, click the link to each log file to view the}

(20)

Configuration migration tools required parameters

21



Migration backup directory name



Installation root directory



Administrative user name for the current installation



Password for the administrative user name of the current installation



Source profile name



Target profile name



Applications to be migrated

(21)

Agenda



_{Configuration Migration Overview}



_{Configuration Migration Tools}



_{Configuration Migration Type}



_{Configuration Migration Scenarios}

(22)

Configuration migration types



_{Migrate to a standalone WAS server}



_{Migrate to a standalone WAS server on remote machine}



_{Migrate to a Deployment Manager server}



_{Migrate to a federated node}

(23)

Migrate to a standalone WAS server procedure

Use Migration Wizard OR

_{Use Migration Tools}

24

1

2

3

1

2

3

4

(24)

Migrate to a standalone WAS server to a remote machine procedure

Use Migration Tools

(25)

Migrate to a Deployment Manager server procedure

Use Migration Wizard to migrate

the WebSphere Deployment

manager node

WAS Manager = WAS Deployment manager

DM Profile = Deployment manager Profile

(26)

Migrate to a federated node procedure

27

Use Migration Wizard to migrate

the WebSphere federated nodes

(27)

Agenda



_{Configuration Migration Overview}



_{Configuration Migration Tools}



_{Configuration Migration Type}



_{Configuration Migration Scenarios}

(28)

Continued Mixed Version Cell Support

v8.5 Deployment Manager

WAS Network Deployment v8.5 Cell

ND Node Agent

ND v7.0 Nodes

ND v8.5 Nodes

v8.5 Cell can contain v6.1,v7.0,v8.0 & v8.5 nodes: for continued operation as well as staging of upgrades Note – Precompile options are not available for application deploy to back level nodes

ND v8.0 Nodes

1st provided in version v6.0

Business Value: Adopt newer infrastructure as your plans require, saving time and money

Support for existing infrastructure in new deployments

ND Node Agent

ND v6.1 Nodes

(29)

Five Network Deployment strategies

1. Side by Side

– Create a new cell and populate with scripts or manually – No runtime migration tools

1. In Place - Copy and replace the cell

– Recreates the exact existing configuration in the new cell – DMgr and nodes are migrated

1. In Place - Copy and replace the DMgr

– Recreates the exact existing configuration in new cell – Add new nodes and move incrementally

1. In Place - Copy and coexist

– Recreates the exact existing configuration in the new cell – Modify the ports in the new cell and coexist

1. Side by Side - Fine Grained

– Create a new cell and incrementally copy existing configuration

– Uses an intermediate profile, runtime migration and wsadmin tools v8.5 Node v8.5 Node Old Node Old Node v8.5 Node v8.5 Node Old Node Old Node Old Node v8.5 Node v8.5 Node Old Node v8.5 Node Old Node Old Node v8.5 Node v8.5 Node v8.5 Node Old Node Old Node

X

30

(30)

Side by Side



Ignores the existing configuration



_{Create a new cell and populate with administration scripts or}

manually



_{Best results with a comprehensive set of scripts or tools for}

configuration automation



Pros

– No dependencies on tooling

– Least risk assuming existing scripts are comprehensive – Can easily migrate applications singly



_Cons

– Comprehensive set of scripts and ongoing maintenance of those scripts can be expensive

– Any required changes to these scripts must be done before migrating

– Any tuning of the old configuration is not carried forward

v8.5 Node v8.5 Node Old Node Old Node 31

(31)

In Place - Copy and replace Cell



_{Use Runtime migration tools on DMgr}

– Recreates the exact existing configuration in the new cell



Later migrate the existing nodes using the runtime

migration tools

– All applications on a managed node are migrated at the same time



_Pros

– Does not require comprehensive set of scripts – All configuration is moved forward



_Cons

– Dependency on using the runtime migration tools

– Requires all applications on a node be ready to migrate at the same time

– Limited value if you are refactoring your topology

– Carries default values forward from the old cell v8.5 Node v8.5 Node Old Node Old Node Old Node Old Node Old Node v8.5 Node v8.5 Node v8.5 Node Old Node Old Node

X

32

(32)

In Place - Copy and replace DMgr



_{Use Runtime migration tools on DMgr}

– Recreates the exact existing configuration in the new cell



_{Add new nodes}

– Applications can be migrated singly when ready – Remove old nodes when no longer needed



_Pros

– Does not require comprehensive set of scripts – All configuration is moved forward

– Cell and cluster level configuration accessible by older nodes



_Cons

– Dependency on using the runtime migration tools – Limited value if you are refactoring your topology – Carries default values forward from the old cell

Old Node Old Node v8.5 Node v8.5 Node Old Node Old Node v8.5 Node v8.5 Node

X

Old Node Old Node Old

Node NodeOld

(33)

In Place - Copy and coexist



_{Same steps as “Copy and replace Cell” except:}

– Use the options of the runtime Migration tools to not disable the DMgr

– Turn off the old DMgr (the federated nodes should be able to continue running)

– Migrate all the nodes

– Modify the new cell to resolve port conflicts

– Start old DMgr, new DMgr and all nodes in the new cell



_{See latest Migration}

redbook

for example

– http://www.redbooks.ibm.com/abstracts/sg248048.html?Open v8.5 Node v8.5 Node Old Node Old Node Old Node Old Node Old Node v8.5 Node v8.5 Node v8.5 Node Old

Node NodeOld

(34)

Side by Side - Fine Grained



_{Uses a combination of tools}

– An intermediate profile

– The runtime migration tools

– Properties based configuration tool (PBC)



_Approach

– Migrate the existing data to an intermediate profile – Extract portions of the configuration from that profile

– Import them into the final DMgr profile using PBC NodeOld

v8.5 Node

v8.5 Node Old

Node