You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* You are familiar with OpenMAMA [core concepts](https://docs.solace.com/Solace-OpenMama/Solace-OpenMAMA-Overview.htm).
20
-
* If not, see [this guide](https://openmama.finos.org/quickstart).
21
-
* You are familiar with Solace [core concepts](https://docs.solace.com/PubSub-Basics/Core-Concepts.htm).
22
-
* You have access to a properly installed OpenMAMA [release](https://github.com/OpenMAMA/OpenMAMA/releases).
23
-
* Solace middleware bridge with its dependencies is also installed
24
-
* You have access to Solace messaging with the following configuration details:
25
-
* Connectivity information for a Solace message-VPN
26
-
* Enabled client username and password
19
+
- You are familiar with OpenMAMA [core concepts](https://docs.solace.com/Solace-OpenMama/Solace-OpenMAMA-Overview.htm).
20
+
- If not, see [this guide](https://openmama.finos.org/quickstart).
21
+
- You are familiar with Solace [core concepts](https://docs.solace.com/PubSub-Basics/Core-Concepts.htm).
22
+
- You have access to a properly installed OpenMAMA [release](https://github.com/OpenMAMA/OpenMAMA/releases).
23
+
- Solace middleware bridge with its dependencies is also installed
24
+
- You have access to Solace messaging with the following configuration details:
25
+
- Connectivity information for a Solace message-VPN
26
+
- Enabled client username and password
27
27
28
28
One simple way to get access to Solace messaging quickly is to create a messaging service in Solace Cloud [as outlined here](https://solace.com/products/platform/cloud/). You can find other ways to get access to Solace messaging below.
29
29
@@ -58,8 +58,8 @@ The program will consist of two major parts:
58
58
59
59
Any OpenMAMA program begins with initialization that consists of loading a bridge and opening it, in this particular order:
60
60
61
-
* load
62
-
* open
61
+
- load
62
+
- open
63
63
64
64
This is how it is done.
65
65
@@ -154,8 +154,8 @@ In order to publish a message we need to do the following **in this particular o
154
154
155
155
Creating of transport includes two steps in this particular order:
Notice how `solace` and `vmr` property token names are the same as in `mama_loadBridge(&bridge, "solace")` and `mamaTransport_create(transport, "vmr", bridge)` calls.
232
232
233
-
*`mama.solace.transport.vmr.session_host` is `Host` and usually has a value of the host address of your **Solace messaging**.
234
-
*`mama.solace.transport.vmr.session_username` is `Client Username`
235
-
*`mama.solace.transport.vmr.session_password` is optional `Client Password`
236
-
*`mama.solace.transport.vmr.session_vpn_name` is `Message VPN`
237
-
*`mama.solace.transport.vmr.allow_recover_gaps` doesn’t have a default value and specifies whether the Solace middleware bridge should override applications settings for recovering from sequence number gaps in subscriptions. When `allow_recover_gaps` is `true` applications are allowed to specify the gap recovery behaviour. When `allow_recover_gaps` is `false`, the gap recovery is disabled for all subscriptions, regardless of applications settings.
233
+
-`mama.solace.transport.vmr.session_host` is `Host` and usually has a value of the host address of your **Solace messaging**.
234
+
-`mama.solace.transport.vmr.session_username` is `Client Username`
235
+
-`mama.solace.transport.vmr.session_password` is optional `Client Password`
236
+
-`mama.solace.transport.vmr.session_vpn_name` is `Message VPN`
237
+
-`mama.solace.transport.vmr.allow_recover_gaps` doesn’t have a default value and specifies whether the Solace middleware bridge should override applications settings for recovering from sequence number gaps in subscriptions. When `allow_recover_gaps` is `true` applications are allowed to specify the gap recovery behaviour. When `allow_recover_gaps` is `false`, the gap recovery is disabled for all subscriptions, regardless of applications settings.
238
238
239
239
Now we need to modify our program to refer to this **properties file** by its name and location (in the current directory: `"."`):
240
240
@@ -369,8 +369,8 @@ int main(int argc, const char** argv)
369
369
370
370
Combining the example source code shown above results in the following source code files:
* You are familiar with OpenMAMA [core concepts](https://docs.solace.com/Solace-OpenMama/Solace-OpenMAMA-Overview.htm).
22
-
* If not, see [this OpenMAMA guide](https://openmama.finos.org/quickstart) and [Solace OpenMAMA “Hello World” tutorial](../hello-world/).
23
-
* You are familiar with Solace [core concepts](https://docs.solace.com/PubSub-Basics/Core-Concepts.htm).
24
-
* You have access to a properly installed OpenMAMA [release](https://github.com/OpenMAMA/OpenMAMA/releases).
25
-
* Solace middleware bridge with its dependencies is also installed
26
-
* You have access to Solace messaging with the following configuration details:
27
-
* Connectivity information for a Solace message-VPN
28
-
* Enabled client username and password
21
+
- You are familiar with OpenMAMA [core concepts](https://docs.solace.com/Solace-OpenMama/Solace-OpenMAMA-Overview.htm).
22
+
- If not, see [this OpenMAMA guide](https://openmama.finos.org/quickstart) and [Solace OpenMAMA “Hello World” tutorial](../hello-world/).
23
+
- You are familiar with Solace [core concepts](https://docs.solace.com/PubSub-Basics/Core-Concepts.htm).
24
+
- You have access to a properly installed OpenMAMA [release](https://github.com/OpenMAMA/OpenMAMA/releases).
25
+
- Solace middleware bridge with its dependencies is also installed
26
+
- You have access to Solace messaging with the following configuration details:
27
+
- Connectivity information for a Solace message-VPN
28
+
- Enabled client username and password
29
29
30
30
One simple way to get access to Solace messaging quickly is to create a messaging service in Solace Cloud [as outlined here](https://solace.com/products/platform/cloud/). You can find other ways to get access to Solace messaging below.
31
31
@@ -37,8 +37,8 @@ This tutorial will show you how to publish a message with one string field to a
37
37
38
38
This tutorial will show you how to use OpenMAMA C API:
39
39
40
-
* to build and send a message on a topic
41
-
* to subscribe to a topic and receive a message
40
+
- to build and send a message on a topic
41
+
- to subscribe to a topic and receive a message
42
42
43
43
## Installation
44
44
@@ -81,9 +81,9 @@ The **receiver** is a data structure with function pointers that are invoked by
81
81
82
82
It has a type of `mamaMsgCallbacks` and it is expected to have, as a minimum, the following function pointers:
83
83
84
-
* `onCreate` that is invoked when a subscription is created
85
-
* `onError` that is invoked when an error occurs
86
-
* `onMsg` that is invoked when a message arrives on the subscribed topic
84
+
- `onCreate` that is invoked when a subscription is created
85
+
- `onError` that is invoked when an error occurs
86
+
- `onMsg` that is invoked when a message arrives on the subscribed topic
87
87
88
88
This is how the routine for creating a subscription is implemented:
89
89
@@ -309,9 +309,9 @@ Our application consists of two executables: _topicSubscriber_ and _topicPublish
309
309
310
310
If you combine the example source code shown above and split them into the two mentioned executables, it results in the source that is available for download:
0 commit comments