Openmama-users@lists.openmama.org

Re: NO_BRIDGE_IMPL() issue (avis is compiled/linked properly)

Glenn McClements <gmcclements@...>

#94

Hi Gigan,
This looks like the avis bridge lib isn't in being loaded for some reason
(FYI bridge libraries are dynamical *loaded* using dlopen() not
dynamically linked). Is the bridge library and the AVIS in your
DYLD_LIBRARY_PATH? Also putting mamalistenc in full verbose mode may give
more info, i.e:

./mamalistenc -m avis -v -v -v -v

As you said, OSX isn't currently supported but I do know of some people
who have tried in the past and did manage to get something up and running.

Did you make any other changes to get it building on OSX? If so, and
provided other platforms aren't affected of course, then I'd be happy to
apply them. I can't see NYSE ever supporting this in their commercial
distribution as there isn't a demand for it with their customers, but for
the open source project additional platform support can only be a good
thing.

Glenn


On 29/11/2012 17:13, "Gagan Sidhu" <gagan@...> wrote:

Hi guys,

Currently I'm on OSX and trying to build the openMAMA libs for my system.

I understand that OSX is not officially supported, but the issue I'm
experiencing is not specific to this platform.

Specifically, I build and install the avis client, copy the config_h to
the suggested directories, and proceed to build mama.

The build and linking goes fine, from what I can see, however the example
programs do *not* work.

I have compiled each one using a slightly modified Makefile.sample (no
-lrt flag or -Xlinker before the -Bstatic/-Bdynamic).

This issue is very strange, because I saw someone else had a bridge issue
but the linked library spit out an error. All I see is:

here's the dump:

GagansMacPro:c Gagan$ make -f Makefile.sample
gcc  -I/opt/openmama/include -dynamic -L/opt/openmama/lib  -o
mamapublisherc mamapublisherc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic
-lpthread -lm -ldl
gcc  -I/opt/openmama/include  -c -o mamasubscriberc.o mamasubscriberc.c
mamasubscriberc.c: In function ŒwildCardMsgCb¹:
mamasubscriberc.c:280:56: warning: cast to pointer from integer of
different size [-Wint-to-pointer-cast]
mamasubscriberc.c:285:13: warning: cast from pointer to integer of
different size [-Wpointer-to-int-cast]
gcc  -I/opt/openmama/include -dynamic -L/opt/openmama/lib  -o
mamasubscriberc mamasubscriberc.o -Bstatic -lmamaavisimpl -lmama
-Bdynamic  -lpthread -lm -ldl
gcc  -I/opt/openmama/include  -c -o mamasymbollistsubscriberc.o
mamasymbollistsubscriberc.c
g++  -I/opt/openmama/include -dynamic -L/opt/openmama/lib  -o
mamasymbollistsubscriberc mamasymbollistsubscriberc.o -Bstatic
-lmamaavisimpl -lmama -Bdynamic  -lpthread -lm -ldl
gcc  -I/opt/openmama/include  -c -o mamaproxyc.o mamaproxyc.c
mamaproxyc.c: In function ŒsubscribeToSymbols¹:
mamaproxyc.c:230:34: warning: cast to pointer from integer of different
size [-Wint-to-pointer-cast]
mamaproxyc.c: In function ŒsubscriptionHandlerOnNewRequestCb¹:
mamaproxyc.c:354:62: warning: cast to pointer from integer of different
size [-Wint-to-pointer-cast]
mamaproxyc.c: In function ŒsubscriptionHandlerOnRequestCb¹:
mamaproxyc.c:422:26: warning: cast from pointer to integer of different
size [-Wpointer-to-int-cast]
mamaproxyc.c:435:26: warning: cast from pointer to integer of different
size [-Wpointer-to-int-cast]
g++  -I/opt/openmama/include -dynamic -L/opt/openmama/lib  -o
mamaproxyc mamaproxyc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic
-lpthread -lm -ldl
gcc  -I/opt/openmama/include  -c -o mamaio.o mamaio.c
g++  -I/opt/openmama/include -dynamic -L/opt/openmama/lib  -o mamaio
mamaio.o -Bstatic -lmamaavisimpl -lmama -Bdynamic  -lpthread -lm -ldl
gcc  -I/opt/openmama/include  -c -o mamamultisubscriberc.o
mamamultisubscriberc.c
g++  -I/opt/openmama/include -dynamic -L/opt/openmama/lib  -o
mamamultisubscriberc mamamultisubscriberc.o -Bstatic -lmamaavisimpl
-lmama -Bdynamic  -lpthread -lm -ldl
gcc  -I/opt/openmama/include  -c -o mamaftmemberc.o mamaftmemberc.c
g++  -I/opt/openmama/include -dynamic -L/opt/openmama/lib  -o
mamaftmemberc mamaftmemberc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic
-lpthread -lm -ldl
GagansMacPro:c Gagan$ ./mamalistenc
Enter one symbol per line and terminate with a .
Symbol> ,
Symbol> .
Could not open MAMA wmw bridge.
GagansMacPro:c Gagan$ ./mamalistenc -m avis
Enter one symbol per line and terminate with a .
Symbol> .
Could not open MAMA avis bridge.Thanks,
Gagan Sidhu,
Director, General Analytics (GA) Inc.

