aboutsummaryrefslogtreecommitdiffstats
path: root/services/services-engine/src/site-docs/adoc/fragments/config-general-format.adoc
blob: 27e076701806d2ff6ca5e7dbbd4940b9c3f0d2d8 (plain)
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
//
// ============LICENSE_START=======================================================
//  Copyright (C) 2016-2018 Ericsson. All rights reserved.
// ================================================================================
// This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE
// Full license text at https://creativecommons.org/licenses/by/4.0/legalcode
// 
// SPDX-License-Identifier: CC-BY-4.0
// ============LICENSE_END=========================================================
//
// @author Sven van der Meer (sven.van.der.meer@ericsson.com)
//

== General Configuration Format

The APEX configuration file is a JSON file containing a few main blocks for different parts of the configuration.
Each block then holds the configuration details.
The following code shows the main blocks:

[source%nowrap,json]
----
{
  "engineServiceParameters":{
    ... // <1>
    "engineParameters":{ <2>
      "engineParameters":{...}, <3>
      "contextParameters":{...} <4>
    }
  },
  "eventInputParameters":{ <5>
    "input1":{ <6>
      "carrierTechnologyParameters":{...},
      "eventProtocolParameters":{...}
    },
    "input2":{...}, <7>
      "carrierTechnologyParameters":{...},
      "eventProtocolParameters":{...}
    },
    ... // <8>
  },
  "eventOutputParameters":{ <9>
    "output1":{ <10>
      "carrierTechnologyParameters":{...},
      "eventProtocolParameters":{...}
    },
    "output2":{ <11>
      "carrierTechnologyParameters":{...},
      "eventProtocolParameters":{...}
    },
    ... // <12>
  }
}
----
<1> main engine configuration
<2> engine parameters for plugin configurations (execution environments and context handling)
<3> engine specific parameters, mainly for executor plugins
<4> context specific parameters, e.g. for context schemas, persistence, etc.
<5> configuration of the input interface
<6> an example input called `input1` with carrier technology and event protocol
<7> an example input called `input2` with carrier technology and event protocol
<8> any further input configuration
<9> configuration of the output interface
<10> an example output called `output1` with carrier technology and event protocol
<11> an example output called `output2` with carrier technology and event protocol
<12> any further output configuration