Search...
FAQs Subscribe
Pie
FAQs
Recent topics Flagged topics Hot topics Best topics
Search...
Search within WebSphere Search Coderanch
Advance search Google search
Register / Login
granny book review grid thread boost advertise on coderanch polymorphism
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
thread boost advertise on coderanch book review grid building better world book meaningless drivel
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Tim Cooke
  • Devaka Cooray
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Mikalai Zaikin
Bartenders:
  • Carey Brown
  • Roland Mueller

WebSphere 3.5 and DB2 UDB 8

 
Dana Hanna
Ranch Hand
Posts: 227
posted 20 years ago
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
We currently use WebSphere 3.5 on NT and it's internally backed DB2 UDB 6.2 database engine (WAS).
This WebSphere application server also has 4 datasources defined which are other DB2 6.2 Databases throughout the company.
We are slowly migrating all datasources to DB2 8, and I need to know if WebSphere 3.5 can connect to both at the same time (1 datasource is 8, 3 others are 6.2).
How do I proceed? Won't installing the DB2 8 client on the WebSphere box cause problems?
I've tried using DB2 8's Type 4 driver but recieve the following stack trace:
 
Howard Kushner
author
Posts: 361
posted 20 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
Hello Dana,
I am curious as to why you are staying so current with your DB2, while staying in the stone age with WebSphere. I would say that you are way overdue for an upgrade.
It has been years since I have worked with version 3.5, and I tend to avoid it like the plague since it is not fully J2EE compliant. The vast majority of the folks I come in contact with believe that that is a very big deal.

Howard Kushner<br />IBM Certified Enterprise Developer - WebSphere Studio Application Developer V5.0<br />IBM Certified Advanced System Administrator - WebSphere Application Server V5.0<br />IBM Certified Solution Developer - Web Services with WebSphere Studio V5.1<br /><a href="http://www.amazon.com/exec/obidos/tg/detail/-/1931182108/" target="_blank" rel="nofollow">Developing J2EE Applications with WebSphere Studio</a> my Certification Study Guide for IBM Test 287

 
Mahesh Chalil
Ranch Hand
Posts: 147
posted 20 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
My best bet is wait till you move your Websphere to upgraded versions before you migrate your database alone. In databases, the main difference between older version and new version is the support for JDBC2.0. DB26.x doesnt support JDBC2 but DB2 7 onwards, it does.
 
Dana Hanna
Ranch Hand
Posts: 227
posted 20 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
So what would the best migration approach be? I have 4 DB2 databases, and 5 applications (some using 2 databases)... I can't possibly upgrade all apps and databases simultaneously.
Databases:
1 ,2 ,3 ,4
Apps and required databases:
App A - 1,2,3,4
App B - 4
App C - 1
App D - 1,3
App E - 1,2
Obviously it's all a little too tightly coupled, and an architecture change should be evaluated as well.
It turns out that the issue is that a DB2 client cannot connect to a server version +/- 2 versions away. So upgrading from 6-8 is too much. What do you all think about putting the version 7 client on the server, and upgrading each database one at a time until they are all done, then putting the db2 8 client (or 9 at that point ) on the server?
Anyone had experience with this?
When should I do the Websphere migration during (or after) this?
What is Websphere 5.0 compatibility with DB2 version past; Can I use DB2 version 7 client to connect to a 6.1 database with Websphere 5?
Thanks all!
 
Kyle Brown
author
Posts: 3892
5
posted 20 years ago
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
    Send
  • Quote
  • Report post to moderator
The recommended migration path is to set up a SEPARATE set of machines running DB2 8 and WAS 5.0. Then you will find you can run both the WAS 3.5 plugin and the WAS 5.0 plugin on the same HTTP Server. So, you slowly move one application at a time to the new machine by removing the plugin entries from the WAS 3.5 plugin files and adding them to the WAS 5.0 plugin files.
Kyle

Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.

 
When all four tires fall off your canoe, how many tiny ads does it take to build a doghouse?
We need your help - Coderanch server fundraiser
https://coderanch.com/wiki/782867/Coderanch-server-fundraiser
reply
reply
    Bookmark Topic Watch Topic
  • New Topic
Boost this thread!
Similar Threads
More...