Our company is planning an upgrade to Windows Server 2003 from 2000. We are currently running Mercator 6.7. Has anyone had any experience running this version of Mercator on Windows Server 2003? What problems, if any, have you run into?
There were some issues (that is one reason we did not update the supported version list for 6.7), and since it is not supported, we did not go any further. If you run in an unsupported environment, and you see an issue, you will need to reproduce it in a supported environment before Support will engage.
The multi-process Event Server is a big reason to go to 7.5.1 BTW, if you do, request patch 60894.
BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!
Will there be issues with Mercator 6.7 if we upgrade to Windows 2003, other than it not being supported? OUr company is doing a company wide upgrade to Windows 2003, but are not upgrading Mercator.
We decided to move away from Mercator and re-write our applcication in java. This has accomplished several advantages;
1) More people on our team can now support the application; we only had two Mercator developers
2) We are not tied to a vendor package
3) Savings on licensing/maintenance costs
4) Java is more stable, in our opinion, than Mercator
5) Java is transportable
6) Java greatly simplifies the mapping process
That's sounds great, but our company is not that intuitive as yours.
So, the upgrade to Windows 2003 is coming soon....and we will still use Mercator 6.7. Will there be compatibility issues?? If so, what sort of problems can we expect? I need to know so we can take preventative messures!
We decided not to even attempt installing 6.7 on WIN2003 so I'm not sure, short of BocaBurger's previous replies to this thread, what would happen. Sorry I couldn't be of more help. Good luck.
Thanks jmlang22 - You started this thread, so you've been quite helpful aready.
Well, if ANYBODY else knows some issue that we can look forward to, please chime in! Becasue it looks like we are not going to upgrade Mercator when we get Windows 2003.
'jmlang22' Let us know how the rewrite goes. We review that option regularly but haven't been able to justify a going home grown based on complex data structures that have ever changing requirements.
'clk430' If you have a maint agreement you should be able to get the v8.0 upgrade at no cost for the applicaitons. You would need to expend some time and effort testing maps and systems. I've been testing 8.0 in my spare time to determine what our overall effort will be to upgrade. So far, it looks minimal. The real cost will come in looking at how we want to deploy systems and making sure that our mercator.ini setting will still work in the DSTX.ini file. We aren't doing much with XML with TX though so that should help too.
Thanks eyetry, you've been very helpful. Since all the lead developers left at once, we're all scrambling to figure out the details of our contract. But for now, I've made some noise and the powers that be are delaying the WIN 2003 upgrade in our area until we can either upgrade to 8.0 or get rid of EDI and just use the U.S post office.
We have had our re-write in production since 9/29 and everything is working great.
Basically we exchange XML files between systems via IBM MQ queues and then run the JAVA mapping application as Middleware on a UNIX box, mapping data from XML to an Oracle database. The application is set up as a deamon and runs automatically any time a message/xml file hits the inbound queue.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.