2.6 Starting Registration Handler and resource management

This steps are for manual configuration and starting of Registration Handler. If you used symbioteCloud.sh this is done for you.

2.6.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 Registration Handler 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.6.2. Building and starting RH

Build and start Registration Handler as any other Symbiote component.

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

If you start all components in one script then it is important order of starting components and that some of then are fish starting before others because some of them are dependent on function of others on startup. For example, RegistrationnHandler must be started after AuthenticationAuthorizationManager is started. The same applies to ResourceAccessProxy. There are two ways to configure them to start after others:

1. Environment variables - set following environment variable:
   • SPRING_BOOT_WAIT_FOR_SERVICES=localhost:8080
2. Command line options:
   • java -DSPRING_BOOT_WAIT_FOR_SERVICES="localhost:8080" -jar build/libs/RegistrationHandler-1.2.0-run.jar

When the service is started it will try to connect to specified host and port and retry it after 1 second. It will repeat it for 1000 times for each specified service. After it can connect to that port it will continue with starting of service. The format for value is "host1:port1;host2:port2;..."

For testing if service is working as expected open http://127.0.0.1:8001/resources. You should get empty JSON array because no resource is registered. You can access it over NGINX:

1. Production - http://sybiotedoc.tel.fer.hr/rh/resources
2. Hackaton - https://b2cb3e08.ngrok.io/rh/resources