Software AG Products 10.7 | Administering Integration Server | Starting and Stopping the Server | Starting the webMethods Integration Server | Starting a Server Instance from the Command Prompt
 
Starting a Server Instance from the Command Prompt
You can start server instances from the command prompt. When you start a server instance from the command prompt, you have the option of overriding certain settings in the configuration file. You can also start the server instance in "debug" mode, so you can record or display server activity.
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.
*To start a server instance from the command prompt in Integration Server
1. At a command prompt, type the following command:
cd Software AG_directory\profiles\IS_instance_name\bin
where instance_name is the name of the Integration Server instance.
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.
2. Type the following command to start the server instance:
For Windows:
bin\startup.bat -switch -switch ...
For UNIX:
bin/startup.sh -switch-switch ...
where switch is optional and can be one of the following :
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. See Architecture for a discussion of remapping ports.
-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.
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 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 Integration Server home directory: Integration Server_directory \instances\instance_name
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).
Server log messages written to STDOUT include the identifier “ISSERVER” to help differentiate server log messages from other messages written to the console.
both
Write server log information to the computer screen (STDOUT) and to the destination specified by the watt.debug.logfile parameter.
The filename and none values override the value assigned to watt.debug.logfile for this session.
Note:
For SSL session logging, a-log switch value specifies where Integration Server writes the SSL session information. For a -log switch value of none, Integration Server writes the SSL session information to a separate file (inboundSSLSessions.log). For a switch value of both, Integration Server writes the SSL session information to the inboundSSLSessions.log file and to the console. For more information on SSL session logging, see Setting Up SSL Session Logging.
Note:
A -log switch value of none or both also determines where Microservices Runtime or an Integration Server equipped with an Microservices Runtime license 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 /instances/instanceName/logs/configurationvariables.log. For more information about configuration variable templates and the associated logging, see Developing Microservices with webMethods Microservices Runtime.
-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.