New posts are disabled while we improve the user experience.
You can browse the site, or for urgent issues, raise a query at MyAccount.
Hi,
I want to implement RIC maintanance (ATS_INSERT_S and ATS_DELETE) for the ATS via EMA-OMMConsumer. In the past I have done this via RFA and everyting works fine. In EMA I tried this with posting a Refresh,- Update- or Status-Message with the FieldList as Payload. I also tried to post the Fieldlist directly as payload. In all cases I got "InvalidContent back by the AckMsg. Can somebody tell me the secrets to handle this in EMA! Thanks
There are articles about Implementing Elektron API applications to work with ATS.
The articles show how to use ATS_INSET_S and ATS_DELETE.
Sample Posting with Adding RIC and Fields
<POST domainType="MARKET_PRICE" streamId="1" containerType="MSG" flags="0x66 (HAS_POST_ID|HAS_MSG_KEY|POST_COMPLETE|ACK)" postId="1" postUserId="18" postUserAddr="10.42.61.200" dataSize="39">
<key flags="0x03 (HAS_SERVICE_ID|HAS_NAME)" serviceId="267" name="ATS_INSERT_S"/>
<dataBody>
<REFRESH domainType="MARKET_PRICE" streamId="0" containerType="FIELD_LIST" flags="0x00" groupId="0" State: Open/Ok/None - text: "" dataSize="23">
<dataBody>
<fieldList flags="0x08 (HAS_STANDARD_DATA)">
<fieldEntry fieldId="-1" data="4E45 572E 5249 43"/>
<fieldEntry fieldId="22" data="0F0C"/>
<fieldEntry fieldId="25" data="0F0F"/>
</fieldList>
</dataBody>
</REFRESH>
</dataBody>
</POST>
Deleting Fields
<POST domainType="MARKET_PRICE" streamId="1" containerType="MSG" flags="0x66 (HAS_POST_ID|HAS_MSG_KEY|POST_COMPLETE|ACK)" postId="4" postUserId="18" postUserAddr="10.42.61.200" dataSize="34">
<key flags="0x03 (HAS_SERVICE_ID|HAS_NAME)" serviceId="267" name="ATS_DELETE"/>
<dataBody>
<UPDATE domainType="MARKET_PRICE" streamId="0" containerType="FIELD_LIST" flags="0x00" updateType="0" dataSize="23">
<dataBody>
<fieldList flags="0x08 (HAS_STANDARD_DATA)">
<fieldEntry fieldId="-1" data="4E45 572E 5249 43"/>
<fieldEntry fieldId="13" data="0F01"/>
<fieldEntry fieldId="25" data="0F02"/>
</fieldList>
</dataBody>
</UPDATE>
</dataBody>
</POST>
Thanks! I compared the information from this articel with what I do and I saw that I'm not provide postUserId and postUserAdress. Defining a valid postUseradress will be easy, but who gives me the valid postUserID. This attribute i never needed before.
