Skip to main content

Cheatsheet: start and stop commands for Talend server modules

The following table sums up the commands or executables you can use to start and stop Talend server modules.

Talend server module Start command/executable Stop command/executable

Apache Tomcat service for Talend Administration Center

sh <TomcatPath>/bin/startup.sh

sh <TomcatPath>/bin/shutdown.sh

JBoss service for Talend Administration Center

sh <JBossPath>/bin/run.sh

sh <JBossPath>/bin/shutdown.sh

Apache Tomcat service for Talend DQ Portal

Talend DQ Portal is deprecated from Talend 7.1 onwards.

sh <TomcatPath>/bin/startup.sh

sh <TomcatPath>/bin/shutdown.sh

Apache Tomcat service for Talend MDM Server

sh <TomcatPath>/bin/startup.sh

sh <TomcatPath>/bin/shutdown.sh

Talend Runtime

<TalendRuntimePath>/bin/trun

Ctrl+C

Talend Artifact Repository

<ArtifactRepositoryPath>/bin/nexus run by default or

nexus.sh console for Nexus 2

Ctrl+C

Talend JobServer

<JobServerPath>/start_rs.sh

<JobServerPath>/stop_rs.sh

Talend LogServer

sh <LogServerPath>/start_logserver.sh

sh <LogServerPath>/stop_logserver.sh

Talend CommandLine

Availability-noteDeprecated
Talend CommandLine as a Server is deprecated from Talend 7.1 onwards.

sh <CommandLinePath>/start_cmdline.sh or sh <CommandLinePath>\commandline-linux_x86_64.sh 1

sh <CommandLinePath>/start_cmdline.sh or Ctrl+C 1

Talend ESB

tesb:start-all

tesb:stop-all

Event Logging

tesb:start-el-default

tesb:stop-el-default

Talend Runtime Container

<TalendESBPath>/container/bin/trun

Ctrl+C

Apache ActiveMQ

In Talend Runtime Container:

feature:install activemq

Ctrl+C

Service Locator

tesb:start-locator

tesb:stop-locator

Service Activity Monitoring

tesb:start-sam

tesb:stop-sam

Security Token Service

tesb:start-sts

tesb:stop-sts

1: The command/executable to use depends whether you installed your Talend product using manual installation or using automatic installation.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!