slc ctl command to control Process Manager at runtime. To control Process Manager remotely, use the
-C) option to specify the URL where Process Manager is running.
For example, if you start Process Manager with this command:
Then you can control it with
where <command> is one of the sub-commands. See slc ctl command reference for details.
The following sub-commands apply to Process Manager itself:
info- display information on Process Manager.
ls- list services under management.
status(the default sub-command) - Display status information.
You can deploy multiple applications to one Process Manager and then use
slc ctl to control and get information on the applications (or services) and also monitor individual worker processes for each application (service).
Sub-commands that apply to a specific service (application runtime instance):
- create, remove - create and remove a service.
- env-get, env-set, env-unset - view, set, and remove environment variables.
- log-dump - Dump the log buffer to the console.
- set-size - Change cluster size of the service.
- stop, soft-stop, restart, soft-restart - stop or restart a service.
Profiling commands that apply to a specific worker process:
- cpu-start, cpu-stop - Start and stop CPU profiling.
- heap-snapshot - Save a heap memory snapshot.
- objects-start, objects-stop - Start and stop Object tracking.
Setting application port
Normally, PM makes applications available on a TCP port guaranteed to be different for each app, typically allocating sequential port numbers starting with 3000 as noted above. To override this behavior and make an application available over a specific port, use this command:Where <service> is the service name or ID, and <n> is the port to use. For example to make "my-app" available at port 7777: