I agree and I raised that issue, but it was decided before it reached my desk that it will be ETL. Seems so 90's :)
Not sure why.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Richard Schoen
Sent: Monday, June 11, 2012 12:06 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: data Extract, Transform, Load (ETL) on Iseries
Why replicate at all ?
Use the iSeries data realtime from .Net.
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------
message: 9
date: Mon, 11 Jun 2012 15:35:05 +0000
from: "Stone, Joel" <Joel.Stone@xxxxxxxxxx>
subject: data Extract, Transform, Load (ETL) on Iseries
New project requires ETL to copy Iseries data to .NET for www inquiries.
Can be daily updates (no requirement for real time).
Can anyone suggest how to handle this?
I have to get changed data to Biztalk, and also have the option for a complete refresh.
There will be data manipulation, for example joining to other files, discarding unnecessary fields, etc.
What is a good method?
* DB triggers?
* Journal data, restore to PF, build recs to Biztalk
* Any shareware that works on Iseries?
* Can Mimix help? Or is that more for replication only (no filtering, no field drops, etc)
* Any other methods I should look at?
Thanks!
______________________________________________________________________
This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
For more information please visit
http://www.symanteccloud.com
______________________________________________________________________
------------------------------
As an Amazon Associate we earn from qualifying purchases.