Menu

Showing posts with label Migration. Show all posts
Showing posts with label Migration. Show all posts

23 Feb 2020

WebSphere ND Migration 7.0 to 8.0 / 9.0 on Same Machine.

Prequesties check:
1. Check O.S prerequisites.
2. Source WAS 7.0 should be completely stopped.
3. Disk space needs to be there. 
4. Targeted WAS 8.0 / 9.0 needs to be installed on a machine.
5. Increase the number of open files limits on the O.S level (ulimit -a).


Tools for Migration
a) Migration 9 GUI based (WCT tool).
b) Command-line (i) WASPreUpgrade (ii) WASPostUpgrade


I have three profiles in existing WAS 7.0(in my scenario), 
a) Dmgr01
b) Custom01
c) Custom02

NOTE: Before proceeding always take config or profile backup.


*****************************************************************************************************
Commands for backup.

a) Dmgr01 backup

Command:
./backupConfig.sh /app/WAS7-APP-ND/IBM/WebSphere/AppServer/profiles/Mig-Backup_Dmgr01.zip   
-profileName Dmgr01 





 b) Custom01 backup

Command:
./backupConfig.sh /app/WAS7-APP-ND/IBM/WebSphere/AppServer/profiles/Mig-Backup_Custom01.zip   
-profileName Custom01 







*****************************************************************************************************

  • Install New instance of WAS 8.0 / 9.0 on Machine.
  • IMP NOTE: Before proceeding, need to create the same profiles in WAS 8.0 / 9.0  with having the same nodeName, cell namehostname, servers instances & no applications.

*****************************************************************************************************

A) create the same profile "Dmgr01" in WAS 8.0 having same nodeName, cellName,  hostname , server instance & with no applications.

Command:
/app/WAS8-APP-ND/IBM/WebSphere/AppServer/bin/manageprofiles.sh -create   
-profileName Dmgr01 
-profilePath /app/WAS8-APP-ND/IBM/WebSphere/AppServer/profiles/Dmgr01   
-templatePath /app/WAS8-APP-ND/IBM/WebSphere/AppServer/profileTemplates/management   
-serverType DEPLOYMENT_MANAGER   
-nodeName Dmgr01Node  -cellName Dmgr01NodeCell -hostName MBox  -defaultPorts 
-enableAdminSecurity true -adminUserName was -adminPassword was123




B) create the same profile "Custom01" in WAS 8.0 / 9.0 having the same nodeName, cellName,  hostname, server instance & with no applications installed.

Command:
/app/WAS8-APP-ND/IBM/WebSphere/AppServer/bin/manageprofiles.sh -create  
-profileName Custom01 -defaultPorts  
-profilePath /app/WAS8-APP-ND/IBM/WebSphere/AppServer/profiles/Custom01  
-templatePath /app/WAS8-APP-ND/IBM/WebSphere/AppServer/profileTemplates/managed  
-nodeName Custom01Node  -cellName Custom01Cell  -hostName MBox -federateLater true





*****************************************************************************************************


Create a folder on targeted WAS 8.0, to place WASPreUpgrade migration command files.

Command:
mkdir -p /app/WAS8-APP-ND/IBM/WebSphere/WASMigration/Dmgr01
mkdir -p /app/WAS8-APP-ND/IBM/WebSphere/WASMigration/Custom01
mkdir -p /app/WAS8-APP-ND/IBM/WebSphere/WASMigration/Custom02












WASPreUpgrade 

  • NOTE: Stop all the WAS services on 7.0.
  • Run WASPreUpgrade command from WAS8-APP-ND/IBM/WebSphere/AppServer/bin/ for "Dmgr01" profile.


Command:
/app/WAS8-APP-ND/IBM/WebSphere/AppServer/bin/WASPreUpgrade.sh   
/app/WAS8-APP-ND/IBM/WebSphere/WASMigration/Dmgr01  
/app/WAS7-APP-ND/IBM/WebSphere/AppServer/    
-traceString Migration.Flow=finer:Migration.*=fine   
-traceFile /app/WAS8-APP-ND/IBM/WebSphere/WASMigration/Dmgr01_WASPreUpgrade.trace  
-oldProfile Dmgr01   -username was   -password was123 




Reference URL :
https://www.ibm.com/support/knowledgecenter/en/SSEQTP_8.5.5/com.ibm.websphere.migration.base.doc/ae/rmig_WASPreUpgrade.html

Syntax
*********************************************************************************
WASPreUpgrade.sh backupDirectory 
                 currentWebSphereDirectory
                 [-traceString trace_spec [-traceFile file_name ]]
                 [-machineChange true | false]
                 [-oldProfile profile_name]
                 [-workspaceRoot profile1=user_workspace_folder_name_1;profile2=user_workspace_folder_name_2]
                 [-username < user name >]
                 [-password < password >]
                 [-javaoption < -Xms...m > -javaoption < -Xmx...m > ]
                 [-requireEmbeddedDBMigration true | false]
                 [-keepDmgrEnabled true | false]
*********************************************************************************

Similarly  

  • Run WASPreUpgrade command from WAS8-APP-ND/IBM/WebSphere/AppServer/bin/ for "Custom01" profile.

Command:
/app/WAS8-APP-ND/IBM/WebSphere/AppServer/bin/WASPreUpgrade.sh   
/app/WAS8-APP-ND/IBM/WebSphere/WASMigration/Custom01  
/app/WAS7-APP-ND/IBM/WebSphere/AppServer/    
-traceString Migration.Flow=finer:Migration.*=fine   
-traceFile /app/WAS8-APP-ND/IBM/WebSphere/WASMigration/Custom01_WASPreUpgrade.trace  -oldProfile Custom01   -username was   -password was123 





*********************************************************************************

