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. |
When starting a server instance from the command prompt in Integration Server, you update the custom_wrapper.conf with the server overrides before running startup.bat/sh.
To start a server instance from the command prompt in Integration Server
1. If you need to override settings in the configuration file, perform the following:
a. In a text editor, open the custom_wrapper.conf file from the following directory:
Software AG_directory \profiles\IS_instance_name\configuration
where instance_name is the name of the Integration Server instance.
b. Add the following property to custom_wrapper.conf:
wrapper.app.parameter.n=switch
where n is the next unused sequential number for the wrapper.app.parameter properties in the file and switch is the switch command.
Most switches require that you add an additional property to custom_wrapper.conf as the very next property in the sequence, as follows:
wrapper.app.parameter.n=switch_parameter
where n is the sequential number and switch_parameter is the value of the switch.
For example, to change the default port number to 8080, you would enter the following to custom_wrapper.conf:
wrapper.app.parameter.7=-port
wrapper.app.parameter.8=8080
For more information about the wrapper.app.parameter property, see Software AG Infrastructure Administrator's Guide.
The following table describes the switches you can use to override settings in the configuration file:
switch | Description |
-port | Specifies the port on which the server listens for HTTP requests. If you add a wrapper.app.parameter property to custom_wrapper.conf for the -port switch, you must also add a wrapper.app.parameter property in which you specify the TCP/IP port number to use. The first wrapper.app.parameter property specifies that you want to override the port by using the -port switch, and the next wrapper.app.parameter property specifies the port number to use. For example: wrapper.app.parameter.7=-port
wrapper.app.parameter.8=8080 Note: | Keep the following points in mind when overriding the port number:  This switch overrides the value assigned to 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. 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. |
|
-home | Specifies the server's home directory. If you add a wrapper.app.parameter property to custom_wrapper.conf for the -home switch, you must also add a wrapper.app.parameter property in which you specify the complete path for the home directory. The first wrapper.app.parameter property specifies that you want to override the home directory by specifying the -home switch, and the next wrapper.app.parameter property specifies the complete path for the home directory. For example: wrapper.app.parameter.9=-home
wrapper.app.parameter.10=D:\wmtest\server Note: | This switch overrides the value assigned to watt.server.home. |
|
-debug | Specifies the level of detail you want the server to maintain in its server log for this session. The -debug switch overrides the value specified for the Default facility on the Settings > Logging page and assigned to watt.debug.level. If you add a wrapper.app.parameter property to custom_wrapper.conf for the -debug switch, you must also add a wrapper.app.parameter property in which you specify the level of detail you want to record in the log. You can specify the following levels: |
| 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. |
| The first wrapper.app.parameter property specifies that you want to override the debug level by specifying the -debug switch, and the next wrapper.app.parameter property specifies the level of detail you want to record in the log. For example: wrapper.app.parameter.11=-debug
wrapper.app.parameter.12=fatal 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 | Specifies where you want the server to write its server log information for this session. If you add a wrapper.app.parameter property to custom_wrapper.conf for the -log switch, you must also add a wrapper.app.parameter property in which you specify the destination of the log information. You can specify the following destinations: |
| 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. |
| The first wrapper.app.parameter property specifies that you want to override the destination of the log information by specifying the -log switch, and the next wrapper.app.parameter property specifies either the complete path for the home directory or none. For example: wrapper.app.parameter.13=-log
wrapper.app.parameter.14=none Note: | This switch overrides the value assigned to watt.debug.logfile for this session. |
|
-quiesce | Specifies that Integration Server starts the server in quiesce mode. When you add a wrapper.app.parameter property to custom_wrapper.conf for the -quiesce switch, Integration Server starts in quiesce mode. The -quiesce switch does not require an additional wrapper.app.parameter property. For example: wrapper.app.parameter.15=-quiesce |
c. In the custom_wrapper.conf, update the wrapper.app.parameter.2 property to reflect the total number of wrapper.app.parameter properties that you added in the previous steps.
For example, if wrapper.app.parameter.2 is set to 4 (the default) and you add two wrapper.app.parameter properties, you would increase the value of wrapper.app.parameter.2 by two. After making your edits, the wrapper.app.parameter.2 would appear as follows:
wrapper.app.parameter.2=6
For more information about the wrapper.app.parameter property, see Software AG Infrastructure Administrator's Guide.
d. Save and close custom_wrapper.conf.
For more information about setting properties in custom_wrapper.conf, see Software AG Infrastructure Administrator's Guide.
2. 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. |
3. Type the following command to start the server instance:
For Windows: | startup.bat |
For UNIX: | startup.sh |