_______________________________________________
Openmama-users mailing list
Openmama-users@...
https://lists.openmama.org/mailman/listinfo/openmama-users
________________________________

Please consider the environment before printing this e-mail.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error, please advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

NO_BRIDGE_IMPL() issue (avis is compiled/linked properly)

Gagan Sidhu <gagan@...>

#93

Hi guys,

Currently I'm on OSX and trying to build the openMAMA libs for my system.

I understand that OSX is not officially supported, but the issue I'm experiencing is not specific to this platform.

Specifically, I build and install the avis client, copy the config_h to the suggested directories, and proceed to build mama.

The build and linking goes fine, from what I can see, however the example programs do *not* work.

I have compiled each one using a slightly modified Makefile.sample (no -lrt flag or -Xlinker before the -Bstatic/-Bdynamic).

This issue is very strange, because I saw someone else had a bridge issue but the linked library spit out an error. All I see is:

here's the dump:

GagansMacPro:c Gagan$ make -f Makefile.sample
gcc  -I/opt/openmama/include -dynamic -L/opt/openmama/lib  -o mamapublisherc mamapublisherc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic  -lpthread -lm -ldl 
gcc  -I/opt/openmama/include  -c -o mamasubscriberc.o mamasubscriberc.c
mamasubscriberc.c: In function ‘wildCardMsgCb’:
mamasubscriberc.c:280:56: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
mamasubscriberc.c:285:13: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
gcc  -I/opt/openmama/include -dynamic -L/opt/openmama/lib  -o mamasubscriberc mamasubscriberc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic  -lpthread -lm -ldl 
gcc  -I/opt/openmama/include  -c -o mamasymbollistsubscriberc.o mamasymbollistsubscriberc.c
g++  -I/opt/openmama/include -dynamic -L/opt/openmama/lib  -o mamasymbollistsubscriberc mamasymbollistsubscriberc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic  -lpthread -lm -ldl 
gcc  -I/opt/openmama/include  -c -o mamaproxyc.o mamaproxyc.c
mamaproxyc.c: In function ‘subscribeToSymbols’:
mamaproxyc.c:230:34: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
mamaproxyc.c: In function ‘subscriptionHandlerOnNewRequestCb’:
mamaproxyc.c:354:62: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
mamaproxyc.c: In function ‘subscriptionHandlerOnRequestCb’:
mamaproxyc.c:422:26: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
mamaproxyc.c:435:26: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
g++  -I/opt/openmama/include -dynamic -L/opt/openmama/lib  -o mamaproxyc mamaproxyc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic  -lpthread -lm -ldl 
gcc  -I/opt/openmama/include  -c -o mamaio.o mamaio.c
g++  -I/opt/openmama/include -dynamic -L/opt/openmama/lib  -o mamaio mamaio.o -Bstatic -lmamaavisimpl -lmama -Bdynamic  -lpthread -lm -ldl 
gcc  -I/opt/openmama/include  -c -o mamamultisubscriberc.o mamamultisubscriberc.c
g++  -I/opt/openmama/include -dynamic -L/opt/openmama/lib  -o mamamultisubscriberc mamamultisubscriberc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic  -lpthread -lm -ldl 
gcc  -I/opt/openmama/include  -c -o mamaftmemberc.o mamaftmemberc.c
g++  -I/opt/openmama/include -dynamic -L/opt/openmama/lib  -o mamaftmemberc mamaftmemberc.o -Bstatic -lmamaavisimpl -lmama -Bdynamic  -lpthread -lm -ldl 
GagansMacPro:c Gagan$ ./mamalistenc 
Enter one symbol per line and terminate with a .
Symbol> ,
Symbol> .
Could not open MAMA wmw bridge.
GagansMacPro:c Gagan$ ./mamalistenc -m avis
Enter one symbol per line and terminate with a .
Symbol> .
Could not open MAMA avis bridge.Thanks,
Gagan Sidhu,
Director, General Analytics (GA) Inc.

