This is documentation for Semarchy xDI 2023.2, which is no longer supported. For more information, see our Global Support and Maintenance Policy. |
Configure Runtime Services
Services Overview
The Semarchy xDI Runtime exposes multiple services:
-
An Internal H2 Database, which is the default destination for the sessions and schedules logs. Its default ports are 42100 for JDBC access and 42101 for HTTP access.
-
An HTTP (REST and SOAP) Service, exposing endpoints to communicate with the Runtime and also start deliveries. Its default port is 42200.
-
A built-in Scheduler Service.
You may have to configure these services to accomodate network and security rules.
Configure Services
You can configure these services in the following section of the engineParameters.xml
configuration file.
<parameters>
<...>
<engineParameters>
<...>
<!-- Services startup -->
<parameter name="launchSchedulerEngine" value="true"/>
<parameter name="launchExecutionEngine" value="true"/>
<parameter name="startInternalDb" value="true"/>
<parameter name="httpHost" value="localhost"/>
<...>
<!-- Services Ports -->
<parameter name="internalDbTcpPort" value="42100"/>
<parameter name="internalDbWebPort" value="42101"/>
<parameter name="httpServerPort" value="42200"/>
<...>
</engineParameters>
<...>
</parameters>
The following table lists the parameters available to configure these services and their listening ports.
Parameter | Default value | Description |
---|---|---|
|
|
Start the built-in scheduler. |
|
|
Start the execution engine. |
|
|
Start an internal H2 database. |
|
|
Internal database TCP port for JDBC access. |
|
|
Internal database port for web access. |
|
|
The HTTP (REST and SOAP) endpoints host (IP address or hostname). You can specify it for specific network configurations. For example, when there are multiple domains, or when address translation generate different IP addresses for the same host. It defaults to localhost when undefined. |
|
|
Listening port for the HTTP (REST and SOAP) endpoints. |
You can also secure the communication with these services. See Runtime Security for more details.