User Define tags

, ,
1

Imported from previous forum

2

Hello, I been looking around the FIX protocol and one thing I don’t understand after reading the documents posted around this site is this. You can define your own tags, UDT, rigth. How do you tell your partner’s FIX engine what new tags you are using?

It should according to me be rather simple like you send over a XML file that defines the tags you use and they can just give it to the engine or something simular. But I havn’t found anything about this.

Do you mean to tell me you havn’t agreed on a stantard way to tell a FIX engine new UDT?

Lars

3

Hi Lars,

Typically counter parties exchange a “rules of engagement” document where they define their UDTs along with usage and examples. There is no standard for defining UDTs in a fix engine. As a result, each engine has its own implementation. This disallows the idea of having a single file that you can send to counterparties that would allow them to automatically load them. However, if both counter parties use the same engine and that engine supports loading tags from a file then you may certainly do so.

Jimmy Noriega
TransactTools

Hello, I been looking around the FIX protocol and one thing I don’t
understand after reading the documents posted around this site is this.
You can define your own tags, UDT, rigth. How do you tell your partner’s
FIX engine what new tags you are using?

It should according to me be rather simple like you send over a XML file
that defines the tags you use and they can just give it to the engine or
something simular. But I havn’t found anything about this.

Do you mean to tell me you havn’t agreed on a stantard way to tell a FIX
engine new UDT?

Lars

4

Ok, thx for the information.

Isn’t this something that should be looked at? Why not make a standard way for FIX engine to read UDT so it’s only to send over a XML(or similar) file to the other’s engine? Then how it’s later interpreted by the OMS might be a whole other page but that’s not important for the engine is it?

Lars

Hi Lars,

Typically counter parties exchange a “rules of engagement” document
where they define their UDTs along with usage and examples. There is no
standard for defining UDTs in a fix engine. As a result, each engine has
its own implementation. This disallows the idea of having a single file
that you can send to counterparties that would allow them to
automatically load them. However, if both counter parties use the same
engine and that engine supports loading tags from a file then you may
certainly do so.

Jimmy Noriega TransactTools

Hello, I been looking around the FIX protocol and one thing I don’t
understand after reading the documents posted around this site is
this. You can define your own tags, UDT, rigth. How do you tell your
partner’s FIX engine what new tags you are using?

It should according to me be rather simple like you send over a XML
file that defines the tags you use and they can just give it to the
engine or something simular. But I havn’t found anything about this.

Do you mean to tell me you havn’t agreed on a stantard way to tell a
FIX engine new UDT?

Lars

5

As of FIX 4.4 there is no standard way of loading UDTs but that doesn’t mean there is no development being done around these sorts of issues. As the Fix continues to grow, working groups continue the development of the protocol. If you are interested take a look in http://www.fixprotocol.org/working_groups/ for the Repository Working Group.

Ok, thx for the information.

Isn’t this something that should be looked at? Why not make a standard
way for FIX engine to read UDT so it’s only to send over a XML(or
similar) file to the other’s engine? Then how it’s later interpreted by
the OMS might be a whole other page but that’s not important for the
engine is it?

Lars

6

[ original email was from G.Vijay Kumar - evervj.extras@gmail.com ]
Actually user define tags are specific between two fixengines and currently there is no specific api to share between other fix engines or it is shared manually by adding custom tags in their configuration manually.

Actually fix has to consider this because this is very important feature to share the user defined tags between fix engines using some kind of Fix Tags handshake apis and this could be a part of fix session.

lets see …

As of FIX 4.4 there is no standard way of loading UDTs but that doesn’t mean there is no development being done around these sorts of issues. As the Fix continues to grow, working groups continue the development of the protocol. If you are interested take a look in http://www.fixprotocol.org/working_groups/ for the Repository Working Group.

Ok, thx for the information.

Isn’t this something that should be looked at? Why not make a standard
way for FIX engine to read UDT so it’s only to send over a XML(or
similar) file to the other’s engine? Then how it’s later interpreted
by the OMS might be a whole other page but that’s not important for
the engine is it?

Lars