Re: mamaMsg_createForWombatMsg

Stuart Beattie <SBeattie@...>

#92

mamaMsg_create(), mamaMsg_createForPayload(), or mamaMsg_createForPayloadBridge() should be used instead.

The function mamaMsg_createForWombatMsg() does not exist in OpenMAMA. The reference to it in the developer's guide is incorrect and will be removed when it is next updated.

Show quoted text

From: openmama-users-bounces@... [mailto:openmama-users-bounces@...] On Behalf Of Nicolas Huyghe
Sent: Thursday, October 18, 2012 4:14 PM
To: openmama-users@...
Subject: [Openmama-users] mamaMsg_createForWombatMsg

Hello,

I cannot find the function mamaMsg_createForWombatMsg which is described in section 11.2 of the developer’s guide (example 62).

Could you tell me where to find it?

Thank you,

-Nicolas Huyghe

Please consider the environment before printing this e-mail.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error, please advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

mamaMsg_createForWombatMsg

Nicolas Huyghe

#91

Hello,

I cannot find the function mamaMsg_createForWombatMsg which is described in section 11.2 of the developer’s guide (example 62).

Could you tell me where to find it?

Thank you,

-Nicolas Huyghe

Re: Openmama-users Digest, Vol 7, Issue 4

kulbhushan chaskar <kulbhushanchaskar@...>

#90

Hi,

I think accept is also work when avis middle ware u used

Regards,

Kulbhushan Chaskar.

Show quoted text

On Thu, Oct 18, 2012 at 5:30 PM, <openmama-users-request@...> wrote:

Send Openmama-users mailing list submissions to
openmama-users@...

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.openmama.org/mailman/listinfo/openmama-users
or, via email, send a message with subject or body 'help' to
openmama-users-request@...

You can reach the person managing the list at
openmama-users-owner@...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Openmama-users digest..."

Today's Topics:

1. Re: Transport Listener issue (Ian Bell)

----------------------------------------------------------------------

Message: 1
Date: Wed, 17 Oct 2012 19:30:04 +0000
From: Ian Bell <IBell@...>
To: Nicolas Huyghe <Nicolas.Huyghe@...>,
"openmama-users@..."
<openmama-users@...>
Subject: Re: [Openmama-users] Transport Listener issue
Message-ID:
<4657D669CDDCE045A4E14365D61F462D061E8D@...>
Content-Type: text/plain; charset="us-ascii"

Hi

There are a number of transport callback events available through OpenMAMA but not all middlewares support them all.

MAMA_TRANSPORT_CONNECT
MAMA_TRANSPORT_CONNECT_FAILED
MAMA_TRANSPORT_RECONNECT
MAMA_TRANSPORT_DISCONNECT
MAMA_TRANSPORT_ACCEPT
MAMA_TRANSPORT_ACCEPT_RECONNECT
MAMA_TRANSPORT_PUBLISHER_DISCONNECT
MAMA_TRANSPORT_QUALITY
MAMA_TRANSPORT_NAMING_SERVICE_CONNECT
MAMA_TRANSPORT_NAMING_SERVICE_DISCONNECT
MAMA_TRANSPORT_WRITE_QUEUE_HIGH_WATER_MARK
MAMA_TRANSPORT_WRITE_QUEUE_LOW_WATER_MARK

