Re: Options for Data Update Between iSeries and MS SQL Server

I built a process to do this and used JDBC for my transport.  You don't 
have direct access, so you are down to a serialized approach.  Easiest and 
cheapest route would be to build a delimited file (or XML) and use ftp to 
move the file to their server and run a stored procedure to import the 
data.  The opcode idea is a good one, you'll only have to transmit the 
changes. 

Mark

message: 8
date: Fri, 29 Sep 2006 10:55:50 -0500
from: Scott Johnson <sjohnson@xxxxxxxxxxxxxxx>
subject: Options for Data Update Between iSeries and MS SQL Server

Background:
MyCompany surveys data. This data is formatted and sold to its clients 
(B2B).  NewCompany will use data from MyCompany to sell to its customers 

on 

a website (B2C).  NewCompany will be using MS SQL Server for its DB. 
Website will be using Java.  The general idea is to get the data updated 

to 

their DB server shortly after the data is updated for MyCompany.

My question is:
What are the options for getting this data from MyCompany to NewCompany?

We do not want to do a complete rebuild of the tables on a schedule. 

Direct 

update of their tables is out.  We are thinking it has to be at the 
record/row level with information on if the record was an add, change, 

or 

delete. It would be nice to have some sort of guarantee of 'delivery' of 

the data. The options we have come up with so far are DataQueues, 

MQSeries, 

JMS, & Mule (mule.codehaus.org).  I am trying to see if there are any 

other 

options.

Thanks,
    Scott