The OofPciPocDmaapConsumers.java DMAAP listener code (similar to other DMAAP listeners also in the same folder), uses  system environment variable (DMAAPLISTENERROOT) to determine other rootDir sub-folders, such as lib where map files are transferred:
 
https://gerrit.onap.org/r/gitweb?p=ccsdk/sli/northbound.git;a=tree;f=dmaap-listener/src/main/java/org/onap/ccsdk/sli/northbound/dmaapclient;h=08cc3812568454e18205a8887767fee3fe280150;hb=refs/heads/master
 
It is expected that this DMAAPLISTENERROOT system variable is set to "/opt/onap/sdnc/dmaap-listener" as done in the docker entry script (start-dmaap-listener.sh):
 
https://gerrit.onap.org/r/gitweb?p=sdnc/oam.git;a=blob;f=installation/dmaap-listener/src/main/scripts/start-dmaap-listener.sh;h=6a8eb13dfad5497401a9b63a31710dd057c9d08a;hb=refs/heads/master
 
This variable is NOt set in the Dockerfile.
 
The OofPciPocDmaapConsumers.java file populates this variable as follows (lines; 80-87), and when it read this value as NULL and populates rootDir as /opt/app/dmaap-listener/lib/
 
        rootDir = System.getenv(DMAAPLISTENERROOT);

        if ((rootDir == null) || (rootDir.length() == 0))

{             rootDir = "/opt/app/dmaap-listener/lib/";         }

        else

{             rootDir = rootDir + "/lib/";         }

 
This code was leveraged from the past and also used in other DMAAP listeners (such as, SdncAaiDmaapConsumer.java in the same folder). 
 
when dmaap-listener docker is started (also in SB-04), we are getting the below error, and because of this we are also not able to invoke appropriate DG.
 
bash-4.4# more dmaap-listener.out 
Starting dmaap-listener
ERROR 2019-06-06 21:23:45.518 +0000 OofPciPocDmaapConsumers - Cannot read map file (/opt/app/dmaap-listener/lib/pci-changes-from-policy-to-sdnr.map)
ERROR 2019-06-07 12:07:04.346 +0000 OofPciPocDmaapConsumers - Cannot read map file (/opt/app/dmaap-listener/lib/pci-changes-from-policy-to-sdnr.map)
ERROR 2019-06-07 12:29:39.119 +0000 OofPciPocDmaapConsumers - Cannot read map file (/opt/app/dmaap-listener/lib/pci-changes-from-policy-to-sdnr.map)
 
I would appreciate if you please advise how to address this...Maybe some configuration is required, may be in HELM charts?