The only one connected up in avis is disconnect.

When an event like this happens at the middleware layer, it is propagated into the middleware bridge which can then call
one of the following OpenMAMA transport functions which will give the transport callback to the application,

mamaTransportImpl_invokeTransportCallback
mamaTransportImpl_disconnect
mamaTransportImpl_reconnect

If the middleware supports the events and the bridge implementation handles it correctly then you should get transport callbacks for CONNECT.

Thanks,
Ian

From: openmama-users-bounces@... [mailto:openmama-users-bounces@...] On Behalf Of Nicolas Huyghe
Sent: 17 October 2012 09:09
To: openmama-users@...
Subject: [Openmama-users] Transport Listener issue

Hi everyone,

When using avis middleware, the transport listener does not receive any connection events except for disconnect when I shutdown the avis router.
Is that feature not supported with avis? Will other middlewares such as tibco notify the transport listener on successful connection (CONNECT event) ?

Thanks

________________________________

Please consider the environment before printing this e-mail.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error, please advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openmama.org/pipermail/openmama-users/attachments/20121017/76cc1884/attachment-0001.html>

------------------------------

_______________________________________________
Openmama-users mailing list
Openmama-users@...
https://lists.openmama.org/mailman/listinfo/openmama-users

End of Openmama-users Digest, Vol 7, Issue 4
********************************************

Re: Transport Listener issue

Ian Bell <IBell@...>

#89

Hi

There are a number of transport callback events available through OpenMAMA but not all middlewares support them all.

MAMA_TRANSPORT_CONNECT

MAMA_TRANSPORT_CONNECT_FAILED

MAMA_TRANSPORT_RECONNECT

MAMA_TRANSPORT_DISCONNECT

MAMA_TRANSPORT_ACCEPT

MAMA_TRANSPORT_ACCEPT_RECONNECT

MAMA_TRANSPORT_PUBLISHER_DISCONNECT

MAMA_TRANSPORT_QUALITY

MAMA_TRANSPORT_NAMING_SERVICE_CONNECT

MAMA_TRANSPORT_NAMING_SERVICE_DISCONNECT

MAMA_TRANSPORT_WRITE_QUEUE_HIGH_WATER_MARK

MAMA_TRANSPORT_WRITE_QUEUE_LOW_WATER_MARK

The only one connected up in avis is disconnect.

When an event like this happens at the middleware layer, it is propagated into the middleware bridge which can then call

one of the following OpenMAMA transport functions which will give the transport callback to the application,

mamaTransportImpl_invokeTransportCallback

mamaTransportImpl_disconnect

mamaTransportImpl_reconnect

If the middleware supports the events and the bridge implementation handles it correctly then you should get transport callbacks for CONNECT.

Thanks,

Ian

Show quoted text

From: openmama-users-bounces@... [mailto:openmama-users-bounces@...] On Behalf Of Nicolas Huyghe
Sent: 17 October 2012 09:09
To: openmama-users@...
Subject: [Openmama-users] Transport Listener issue

Hi everyone,

When using avis middleware, the transport listener does not receive any connection events except for disconnect when I shutdown the avis router.

Is that feature not supported with avis? Will other middlewares such as tibco notify the transport listener on successful connection (CONNECT event) ?

Thanks

Please consider the environment before printing this e-mail.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error, please advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Transport Listener issue

Nicolas Huyghe

#88

Hi everyone,

When using avis middleware, the transport listener does not receive any connection events except for disconnect when I shutdown the avis router.

Is that feature not supported with avis? Will other middlewares such as tibco notify the transport listener on successful connection (CONNECT event) ?

Thanks

Re: dictionary publisher and avis

Ian Bell <IBell@...>

#87

Hi

