Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.
The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…
Jython is a language which can be used in scripting actions, allowing to use Python scripts in Java.
On a default installation Jython 2.2 version is shipped and used.
You can now change the Jython version used by the Runtime.
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
Java options are generally added directly to the Java command launching the Runtime with the -DmyOption01=value01 argument.
The Stambia DI Runtime allows to set them in a more convenient way directly in its configuration file.
All the options specified will then be loaded just after the Runtime's start.
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.
The Stambia Web Services which are designed to have Input and Output files will generate these at invocation.
By default, they are deleted except if the invocation ends with errors, but this can be configured in the Runtime properties.
Read more: Automatically deleting the temporary files generated at Web Services invocation