16.3.3 Editing the setup file

(1) Administration Agent settings

Among the items to be specified in adminagent.properties (Administration Agent property file), this section describes the settings to be noted when integrating with cluster software.

• adminagent.adapter.bind_host

  If you provide only one standby for two or more executing nodes, you must specify a real IP address for the adminagent.adapter.bind_host key.

  If you provide one standby node for one executing node, you can specify a virtual IP address or real IP address for the adminagent.adapter.bind_host key.

To Page Top

(2) Management Server settings

Among the items to be specified in mserver.properties (Management Server environment setup file), this section describes the settings to be noted when integrating with cluster software.

• com.cosminexus.mngsvr.logical_server_abnormal_stop.exit

  Specify the settings (true) for switching the node when the logical server status is "abnormal termination" (when exceeds the automatic restart frequency or when 0 is specified as the automatic restart frequency and a failure is detected).

  A settings example is as follows:

  com.cosminexus.mngsvr.logical_server_abnormal_stop.exit = true

  Important note

  If automatic restart is specified for Management Server, node switching is not executed during this time. For executing the node switching during this time, do not specify automatic restart for Management Server.

  In a configuration in which two or more executing nodes exist, do not specify com.cosminexus.mngsvr.logical_server_abnormal_stop.exit=true. If you do so, multiple systems of these executing nodes might start on the standby node.

• webserver.connector.http.bind_host

  If you provide only one standby node for two or more executing nodes, you must specify a real IP address for the webserver.connector.http.bind_host key.

  If you provide one standby node for one executing node, you can specify a virtual or real IP address for the webserver.connector.http.bind_host key.

• mngsvr.myhost.name

  If you provide only one standby node for two or more executing nodes, you must specify a real IP address for the mngsvr.myhost.name key.

  If you provide one standby node for one executing node, you can specify a virtual or real IP address for the mngsvr.myhost.name key.

To Page Top

(3) Settings for the property file for issuing Management events

The mevent.logical-server-name.properties file (Property file for issuing Management events) is a setup file related to the J2EE servers; therefore, the file is created after you set up the system using the Smart Composer functionality. Specify the following key after the system setup:

• manager.mevent.send.host

  If you provide only one standby node for two or more executing nodes, you must specify a real IP address for the manager.mevent.send.host key.

  If you provide one standby node for one executing node, you can specify a virtual or real IP address for the manager.mevent.send.host key.

To Page Top

(4) Settings for the Management Server management command (mngsvrutil)

Specify the following keys in the client-side definition file (.mngsvrutilrc) or client-side common definition file (mngsvrutilcl.properties) of the Management Server management command (mngsvrutil):

• mngsvrutil.connect.host

  If you provide only one standby node for two or more executing nodes, you must specify a real IP address for the mngsvrutil.connect.host key.

  If you provide one standby node for one executing node, you can specify a virtual or real IP address for the mngsvrutil.connect.host key.

• mngsvrutil.target_name

  Specify the virtual IP address in the mngsvrutil.target_name key. Check that you specify this key only when specifying the host name.

  Reference note

  Use the .mngsvrutilrc file to set up individual default values for each client. If you want to set up a common default value for all the clients, use the mngsvrutilcl.properties file. Note that when you are using both the files, the .mngsvrutilrc file is applied. The mngsvrutilcl.properties file is not read.

The mngsvrutilcl.properties file is used when the mngsvrutil command is executed with the script for monitoring, starting, and stopping Management Server.

To Page Top

(5) Settings for the commands provided in the Smart Composer functionality

Specify the following key in the client settings property file (.cmxrc) or client common settings property file (cmxclient.properties):

• cmx.connect.host

  If you provide only one standby node for two or more executing nodes, you must specify a real IP address for the cmx.connect.host key.

  If you provide one standby node for one executing node, you can specify a virtual or real IP address for the cmx.connect.host key.

  Reference note

  Use the .cmxrc file to set up individual default values for each client. If you want to set up a common default value for all the clients, use the cmxclient.properties file. Note that when you are using both the files, the .cmxrc file is applied. The cmxclient.properties file is not read.

To Page Top

(6) Settings for the invoke monitor command (In Windows)

You can only use the invoke monitor command in Windows.

Specify the following key in the .mngsvrmonitorrc file (invoke monitor setup file for JP1/IM integration). For details about the .mngsvrmonitorrc file, see 8.2.17 .mngsvrmonitorrc (Settings file of the monitor startup command for JP1/IM integration) in the uCosminexus Application Server Definition Reference Guide.

• mngsvrmonitor.connect.host

  If you provide only one standby node for two or more executing nodes, you must specify a real IP address for the mngsvrmonitor.connect.host key.

  If you provide one standby node for one executing node, you can specify a virtual or real IP address for the mngsvrmonitor.connect.host key.

To Page Top