Currently avis can’t support the dictionary as the point of the dictionary is to relate fids to names and the avis payload can’t have both.

A way to fix this may be to modify the avis bridge so that the name and fid could be passed in a field

Ie currently the id string is a fid or a name we could change the id string for the field to contain the name and fid separated by a

particular character if you wan to send both.

If the character is not present that it could fall back to looking for a fir or a name.

Eg

699_wPriceLevels

Ian

Show quoted text

From: openmama-users-bounces@... [mailto:openmama-users-bounces@...] On Behalf Of Nicolas Huyghe
Sent: 12 October 2012 16:40
To: openmama-users@...
Subject: [Openmama-users] dictionary publisher and avis

Hello

I am trying to publish a dictionary over avis. The sample listener (written in C) crashes on reception of the dictionary message (during iteration on the fields of the dictionary message).

Can you actually publish/subscribe a dictionary over avis? I also noticed that fields in avis message cannot have a fid and a name at the same time.

Thank you

Please consider the environment before printing this e-mail.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error, please advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

dictionary publisher and avis

Nicolas Huyghe

#86

Hello

I am trying to publish a dictionary over avis. The sample listener (written in C) crashes on reception of the dictionary message (during iteration on the fields of the dictionary message).

Can you actually publish/subscribe a dictionary over avis? I also noticed that fields in avis message cannot have a fid and a name at the same time.

Thank you

Re: Announcing the Tick42 Blp Bridge for OpenMama (with attached documents this time)

Tom Doust

#85

Show quoted text

From: Tom Doust
Sent: 27 September 2012 12:44 PM
To: Openmama-dev@...; 'openmama-users@...'
Subject: Announcing the Tick42 Blp Bridge for OpenMama

We are pleased to announce version 1.0 of the Tick42 blp bridge which uses the Bloomberg Open API. This provides OpenMama access to Bloomberg data from Bloomberg Terminal, Server API and Managed B-Pipe data sources.

The source code is released under the “GNU Lesser General Public License”

I am currently in the process of figuring out how to get the source code into the OpenMama git. In the meantime, a binary release of the bridge is available for download on the tick42 website. Please contact blpBridge@... for details.

The attached documents provide an overview of the bridge (Tick42 BLP Bridge for Open Mama.pdf) and a description of how to build the source code (Tick42 BLP Bridge Development environment.pdf)

Best regards

Tom Doust

TOM DOUST | Head of Consultancy

TICK42

P: +44 (0) 1628 477444 | M: +44 (0) 7710 479924 | E: tom.doust@... | http://www.tick42.com

PDF

Tick42 BLP Bridge for Open Mama.pdf

PDF

Tick42 BLP Bridge Development environment.pdf

Announcing the Tick42 Blp Bridge for OpenMama

Tom Doust

#84

We are pleased to announce version 1.0 of the Tick42 blp bridge which uses the Bloomberg Open API. This provides OpenMama access to Bloomberg data from Bloomberg Terminal, Server API and Managed B-Pipe data sources.

The source code is released under the “GNU Lesser General Public License”

I am currently in the process of figuring out how to get the source code into the OpenMama git. In the meantime, a binary release of the bridge is available for download on the tick42 website. Please contact blpBridge@... for details.

The attached documents provide an overview of the bridge (Tick42 BLP Bridge for Open Mama.pdf) and a description of how to build the source code (Tick42 BLP Bridge Development environment.pdf)

Best regards

Tom Doust

TOM DOUST | Head of Consultancy

TICK42

P: +44 (0) 1628 477444 | M: +44 (0) 7710 479924 | E: tom.doust@... | http://www.tick42.com

Re: Handling stale messages

Glenn McClements <gmcclements@...>

#83

Hi Nicolas,

The main difference is that MAMA_QUALITY_STALE is a property of a mamaSubscription object, while MAMA_MSG_STATUS_STALE is a property of the mamaMsg object - you will receive stale messages whenever a gap is detected, and the subscription will be stale at that point also. The best way to detect whether a particular topic is stale however is to implement the relevant subscription callbacks and you will be automatically notified.

