|
I can second that. MQ Series is great stuff. It's a separate product and costs extra (not part of the OS), but it's not too expensive. On 1/17/07, pnelson@xxxxxxxxxx <pnelson@xxxxxxxxxx> wrote:
Have you looked into MQ Series? -- Paul Nelson Arbor Solutions, Inc. 708-670-6978 Cell pnelson@xxxxxxxxxx Dave Murvin <davem@xxxxxxxx> Sent by: midrange-l-bounces+pnelson=arbsol.com@xxxxxxxxxxxx 01/16/2007 11:57 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Subject Recommendations on 550 to 520 communications Hello, I have been asked to do some preliminary research on the best methods to communicate between two iSeries machines. The situation is as follows: The 550 is a large zero interactive machine running Lawson M3 ERP software (was Intentia) written in Java with Websphere running in a separate partition. The other machine is a 520 Express green screen machine running EDI and the Varsity Shipping package (RPGLE), it will also be used for development. The EDI package will be communicating both ways to the ERP package through possibly a Lawson interface of some sort (we don't know the details yet) or just mapping to some specific file layouts on the 550. The Varsity shipping package will be doing all the shipping calculations for customer orders, but will also need to work both ways with the ERP package. Both machines are in the same equipment rack. What do you recommend for communications and why? DDM files over IP? Java calling RPGLE programs? How would we do this between machines? RPGLE calling Java programs? Again, how would we do this between machines? How do the systems know about each other? Is there some magic red book or other manual that would be helpful? What works and what doesn't? We also plan to talk to the Lawson people, but would like some independent ideas too. Thanks for your suggestions. Dave Murvin DRM Enterprises, Inc. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.