How extensive is the data warehouse "refresh"? If it's not extensive, you
might think about journaling the file and sending the journal to the other
system for updating. Another idea might be to take a look at the Mimix DR1
product. It is simple to set up and administer, and allows easy definition
of those things you want to have replicated to the other system.
Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Roy Luce
Sent: Saturday, August 04, 2007 2:17 PM
To: midrange-l@xxxxxxxxxxxx
Subject: iSeries connectivity
To All:
A major client has 3 iSeries servers, 1 in the US, 1 in Canada and 1 in
Sweden; all these servers are on the same private network.
Each of these servers runs major enterprise applications - ERP, CRM, etc.
The Swedish server runs multiple environments of one of these application
systems. Data is currently exchanged between the applications using FTP and
EDI protocols
The client is interested in pulling data from all the application systems'
databases into a consolidated data warehouse and has determined the current
FTP and EDI approach is too cumbersome for the intended use of the data
warehouse.
I've been told that one solution is to establish TCP/IP connections from the
server hosting the data warehouse to the other two machines then create a
logical file on the host server for the target files needed on the 2 remote
systems. The target files would be referenced by their server's ip address,
their resident library and file name.
My questions:
1. is establishing TCP/IP connections a difficult, time consuming
proposition?
2. do I have the process defined correctly
3. Are there better ways to do this?
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.