Generally you do not have to do anything to recover from stale subscriptions, as OpenMAMA will attempt to recover automatically, though you may have application specific code that you wish to invoke e.g. some warning propagated to the user. Also note that the concept of a gap and staleness is only for "market data" subscriptions, not "basic" subscriptions.

The OpenMAMA Developer's Guide, p67-70, gives a good overview of the data quality state machine.

http://www.openmama.org/sites/openmama.org/files/openmama-developers-guide.pdf

Glenn

From: Nicolas Huyghe <Nicolas.Huyghe@...>
Date: Fri, 14 Sep 2012 05:49:31 -0500
To: "openmama-users@..." <openmama-users@...>
Subject: [Openmama-users] Handling stale messages

Hi there,

When looking at source code, I see two ways of notifying subscription staleness: mamaStatus: MAMA_MSG_STATUS_STALE and mamaQuality: MAMA_QUALITY_STALE

What is the difference between the two and should both be handled?

Thanks

-Nicolas

_______________________________________________ Openmama-users mailing list Openmama-users@... https://lists.openmama.org/mailman/listinfo/openmama-users

Please consider the environment before printing this e-mail.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error, please advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Handling stale messages

Nicolas Huyghe

#82

Hi there,

When looking at source code, I see two ways of notifying subscription staleness: mamaStatus: MAMA_MSG_STATUS_STALE and mamaQuality: MAMA_QUALITY_STALE

What is the difference between the two and should both be handled?

Thanks

-Nicolas

Re: create new bridge

Glenn McClements <gmcclements@...>

#81

Hi Nicolas,

There is a wiki page at http://wiki.openmama.org/index.php/OpenMAMA_Bridge_Documentation which give a good introduction to building your own bridge.

You can also take a look at the sample Avis bridge and there is a development mailing list for questions:

http://lists.openmama.org/mailman/listinfo/openmama-dev

Glenn

From: Nicolas Huyghe <Nicolas.Huyghe@...>
Date: Wed, 12 Sep 2012 05:18:36 -0500
To: "openmama-users@..." <openmama-users@...>
Subject: [Openmama-users] create new bridge

Hello

Is there a document that explains how to create a new bridge?

Thanks

_______________________________________________ Openmama-users mailing list Openmama-users@... https://lists.openmama.org/mailman/listinfo/openmama-users

Please consider the environment before printing this e-mail.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error, please advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

create new bridge

Nicolas Huyghe

#80

Hello

Is there a document that explains how to create a new bridge?

Thanks

Protobuf Payload Addendum

Tim Jones <Tgjones@...>

#79

Hi,

As I am a NYSE Technologies employee, I have been asked to clarify a few points regarding the Protocol Buffers Payload for OpenMAMA library.

Firstly, the Protocol Buffers for OpenMAMA library is a home project, and is not, at this stage, affiliated or endorsed by NYSE Technologies or NYSE Euronext. It is entirely, independent, open-source, and is not provided with a warranty of any kind.

Secondly, in my license ignorance I posted that the library is distributed under the GPL. I was incorrect, it is distributed under the Lesser GPL, to match OpenMAMA. The license is viewable in the LICENSE file under the mama_protobuf repository.

Thanks

Tim

Please consider the environment before printing this e-mail.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error, please advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Protobuf Payload

Tim Jones <Tgjones@...>

#78

Hi,

I've recently been working on an open-source demonstrator payload for OpenMAMA which wraps Google Protocol Buffers.

Firstly, its not complete! It builds but I have no facility to test it (and therefore debug it), as the only open-source middleware (that I know of), Avis, is not payload-agnostic.

It is distributed under the GPL and is available at https://github.com/tgjonesuk/mama_protobuf. Please feel free to clone, fork or whatever. If you make any progress, please let me know and I'll add you as a GitHub collaborator or commit the changes myself.

Thanks

Tim

Tim Jones

tgjones@...

Please consider the environment before printing this e-mail.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error, please advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Re: Publishing own dictionary

Jacobraj Benet <JBenet@...>

#77

