In terms of long term costs, it would seem more efficient to migrate to Webmethods and eliminate the dual support cost and dual support role. In terms of applicability of Webmethods vs. Mercator, I can't answer that part of the equation. But if you can do everything with Webmethods that you can do with Mercator with no loss of functionality, I would think that would be an appropriate way to go. My 2ยข.
Dave Records Records Consulting, LLC Phone: 616.583.0090 Email: [email protected] On May 24, 2011, at 10:58 AM, Steven Santillo wrote: > We have Webmethods, current version on a new machine. > AS2 functions, some simple XML maps. > > We have Mercator, unsupported version, on a very old server. > High volume, app to app, xml to idoc, etc, about 120 maps > > We could move all the Mercator functions over to Webmethods and re-map and > save cost by removing Mercator or upgrade Mercator(WTX). > > The goal is to reduce cost and get this middleware back to being supported. > > [Non-text portions of this message have been removed] ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
