WebSphere Migration

 WebSphere Migration from WAS 8.5.5.x to WAS 9.0.x.x














Self -Help Understanding:
WebSphere Migration from WAS 8.5.5.x to WAS 9.0.x.x

Prerequisite for WebSphere Migration:
Existing environment: WAS ND 8.5.5.0
IBMIM 1.6 version
WAS Binaries
WAS Profiles(Dmgr01, Custom01)
=============================================
Up-gradation steps from WAS ND 8.5.5.0 to 9.0.x.x

Step 1: We need to Upgrade IBMIM 1.6 version to IBMIM 1.8 version.(upgrading IBMIM means installing latest one 1.8 version)

Step 2: We need to install WebSphere AppServer ND 9.0.x.x freshly using latest IBMIM 1.8

Step 3: After installation, create Empty profiles but with same name(like Profilename, Cellname, Nodename) and same port of existing one.

Step 4: Stop old Dmgr profile(WASND 8.5.5.x) and start new Dmgr profile(WASND 9.0.x.x)

Step 5: Crate custom profile with same node name(like older one is having) and don't federate it.

Now actual Migration process will start:

Step 6: WASPreUpgrade command
 Backup Profiles (./WASPreUpgrade.sh /tmp $wasroot -oldprofile Dmgr01)
 ($wasroot= /app/IBM/WebSphere/AppServer/)

Step 7: Post Upgrade (./WASPostUpgrade.sh /tmp -oldprofile Dmgr01 -profileName Dmgr01)

Step 8: Start New Dmgr

Step 9: Repeat same steps for other Profiles.
===================================== 

older WAS Path
/app/IBM/WebSphere/AppServerV8.5

New WAS Path:
/app/IBM/WebSphere/AppServerV9

Continue from Step 6:

Step6: WASPreUpgrade command
go to path /app/IBM/WebSphere/AppServerV9/bin]
./WASPreUpgrade.sh /tmp /app/IBM/WebSphere/AppServerV8.5 -oldProfile Dmgr01

Step 7: WASPostUpgrade command
go to path /app/IBM/WebSphere/AppServerV9/bin]
./WASPostUpgrade.sh /tmp -oldProfile Dmgr01 -profileName Dmgr01

Step 8: Start Newly migrated Dmgr01(/app/IBM/WebSphere/AppServerV9/profiles/Dmgr01/bin]./startManager.sh)

Step 9: Migrate other profile like(Custome01) WASPreUpgrade command:
go to path /app/IBM/WebSphere/AppServerV9/bin]
./WASPreUpgrade.sh /tmp/Custom01 /app/IBM/WebSphere/AppServerV8.5 -oldProfile Custom01

Step 10: WASPostUpgrade command:
go to path /app/IBM/WebSphere/AppServerV9/bin]
./WASPostUpgrade.sh /tmp/Custom01/ -oldProfile Custom01 -profileName Custom01

Step 11: Start newly Migrated Custom profile node
([/app/IBM/WebSphere/AppServerV9/profiles/Custom01/bin]./startNode.sh)

======================**************=================================

Screenshot Examples:







========================***************=================================

WebSphere Migration Knowledge Collection: Migrating WebSphere Traditional Versions:


Full-Cell Distributed Migration:
Each WebSphere release is shipped with an updated set of migration tools which must be used to upgrade to the new release. These tools work on a profile by profile basis using the following process which must be repeated for each profile in the cell starting with the deployment manager:
1. WASPreUpgrade - captures the old configuration data and applications.
2. manageprofiles - creates a target profile in the new release.
3. WASPostUpgrade - merges in the old configuration data into the target profile and installs the applications.

IBM Cloud Transformation Advisor supports migrating a single application from a WebSphere Application Server environment by generating a configuration script that can be used to configure the server. In addition to providing configuration, Transformation Advisor assists in creating other deployment artifacts such as a Dockerfile and configuration yaml files used for deploying traditional WebSphere images to Kubernetes. Transformation Advisor is included with IBM Cloud Pak for Applications and has a free local trial version.

You can also use the WebSphere Migration Toolkit for Application Binaries (binary scanner) to generate an application-specific traditional WebSphere configuration script. Use the binary scanner's --generateConfig and --targetServer=was90 or was855 options to produce a wsadmin script which will configure your new target profile to support the specified application you are installing.

You can learn more about the WebSphere Application Server traditional container images IBM publishes as well best practices for their use.















WAS-PreUpgrade:

