Just a start. Look at it and let me know if I am thinking in the right
direction or not. I wrote it for just Input and it more looked like I am
repeating what we had in other documents. Let me know your thoughts on this=
.
I want to go over this over a call. So let me know if tomorrow 9:30 pm is
fine for you all so that we can start discussion over it.
Requirements IO Transactions
This document contains requirement specifications for three components of
the EBS, namely Input Transactions API, Output Transaction API and
Transaction Management Kit. All API are provided in Java
S. No.
Requirement
Description
1
Input Transaction API
1.1
Independent of Batch Framework
Should be able to be used as a separate module
1.2
Should be pluggable with Batch Framework
Should obey the Batch Framework rules and should be able to completely
integrate with Batch Framework
1.4
Input Reference Implementations to interact with various data formats.
Should provide input reference implementations to interact with different
kinds of data formats. Initial plan is to provide implementations for XML
Format Files, Flat files and RDBMS data formats.
1.5
A Common API to read from various data formats.
Should be able to provide common API implementation to interact with any
kind of data format like XML files, FLAT files or any kind of database like
Oracle, Sybase, etc.
On 2/5/06, Suresh Pragada <sur...@gm...> wrote:
>
> Hi Sridhar & Balu,
> Do you guys have started anything on the detailed requirements of IO API=
,
> Implemenation and Transaction Services? Please share those requirements i=
n
> this mailing list.
> Thank you,
> Suresh.
>
--
Sridhar Kalaga
408 368 0848
|
