webMethods is our corp standard. Our company has recently embarked on bunch of EAI (behind-the-firewall type) projects. These applications belong to different functional areas and appropriate data will be exchanged between these applications. I understand that webMethods recently announced v6.x which contains enhancements (inclusion of JBOSS app server, support for WebSvcs, enhanced business process monitoring etc) over the existing v4.6. Because of immediate project timelines & stability issues, one functional area is leaning towards using webMethods version 4.6 (although there is a plan to move to version 6.x by next year or so). The other functional area (which has a bit relaxed deadlines) will use webMethods version 6.x.
Since I’m not familiar with intricacies between the two versions, I’m hoping if anyone can shed a light on potential issues (wm 4.6 application talking to wm 6.x, potential dangers (if any) in not taking advantage of enhanced features of wm6.x, migration issues, migration costs, stability issues, etc) that we might get into and whether there’re any best practices.
Any response is appreciated.
#webMethods#Integration-Server-and-ESB#webMethods-General