Hi Nicolas,

We don't have any sample example program for populating/publishing dictionary, but those method should work out of box with no issues, as it has been used internally in other products.

Thanks,

--

Jacob

From: Nicolas Huyghe <Nicolas.Huyghe@...>
Date: Thursday, August 30, 2012 4:47 AM
To: "openmama-users@..." <openmama-users@...>
Subject: [Openmama-users] Publishing own dictionary

Hi there

I’d like to publish the dictionary, which is possible as specified in “Advanced Publishing” section of the dev guide.

I also noticed that there is a way to populate a dictionary from file, but could not find any sample file.

Is there sample code available for publishing the dictionary? Does anyone has a sample dictionary I could use to populate the dictionary to be published from a file?

Many thanks

-Nicolas

Please consider the environment before printing this email.

Visit our website at http://www.nyse.com
*****************************************************************************
Note: The information contained in this message and any attachment to it is privileged, confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to the message, and please delete it from your system. Thank you. NYSE Euronext.

Re: MAMA API not enforcing entitlement checks message

Jacobraj Benet <JBenet@...>

#76

Hi Nicolas,

Good to hear that the example program was fine.

By default the OpenMAMA API does not enforce entitlement but can be enabled through the mama.properties to enforce entitlements.

For the entitlement to work, you would need to have the entitlement server, where user are authenticated to particular markets and where the reports are generated.

OEA is Entitlement API that mama uses internally to enforce entitlement.

Thanks,

--

Jacob

From: Nicolas Huyghe <Nicolas.Huyghe@...>
Date: Thursday, August 30, 2012 3:40 AM
To: Jacobraj Benet <jbenet@...>, "openmama-users@..." <openmama-users@...>
Subject: RE: [Openmama-users] MAMA API not enforcing entitlement checks message

Hi Jacob,

The publisher / subscriber samples work fine (as well as the JNI samples).

I need to understand how entitlements are working when using OpenMAMA.

Is the entitlement server proprietary (as well as the entitlement client code which is disabled by default when compiling OpenMAMA)?.

Can you tell me what OEA entitlement stand for in the dev guide?

Thanks

-Nicolas

Show quoted text

From: Jacobraj Benet [mailto:JBenet@...]
Sent: Wednesday, August 29, 2012 4:37 PM
To: Nicolas Huyghe; openmama-users@...
Subject: Re: [Openmama-users] MAMA API not enforcing entitlement checks message

Hi Nicolas,

The below message is only a warning message that informs that application is not enforcing entitlement.

This is not of any concern, How are you running the example program? Can you run the same application with –v –v –v –v and send us the error output.

Thanks,

--

Jacob

From: Nicolas Huyghe <Nicolas.Huyghe@...>
Date: Wednesday, August 29, 2012 11:01 AM
To: "openmama-users@..." <openmama-users@...>
Subject: [Openmama-users] MAMA API not enforcing entitlement checks message

Hi,

I am new to Open MAMA and have the message below when starting a sample subscriber.

********************************************************************************

Note: This build of the MAMA API is not enforcing entitlement checks.

Please see the Licensing file for details

**********************************************************************************

Does anybody know where this “licensing file” is or what this message is about?

Thanks

Nicolas

Please consider the environment before printing this email.

Visit our website at http://www.nyse.com
*****************************************************************************
Note: The information contained in this message and any attachment to it is privileged, confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to the message, and please delete it from your system. Thank you. NYSE Euronext.

Please consider the environment before printing this email.

Visit our website at http://www.nyse.com
*****************************************************************************
Note: The information contained in this message and any attachment to it is privileged, confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to the message, and please delete it from your system. Thank you. NYSE Euronext.

Publishing own dictionary

Nicolas Huyghe

#75

Hi there

I’d like to publish the dictionary, which is possible as specified in “Advanced Publishing” section of the dev guide.

I also noticed that there is a way to populate a dictionary from file, but could not find any sample file.

Is there sample code available for publishing the dictionary? Does anyone has a sample dictionary I could use to populate the dictionary to be published from a file?

Many thanks

-Nicolas