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

Transcription

1 An IBM Proof of Technology Getting Started with WebSphere Application Server Version to Version Migrations WebSphere Application Server Configuration Migration

2 Agenda Configuration Migration Overview Configuration Migration Tools Configuration Migration Type Configuration Migration Scenarios 2

3 Runtime Environment Most likely will need to support parallel development Migrate some test systems iteratively Assessment Planning Integration System test Performance Pre-Production Production Development Environment Code Migration Skills Runtime Environment Runtime Migration Unit Test Test Systems Test Use the same migration process throughout if possible Or at least before you do production migration Production Review results 3

4 Configuration migration process v6.x, v7.0 Profile WAS PreUpgrade Backup Files Server Configuration Applications Resources Create V8.x Profile V8.x Profile WAS PostUpgrade Migrated 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 5

5 Agenda Configuration Migration Overview Configuration Migration Tools Configuration Migration Type Configuration Migration Scenarios 6

6 Configuration migration tools 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 WASPreUpgrade tool stored the data. 7 7

7 Benefits of using configuration migration tools Migrate WebSphere environments faster with minimized risk 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 8

8 Migration Wizard 1. Migration Wizard is included in the WebSphere Application Server s Customization Toolbox Installed as a feature when installing WebSphere Application Server 2. Launch the Configuration Migration Tool from the Customization toolbox 9 9

9 Migration Wizard detects WebSphere Application Servers Automatically detects existing WebSphere Application Servers that exist on the system 10 IBM Confidential 10

10 Choose a Profile to Migrate Choose the profile you want to migrate Select if you want to backup the existing configuration prior to migrating the profile 11 IBM Confidential 11

11 Disable the old Deployment manager? You have the option to disable the source Dmgr after a successful migration If selected, the OLD Dmgr will be shutdown. This will prevent port conflicts between the source and target Dmgr s 12 IBM Confidential 12

12 Migration Output Specify the migration output and trace directories Specify the trace level for the migration commands (default=fine) 13 IBM Confidential 13

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

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. WebSphere Sample applications will NOT be migrated. 15

15 What to do about Port Conflicts Guide the migration wizard on the appropriate action to take in the event of port conflicts during the migration. The default values are selected below 16 IBM Confidential 16

16 Generate Migration Commands Migration commands can be generated and used for subsequent Command Line profile migrations 17 IBM Confidential 17

17 Example of Generated Migration Commands 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 IBM Confidential 18

18 Monitor the steps during the migration 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 4. Migrate to Target Profile 19 IBM Confidential 19

19 Migration Results On the Migration Results screen, click the link to each log file to view the migration output. 20 IBM Confidential 20

20 Configuration migration tools required parameters 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 Port value assignments 21 21

21 Agenda Configuration Migration Overview Configuration Migration Tools Configuration Migration Type Configuration Migration Scenarios 22

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

23 Migrate to a standalone WAS server procedure Use Migration Wizard OR Use Migration Tools

24 Migrate to a standalone WAS server to a remote machine procedure Use Migration Tools 25

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

26 Migrate to a federated node procedure Use Migration Wizard to migrate the WebSphere federated nodes WAS Manager = WAS Deployment manager 27

27 Agenda Configuration Migration Overview Configuration Migration Tools Configuration Migration Type Configuration Migration Scenarios 28

28 Continued Mixed Version Cell Support Support for existing infrastructure in new deployments Business Value: Adopt newer infrastructure as your plans require, saving time and money WAS Network Deployment Cell Deployment Manager 1st provided in version v6.0 ND Agent ND Agent ND Agent ND Agent ND s ND v6.1 s ND v7.0 s ND v8.0 s Cell can contain v6.1,v7.0,v8.0 & nodes: for continued operation as well as staging of upgrades Note Precompile options are not available for application deploy to back level nodes 29

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 X 1. In Place - Copy and replace the DMgr Recreates the exact existing configuration in new cell Add new nodes and move incrementally X 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 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 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 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 X Dependency on using the runtime migration tools Limited value if you are refactoring your topology Carries default values forward from the old cell 33

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 34

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 35