Page History

...

To verify that the PM Mapper is working as it should, we can publish a 3GPP XML file to the PM Mapper, and verify that the output on Message Router is:

...

counters in the VES match what we expect based on our filtering.

To publish a file to the PM Mapper we can use the following example curl. Where <filename> Must begin with A or C and the file extension must be . xml.

curl -k -X PUT https://dcae-pm-mapper:8443/delivery/<filename> -H 'X-DMAAP-DR-META:{"productName": "Acme","vendorName": "Acme","lastEpochMicrosec": "1538478000000","sourceName": "oteNB5309","startEpochMicrosec": "1538478900000","timeZoneOffset": "UTC+05:00","location": "ftpes://127.0.0.1:22/ftp/rop/A20161224.1045-1100.bin.gz","compression": "gzip","fileFormatType": "org.3GPP.32.435#measCollec","fileFormatVersion": "V9"}' -H "Content-Type:application/xml" --data-binary @<filename> -H 'X-ONAP-RequestID: 12345' -H 'X-DMAAP-DR-PUBLISH-ID: 12345'

We can then check that the XML has been processed and published to Message Router as a VES event by curling the PM Mapper topic on Message Router.

We first need to set up a subscriber to the PM Mapper topic as this is not set up by default. We can do this with the following curl to Bus Controller:

curl -X POST http://dmaap-bc:8080/webapi/mr_clients -H "Content-Type:application/json" --data @sub-client.json

Once the subscriber is set up, we can curl the topic on Message Router to retrieve the published event:

curl -k https:

curl -k https://message-router:3905/events/org.onap.dmaap.mr.PM_MAPPER -u 'dcae@dcae.onap.org:<password>'

...

Configuration

Configuration of the service consists of generating an inputs file which will be used as part of the Cloudify install. The PM-Mapper blueprints were designed with sane defaults for the majority of the fields.
Below you will find some examples of fields which can be configured, and some of the fields which must be configured.

...