blob: 82f58edc0839d48e82669f3230e997f5304c2af4 (
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
|
# DFC (DataFile Collector)
Physical Network Function Registration Handler is responsible for registration of PNF (Physical Network Function) to
ONAP (Open Network Automation Platform) in plug and play manner.
## Introduction
DFC is delivered as one **Docker container** which hosts application server and can be started by `docker-compose`.
## Compiling DFC
Whole project (top level of DFC directory) and each module (sub module directory) can be compiled using
`mvn clean install` command.
## Main API Endpoints
Running with dev-mode of DFC
- **Heartbeat**: http://<container_address>:8100/**heartbeat** or https://<container_address>:8443/**heartbeat**
- **Start DFC**: http://<container_address>:8100/**start** or https://<container_address>:8433/**start**
- **Stop DFC**: http://<container_address>:8100/**stopDatafile** or https://<container_address>:8433/**stopDatafile**
## Maven GroupId:
org.onap.dcaegen2.collectors
### Maven Parent ArtifactId:
dcae-services
### Maven Children Artifacts:
1. datafile-app-server: Datafile Collector (DFC) server
2. datafile-commons: Common code for whole dfc modules
3. datafile-dmaap-client: http client used to connect to dmaap message router/data router
## License
Copyright (C) 2018-2019 NOKIA Intellectual Property, 2018-2019 Nordix Foundation. All rights reserved.
[License](http://www.apache.org/licenses/LICENSE-2.0)
|
