Skip to main content
Skip table of contents

Starting LightWave Server

LightWave Server runs as a group of NonStop Server Guardian processes using the Supervisor-Worker pattern. The SERVER process services the management console and connection requests for API services. When a client creates a TCP/IP connection to a LightWave Server TCP/IP port, the SERVER process delegates the connection and all future processing of that connection to an SWORKER process. In the event that no SWORKER processes are attached to the SERVER process, the SERVER process itself takes over processing of API service requests. This allows LightWave Server to easily scale according to demand.

The SERVER process runs as a single fault tolerant process pair and may be configured to listen on one or more TCP/IP processes and ports. To meet service demand, any number of SWORKER processes, running in any CPU, can be attached to a supervisor. Worker processes assume control of TCP/IP connections from the SERVER but do not listen on TCP/IP ports and therefore will not conflict with other processes listening on TCP/IP ports.


A sample LightWave Server startup macro, ZSTARTUP, is included with the release. Before using for the first time, copy or rename the file to a new name (e.g. FUP DUP ZSTARTUP, STARTUP) so it won't be overwritten by future releases. The sample macro should be suitable for most installations, but it may be necessary to modify certain parameters for your environment. To use the macro: RUN STARTUP

Starting a Server Process

LightWave Server is started by running the SERVER program from TACL.

tacl> run server / run-options / command-line-options

Starting a Worker Process

An Worker process is started by running the SWORKER program from TACL.

tacl> run sworker / run-options / --server $server-process-name

More Information

Refer to the Command Line Reference for details about starting LightWave Server and Worker processes.


Start the SERVER process as a process pair in CPU 0 and 1 with SWORKER processes in CPU 2 and 3. The Console may be accessed on port 8080 using HTTP or port 8443 using HTTPS. Services may be accessed on port 9080 using HTTP or 9443 using HTTPS. This example assumes that a server certificate with Common Name has already been installed.

tacl> run server / name $LWS, cpu 0 / --backupcpu 1 &
--console-ports $ztc0:8080 $ &
--service-ports $ztc0:9080 $ &
--log $zhome info
tacl> run sworker / name, cpu 2 / --server $LWS
tacl >run sworker / name, cpu 3 / --server $LWS
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.