Option 2.
Directly updating a partner’s database has many risks. There are software compatibility issues, and exposure to service interruptions due to changes on your end or theirs. If your limited-capability partner accidently forgets some security constraints, you don’t want to be responsible for possibly screwing up some of their important data.
It’s been a while since I looked into it, but JDBC network traffic used to be “chatty” in small bursts. This caused performance issues over slow links or over long distances with significant network latency.
I think that using a flat file will make your life a lot easier in the long run. webMethods provides some pretty good tools for making this relatively painless.
#Integration-Server-and-ESB#webMethods#webMethods-Architecture#webMethods-General