Improved logging

Fixed problem with startup which lead
to that the REST API was not working running
locally.

Fixed problem with DmaapProducerHttpClient which would use
no timeout, which can lead to infinitly haninging threads.
A long timeout is used instead.

Change-Id: I28469b1b3aaad0dab4cf247bb8af968e71a60133
Issue-ID: DCAEGEN2-1305
Signed-off-by: PatrikBuhr <patrik.buhr@est.tech>
22 files changed
tree: e0d5d295e8419311f7f53b2baa0501e395150163
  1. datafile-app-server/
  2. datafile-commons/
  3. datafile-dmaap-client/
  4. docker-compose/
  5. .gitignore
  6. .gitreview
  7. INFO.yaml
  8. LICENSE.txt
  9. pom.xml
  10. README.md
  11. swagger.yaml
  12. version.properties
README.md

DFC (DataFile Collector)

Datafile Collector is responsible for collecting PM counter files from PNF (Physical Network Function) and then publish these files to Dmaap DataRouter.

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