1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
DMaaP connection objects
========================
DMaaP connection objects are JSON objects that:
1. Components should expect at runtime in their application
configuration and is to be used to connect to the appropriate DMaaP
feed or topic.
2. Developers must provide through the command-line argument
``--dmaap-file`` to test their component with manually provisioned
feeds and topics.
This page is a reference to the specific structure that each type of
DMaaP stream requires.
Note for #1 that components should expect the entire object with all
properties at runtime where the default will be ``null`` unless
specified otherwise.
Note for #2 that developers are not required to provide the entire
object. The required properties will be labeled with “*required as
input*”.
.. _dmaap-message-router:
Message router
--------------
Publishers and subscribers both have the same JSON object structure.
Here’s an example:
.. code:: json
{
"type": "message_router",
"aaf_username": "some-user",
"aaf_password": "some-password",
"dmaap_info": {
"client_role": "com.dcae.member",
"client_id": "1500462518108",
"location": "mtc00",
"topic_url": "https://we-are-message-router.us:3905/events/some-topic"
}
}
At the top-level:
+-------------+----+--------------------+
| Property | Ty\| Descript\ |
| Name | pe | ion |
+=============+====+====================+
| type | st\| *Require\ |
| | ri\| d \ |
| | ng | as \ |
| | | input*. |
| | | Must be |
| | | ``message_router`` |
| | | for |
| | | message |
| | | router |
| | | topics |
+-------------+----+--------------------+
| aaf_usernam\| st\| AAF |
| e | ri\| username |
| | ng | message |
| | | router |
| | | clients |
| | | use to |
| | | authenti\ |
| | | cate |
| | | with |
| | | secure |
| | | topics |
+-------------+----+--------------------+
| aaf_passwor\| st\| AAF |
| d | ri\| password |
| | ng | message |
| | | router |
| | | clients |
| | | use to |
| | | authenti\ |
| | | cate |
| | | with |
| | | secure |
| | | topics |
+-------------+----+--------------------+
| dmaap_info | JS\| *Require\ |
| | ON | d \ |
| | ob\| as \ |
| | je\| input*. |
| | ct | Contains |
| | | the |
| | | topic |
| | | connecti\ |
| | | on |
| | | details |
+-------------+----+--------------------+
The ``dmaap_info`` object contains:
+-------------+----+----------+
| Property | Ty\| Descript\|
| Name | pe | ion |
+=============+====+==========+
| client_role | st\| AAF |
| | ri\| client |
| | ng | role |
| | | that’s |
| | | requesti\|
| | | ng |
| | | publish |
| | | or |
| | | subscrib\|
| | | e |
| | | access |
| | | to the |
| | | topic |
+-------------+----+----------+
| client_id | st\| Client |
| | ri\| id for |
| | ng | given |
| | | AAF |
| | | client |
+-------------+----+----------+
| location | st\| DCAE |
| | ri\| location |
| | ng | for the |
| | | publishe\|
| | | r |
| | | or |
| | | subscrib\|
| | | er, |
| | | used to |
| | | set up |
| | | routing |
+-------------+----+----------+
| topic_url | st\| *Require\|
| | ri\| d \ |
| | ng | as \ |
| | | input*. |
| | | URL for |
| | | accessin\|
| | | g |
| | | the |
| | | topic to |
| | | publish |
| | | or |
| | | receive |
| | | events |
+-------------+----+----------+
Here’s an example of the minimal JSON that must be provided as an input:
.. code:: json
{
"type": "message_router",
"dmaap_info": {
"topic_url": "https://we-are-message-router.us:3905/events/some-topic"
}
}
.. _dmaap-data-router:
Data router
-----------
Publisher
~~~~~~~~~
Here’s an example of what the JSON object connection for data router
publisher looks like:
.. code:: json
{
"type": "data_router",
"dmaap_info": {
"location": "mtc00",
"publish_url": "https://we-are-data-router.us/feed/xyz",
"log_url": "https://we-are-data-router.us/feed/xyz/logs",
"username": "some-user",
"password": "some-password",
"publisher_id": "123456"
}
}
At the top-level:
+-------------+----+----------------+
| Property | Ty\| Descript\ |
| Name | pe | ion |
+=============+====+================+
| type | st\| *Require\ |
| | ri\| d \ |
| | ng | as \ |
| | | input*. |
| | | Must be |
| | | ``data_router``|
| | | for data |
| | | router |
| | | feeds |
+-------------+----+----------------+
| dmaap_info | JS\| *Require\ |
| | ON | d \ |
| | ob\| as \ |
| | je\| input*. |
| | ct | Contains |
| | | the |
| | | topic |
| | | connecti\ |
| | | on |
| | | details |
+-------------+----+----------------+
The ``dmaap_info`` object contains:
+-------------+----+----------+
| Property | Ty\| Descript\|
| Name | pe | ion |
+=============+====+==========+
| location | st\| DCAE |
| | ri\| location |
| | ng | for the |
| | | publishe\|
| | | r, |
| | | used to |
| | | set up |
| | | routing |
+-------------+----+----------+
| publish_url | st\| *Require\|
| | ri\| d \ |
| | ng | as \ |
| | | input*. |
| | | URL to |
| | | which |
| | | the |
| | | publishe\|
| | | r |
| | | makes |
| | | Data |
| | | Router |
| | | publish |
| | | requests |
+-------------+----+----------+
| log_url | st\| URL from |
| | ri\| which |
| | ng | log data |
| | | for the |
| | | feed can |
| | | be |
| | | obtained |
+-------------+----+----------+
| username | st\| Username |
| | ri\| the |
| | ng | publishe\|
| | | r |
| | | uses to |
| | | authenti\|
| | | cate |
| | | to Data |
| | | Router |
+-------------+----+----------+
| password | st\| Password |
| | ri\| the |
| | ng | publishe\|
| | | r |
| | | uses to |
| | | authenti\|
| | | cate |
| | | to Data |
| | | Router |
+-------------+----+----------+
| publisher_i | st\| Publishe\|
| d | ri\| r |
| | ng | id in |
| | | Data |
| | | Router |
+-------------+----+----------+
Here’s an example of the minimal JSON that must be provided as an input:
.. code:: json
{
"type": "data_router",
"dmaap_info": {
"publish_url": "https://we-are-data-router.us/feed/xyz"
}
}
Subscriber
~~~~~~~~~~
Here’s an example of what the JSON object connection for data router
subscriber looks like:
.. code:: json
{
"type": "data_router",
"dmaap_info": {
"location": "mtc00",
"delivery_url": "https://my-subscriber-app.dcae:8080/target-path",
"username": "some-user",
"password": "some-password",
"subscriber_id": "789012"
}
}
At the top-level:
+-------------+----+----------------+
| Property | Ty\| Descript\ |
| Name | pe | ion |
+=============+====+================+
| type | st\| *Require\ |
| | ri\| d |
| | ng | as \ |
| | | input*. |
| | | Must be |
| | | ``data_router``|
| | | for data |
| | | router |
| | | feeds |
+-------------+----+----------------+
| dmaap_info | JS\| *Require\ |
| | ON | d \ |
| | ob\| as \ |
| | je\| input*. |
| | ct | Contains |
| | | the |
| | | topic |
| | | connecti\ |
| | | on |
| | | details |
+-------------+----+----------------+
The ``dmaap_info`` object contains:
+--------------+----+----------+
| Property | Ty\| Descript\|
| Name | pe | ion |
+==============+====+==========+
| location | st\| DCAE |
| | ri\| location |
| | ng | for the |
| | | publishe\|
| | | r, |
| | | used to |
| | | set up |
| | | routing |
+--------------+----+----------+
| delivery_ur\ | st\| URL to |
| l | ri\| which |
| | ng | the Data |
| | | Router |
| | | should |
| | | deliver |
| | | files |
+--------------+----+----------+
| username | st\| Username |
| | ri\| Data |
| | ng | Router |
| | | uses to |
| | | authenti\|
| | | cate |
| | | to the |
| | | subscrib\|
| | | er |
| | | when |
| | | deliveri\|
| | | ng |
| | | files |
+--------------+----+----------+
| password | st\| Password |
| | ri\| Data |
| | ng | Router |
| | | uses to |
| | | authenti\|
| | | cate |
| | | to the |
| | | subscrib\|
| | | er |
| | | when |
| | | deliveri\|
| | | ng |
| | | files |
+--------------+----+----------+
| subscriber_i\| st | Subscrib\|
| d | ri | er |
| | ng | id in |
| | | Data |
| | | Router |
+--------------+----+----------+
Here’s an example of the minimal JSON that must be provided as an input:
.. code:: json
{
"type": "data_router",
"dmaap_info": {
}
}
Developers are recommended to use ``username`` and ``password`` since
this is the recommended security practice.
Note that the dcae-cli will construct the ``delivery_url`` when
deploying the component since this can only be known at deployment time.
|
