Due to some maintenance operations, stambia.org will be switched to read-only mode during the 13th November. It will be possible to read and download, but impossible to post on the forums or create new accounts. For any question please contact the support team.
Runtime configuration file can be dynamized using environment variables and Java Properties.
When starting, the Runtime will automatically retrieve and use the specified variables, with a mechanism allowing to specify a default value if it does not exist.
Prerequisites:
- Stambia DI Runtime S17.6.2 or higher
Read more: Using environment variables and java properties in the configuration file
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
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 |
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
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
The Runtime offers the possibility to specify a list of keystores in its configuration file.
You can find below how to define them and then how to use them.
Passwords, mostly configured in Metadata by users, are encrypted to not appear in clear in the delivery files or in the logs for instance.
The key used by a Stambia DI Runtime to encrypt or decrypt passwords can be customized in configuration files.
This article demonstrates how to configure the Stambia DI Runtime to change it.
When the Runtime needs a connection to a JDBC Database, it will open a new connection, perform the operation, and then close it at the end of the session.
The same behavior applies for all the operations on the Runtime's Log Database.
This is the default behavior, which can be modified in properties to enable connection pooling to mutualize connections, as explained in this article.