Win a copy of Programmer's Guide to Java SE 8 Oracle Certified Associate (OCA) this week in the OCAJP forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Migrating from Axis to WebSphere stack

 
Greg T Robertson
Ranch Hand
Posts: 91
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Just wondering if anyone has any experience with moving a service from the Axis stack to run on the WebSphere stack. Any thoughts on the differences between the two (config etc).
 
Rr Kumaran
Ranch Hand
Posts: 548
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
can u be more specific on what you are looking for ?

are u asking how to use Apache AXIS inside WebSphere rather than relying on WebSphere-AXIS version like IBM web services toolkit provides ?
 
Greg T Robertson
Ranch Hand
Posts: 91
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Actually I currently have a web service that is running on the Axis stack and was developed under WAS4. Now that we are moving to WAS5 - we'd like to know how much work is going to be involved with migrating our web service to run on top of the WebSphere stack and removing the Axis stack.
 
JeanLouis Marechaux
Ranch Hand
Posts: 906
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is it a service provider you want to move from Axis to WAS 5 or a service consumer ??
 
Greg T Robertson
Ranch Hand
Posts: 91
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
both consumer & producer
 
JeanLouis Marechaux
Ranch Hand
Posts: 906
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Well, of course I have no idea of your application nor your services but...

I thing migrating the service provider to the WAS 5 (JAX-RPC) stack is not really difficult. You just have to republish your class as a service using the new APIs. With a tool like WSAD, it's quite easy.

As far as the service consumer is concerned, it will certainely be a bit more difficult. You must have a lot of axis packages here and there in your code and you will have to replace them with the JAX-RPC equivalent. This could be a little bit more touchy, depending on the kind of consumer you had developped before.

But according to me, the most difficult part of the "migration" is not related to tools (Axis vs WAS), but to design issues. If you had developped a software with WAS 4, then you were probably not WS-I compliant (because the ws-i basic profile did not exist in these old times)
Upgrading to WAS 5 is certainly the opportunity to solve these compliance issues. This can be the most touchy part as it can involve design changes. (web services, datatypes, etc...)
 
Rr Kumaran
Ranch Hand
Posts: 548
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
>>run on top of the WebSphere stack and removing the Axis stack.

does this mean that you want to replace your AXIS(not websphere provided using WebSphere web services Development Kit) based web services on WAS 4.0 with websphere provided version of AXIS on WAS 5.0 ... if so then there are lot of incompatibility issues w.r.t schema, wsdl, custom types support and to adhere to Basic Profile 1.0 you need to develop interopable web services which I guess WebSphere web services kit is successfull to some extent but not completely . please correct me if my understanding is wrong .
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic