|
At 04:06 AM 1/17/2007, Michael Ryan wrote:
What are you going to do with the data? Execute a program? In other words, do you want to send some data and then have something happen? I might recommend data queues for this. Easy to set up, free, pretty darn reliable. Have a program at each end that processes queue entries and does stuff with the data.
I think the EDI process on the 520 will just map data to a Lawson file format for incoming EDI orders, which I "assume" will be on the 550. Not sure yet what the process will be for outgoing EDI conformations - Information would have to come from the 550 somehow. I should know more details in the not too distant future.
Varsity shipping package on 520 will need to receive the carton information (weight, size, send to address, etc.) from the 550 and return the shipping charge to the 550 for the customer order.
DDM is always a possibility. Then you're writing/reading a file. Is it important to keep the data on the other system? If not, I probably wouldn't use DDM files.
The rules are "no package modifications", so that was why I was thinking DDM. Lawson package runs on the 550 and the Varsity Shipping package and EDI run on the 520.
At 06:26 AM 1/17/2007, pnelson wrote: Have you looked into MQ Series?They do not want to purchase any more software, but I will include this in my recommendations.
At 07:42 AM 1/17/2007, Chris Bipes wrote: I would use imbedded SQL to perform the data inquiries to the remote system and call the interface programs to the packaged software for updates. I would not directly manipulate the files for update or us any interface that would be effected by packaged updates to the application software.Good idea. We certainly don't want to take the chance of confusing the packaged software.
Thanks to all for the suggestions. I may have additional questions as the project progresses and we learn more on our side. Both the 550 and the 520 were just installed this week and the Lawson software gets loaded onto the 550 next week.
Dave Murvin DRM Enterprises, Inc.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.