Node Manager Settings

This section explains the local Node Manager configuration file, which defines the server processes to be started and the process control options.

In addition to the shared and local cluster-wide configuration properties, each Node Manager reads its local configuration file, which defines the server processes to be started and the process control options.

Node Manager Configuration

The local Node Manager configuration is defined in the nodemanager.properties file (in <IS.INSTANCE.LOCAL>/engine/nodemanager/config/).

Note:
The location of the nodemanger.properties file can be set as JVM property via the commandline expression -Dnodemanger.config.dir=<path>.

As one Node Manager controls all server processes in an Intershop Commerce Management instance, these settings apply to all servers. The following table lists the Node Manager properties in the nodemanager.properties file.

Table 1. Node Manager properties
Property Description
network.protocol Defines the protocol to use for communication (default http).
network.interface Specifies the IP of the network interface to use; by default, the primary IP is set.
network.port Sets the port for receiving requests from the Cluster Management instance (default: 10050). If not set, the Node Manager starts without communication functionality.
config.update.timeout Defines the interval (in seconds) between two configuration look-ups to enable configuration changes at runtime. If not specified or set 0, the Node Manager reads its configuration once at startup.

The table below lists the properties that can be set for the processes controlled by the Node Manager.

Table 2. Process properties
Property Description
process.allowedExitCodes Specifies untreated exit codes of the Node Manager subprocesses. If a subprocess exits with one of these exit codes, the Node Manager will not restart it.
process.list Specifies the names of the subprocesses that are controlled by the current Node Manager instance (comma separated list), e.g., appserver0,appserver1.
process.<process_name>. command Specifies the command line string to start the subprocess. This string can include command line arguments to be passed to the subprocess.
process.<process_name>. autostart A boolean value indicating whether the Node Manager should start the specified subprocess at startup. The default value is true. If set false, only the Cluster Management instance can start this subprocess.

To pass additional properties to the application server process, either edit the startup script (this would apply to all server processes) or enter the required arguments in the command shell when starting a single instance. Additional properties include specific memory allocation, additional classpaths, etc.

Node Manager Startup Command

As the command line call to start the Node Manager is very complex, a command line script is used for convenience reasons (nodemanager.sh on Unix platforms, nodemanager.bat on Windows, located in <IS.INSTANCE.LOCAL>/bin/).

The startup script performs the following tasks:

  • prepares the Node Manager system environment via the environment shell script

  • assembles the class path for the watchdog Java process

  • starts the Node Manager process

Note:
Intershop recommends not to change the Node Manager startup scripts.

Once running, the Node Manager starts the Intershop Commerce Management server processes, as defined in the nodemanager.properties file (see Node Manager Configuration).

Note:
You should use nodemanager.sh only for development or debugging purposes.