2.7 Set up of Resource Access Proxy

Resource Access Proxy (RAP) is the component in charge of accessing to the resources. This requires the implementation of a software layer (the RAP platform plugin) in order to allow symbIoTe to be able to communicate with the internal mechanisms of the platform. The plugin will communicate with the generic part of the RAP through the rabbitMQ protocol, in order to decouple the symbIoTe Java implementation from the platform specific language. This figure shows the architecture of the RAP component (orange parts on the bottom are part of the platform specific plugin, to be implemented from platform owners):

Here a quick list of actions and features that RAP platform specific plugin has to implement:

• Registers to generic RAP specifying support for filters, notifications
• Get read / write requests from RAP generic (w/ or w/o filters)
• Applies filters to =E2=80=98get history=E2=80=99 requests (optional)
• Actuate actuators
• Invoke services provided by platform
• Get subscribe requests from generic RAP (if it supports notifications)
• Forwards notifications coming from platform to generic RAP

Source, from RAP repository, has already implemented dummy example of RAP plugin with one dummy sensor, actuator and service.

There are 3 way to create RAP plugin:

1. Use dummy plugin already provided in source and extend it with your functionality. This way every time something need to be changed in RAP plugin you have to recompile whole RAP component and redeploy in production environment.
2. Use RAP plugin starter project. I this way you need to create another SpringBoot component in Java for implementing RAP plugin. You also need to start this new component on the machine that has access to RabbitMQ server.
3. Implement RabbitMQ communication in any language you want.

All 3 approaches are explained later in this document.

In order to just start RAP and test whole process of installing components and checking that everything is working we will use approach 1 with default implementation. For this case you need to change the configuration as explained here

2.7.1 Creating configuration for accessing PAAM

If you have downloaded from Administration the .zip containing the configuration files, then you can use the bootstrap.properties file contained in the RegistrationHandler folder. You just need to move it to the RAP directory. Otherwise, you will have to create it yourselves with the following content:

# The credentials of the Platform Owner account in the PAAM
symbIoTe.component.username=TODO
symbIoTe.component.password=TODO

# Keystore configuration
symbIoTe.component.keystore.path=keystore.jks
symbIoTe.component.keystore.password=pass

This is concrete file for our example:

# The credentials of the Platform Owner account in the PAAM
symbIoTe.component.username=masterPaamUsername
symbIoTe.component.password=masterPaamPassword

# Keystore configuration
symbIoTe.component.keystore.path=keystore.jks
symbIoTe.component.keystore.password=pass

2.7.1 Building and starting RAP

Build and start Registration Handler as any other Symbiote component.

$ cd /opt/symbiote/SymbioteCloud/ResourceAccessProxy
$ gradle assemble --refresh-dependencies
$ java -jar build/libs/ResourceAccessProxy-1.2.3-run.jar

If you want to put starting RAP from script and need to wait for PAAM apply same approach as for RH.