Configure Runtime Services

Services Overview

The Semarchy xDI Runtime exposes multiple services:

An RMI Service for Java applications (Designer and Semarchy xDI Production Analytics) to communicate with the Runtime. Its default port is 42000.
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.
A REST/SOAP Service, exposing endpoints to 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.

Example 1. Service configuration

<parameters>
  <...>
  <engineParameters>
	<...>
	<!-- Services startup -->
	<parameter name="launchSchedulerEngine" value="true"/>
	<parameter name="launchExecutionEngine" value="true"/>
	<parameter name="startInternalDb" value="true"/>
	<parameter name="startSoapServer" value="true"/>
	<parameter name="rmiHost" value="localhost"/>
	<parameter name="soapHost" value="localhost"/>
	<...>
	<!-- Services Ports -->
	<parameter name="rmiPort" value="42000"/>
	<parameter name="internalDbTcpPort" value="42100"/>
	<parameter name="internalDbWebPort" value="42101"/>
	<parameter name="soapServerPort" value="42200"/>
	<...>
  </engineParameters>
  <...>
</parameters>

The following table lists the parameters available to configure these services and their listening ports.

Parameter Default value Description

Parameter	Default value	Description
`launchSchedulerEngine`	`true`	Start the built-in scheduler.
`launchExecutionEngine`	`true`	Start the execution engine.
`startInternalDb`	`true`	Start an internal H2 database.
`internalDbTcpPort`	`42100`	Internal database TCP port for JDBC access.
`internalDbWebPort`	`42101`	Internal database port for web access.
`startSoapServer`	`true`	Start the SOAP and REST servers that enable Semarchy xDI to expose web services.
`soapHost`	`localhost`	SOAP and REST host (IP address or host name). 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.
`soapServerPort`	`42200`	Listening port for the SOAP and REST servers.
`enableHttpClientConnections`	`true`	Enables connecting and operations on the Runtime using the HTTP protocol.
`rmiHost`	`localhost`	RMI host (IP address or host name). 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.
`rmiPort`	`42000`	Listening port for the RMI.

launchSchedulerEngine

true

Start the built-in scheduler.

launchExecutionEngine

true

Start the execution engine.

startInternalDb

true

Start an internal H2 database.

internalDbTcpPort

42100

Internal database TCP port for JDBC access.

internalDbWebPort

42101

Internal database port for web access.

startSoapServer

true

Start the SOAP and REST servers that enable Semarchy xDI to expose web services.

soapHost

localhost

SOAP and REST host (IP address or host name). 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.

soapServerPort

42200

Listening port for the SOAP and REST servers.

enableHttpClientConnections

true

Enables connecting and operations on the Runtime using the HTTP protocol.

rmiHost

localhost

RMI host (IP address or host name). 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.

rmiPort

42000

Listening port for the RMI.

You can also secure the communication with these services. See Runtime Security for more details.