Connection on the Runtime by clients such as Stambia DI Designer or Stambia DI Production Analytics are performed through the RMI service which is exposed.
This RMI service can be configured to be secured through TLS with little configuration.
Prerequisites:
- Stambia DI Designer S19.0.12 or higher
- Stambia DI Runtime S17.6.0 or higher
Configuration
Activating TLS for the RMI service
Open the <stambiaRuntime>/properties/engineParameters.xml file.
Then change the value of the "rmiEnableTls" parameter to true:
<parameters>
<...>
<engineParameters>
<...>
<parameter name="rmiEnableTls" value="true"/>
<...>
</engineParameters>
<...>
</parameters>
That's it, when restarting the Runtime the RMI service will be secured through TLS.
About the TLS version used
The TLS version used will vary depending on the JVM version used.
You can find below the standard for the 1.6, 1.7, and 1.8 Java versions.
Please refer to the Java reference documentation of your version for further information.
| Java Version | 1.6 | 1.7 | 1.8 |
| TLS version used | TLSv1 | TLSv1 | TLSv1.2 |
Connecting to TLS secured Runtime from Stambia DI Designer
Nothing has to be done on the Designer side, simply connect to the Runtime and let the Designer handle everything.
When the connection to the Runtime is secured through TLS, the icon in the Runtime view is the following:
Prerequisites:
- Stambia DI Designer S19.0.12 or higher
Connecting to TLS secured Runtime from Stambia DI Production Analytics
As for the Designer, nothing has to be done on Analytics side, simply connect to the Runtime and let Analytics handle everything.
Prerequisites:
- Stambia DI Production Analytics 2.3.0 or higher