-
Notifications
You must be signed in to change notification settings - Fork 8
/
RegistryOffice.yaml
13891 lines (13871 loc) · 792 KB
/
RegistryOffice.yaml
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
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
openapi: 3.0.0
info:
title: RegistryOffice
version: 2.1.2
x-gui-paths:
########################################################################################################################
# Representation Layer
########################################################################################################################
/docs:
get:
operationId: docs
summary: 'Represents Swagger API description page'
tags:
- RepresentationServices
responses:
'200':
description: 'Swagger API description page represented'
# Not explixitly described
'400':
$ref: '#/components/responses/responseForErroredOamRequests'
'401':
$ref: '#/components/responses/responseForErroredOamRequests'
'403':
$ref: '#/components/responses/responseForErroredOamRequests'
'404':
$ref: '#/components/responses/responseForErroredOamRequests'
'500':
$ref: '#/components/responses/responseForErroredOamRequests'
default:
$ref: '#/components/responses/responseForErroredOamRequests'
paths:
########################################################################################################################
# Service Layer - Individual Part
########################################################################################################################
/v1/bequeath-your-data-and-die:
parameters:
- $ref: '#/components/parameters/user'
- $ref: '#/components/parameters/originator'
- $ref: '#/components/parameters/x-correlator'
- $ref: '#/components/parameters/trace-indicator'
- $ref: '#/components/parameters/customer-journey'
post:
operationId: bequeathYourDataAndDie
summary: 'Initiates process of embedding a new release'
tags:
- IndividualServices
security:
- apiKeyAuth: []
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- new-application-name
- new-application-release
- new-application-protocol
- new-application-address
- new-application-port
properties:
new-application-name:
type: string
description: >
'Name of application that shall be target of the handover process
update [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-c-nr-2-1-2-000/layer-protocol=0/http-client-interface-1-0:http-client-interface-pac/http-client-interface-configuration/application-name]'
new-application-release:
type: string
pattern: '^([0-9]{1,2})\.([0-9]{1,2})\.([0-9]{1,2})$'
description: >
'Release of application that shall be target of the handover process
update [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-c-nr-2-1-2-000/layer-protocol=0/http-client-interface-1-0:http-client-interface-pac/http-client-interface-configuration/release-number]'
new-application-protocol:
type: string
enum:
- 'HTTP'
- 'HTTPS'
description: >
'Protocol to be used for addressing the application that shall be target of the handover process
update [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-protocol]'
new-application-address:
type: object
minProperties: 1
maxProperties: 1
additionalProperties: false
properties:
ip-address:
type: object
minProperties: 1
additionalProperties: false
properties:
ipv-4-address:
type: string
pattern: '^((25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)$'
description: >
'IPv4 address of application that shall be target of the handover process
update [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/ip-address/ipv-4-address]'
domain-name:
type: string
pattern: '^([a-z0-9]+(-[a-z0-9]+)*\.)+[a-z]{2,}$'
description: >
'Domain name of application that shall be target of the handover process
update [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/domain-name]'
new-application-port:
type: integer
minimum: 0
maximum: 65535
description: >
'Port of application that shall be target of the handover process
update [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-port]'
example:
new-application-name: 'NewApplicationName'
new-application-release: '32.6.3'
new-application-protocol: 'HTTP'
new-application-address:
ip-address:
ipv-4-address: '1.1.3.1'
new-application-port: 3001
responses:
'204':
description: 'Process of embedding a new release initiated'
headers:
x-correlator:
schema:
type: string
example: '550e8400-e29b-11d4-a716-446655440000'
description: 'UUID for the service execution flow that allows to correlate requests and responses. Its value must be identical at the response compared with its corresponding request'
exec-time:
schema:
type: integer
example: 1100
description: 'Value written by the service provider, reporting the total elapsed time for the execution, including all the additional processing needed to retrieve the data from the backend service. Expressed in milliseconds'
backend-time:
schema:
type: integer
example: 850
description: 'Value written by the service provider, reporting the elapsed time for data retrieval from the backend (service invocation, database access…). Expressed in milliseconds'
life-cycle-state:
schema:
type: string
enum:
- 'EXPERIMENTAL'
- 'OPERATIONAL'
- 'DEPRECATED'
- 'OBSOLETE'
- 'UNKNOWN'
- 'NOT_YET_DEFINED'
example: 'EXPERIMENTAL'
description: >
'Life cycle state of the consumed service
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-s-im-000/layer-protocol=0/operation-server-interface-1-0:operation-server-interface-pac/operation-server-interface-configuration/life-cycle-state]'
'400':
$ref: '#/components/responses/responseForErroredServiceRequests'
'401':
$ref: '#/components/responses/responseForErroredServiceRequests'
'403':
$ref: '#/components/responses/responseForErroredServiceRequests'
'404':
$ref: '#/components/responses/responseForErroredServiceRequests'
'500':
$ref: '#/components/responses/responseForErroredServiceRequests'
default:
$ref: '#/components/responses/responseForErroredServiceRequests'
callbacks:
PromptForBequeathingDataCausesNewApplicationBeingRequestedToInquireForApplicationTypeApprovals:
url: #[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-protocol]://[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/domain-name or /core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/ip-address/ipv-4-address]:[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-port][/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-c-im-nr-2-1-2-002/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name]
post:
parameters:
- $ref: '#/components/parameters/user'
- $ref: '#/components/parameters/originator'
- $ref: '#/components/parameters/x-correlator'
- $ref: '#/components/parameters/trace-indicator'
- $ref: '#/components/parameters/customer-journey'
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- approval-application
- approval-application-release-number
- approval-operation
- approval-application-protocol
- approval-application-address
- approval-application-port
properties:
approval-application:
type: string
description: >
'Name of application that wants to receive information about new registrations
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-c-tar-2-1-2-000/layer-protocol=0/http-client-interface-1-0:http-client-interface-pac/http-client-interface-configuration/application-name]'
approval-application-release-number:
type: string
description: >
'Release of application that wants to receive information about new registrations
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-c-tar-2-1-2-000/layer-protocol=0/http-client-interface-1-0:http-client-interface-pac/http-client-interface-configuration/release-number]'
approval-operation:
type: string
description: >
'Operation that shall be addressed by information about new registrations
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-c-im-tar-2-1-2-003/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name]'
approval-application-protocol:
type: string
description: >
'Protocol to be used for addressing the application that wants to receive information about new registrations
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-tar-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-protocol]'
approval-application-address:
type: object
properties:
ip-address:
type: object
properties:
ipv-4-address:
type: string
description: >
'IPv4 address of application that wants to receive information about new registrations
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-tar-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/ip-address/ipv-4-address]'
domain-name:
type: string
description: >
'Domain name of application that wants to receive information about new registrations
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-tar-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/domain-name]'
approval-application-port:
type: integer
description: >
'TCP port of application that wants to receive information about new registrations
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-tar-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-port]'
example:
approval-application: 'TypeApprovalRegister'
approval-application-release-number: '2.0.1'
approval-operation: '/v1/regard-application'
approval-application-protocol: 'HTTP'
approval-application-address:
ip-address:
ipv-4-address: '127.0.0.1'
approval-application-port: 3032
responses:
'204':
description: 'Subscribed for notifications about new registrations'
headers:
x-correlator:
schema:
type: string
example: '550e8400-e29b-11d4-a716-446655440000'
description: 'UUID for the service execution flow that allows to correlate requests and responses. Its value must be identical at the response compared with its corresponding request'
exec-time:
schema:
type: integer
example: 1100
description: 'Value written by the service provider, reporting the total elapsed time for the execution, including all the additional processing needed to retrieve the data from the backend service. Expressed in milliseconds'
backend-time:
schema:
type: integer
example: 850
description: 'Value written by the service provider, reporting the elapsed time for data retrieval from the backend (service invocation, database access…). Expressed in milliseconds'
life-cycle-state:
schema:
type: string
enum:
- 'EXPERIMENTAL'
- 'OPERATIONAL'
- 'DEPRECATED'
- 'OBSOLETE'
- 'UNKNOWN'
- 'NOT_YET_DEFINED'
example: 'EXPERIMENTAL'
description: 'Life cycle state of the consumed service'
'400':
$ref: '#/components/responses/responseForErroredServiceRequests'
'401':
$ref: '#/components/responses/responseForErroredServiceRequests'
'403':
$ref: '#/components/responses/responseForErroredServiceRequests'
'404':
$ref: '#/components/responses/responseForErroredServiceRequests'
'500':
$ref: '#/components/responses/responseForErroredServiceRequests'
default:
$ref: '#/components/responses/responseForErroredServiceRequests'
PromptForBequeathingDataCausesTransferOfListOfAlreadyRegisteredApplications:
url: #[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-protocol]://[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/domain-name or /core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/ip-address/ipv-4-address]:[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-port][/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-c-im-nr-2-1-2-005/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name]
post:
parameters:
- $ref: '#/components/parameters/user'
- $ref: '#/components/parameters/originator'
- $ref: '#/components/parameters/x-correlator'
- $ref: '#/components/parameters/trace-indicator'
- $ref: '#/components/parameters/customer-journey'
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- application-name
- release-number
- embedding-operation
- client-update-operation
- operation-client-update-operation
- dispose-remainders-operation
- preceding-release-operation
- subsequent-release-operation
- tcp-server
properties:
application-name:
type: string
description: >
'Name of application that wants to register
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-c-*/layer-protocol=0/http-client-interface-1-0:http-client-interface-pac/http-client-interface-configuration/application-name]'
release-number:
type: string
description: >
'Release of application that wants to register
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-c-*/layer-protocol=0/http-client-interface-1-0:http-client-interface-pac/http-client-interface-configuration/release-number]'
preceding-application-name:
type: string
description: >
'If provided, the new application will address /v1/bequeath-your-data-and-die at the preceding application after receiving /v1/embed-yourself
from LOADfile'
preceding-release-number:
type: string
description: >
'If provided, the new application will address /v1/bequeath-your-data-and-die at the preceding release after receiving /v1/embed-yourself
from LOADfile'
embedding-operation:
type: string
description: >
'Name of service for initiating embedding process
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-c-im-*-*-*-*-000/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name]'
client-update-operation:
type: string
description: >
'Name of service for broadcasting server changes
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-c-im-*-*-*-*-001/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name]'
operation-client-update-operation:
type: string
description: >
'Name of service for broadcasting replacements of operations by backward compatible substitutes
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-c-im-*-*-*-*-002/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name]'
dispose-remainders-operation:
type: string
description: >
'Name of service for broadcasting de-registrations of applications
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-c-im-*-*-*-*-006/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name]'
preceding-release-operation:
type: string
description: >
'Name of service for retrieving information about the preceding release of a new application
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-c-im-*-*-*-*-008/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name]'
subsequent-release-operation:
type: string
description: >
'Name of service for configuring the newRelease at the existing application
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-c-im-*-*-*-*-009/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name]'
tcp-server:
type: object
properties:
protocol:
type: string
description: >
'Protocol to be used for addressing the application that wants to register
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-*/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-protocol]'
address:
type: object
properties:
ip-address:
type: object
properties:
ipv-4-address:
type: string
description: >
'IPv4 address of application that wants to register
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-*/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/ip-address/ipv-4-address]'
domain-name:
type: string
description: >
'Domain name of application that wants to register
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-*/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/domain-name]'
port:
type: integer
description: >
'TCP port of application that wants to register
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-*/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-port]'
responses:
'204':
description: 'Application registered'
headers:
x-correlator:
schema:
type: string
example: '550e8400-e29b-11d4-a716-446655440000'
description: 'UUID for the service execution flow that allows to correlate requests and responses. Its value must be identical at the response compared with its corresponding request'
exec-time:
schema:
type: integer
example: 1100
description: 'Value written by the service provider, reporting the total elapsed time for the execution, including all the additional processing needed to retrieve the data from the backend service. Expressed in milliseconds'
backend-time:
schema:
type: integer
example: 850
description: 'Value written by the service provider, reporting the elapsed time for data retrieval from the backend (service invocation, database access…). Expressed in milliseconds'
life-cycle-state:
schema:
type: string
enum:
- 'EXPERIMENTAL'
- 'OPERATIONAL'
- 'DEPRECATED'
- 'OBSOLETE'
- 'UNKNOWN'
- 'NOT_YET_DEFINED'
example: 'EXPERIMENTAL'
description: 'Life cycle state of the consumed service'
'400':
$ref: '#/components/responses/responseForErroredServiceRequests'
'401':
$ref: '#/components/responses/responseForErroredServiceRequests'
'403':
$ref: '#/components/responses/responseForErroredServiceRequests'
'404':
$ref: '#/components/responses/responseForErroredServiceRequests'
'500':
$ref: '#/components/responses/responseForErroredServiceRequests'
default:
$ref: '#/components/responses/responseForErroredServiceRequests'
PromptForBequeathingDataCausesTransferOfListOfSubscriptionsForEmbeddingStatusChanges:
url: #[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-protocol]://[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/domain-name or /core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/ip-address/ipv-4-address]:[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-port][/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-c-im-nr-2-1-2-006/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name]
post:
parameters:
- $ref: '#/components/parameters/user'
- $ref: '#/components/parameters/originator'
- $ref: '#/components/parameters/x-correlator'
- $ref: '#/components/parameters/trace-indicator'
- $ref: '#/components/parameters/customer-journey'
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- subscriber-application
- subscriber-release-number
- subscriber-operation
- subscriber-protocol
- subscriber-address
- subscriber-port
properties:
subscriber-application:
type: string
description: >
'Name of application that wants to receive notifications about changes of the embedding status
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-c-*/layer-protocol=0/http-client-interface-1-0:http-client-interface-pac/http-client-interface-configuration/application-name]'
subscriber-release-number:
type: string
description: >
'Release of application that wants to receive notifications about changes of the embedding status
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-c-*/layer-protocol=0/http-client-interface-1-0:http-client-interface-pac/http-client-interface-configuration/release-number]'
subscriber-operation:
type: string
description: >
'Names of the operation that shall be addressed by notifications about changes of the embedding status
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-c-im-*-*-*-*-007/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name]'
subscriber-protocol:
type: string
description: >
'Protocol to be used for addressing the application that wants to receive notifications about changes of the embedding status
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-*/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-protocol]'
subscriber-address:
type: object
minProperties: 1
maxProperties: 1
additionalProperties: false
properties:
ip-address:
type: object
minProperties: 1
additionalProperties: false
properties:
ipv-4-address:
type: string
description: >
'IPv4 address of application that wants to receive notifications about changes of the embedding status
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-*/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/ip-address/ipv-4-address]'
domain-name:
type: string
description: >
'Domain name of application that wants to receive notifications about changes of the embedding status
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-*/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/domain-name]'
subscriber-port:
type: integer
description: >
'TCP port of application that wants to receive notifications about changes of the embedding status
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-*/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-port]'
responses:
'204':
description: 'Subscribed for notifications about changes of the embedding status'
headers:
x-correlator:
schema:
type: string
example: '550e8400-e29b-11d4-a716-446655440000'
description: 'UUID for the service execution flow that allows to correlate requests and responses. Its value must be identical at the response compared with its corresponding request'
exec-time:
schema:
type: integer
example: 1100
description: 'Value written by the service provider, reporting the total elapsed time for the execution, including all the additional processing needed to retrieve the data from the backend service. Expressed in milliseconds'
backend-time:
schema:
type: integer
example: 850
description: 'Value written by the service provider, reporting the elapsed time for data retrieval from the backend (service invocation, database access…). Expressed in milliseconds'
life-cycle-state:
schema:
type: string
enum:
- 'EXPERIMENTAL'
- 'OPERATIONAL'
- 'DEPRECATED'
- 'OBSOLETE'
- 'UNKNOWN'
- 'NOT_YET_DEFINED'
example: 'EXPERIMENTAL'
description: 'Life cycle state of the consumed service'
'400':
$ref: '#/components/responses/responseForErroredServiceRequests'
'401':
$ref: '#/components/responses/responseForErroredServiceRequests'
'403':
$ref: '#/components/responses/responseForErroredServiceRequests'
'404':
$ref: '#/components/responses/responseForErroredServiceRequests'
'500':
$ref: '#/components/responses/responseForErroredServiceRequests'
default:
$ref: '#/components/responses/responseForErroredServiceRequests'
PromptForBequeathingDataCausesTARbeingRequestedToRedirectInfoAboutApprovalsToNewApplication:
url: #[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-tar-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-protocol]://[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-tar-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/domain-name or /core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-tar-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/ip-address/ipv-4-address]:[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-tar-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-port][/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-c-im-tar-2-1-2-005/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name]
post:
parameters:
- $ref: '#/components/parameters/user'
- $ref: '#/components/parameters/originator'
- $ref: '#/components/parameters/x-correlator'
- $ref: '#/components/parameters/trace-indicator'
- $ref: '#/components/parameters/customer-journey'
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- subscriber-application
- subscriber-release-number
- subscriber-operation
- subscriber-protocol
- subscriber-address
- subscriber-port
properties:
subscriber-application:
type: string
description: >
'Future application name
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-c-nr-2-1-2-000/layer-protocol=0/http-client-interface-1-0:http-client-interface-pac/http-client-interface-configuration/application-name]'
subscriber-release-number:
type: string
description: >
'Future release number
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-c-nr-2-1-2-000/layer-protocol=0/http-client-interface-1-0:http-client-interface-pac/http-client-interface-configuration/release-number]'
subscriber-operation:
type: string
description: >
'Names of the operation that shall be addressed by notifications about documentation of an approval status
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-s-is-003/layer-protocol=0/operation-server-interface-1-0:operation-server-interface-pac/operation-server-interface-capability/operation-name]'
subscriber-protocol:
type: string
description: >
'Protocol to be used for addressing the application in future
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-protocol]'
subscriber-address:
type: object
properties:
ip-address:
type: object
properties:
ipv-4-address:
type: string
description: >
'Future IPv4 address
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/ip-address/ipv-4-address]'
domain-name:
type: string
description: >
'Future Domain name
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/domain-name]'
subscriber-port:
type: integer
description: >
'Future IP address
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-port]'
example:
subscriber-application: 'RegistryOffice'
subscriber-release-number: '2.1.0'
subscriber-operation: '/v1/regard-updated-approval-status'
subscriber-protocol: 'HTTP'
subscriber-address:
ip-address:
ipv-4-address: '1.1.3.17'
subscriber-port: 3017
responses:
'204':
description: 'Subscribed for notifications about approval status updates'
headers:
x-correlator:
schema:
type: string
example: '550e8400-e29b-11d4-a716-446655440000'
description: 'UUID for the service execution flow that allows to correlate requests and responses. Its value must be identical at the response compared with its corresponding request'
exec-time:
schema:
type: integer
example: 1100
description: 'Value written by the service provider, reporting the total elapsed time for the execution, including all the additional processing needed to retrieve the data from the backend service. Expressed in milliseconds'
backend-time:
schema:
type: integer
example: 850
description: 'Value written by the service provider, reporting the elapsed time for data retrieval from the backend (service invocation, database access…). Expressed in milliseconds'
life-cycle-state:
schema:
type: string
enum:
- 'EXPERIMENTAL'
- 'OPERATIONAL'
- 'DEPRECATED'
- 'OBSOLETE'
- 'UNKNOWN'
- 'NOT_YET_DEFINED'
example: 'EXPERIMENTAL'
description: 'Life cycle state of the consumed service'
'400':
$ref: '#/components/responses/responseForErroredServiceRequests'
'401':
$ref: '#/components/responses/responseForErroredServiceRequests'
'403':
$ref: '#/components/responses/responseForErroredServiceRequests'
'404':
$ref: '#/components/responses/responseForErroredServiceRequests'
'500':
$ref: '#/components/responses/responseForErroredServiceRequests'
default:
$ref: '#/components/responses/responseForErroredServiceRequests'
PromptForBequeathingDataCausesRequestForBroadcastingInfoAboutServerReplacement:
url: #[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-ro-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-protocol]://[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-ro-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/domain-name or /core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-ro-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/ip-address/ipv-4-address]:[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-ro-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-port][/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-c-bm-ro-2-1-2-001/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name]
post:
parameters:
- $ref: '#/components/parameters/user'
- $ref: '#/components/parameters/originator'
- $ref: '#/components/parameters/x-correlator'
- $ref: '#/components/parameters/trace-indicator'
- $ref: '#/components/parameters/customer-journey'
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- current-application-name
- current-release-number
- future-application-name
- future-release-number
- future-protocol
- future-address
- future-port
properties:
current-application-name:
type: string
description: >
'Own application name
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-s-000/layer-protocol=0/http-server-interface-1-0:http-server-interface-pac/http-server-interface-capability/application-name]'
current-release-number:
type: string
description: >
'Own release number
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-s-000/layer-protocol=0/http-server-interface-1-0:http-server-interface-pac/http-server-interface-capability/release-number]'
future-application-name:
type: string
description: >
'Future name of the application that has updated connection data
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-c-nr-2-1-2-000/layer-protocol=0/http-client-interface-1-0:http-client-interface-pac/http-client-interface-configuration/application-name]'
future-release-number:
type: string
description: >
'Future release number of the application that has updated connection data
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-c-nr-2-1-2-000/layer-protocol=0/http-client-interface-1-0:http-client-interface-pac/http-client-interface-configuration/release-number]'
future-protocol:
type: string
description: >
'Protocol to be used in future for addressing the application that has updated connection data
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-protocol]'
future-address:
type: object
properties:
ip-address:
type: object
properties:
ipv-4-address:
type: string
description: >
'Future IPv4 address of the application that has updated connection data
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/ip-address/ipv-4-address]'
domain-name:
type: string
description: >
'Future domain name of the application that has updated connection data
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/domain-name]'
future-port:
type: integer
description: >
'Future port of the application that has updated connection data
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-nr-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-port]'
responses:
'204':
description: 'Will broadcast server replacement'
headers:
x-correlator:
schema:
type: string
example: '550e8400-e29b-11d4-a716-446655440000'
description: 'UUID for the service execution flow that allows to correlate requests and responses. Its value must be identical at the response compared with its corresponding request'
exec-time:
schema:
type: integer
example: 1100
description: 'Value written by the service provider, reporting the total elapsed time for the execution, including all the additional processing needed to retrieve the data from the backend service. Expressed in milliseconds'
backend-time:
schema:
type: integer
example: 850
description: 'Value written by the service provider, reporting the elapsed time for data retrieval from the backend (service invocation, database access…). Expressed in milliseconds'
life-cycle-state:
schema:
type: string
enum:
- 'EXPERIMENTAL'
- 'OPERATIONAL'
- 'DEPRECATED'
- 'OBSOLETE'
- 'UNKNOWN'
- 'NOT_YET_DEFINED'
example: 'EXPERIMENTAL'
description: 'Life cycle state of the consumed service'
'400':
$ref: '#/components/responses/responseForErroredServiceRequests'
'401':
$ref: '#/components/responses/responseForErroredServiceRequests'
'403':
$ref: '#/components/responses/responseForErroredServiceRequests'
'404':
$ref: '#/components/responses/responseForErroredServiceRequests'
'500':
$ref: '#/components/responses/responseForErroredServiceRequests'
default:
$ref: '#/components/responses/responseForErroredServiceRequests'
PromptForBequeathingDataCausesRequestForDeregisteringOfOldRelease:
url: #[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-ro-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-protocol]://[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-ro-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/domain-name or /core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-ro-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/ip-address/ipv-4-address]:[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-ro-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-port][/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-c-bm-ro-2-1-2-002/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name]
post:
parameters:
- $ref: '#/components/parameters/user'
- $ref: '#/components/parameters/originator'
- $ref: '#/components/parameters/x-correlator'
- $ref: '#/components/parameters/trace-indicator'
- $ref: '#/components/parameters/customer-journey'
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- application-name
- release-number
properties:
application-name:
type: string
description: >
'Own application name
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-s-000/layer-protocol=0/http-server-interface-1-0:http-server-interface-pac/http-server-interface-capability/application-name]'
release-number:
type: string
description: >
'Own release number
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-s-000/layer-protocol=0/http-server-interface-1-0:http-server-interface-pac/http-server-interface-capability/release-number]'
responses:
'204':
description: 'Application deregistered'
headers:
x-correlator:
schema:
type: string
example: '550e8400-e29b-11d4-a716-446655440000'
description: 'UUID for the service execution flow that allows to correlate requests and responses. Its value must be identical at the response compared with its corresponding request'
exec-time:
schema:
type: integer
example: 1100
description: 'Value written by the service provider, reporting the total elapsed time for the execution, including all the additional processing needed to retrieve the data from the backend service. Expressed in milliseconds'
backend-time:
schema:
type: integer
example: 850
description: 'Value written by the service provider, reporting the elapsed time for data retrieval from the backend (service invocation, database access…). Expressed in milliseconds'
life-cycle-state:
schema:
type: string
enum:
- 'EXPERIMENTAL'
- 'OPERATIONAL'
- 'DEPRECATED'
- 'OBSOLETE'
- 'UNKNOWN'
- 'NOT_YET_DEFINED'
example: 'EXPERIMENTAL'
description: 'Life cycle state of the consumed service'
'400':
$ref: '#/components/responses/responseForErroredServiceRequests'
'401':
$ref: '#/components/responses/responseForErroredServiceRequests'
'403':
$ref: '#/components/responses/responseForErroredServiceRequests'
'404':
$ref: '#/components/responses/responseForErroredServiceRequests'
'500':
$ref: '#/components/responses/responseForErroredServiceRequests'
default:
$ref: '#/components/responses/responseForErroredServiceRequests'
PromptingNewReleaseForUpdatingServerCausesRequestForBroadcastingInfoAboutBackwardCompatibleUpdateOfOperation:
url: #[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-ro-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-protocol]://[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-ro-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/domain-name or /core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-ro-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-address/ip-address/ipv-4-address]:[/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-tcp-c-ro-2-1-2-000/layer-protocol=0/tcp-client-interface-1-0:tcp-client-interface-pac/tcp-client-interface-configuration/remote-port][/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-c-bm-ro-2-1-2-003/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name]
description: >
'This callback belongs to the sequence of actions that have to be done during the bequeath-your-data-and-die process, despite the forwarding gets neither managed nor directly initiated by the /v1/bequeath-your-data-and-die request.
After consuming applications have been redirected to the new release, the new release is triggered (this callback) to request the RegistryOffice for broadcasting information about backward compatible replacements of services.'
post:
parameters:
- $ref: '#/components/parameters/user'
- $ref: '#/components/parameters/originator'
- $ref: '#/components/parameters/x-correlator'
- $ref: '#/components/parameters/trace-indicator'
- $ref: '#/components/parameters/customer-journey'
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- application-name
- release-number
- old-operation-name
- new-operation-name
properties:
application-name:
type: string
description: >
'Own application name
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-s-000/layer-protocol=0/http-server-interface-1-0:http-server-interface-pac/http-server-interface-capability/application-name]'
release-number:
type: string
description: >
'Own release number
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-s-000/layer-protocol=0/http-server-interface-1-0:http-server-interface-pac/http-server-interface-capability/release-number]'
old-operation-name:
type: string
description: >
'Name of the deprecated operation
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-s-*/layer-protocol=0/operation-server-interface-1-0:operation-server-interface-pac/operation-server-interface-capability/operation-name]'
new-operation-name:
type: string
description: >
'Name of the replacing operation
from [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-s-*/layer-protocol=0/operation-server-interface-1-0:operation-server-interface-pac/operation-server-interface-capability/operation-name]'
responses:
'204':
description: 'Will broadcast operation update'
headers:
x-correlator:
schema:
type: string
example: '550e8400-e29b-11d4-a716-446655440000'
description: 'UUID for the service execution flow that allows to correlate requests and responses. Its value must be identical at the response compared with its corresponding request'
exec-time:
schema:
type: integer
example: 1100
description: 'Value written by the service provider, reporting the total elapsed time for the execution, including all the additional processing needed to retrieve the data from the backend service. Expressed in milliseconds'
backend-time:
schema:
type: integer
example: 850
description: 'Value written by the service provider, reporting the elapsed time for data retrieval from the backend (service invocation, database access…). Expressed in milliseconds'
life-cycle-state:
schema:
type: string
enum:
- 'EXPERIMENTAL'
- 'OPERATIONAL'
- 'DEPRECATED'
- 'OBSOLETE'
- 'UNKNOWN'
- 'NOT_YET_DEFINED'
example: 'EXPERIMENTAL'
description: 'Life cycle state of the consumed service'
'400':
$ref: '#/components/responses/responseForErroredServiceRequests'
'401':
$ref: '#/components/responses/responseForErroredServiceRequests'
'403':
$ref: '#/components/responses/responseForErroredServiceRequests'
'404':
$ref: '#/components/responses/responseForErroredServiceRequests'
'500':
$ref: '#/components/responses/responseForErroredServiceRequests'
default:
$ref: '#/components/responses/responseForErroredServiceRequests'
/v1/register-application:
description: >
'DEPRECATED
Service shall be deleted with RO v3.0.0
Starting from AP v2.1.0, /v2/register-application shall be applied as a backward compatible update'
parameters:
- $ref: '#/components/parameters/user'
- $ref: '#/components/parameters/originator'
- $ref: '#/components/parameters/x-correlator'
- $ref: '#/components/parameters/trace-indicator'
- $ref: '#/components/parameters/customer-journey'
post:
operationId: registerApplication
summary: 'Adds to the list of known applications'
tags:
- IndividualServices
description: >
'Registration service is not protected by operationKey.
Receiving a de-registration request shall be assumed after passing wait time to approve
from [/core-model-1-4:control-construct/profile-collection/profile=ro-2-1-2-integer-p-010/integer-profile-1-0:integer-profile-pac/integer-profile-configuration/integer-value]'
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- application-name
- release-number
- embedding-operation
- client-update-operation
- operation-client-update-operation
- tcp-server-list
properties:
application-name:
type: string
pattern: '^([A-Z][a-z0-9]+){2,}$'
description: >
'Name of application that wants to register
find, but not at OldRelease or NewRelease, or create [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-c-*/layer-protocol=0/http-client-interface-1-0:http-client-interface-pac/http-client-interface-configuration/application-name]'
release-number:
type: string
pattern: '^([0-9]{1,2})\.([0-9]{1,2})\.([0-9]{1,2})$'
description: >
'Release of application that wants to register
find, but not at OldRelease or NewRelease, or create [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-http-c-*/layer-protocol=0/http-client-interface-1-0:http-client-interface-pac/http-client-interface-configuration/release-number]'
preceding-application-name:
type: string
minLength: 3
description: >
'If provided, the new application will address /v1/bequeath-your-data-and-die at the preceding application after receiving /v1/embed-yourself
update or create in LOADfile'
preceding-release-number:
type: string
pattern: '^([0-9]{1,2})\.([0-9]{1,2})\.([0-9]{1,2})$'
description: >
'If provided, the new application will address /v1/bequeath-your-data-and-die at the preceding release after receiving /v1/embed-yourself
update or create in LOADfile'
embedding-operation:
type: string
minLength: 6
description: >
'Name of service for initiating embedding process
update or create [/core-model-1-4:control-construct/logical-termination-point=ro-2-1-2-op-c-im-*-*-*-*-000/layer-protocol=0/operation-client-interface-1-0:operation-client-interface-pac/operation-client-interface-configuration/operation-name]'
client-update-operation:
type: string
minLength: 6
description: >
'Name of service for broadcasting server changes