Runtime Engine Monitoring

You can use the Designer thick client to monitor the sessions running in a runtime engine, as well as Semarchy Convergence for DI Analytics to monitor these from a web UI.

It is also possible from the runtime engine console to monitor runtime engine activity.

Connecting the Runtime

Once you are in the command line (using startcommand.bat or startcommand.sh), connect to the runtime running the session.

To connect to a remote runtime, use the command:

>connect to <host_name> port <port_number>

where <host_name> is the name of the host running the runtime engine and <port_number> is the port of the runtime engine.

To connect a runtime from its server’s comment line, just run the following:

>connect

Managing Runtime Services

The runtime runs several services which can be started and stopped from the console.

To retrieve the status of a given service (or all services) in a given format:

>get services [name <name>] [format <format>]

To stop/start/restart services:

><start|stop|restart> <name> service

Managing Sessions

The following commands allow monitoring and configuring of the list of sessions managed by the runtime.

To retrieve a list of sessions by name, id, status or duration:

>get sessions [name <name>] [id <id1,id2,idn>] [status <running,error,done,stopped>] [duration <min> [to <max>]] [limit <limit>] [format <format>]]

To stop, restart or wait for the end of a given session identified by its ID:

><stop|restart|wait> session <id>

Stopping the Runtime

To stop the runtime, optionally waiting for all sessions to complete (recommended):

>stop runtime [wait sessions] 

To kill the runtime process (not recommended):

>kill runtime [wait sessions] 

Note: You can stop a runtime remotely, but you need to connect to this runtime’s server (using SSH for example) to restart it.

Batch Commands

You can create batches of commands and run them using the startcommand script.

This command supports the following syntaxes.

startcommand[.sh|.bat] [-separator <separator>] [<command1>;<command2>;...;<commandx>]
startcommand[.sh|.bat][-file <commands file>]

The first syntax allows you to start a sequence of commands separated by a separator (defaults to “;”).
The second syntax allows you to specify a file containing a sequence of commands.

Note that the first command in the sequence should be a connect command.