The Runtime is using specific ports for its log database and services.
All can be configured easily in the Runtime property files, as shown in this article.
Configuration
The default configuration file can be found under the following path:
- Runtime version ≥ 17.4.x : <stambiaRuntime>/properties/engineParameters.xml
- Previous versions : <stambiaRuntime>/properties/engines/engineParameters42000.xml
...
<parameter name="rmiPort" value="42000"/>
<!--<parameter name="rmiCallbackPort" value="42000"/>-->
<parameter name="internalDbTcpPort" value="42100"/>
<parameter name="internalDbWebPort" value="42101"/>
<parameter name="soapServerPort" value="42200"/>
...
If you are planning to have multiple Runtimes on the same machine, each Runtime must have its own Ports.
If you change the internalDbTcpPort and if the Runtime uses this internalDb as a Log Database, then also edit the userLogRdbmsUrl property with the correct port:
...
<parameter name="userLogRdbmsDriver" value="org.h2.Driver"/>
<parameter name="userLogRdbmsUrl" value="jdbc:h2:tcp://localhost:42100/sessions/internalDb/sessionLogs"/>
...
If you want to use a different log database, refer to this article.
Note: For more detailed information about all the parameters of these files, please consult the Designer's Help Contents.Help > Help Contents > Stambia > Configuration and setup Guide > Runtime parameters referential
Stopping a Runtime running on a different port
When using engines not running on the default port, the use of stopengine.bat (or .sh) will not work.
To stop it, a parameter needs to be added to the command:
- stopengine.bat -port <runtimePort>