We need to migrate E2M & E2T to the latest RMR library.

RMR wiki in Confluence: https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=3605041

The current version is 3.2.3 links to the .deb/.rpms:

https://packagecloud.io/o-ran-sc/staging/packages/debian/stretch/rmr_3.2.3_amd64.deb

https://packagecloud.io/o-ran-sc/staging/packages/debian/stretch/rmr-dev_3.2.3_amd64.deb

https://packagecloud.io/o-ran-sc/staging/packages/el/5/rmr-devel-3.2.3-1.x86_64.rpm

https://packagecloud.io/o-ran-sc/staging/packages/el/5/rmr-3.2.3-1.x86_64.rpm

These packages have support for both the SI95 and the NNG transport mechanisms, so you can pull them and build with your current CMake/Make environment to run an initial test, then flip to using the SI95 when ready.

The API is identical, so all that should be needed to switch to using SI95 is to change the library reference in your CMake or Makefile to something like this:

gcc sender.c -g -o sender -lrmr_si  -lpthread -lm

 Please note, all applications on the same RIC instance will need to be using the same transport (NNG or SI95) in order to be able to communicate.

Related to the need for all xAPPs to be using the same transport library, when the Route Manager begins to support a request for a route table load from RMR, there will be a new environment variable, and the RMR_RTG_SVC variable value will need to change to reference the Route Manager. Scott need to talk to either Felix or Lusheng about how these factor into a container's setup.  

Please contact Scott (DANIELS, EDWARD <daniels@research.att.com>) if you have any questions, or have difficulty finding the packages.

Acceptance criteria:

Automation passed successfully.