Re: OpenMAMA and Enterprise Mama

Glenn McClements <g.mcclements@...>

Issues around the entitlements were brought up on the OpenMAMA Steering Committee call yesterday, so we’ll be discussing it in the next Technical Committee meeting and get a plan together. 


From: Gary Molloy <g.molloy@...>
Date: Friday, 16 January 2015 11:26
To: "Alpert, Reed" <reed.alpert@...>, "openmama-dev@..." <openmama-dev@...>
Subject: Re: [Openmama-dev] OpenMAMA and Enterprise Mama

Hi Reed,


Thanks for your email, sorry for the delay in reply. 


I think you have touched upon 2 items here:

1.       When /are there any plans for Enterprise MAMA and OpenMAMA to come into sync?

2.       Is it possible for have multiple entitlements bridges?


To answer your first question. 

We have made a concerted effort over the last 6 months to bring these into sync and have made substantial progress with this.

With the latest release of OpenMAMA Enterprise Edition, 6.0.3f, there are very few differences with the current OpenMAMA RC 2.3.2 rc1 and we will continue to keep these in line going forwarded with regular synced up releases.


To answer your second question, MAMA is currently only built to handle 1 set of entitlements. 

If we were to extend this to cover 3 (or more) bridges we would need to consider a few things:

·         We would need to be able to tie entitlements with a particular topic or source (most likely the source?) – currently we only have 1 set of global entitlements options so the properties would need extended (or re-thought).

·         Would every source have to have entitlements enabled?  How can we enforce entitlements for 1 bridge and not another?

·         We need to be careful in this area for compliance reasons.

·         Seems like we would need the entitlement bridging first, and then the ability to specify entitlement bridges for a source.






Gary Molloy – SR Labs

Adelaide Exchange | 24-26 Adelaide Street | Belfast | BT2 8GD



From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Alpert, Reed
Sent: 15 December 2014 21:21
To: openmama-dev@...
Subject: [Openmama-dev] OpenMAMA and Enterprise Mama




What is the plan for OM and EM?

The entitlements in EM are not available in OM, and it looks like turning on entitlements in mama layer is for all of the loaded bridges.

Are patches to OM made available in EM (and vice-versa) – how long does the dev cycle take for that?


Our concern is that we run 3 bridges : wombat, tick42/rmds, and solace.

For entitlements we use dart for wombat (our DF5/6/mamacache env), and dacs for tick42/rmds and solace.

We’d like to run OM for all of this (or EM if that is the best way to go).






Reed Alpert | Corporate & Investment Bank | Market Data Services | J.P. Morgan | 4 Metrotech Center, 23rd Floor, Brooklyn, NY 11245 | T: 718.242.5198  | M: 917.414.4613 | reed.alpert@...


Alternate Contact:  CIB PIM Trading Technology Solutions NA | CIB_PIM_Trading_Technology_Solutions_NA@...


This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to for disclosures relating to European legal entities.

Join to automatically receive all group messages.