|
General Q/A
< Previous Next >
Re: FIX to Any format - Use cases
ophir chen / informatica
2 Sep 2007 1:57AM ETHi,
Thanks again for your help.
I totally understand the concept your point there, and as I said my only interest is in the "need" which is as you said the motivation for the business requirement.
From what I could gather till now I think I can identify two scenarios:
1) Back office that needs to feed a TLM (transaction lifecycle management) system with the FIX trades, needs to convert the FIX messages to TLM's format.
2) From your pointer in the next message, I get that in some cases the OMS system needs to be able to "talk" FIX therefore if the ability doesn't exist naturally it has to be developed.
I read the thread you were pointing me to, regarding the COBOL <-> FIX requirement, this is exactly what I'm looking for although what I need to understand is why or in which scenario, COBOL and FIX needs to interact.
If you are familiar with other cases like this I'll be happy to know about them, if you know the answer for my real question there or can point me to someone who can answer it I'll be very happy. :-)
Thanks
Ophir
> I could not get the "need" factor in your question. I am a programmer
> and hence the "need" comes from business. Recursively for them the need
> to convert between FIX and a non-FIX format comes from their need to use
> different software (some may be legacy) and these softwares are not by
> design directly interoperable, So I as programmer "glue" these
> software(s) together - Enterprise Application Integration (EAI).
>
> When I say "the need comes from business" - I mean the business tells
> technology "integrate x with y". For example :- the business already is
> using an accounting system and a trading system, but these are currently
> not integrated - data transfer between them is manual. Now with the idea
> of streamlining operations an EAI project starts to integrate the
> accounting and trading system. This is the need.
>
> I as technology may have alternatives like "build an inhouse product z
> which is x + y + whatever else you need", but the business would not
> prefer this if the cost difference between building z is large
> compared to integrating x <-> y. Another alternative may be "find a
> product z2 = x + y" and procure and migrate. Again similar criteria
> may rule it out :-(
>
> > Hi,
> >
> > Thanks for your reply, Are you familiar with the business case behind
> > the need to convert between COBOL and Fix messages? Who has this
> > problem? Any other cases like this one that you know of?
> >
> > Thanks a lot for your help.
> >
> >
> >
> >
> >
> > > Refer
> > >
> > > http://fixprotocol.org/discuss/read/0c88025f
> > >
> > > where there is an example of "FIXML DTD to Cobol record". Please
> > > feel free to post any questions you have.
> > >
> > > Regards,
> > > K. Mahesh
> > >
> > > > Hi,
> > > >
> > > >
> > > >
> > > > My name is Ophir Chen, and I'm currently doing my first steps in
> > > > the FIX world.
> > > >
> > > > I'm trying to answer a simple question:
> > > >
> > > > What are the use cases where there is a need to convert to/from
> > > > FIX and any other format or take FIX into non FIX system?
> > > >
> > > >
> > > >
> > > > One example I could think of :
> > > >
> > > > Back office that needs to load to TLM system all FIX transaction
> > > > and therefore needs to convert FIX messages to TLM format (can be
> > > > CSV, DB, XML etc.)
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > I would appreciate a lot any kind of help.
> > > >
> > > > Thanks for your time.
> > > >
> > > >
> > > >
> > > > -----------------
> > > > Ophir Chen
> > > >
> > > > Sales consultant, Complex Data Exchange
> > > >
> > > > Email: ochen@informatica.com
Re: FIX to Any format - Use cases
ophir chen / informatica 2 Sep 2007 1:57AM ET
|
