Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »


You can start or stop Adeptia services as and when you need to do. Follow the steps below to stop or start services on Windows and Linux.

On Windows

You can start or stop Kernel and WebRunner in two ways:

  • As a service
  • From Start menu/Desktop

Starting or stopping Kernel and WebRunner as a Service

If you have installed Adeptia Connect as a service, follow the steps below to start or stop Kernel and WebRunner:

  1. Go to Control Panel > Administrative Tools > Services.
  2. Right-click Adeptia Kernel or Adeptia WebRunner and then click Start or Stop based on your requirement.

Starting Kernel and WebRunner from Start Menu/Desktop

  • Start Menu: Go to Start > Programs > Adeptia Connect and select the service.
  • Desktop: Double-click Adeptia Kernel and Adeptia WebRunner shortcut from the desktop.

This action will display the service console window.
To stop any of the services, go to the service console window, and press Ctrl+ C. If you close Kernel and WebRunner console by clicking the cross button, the Java Virtual Machine (JVM) used by Adeptia Connect may not shut down properly.

If you stop Kernel or WebRunner by clicking the cross button, ensure that you go to Task manager thereafter and kill the Java.exe and JSL.exe.

On Linux

Perform the following steps to start or stop Kernel and WebRunner:

  1. Open Terminal.
  2. Go to the directory where Adeptia Connect is installed. .../<AdeptiaConnectInstallFolder>/AdeptiaServer/ServerKernel.
  3. Type ./startup.sh to start, or, type ./stop.sh to stop.

To ensure that Adeptia Connect Kernel and WebRunner are started successfully, go to the directory .../<AdeptiaConnectInstallFolder>/AdeptiaServer/ServerKernel/logs/applicationlogs and type the command

cat KernelApplication.log
and
cat WebrunnerApplication.log

These commands will display the details of the KernelApplication.log and WebrunnerApplication.log files respectively. Ensure that these files contain the message that "Kernel has started successfully" and "WebRunner has started successfully".


  • No labels