diff options
| author |   liamfallon <liam.fallon@est.tech> | 2020-10-16 13:09:11 +0100 |
|---|---|---|
| committer | liamfallon <liam.fallon@est.tech> | 2020-10-16 13:09:16 +0100 |
| commit | 0cf967c0239a8ab9c8b8831b700b72d9a08f7b03 (patch) | |
| tree | a4fbcd97008769d55ac443bc22abf517308bf6a7 /examples/examples-myfirstpolicy/src/site-docs/adoc/fragments/01-introduction.adoc | |
| parent | 9833876720ff14517ee78bda557e6021df723800 (diff) | |
Remove apex asciidoc documents
Apex documentation has now all been ported to use the ONAP recommended
rst format. This review removes the old asciidoc documents.
Issue-ID: POLICY-2824
Change-Id: I562bd344cb7d6ff36e7d54bdb8f95e3b656468f8
Signed-off-by: liamfallon <liam.fallon@est.tech>
Diffstat (limited to 'examples/examples-myfirstpolicy/src/site-docs/adoc/fragments/01-introduction.adoc')
| -rw-r--r-- | examples/examples-myfirstpolicy/src/site-docs/adoc/fragments/01-introduction.adoc | 25 |
1 files changed, 0 insertions, 25 deletions
diff --git a/examples/examples-myfirstpolicy/src/site-docs/adoc/fragments/01-introduction.adoc b/examples/examples-myfirstpolicy/src/site-docs/adoc/fragments/01-introduction.adoc deleted file mode 100644 index 02a7a0e76..000000000 --- a/examples/examples-myfirstpolicy/src/site-docs/adoc/fragments/01-introduction.adoc +++ /dev/null @@ -1,25 +0,0 @@ -// -// ============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) -// - -== Introduction - -Consider a scenario where a supermarket chain called _HyperM_ controls how it sells items in a policy-based manner. -Each time an item is processed by _HyperM_'s point-of-sale (PoS) system an event is generated and published about that item of stock being sold. -This event can then be used to update stock levels, etc.. - -__HyperM__ want to extend this approach to allow some checks to be performed before the sale can be completed. -This can be achieved by requesting a policy-controlled decision as each item is processed by for sale by each PoS system. -The decision process is integrated with __HyperM__'s other IT systems that manage stock control, sourcing and purchasing, personnel systems, etc. - -In this document we will show how APEX and APEX Policies can be used to achieve this, starting with a simple policy, building up to more complicated policy that demonstrates the features of APEX. - |