filebc is a jbi (jsr208) binding component, it is devised to help a
"message" flow in/out of ESB centered system(s), for filebc, the binding
'protocol' is file, so:
externally (among systems), the "message" flows through file system,
e.g. system 'A' write a file to path 'P' and system 'B' pick it up at
the path 'P'
internally (within a system), the "message" flows on the ESB bus (MxN
mix-match between BCs and SEs)
the unit of processing (routing) is the 'message', what makes up a
"message" depends on the application, e.g. a purchase order, a
prescription record for a patient, a medical provider's profile, etc.
in case of filebc, the "message" is persisted and transfered as file
system files, it can be one record per file or multiple-records per
file, the record can be delimited or fixed length enveloped.
most time, one record per file works fine, if it is needed to pack
multiple records into a physical file, then properly grouping (divide
into groups) the records into separate files are recommended...
the minimum unit of processing of filebc is "record" as described above,
if I found myself have to deal a record of 1GB, then I might want to
review by application design...
HTH
regards
Jim
hrishi09 wrote:
> Hi all,
> I want to know how File BC handles multiple files.
> Is it beneficial to have a single file with large no of records or multiple
> files with less records.
> I mean what would be efficient
> 1. Processing 1 file with 1 lakh records or
> 2. 10 files with 10000 records
> It would be great if someone can can tell me pros and cons of above
> strategies.
> Thanks,
> Hrishi
>
---------------------------------------------------------------------
To unsubscribe, e-mail:
[hidden email]
For additional commands, e-mail:
[hidden email]
