Starting a Server Instance from the Command Prompt

Note:

If you are running the Windows Server 2008 r2 operating system with the User Account Control security feature enabled, the command prompt you use to run the startup.bat service must be launched with full Administrator privileges. To launch the command prompt with full Administrator privileges, navigate to All Programs > Accessories, right-click on the Command Prompt listing, and select the Run as Administrator option. If you are not logged into the operating system with Administrator privileges, you will be prompted to supply Administrator credentials.

Note:

The startup.bat/sh and shutdown.bat/sh scripts contained in the Integration Server_directory \instances\instance_name\bin directory are deprecated. Software AG recommends the use of the scripts contained in the Software AG_directory \profiles\IS_instance_name\bin directory. If you will manage Integration Server through Command Central, you must use the scripts located in the Software AG_directory \profiles\IS_instance_name\bin directory.

For Windows:	bin\startup.bat -switch -switch ...
For UNIX:	bin/startup.sh -switch-switch ...

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 8080 for HTTPS), and if necessary have the firewall remap port 80 to the desired port. See Architecture for a discussion of remapping ports.

-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.

Note:

Prior to Integration Server 7.1, Integration Server used a number-based system to set the level of debug information written to the server log. Integration Server maintains backward compatibility with this system. For more information about the number-based logging levels, see the description of the watt.debug.level property in Server Configuration Parameters.

-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 to the file in which you want the server to write server log information for this session. The default is serveryyyymmdd.log.

none

Display server log information on the computer screen. When you use this option, the server records a timestamp in the journal log file, but does not record any other log information in the file.

This switch overrides the value assigned to watt.debug.logfile for this session.

-quiesce

Specifies to start the server in quiesce mode.

For more information about quiesce mode, see Quiescing the Server for Maintenance.

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.