3. Usage¶
This chapter explains how to run Web Integration Service once it has been installed. In particular, it describes:
Starting Web Integration Service (Section 3.1).
Stopping Web Integration Service (Section 3.2).
Command-line Options (Section 3.3).
3.1. Starting Web Integration Service¶
Web Integration Service runs as a separate application. The script to run the
executable is in <NDDSHOME>/bin
.
To start Web Integration Service, enter:
$NDDSHOME/bin/rtiwebintegrationservice [options] -cfgName <cfgName>
For example:
$NDDSHOME/bin/rtiwebintegrationservice -cfgFile example.xml -cfgName example
Table 3.1 describes the command-line options.
3.2. Stopping Web Integration Service¶
To stop Web Integration Service, press Ctrl-c. Web Integration Service will perform a clean shutdown.
3.3. Command-Line Parameters¶
The following table describes the command-line parameters for
Web Integration Service. They are all optional, except for -cfgName
.
Option |
Description |
---|---|
|
Path to the web server’s access log. |
|
Access Control List file. This parameter loads an Access Control
List file, which enables access control in all the HTTP requests and
WebSocket (WS) connections. It is recommended to use this parameter with a
secured connection;
i.e., it is important to enable HTTPS and Secure WebSocket (WSS) in
every single |
|
Specifies a configuration file to be loaded. See How to Load the XML Configuration in Section 4.3. |
|
Required. |
|
Adds a new API key to an Access Control List file along with a
description of the purpose of the API key to be generated. |
|
Deletes an API key from an Access Control List file. |
|
Directory that will be served by Web Integration Service’s web
server on |
|
Allows clients to reuse TCP connections for subsequent HTTP requests,
which improves performance. It is important to add the correct
|
|
Caches WaitSet, Sample Buffer, and DynamicData ojects in the
thread-specific storage of the worker threads that handle HTTP requests.
You can limit the allocated resources by reducing the number of worker
threads via the |
|
Allows clients to read/write data through WebSocket. |
|
Idle timeout, in milliseconds, between two requests in a
keep-alive connection. If |
|
When heap monitoring is enabled, this
parameter specifies the directory where the heap snapshots are to be
dumped. Note that the given directory must exist. |
|
Enables heap monitoring and generates a heap snapshot file every
|
|
Displays help information. |
|
Lists all the API keys available in an Access Control List file. |
|
Comma-separated list of ports to listen on. To enable HTTPS/WSS on a
specific port, append “ |
|
Maximum number of thread-specific objects that can be created. |
|
Number of worker threads for the web server. The web server handles
each incoming connection in a separate thread. Therefore, the value
of this option is effectively the number of connections that can be
handled. |
|
Path to the SSL certificate file. This option is only required when
one of the |
|
Controls what type of messages are logged: |
|
Prints the Web Integration Service version number. |