Starting Microservices Runtime from the Command Line

Switch	Description
-port portNumber	Specifies the port on which the server listens for HTTP requests. portNumber specifies the TCP/IP port number Example: -port 8080 This switch overrides the value assigned to watt.server.port. Note: In addition to overriding the value of watt.server.port, the -port switch permanently adds a new HTTP port to the WmRoot package. This new port is added as the primary port and contains default values. If a port with the same TCP/IP number already exists in the WmRoot package, the -port switch overrides its settings with the new default values. In effect, deleting the existing port and then adding a new port with default settings. Note: To use port 80 (the standard for HTTP) or port 443 (the standard for HTTPS), UNIX users must be running as "root". For security reasons, a better method is to use a higher number port (5555 for HTTP and 5543 for HTTPS), and if necessary have the firewall remap port 80 to the desired port.
-secureport portNumber	Specifies the port number for the DefaultSecure (HTTPS) port. portNumber specifies the TCP/IP port number Example: -secureport 4355 This switch overrides the value assigned to watt.server.securePort. Note: In addition to overriding the value of watt.server.securePort, the -secureport switch permanently adds a new HTTPS port to the WmRoot package. This new port is added as the DefaultSecure port and contains default values.
-debug level	Specifies the level of detail you want the server to maintain in its server log for this session. level indicates the level of detail you want to record in the log.
	Specify...	To record...
	Fatal	Fatal messages only.
	Error	Error and fatal messages.
	Warn	Warning, error, and fatal messages.
	Info	Informational, warning, error, and fatal messages.
	Debug	Debug, informational, warning, error, and fatal messages.
	Trace	Trace, debug, informational, warning, error, and fatal messages.
	For this session, this switch overrides the value specified for the Default facility on the Settings > Logging page and assigned to watt.debug.level.
-log destination	Specifies where you want the server to write its server log information for this session. Specify one of the following for destination:
	Option	Description
	filename	Specify the fully qualified path or relative path to the file in which you want the server to write server log information for this session. Relative path is relative to the Microservices Runtime home directory. The filename must specify a directory and filename. The default destination is controlled by the watt.debug.logfile server configuration parameter.
	none	Write server log information to the computer screen (STDOUT).
	both	Write server log information to the computer screen (STDOUT) and to the destination specified by the watt.debug.logfile parameter. When setting -log both, server log messages written to STDOUT include the identifier “ISSERVER” to help differentiate server log messages from other messages written to the console.
	The filename and none values override the value assigned to watt.debug.logfile for this session.
	For UNIX, setting -log to none or both results in the redirection of STDOUT to the server.out file located under Integration Server_directory /bin/logs
	Note: A -log switch value of none or both also determines where Microservices Runtime writes the configuration variables log. However, Microservices Runtime ignores a filename value. If you specify a filename, Microservices Runtime writes the configuration variables log file to this location only: Integration Server_directory /i/logs/configurationvariables.log. For more information about configuration variable templates and the associated logging, see Using Configuration Variables Templates with Microservices Runtime
-quiesce	Specifies to start the server in quiesce mode. Note: If the server cannot disable or suspend an asset or activity as it enters quiesce mode, the server displays a warning message and continues the quiesce process. If the condition stated in the warning interferes with a maintenance task you intend to perform, resolve the issue stated in the warning and then restart the server in quiesce mode.