You said they are replicating the application. Does that mean they intend
to replicate the database, or just the application? You already have the
database setup. Just have the .net application read your files, The data
is then real time.
If the programming language is still up for debate. It is not hard to
create display only web applications using RPG, EGL or PHP that runs
natively on the I-series.
Our .NET developers that use I-series data read our files, we do not
replicate them to another server. The only replication I can think of is
the data warehouse reading files from many different systems.
"Stone, Joel" <Joel.Stone@xxxxxxxxxx>
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>,
10/05/2012 09:26 AM
replicating an I-series home-grown application to a .net platform
My company is replicating our I-series home-grown application to a .net
platform for read-only. This .net app will provide customers with a
typical web-based myAccount view as seen on many websites.
I have two questions for this forum:
1) For the read-only mirrored version on .net, does it make sense to
have referential integrity (RI) constraints on file relationships? Either
from a purist database design standpoint or from a common business rules
standpoint? It seems to me that one HAS to assume that the source app has
R-I that is intact, and it seems to be asking for trouble and headaches to
try to enforce RI on a mirrored system that is read-only. This will
require file loads and updates in a certain sequence, which could be
2) Do other companies try to replicate an app onto another platform
in almost real-time? It seems that it would be SOoooo much simpler to
read the Iseries DB directly. Is this replication a common practice
today? Or is it more suited to the 1990's?
This outbound email has been scanned for all viruses by the MessageLabs
For more information please visit http://www.symanteccloud.com