Win a copy of Learn Java with Math: Using Fun Projects and Games this week in the Beginning Java forum!
  • 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Junilu Lacar
  • Martin Vashko
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Scott Selikoff
  • salvin francis
  • Piet Souris

Migration from WAS 3.02 to WAS 4.02

 
Ranch Hand
Posts: 71
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you Kyle Brown!

Just in case it might help somebody else, I am including in this post a private response that I received from Kyle Brown on a WAS 4.0 question.
Thanks again,
... the question and the answer ...

Kyle,
My comany is migrating from a WAS 3.02 platform to WAS 4.02 platform running on AS/400. I am a developer tasked with writing a White Paper on the migration process for our current applications and the need for VAJ4 (or, WASD, or both).
After reading all of your most impressive writings in ibm.com articles, EnterpriseJavaProgramming with IBM WebSphere, and posts here at JavaRanch, I have much respect for your opinion.
Please answer a question:
The application that we are trying to migrate uses a single servlet and a few JSPs. Should we expect any problems? Does the WAS 4.0 platform require WAR files and EAR files only?
The ibm articles about WAS 4 migration all convey ease of migration.
Thanks for any help (ie, any sources to research, etc.)
--------------------
Tom Hennigan
Sun Certified Java 2 Platform Programmer

--------------------------------------------------------------------------------
Posts: 58 | Registered: Feb 2001

Kyle Brown
bartender
Member # 18625 posted March 15, 2002 05:30 AM
--------------------------------------------------------------------------------
Tom, you shouldn't experience too many problems. The main things to look out for are:
(1) Yes, WebSphere requires WAR files -- however, you can build those from your servlet and JSP files using the AAT without much trouble.
(2) You will have to make sure you've updated your JSP's from JSP 0.91 to 1.0 in the process, if you have not already done so.
(3) Be aware that some Servlet API's have been deprecated. Pay special attention to compiler warnings when you recompile your servlet.
Kyle
--------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
See my homepage at http://members.aol.com/kgb1001001 for other WebSphere information.

--------------------------------------------------------------------------------
 
Ranch Hand
Posts: 79
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Well as usual Kyle has been precise, accurate and brilliant in his replies. I have been involved in migrating a banking application from WAS3.5 to WAS4.0.2 and for coding changes we have used WSAD.
One thing I am very curious to know and will like Kyle to answer that is why has IBM moved from VAJ to WSAD. I mean VAJ is a great IDE tool and people have been working in it for a long time so there are skills available in the market for VAJ but WSAD is a new thing and one has to explore from the start. Although both VAJ and WSAD have their own advantages and disavantages but IBM could have introduced all the features of WSAD in VAJ also. Is this a marketing strategy?
 
Tom Hennigan
Ranch Hand
Posts: 71
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
A short answer to why WSAD is successor to VAJ is that WSAD is an open-source IDE (ie Eclipse component donated to open source community back in Nov 2001) versus VAJ strictly proprietary.
I think that the need to support Web services might have driven the change in stance by IBM. The new open-source approach allows third-party tool-maker add-in in a much more useful manner.
What issues required WSAD versus VAJ in your migration efforts? How did you handle versioning and source control with WSAD?
[ March 18, 2002: Message edited by: Tom Hennigan ]
 
Balbir Singh
Ranch Hand
Posts: 79
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Tom,
Thanks for the reply. Actually moving from VAJ to WSAD hasnt been so difficult as once we supposed to be coz of the unstable behaviour of WSAD. The only place in our application which required coding changes was EJB's i.e. from 1.0 to 1.1 (mainly the change from RemoteException to EJBException and return type of ejbCreate in CMP's)
We have used CVS for Versioning and Source Control with WSAD (theres a team prospective specifically built for this purpsose).
 
Tom Hennigan
Ranch Hand
Posts: 71
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for the reply Balbir!
 
Doody calls. I would really rather that it didn't. Comfort me wise and sterile tiny ad:
Sauce Labs - World's Largest Continuous Testing Cloud for Websites and Mobile Apps
https://coderanch.com/t/722574/Sauce-Labs-World-Largest-Continuous
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!