WASPreUpgrade.sh backupDirectory 
                 currentWebSphereDirectory
                 [-properties properties_file_name]
                 [-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]

 

WASPreUpgrade.bat backupDirectory 
                  currentWebSphereDirectory
                  [-properties properties_file_name]
                  [-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] 



Post-Upgrade:
WASPostUpgrade.sh backupDirectory
                     [-properties properties_file_name]
                     [-username userID]
                     [-password password]
                     [-oldProfile profile_name]
                     [-profileName profile_name]
                     [-setPorts useOld | generateNew | port_starting_number]
                     [-resolvePortConflicts incrementCurrent | port_starting_number]
                     [-backupConfig true | false]
                     [-includeApps true | false | script]
                     [-clone true | false]
                      [-newDmgrHostname host_name]
                      [[-newDmgrSoapPort port_number] | [-newDmgrRmiPort port_number]]
                     [-keepDmgrEnabled true | false]
                     [-requestTimeout seconds]
                     [-javaoption -Xms...m -javaoption -Xmx...m]
                     [[-appInstallDirectory user_specified_directory] | 
                      [-keepAppDirectory true | false]]
                     [-traceString trace_spec [-traceFile file_name]]


WASPostUpgrade.bat backupDirectory
                     [-properties properties_file_name]
                     [-username userID]
                     [-password password]
                     [-oldProfile profile_name]
                     [-profileName profile_name]
                     [-setPorts useOld | generateNew | port_starting_number]
                     [-resolvePortConflicts incrementCurrent | port_starting_number]
                     [-backupConfig true | false]
                     [-includeApps true | false | script]
                     [-clone true | false]
                      [-newDmgrHostname host_name]
                      [[-newDmgrSoapPort port_number] | [-newDmgrRmiPort port_number]]
                     [-keepDmgrEnabled true | false]
                     [-requestTimeout seconds]
                     [-javaoption -Xms...m -javaoption -Xmx...m]
                     [[-appInstallDirectory user_specified_directory] | 
                      [-keepAppDirectory true | false]]
                     [-traceString trace_spec [-traceFile file_name]]



WASMigrationAppInstaller command

Comments

Post a Comment

Popular posts from this blog

Understanding SSL

Image
Understanding SSL: There are many ways to go about creating an SSL connection between servers,  and the best one for your situation will depend upon the type of protocol you're planning to tunnel through it. As you probably know, the Secure Sockets Layer (SSL) allows the use of encryption to protect data sent via a TCP/IP connection. The most commonly used implementation of SSL is the HTTPS protocol: a secure encrypted alternative to HTTP for transferring information over the Web. Secure Sockets Layer ( SSL ) is a computer networking protocol for securing connections between network application clients and servers over an insecure network, such as the internet. Due to numerous protocol and implementation flaws and vulnerabilities, SSL was deprecated for use on the internet by the Internet Engineering Task Force ( IETF ) in 2015 and has been replaced by the Transport Layer Security ( TLS ) protocol. While TLS and SSL are not interoperable, TLS is backwards-compatible with
Read more

Session Management Part-1

Image
WebSphere Application Server Session Management Session support allows a Web application developer to maintain state information across multiple user visits to the application.  We will cover below points 1. HTTP session management 2. Session manager configuration 3. Session identifiers 4. Local sessions 5. General properties for session management 6. Session affinity 7. Persistent session management 1.HTTP session management: When an HTTP client interacts with a servlet, the state information associated with a series of client requests is represented as an HTTP session and identified by a session ID. Session management is responsible for managing HTTP sessions, providing storage for session data, allocating session IDs, and tracking the session ID associated with each client request through the use of cookies or URL rewriting techniques. 2.Session manager configuration: Session management in WebSphere Application Server can be defined at the follow
Read more

WebSphere Application Server

Image
What is WebSphere Application Server  ? WebSphere is a set of Java-based tools from IBM that allows customers to create and manage sophisticated business Web sites. The central WebSphere tool is the WebSphere Application Server (WAS), an application server that a customer can use to connect Web site users with Java applications or servlets. IBM released WebSphere Application Server 8.5 in June 2012 and 8.5.5 in June 2013 A pplication Server provides the infrastructure to host enterprise application. It handles application operation between user request to backend business application like a database, messaging, etc. Enterprise application, which is usually transactional based or heavily used, must have an application server with built-in redundancy, high availability, and performance oriented like WebSphere Application Server. Application Server usually sits between Web Server and Database or another backend like messaging, etc. Below is the typic
Read more