| ramverma | af74a62 | 2018-07-31 18:25:39 +0100 | [diff] [blame] | 1 | // |
| 2 | // ============LICENSE_START======================================================= |
| 3 | // Copyright (C) 2016-2018 Ericsson. All rights reserved. |
| 4 | // ================================================================================ |
| 5 | // This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE |
| 6 | // Full license text at https://creativecommons.org/licenses/by/4.0/legalcode |
| 7 | // |
| 8 | // SPDX-License-Identifier: CC-BY-4.0 |
| 9 | // ============LICENSE_END========================================================= |
| 10 | // |
| 11 | // @author Sven van der Meer (sven.van.der.meer@ericsson.com) |
| 12 | // |
| 13 | |
| 14 | == Introduction to APEX Configuration |
| 15 | |
| 16 | An APEX engine can be configured to use various combinations of |
| 17 | event input handlers, |
| 18 | event output handlers, |
| 19 | event protocols, |
| 20 | context handlers, and |
| 21 | logic executors. |
| 22 | The system is build using a plugin architecture. |
| 23 | Each configuration option is realized by a plugin, which can be loaded and configured when the engine is started. |
| 24 | New plugins can be added to the system at any time, though to benefit from a new plugin an engine will need to be restarted. |
| 25 | |
| 26 | .APEX Configuration Matrix |
| 27 | image::apex-intro/ApexEngineConfig.png[APEX Configuration Matrix] |
| 28 | |
| 29 | The APEX distribution already comes with a number of plugins. |
| 30 | The figure above shows the provided plugins. |
| 31 | Any combination of input, output, event protocol, context handlers, and executors is possible. |