...
Create the file type_config.json with the content below:
Code Block | ||
---|---|---|
| ||
{ |
...
"types": |
...
[ { "id": |
...
"STD_Fault_Messages", |
...
"dmaapTopicUrl": |
...
"/events/unauthenticated.dmaapmed.json/dmaapmediatorproducer/STD_Fault_Messages?timeout=15000&limit=100" |
...
} ] } |
There are a number of environment variables that need to be set when starting the application. See these example settings:
...
Start the Dmaap Mediator Producer in a separate shell with the following command:
file >
|
Setup jobs to produce data according to the types in type_config.json
Create a file job3.json with the job definition (replace paths <url-for-jod-data-delivery> and <url-for-jod-status-delivery> to fit your environment:
Code Block | ||
---|---|---|
| ||
{ |
...
"info_type_id": |
...
"STD_Fault_Messages", |
...
"job_result_uri": |
...
"<url-for-job-data-delivery>", |
...
"job_owner": |
...
"job3owner", |
...
"status_notification_uri": |
...
"<url-for-job-status-delivery>", |
...
"job_definition": {} |
...
} |
Create job3 for type 'ExampleInformationType'
|
Check that the job has been enabled - job accepted by the Dmaap Adapter Service
...
Data posted on the message router topic unauthenticated.dmaapmed.json will be delivered to the path as specified in the job3.json
Run usecases
Within NON-RT RIC a number of usecase implementations are provided. Follow the links below to see how to run them.
...
Run use cases
Within NON-RT RIC a number of use case implementations are provided. Follow the links below to see how to run them.
...