Configure SCP as HTTP Proxy

Customer NFs are required to set http_proxy/HTTP_PROXY to scp-worker's <FQDN or IPV4 address>:<PORT of SCP-Worker> for customer NFs to route messages towards SCP.

Also all NFs are required to register with NRF so that SCP can create rules based on the notifications from NRF.

Note:

Execute this command from where SCP worker and FQDN can be accessed.

Table 2-7 Configure SCP as HTTP Proxy

Step #	Procedure	Description
1	Test successful deploy of SCP	To test SCP deployed successfully and is able to receive message as an proxy and route it to the appropriate producer, use the below curl command: $ curl -v -X GET --url 'http://<FQDN:PORT of SCP-Worker>/nnrf-nfm/v1/subscriptions/' --header 'Host:<FQDN:PORT of NRF>'
2	Fetch the current subscription list	The curl command is to fetch the current subscription list (as a client) from NRF by sending the request to NRF via SCP. Example: $ curl -v -X GET --url 'http://scp-worker.scpsvc:8000/nnrf-nfm/v1/subscriptions/' --header 'Host:ocnrf-ambassador.nrfsvc:80'

Step #

Procedure

Description

Test successful deploy of SCP

To test SCP deployed successfully and is able to receive message as an proxy and route it to the appropriate producer, use the below curl command:

$ curl -v -X GET --url 'http://<FQDN:PORT of SCP-Worker>/nnrf-nfm/v1/subscriptions/' --header 'Host:<FQDN:PORT of NRF>'

Fetch the current subscription list

The curl command is to fetch the current subscription list (as a client) from NRF by sending the request to NRF via SCP.

Example:

$ curl -v -X GET --url 'http://scp-worker.scpsvc:8000/nnrf-nfm/v1/subscriptions/' --header 'Host:ocnrf-ambassador.nrfsvc:80'