4.0.0 dmaap-bc ${revision} dmaap-bc jar org.onap.dmaap.buscontroller parent ${revision} ../pom.xml Data Movement as a Platform (DMaaP) Bus Controller provides a REST API for other DCAE infrastructure components to provision DMaaP resources. A DMaaP resource is a Data Router Feed or a Message Router Topic, and their associated publishers and subscribers. /content/sites/site/${project.groupId}/${project.artifactId}/${project.version} 1.0.0 ${docker.image.root}${project.artifactId} 1.5.19 2.9.5 2.29 UTF-8 9.4.40.v20210413 1.0.0 4.12 **/gen/**,**/generated-sources/**,**/yang-gen**,**/pax/** /target/docker-stage/opt/app/dmaapbc/ org.glassfish.jersey jersey-bom ${jersey.version} pom import org.glassfish.jersey.media jersey-media-json-jackson org.glassfish.jersey.containers jersey-container-servlet-core org.glassfish.jersey.media jersey-media-moxy org.glassfish.jersey.test-framework.providers jersey-test-framework-provider-jdk-http 2.29.1 org.glassfish.jersey.inject jersey-hk2 2.29.1 org.onap.aaf.authz aaf-cadi-aaf 2.1.7 full log4j log4j com.fasterxml.jackson.core jackson-annotations ${jackson.version} com.fasterxml.jackson.dataformat jackson-dataformat-yaml ${jackson.version} snakeyaml org.yaml ch.qos.logback logback-core 1.2.3 ch.qos.logback logback-classic 1.2.3 com.google.guava guava 24.1.1-jre io.swagger swagger-core ${swagger.version} com.fasterxml.jackson.core jackson-databind io.swagger swagger-jersey2-jaxrs ${swagger.version} jersey-common org.glassfish.jersey.core io.swagger swagger-annotations ${swagger.version} org.eclipse.jetty jetty-server ${jettyVersion} compile org.eclipse.jetty jetty-servlet ${jettyVersion} compile org.eclipse.jetty jetty-servlets 9.4.41.v20210516 compile org.eclipse.jetty jetty-http ${jettyVersion} compile com.googlecode.json-simple json-simple 1.1.1 commons-codec commons-codec 1.15 org.postgresql postgresql 42.2.14 org.slf4j slf4j-api 1.7.22 javax.xml.bind jaxb-api 2.3.1 junit junit ${junit.version} test pl.pragmatists JUnitParams 1.1.0 test org.mockito mockito-core 3.9.0 test org.apache.maven.plugins maven-enforcer-plugin 3.0.0-M3 commons-io commons-io maven-compat org.apache.maven maven-settings org.apache.maven maven-shared-utils org.apache.maven.shared bsh org.beanshell com.att.eelf eelf-core ${eelf.version} org.mockito mockito-core org.powermock powermock-module-junit4 org.powermock powermock-api-mockito dmaap-bc ${basedir}/target/docker-stage ${basedir}/src/main/resources/docker Dockerfile ${basedir}${docker-stage.target.path}etc ${basedir}/src/main/resources/misc logback.xml LocalKey ${basedir}${docker-stage.target.path}etc ${multiproject.basedir} version.properties ${basedir}${docker-stage.target.path}misc ${basedir}/src/main/resources/misc *.tmpl ${basedir}${docker-stage.target.path}bin ${basedir}/src/main/resources/misc dmaapbc ${basedir}${docker-stage.target.path}misc ${basedir}/src/main/resources/misc schema_all.sql maven-assembly-plugin 2.4 jar-with-dependencies ${basedir}/target/docker-stage/opt/app/dmaapbc/lib true org.onap.dmaap.dbcapi.server.Main dmaap-bc.jar false make-assembly package single maven-checkstyle-plugin onap-java-style false com.github.kongchen swagger-maven-plugin 3.1.5 false org.onap.dmaap.dbcapi.resources http https www.[host]:[port] /webapi 1.1.0 provides an API for OpenDCAE components which need to provision underlying DMaaP technologies (Data Router and Message Router). Primary clients for this API are anticipated to be the OpenDCAE Controller, OpenDCAE Orchestrator, OpenDCAE Inventory and the ECOMP Portal. Objects managed by DMaaP are deployed in a dcaeLocation which is a unique identifier for an OpenStack tenant for a dcaeLayer, opendcae-central (aka ecomp) or opendcae-local-ntc (aka edge). A dcaeEnvironment (e.g. FTL or prod) has a single DMaaP. A DMaaP is managed by a one or more stateless DMaaP Bus Controller(s), though Bus Controller relies on PGaaS for persistence. Each DMaaP has a single instance of Data Router, which has 1 or more DR_Nodes deployed at each dcaeLocation. DR Clients of type DR_Pub generally publish to a DR_Node that is local to its dcaeLocation. Routing for a Feed is determined by the dcaelocation of its DR_Sub clients. A DMaaP may have many Message Router instances. Each instance is deployed as an MR_Cluster. One MR_Cluster is deployed at each dcaeLocation. MR_Clients generally communicate to the MR_Cluster at the same dcaeLocation. Replication of messages between MR_Clusters is accomplished by MR Bridge, which is provioned by DMaaP Bus Controller based on Topic attributes. Therefore, the role of DMaaP Bus Controller is to support other DCAE infrastructure components to dynamically provision DMaaP services on behalf of DMaaP clients, and to assist in any management or discovery activity of its clients. A convention of this API is to return JSON responses per OpenStack style. http://www.apache.org/licenses/LICENSE-2.0 http://www.onap.org http://www.apache.org/licenses/LICENSE-2.0 Licensed under the Apache License, Version 2.0 target/generated-sources/ compile generate docker ${skip.docker.build} false org.codehaus.gmaven gmaven-plugin io.fabric8 docker-maven-plugin ${dmaapbc.image.name} try true true ${basedir}/target/docker-stage Dockerfile ${dockertag1} ${dockertag2} generate-images install build push-images deploy push org.apache.maven.plugins maven-javadoc-plugin 2.10.4 false org.umlgraph.doclet.UmlGraphDoc org.umlgraph umlgraph 5.6 -views true ecomp-site dav:${nexusproxy}${sitePath}