*********************************************************************************

WASPostUpgrade 
  • Run WASPostUpgrade command from WAS8-APP-ND/IBM/WebSphere/AppServer/bin/ for "Dmgr01" profile.


Command:
/app/WAS8-APP-ND/IBM/WebSphere/AppServer/bin/WASPostUpgrade.sh  
/app/WAS8-APP-ND/IBM/WebSphere/WASMigration/Dmgr01  
-oldProfile Dmgr01  -profileName Dmgr01 -scriptCompatibility true   
-replacePorts false  -includeApps true  -keepAppDirectory false  
-traceString Migration.Flow=finer:Migration.*=fine 
-traceFile /app/WAS8-APP-ND/IBM/WebSphere/WASMigration/Dmgr01_WASPostUpgrade.trace 
-username was   -password was123




https://www.ibm.com/support/knowledgecenter/SS7K4U_8.5.5/com.ibm.websphere.migration.nd.doc/ae/rmig_WASPostUpgrade.html

Syntax: 
*****************************************************************************************************
WASPostUpgrade.sh backupDirectory
                     [-username userID]
                     [-password password]
                     [-oldProfile profile_name]
                     [-profileName profile_name]
                     [-scriptCompatibility true | false]
                     [-portBlock port_starting_number]
                     [-backupConfig true | false]
                     [-replacePorts true | false]
                     [-includeApps true | false | script]
                     [-keepDmgrEnabled true | false]
                     [-requestTimeout seconds]
                     [-javaoption -Xms...m -javaoption -Xmx...m]
                     [[-appInstallDirectory user_specified_directory] | 
                      [-keepAppDirectory true | false]]
                     [-traceString trace_spec [-traceFile file_name]]
*****************************************************************************************************


IMP NOTE:
Start the Dmgr01 profile, and force delete the already federate nodes in dmgr from DMGR console.
Since it contains WAS 7.0 node agents.







  • Run WASPostUpgrade command from WAS8-APP-ND/IBM/WebSphere/AppServer/bin/ for "Custom01" profile.


Command:
 /app/WAS8-APP-ND/IBM/WebSphere/AppServer/bin/WASPostUpgrade.sh  
/app/WAS8-APP-ND/IBM/WebSphere/WASMigration/Custom01  
-oldProfile Custom01  -profileName Custom01 -scriptCompatibility true   -replacePorts false  
-includeApps true  -keepAppDirectory false  
-traceString Migration.Flow=finer:Migration.*=fine 
-traceFile /app/WAS8-APP-ND/IBM/WebSphere/WASMigration/Custom01_WASPostUpgrade.trace -username was   -password was123


NOTE: The above command will automatically federate the node, with the running Dmgr01 profile.







For understanding.
  1. stop WAS 7.0 services & profiles completely.
  2. take existing WAS 7.0 Backup.
  3. install WAS 8.0 and create same profiles on new WAS 8.0 /9.0 , having same nodeName, cellName,  hostname, server instance & with no applications.
  4. Run $WAS8_HOME/bin/WASPreUpgrade command, & save the pre upgrades migration files.
  5. Run $WAS8_HOME/bin/WASPostUpgrade command & for Dmgr01.
  6. Start WAS 8.0 Dmgr01 and force delete the nodes of WAS7.0
  7. Run $WAS8_HOME/bin/WASPostUpgrade command for Custom01, (it will automatically federate the nodes with WAS8.0 dmgr01)
  8. Do the same for Custom02 also.
  9. Clear all profiles wstemp, temp, tranlog & logs files.
  10. federate the nodes with dmgr and start node & servers instances.

Reference links: 

Thanks :-)




26 Jan 2020

JBOSS EAP 6 TO 7 Migration

Migration of JBOSS EAP 6 to JBOSS EAP 7 is now made easy.

  • The JBoss Server Migration Tool is a Java application that automatically migrates JBoss EAP server configurations with minimal or no interaction required.
  • The JBoss Server Migration Tool reads your existing source server configuration files and adds configurations for any new subsystems, updates the existing subsystem configurations with new features, and removes any obsolete subsystem configurations.

You can run the JBoss Server Migration Tool in either of the following ways

  • Interactive mode: This mode, which is the default, allows you to choose exactly which configurations you want to migrate.
  •  Non-interactive mode: This mode allows you to run the tool without prompts.

NOTE: You must Stop both target and source JBOSS EAP servers & Take Full Backup of target & Source JBoss EAP servers.


Command Syntax: 

$JBOSS-7.2-HOME/bin/jboss-server-migration.sh --source ../jboss-eap-6.4 --target ../jboss-eap-7.2


Step 1: Navigate to Target $JBOSS-7-HOME Server /bin folder.


Step 2: Use below command for Interactive mode way, it’s by default.

./jboss-server-migration.sh --source /JBOSS/jboss-eap-6.4 --target /JBOSS/jboss-eap-7.2





Where,
jboss-server-migration.sh : JBoss Migration tool script.
--source : location of old JBoss EAP Server.
-- target : Location of New targeted JBoss EAP server.

You may ask multiple interactive question for migration of  source standalone configuration, deployments & domain configurations.







Step 3: On Completion Migration Success message is available.






Step 4: New migration Configuration is available now.




Step 5: Migration Logs & reports, Reports are available in .xml & html file formats:



FOR,

 JBoss Server Migration Tool in  NonInteractive Mode:

NOTE: The JBoss Server Migration Tool automatically migrates all subsystem configurations for all server configuration files ONLY,  Deployements will going to be SKIP.

Use below Commands:

./jboss-server-migration.sh --source /JBOSS/jboss-eap-6.4 --target /JBOSS/jboss-eap-7.2 --interactive false






JBoss Migration Report is HTML format:



Thanks:-)