Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.
Curious about IBM WebSphere V9 but unsure how to migrate? Whether you’re looking to connect to the cloud or enhance your existing on-premises applications, WebSphere V9 has fast and easy ways to include hybrid capabilities into your application infrastructure. If you're looking to learn more about the newest features of V9 click here for our previous webinar on WebSphere v9 Technical Update. And if you're wondering how to do a migration, join this webinar with a panel of IBM experts who will show you how you can seamlessly migrate to WebSphere V9. This session covers migration planning, best practices and new clone techniques ,source and binary application migration tools from the IBM WebSphere Application Server Migration Toolkit. Both configuration and application migration considerations will be covered. This session pertains to WebSphere Application Server versions 7.0 and beyond, and also includes a live demo for you to better understand the technical aspects, migration resources and support available for WebSphere V9. Speakers: Cindy High, Software Engineer, WebSphere Development Ray V Scott, WebSphere Development, IBM Cloud
02:04:51
RE: Migration and Datasources
Bhaskar,
The answer to your questions are as follows:
First - let's establish which JDBC drivers are supported by which WebSphere release. WebSphere v855 supports JDBC 4.0 and some previous versions. WebSphere V9.0 support JDBC 4.1 and some previous versions. JDBC is not officially supported at this time. Please open an RFE requesting support for JDBC 4.2. You could install and configure JDBC 4.2 on release v9.0 as long as you only use those features and functions already supported by JDBC 4.1.
So on to migration...
As stated in the presentation, you should migrate only one piece at a time and fully test that before moving on to the next. Given that both V855 and V9 support the common JDBC version 4.0 driver. You should remain at that JDBC version until all nodes are migrated to v9.0. Remember that the Deployment Manager is the master of all config files for the entire cell. So if you only migrate the Dmgr and not the nodes and then migrate to JDBC 4.1, that configuration is synced to the nodes - which are still at v855, which does not officially support JDBC 4.1. You stated that you are doing a standard migration, therefore you will be in a mixed cell environment (Dmgr is managing one or more nodes at a previous release). So yes - migrate all nodes to v9 before upgrading to JDBC 4.1.
Kind of long winded answer - hope that answers your questions.
Thank you for the presentation
Thank you Kelsy Tibshraeny for presentation arrangement and made it to be here. and Thank you for Cindy High and Ray V Scott. I have question about Datasource.. The existing websphere 8.5.5.9 having sql driver 4.0 ( running in JDK 1.6 ) but planning to modify the driver to 4.2 ( needs JDK 1.8) in WAS9.0, can I do that update after migration is done at WAS 8.5.5.0 DMGR to WAS 9001 DMGR or after completeing all the nodes in the cell? if I do changes before all nodes are modify, will the driver ( new driver ) affect the existing node ( to maintain zero downtime ) - Planning for standard migration ( to maintain the port number to be same as old ).. Need you advice or guidelines on this.. ( yes I am going to disable the File Synchronization during this migration ).