4.1.15 Information to be set for using Management Server
This section describes the information to be set for using the Management Server. You can use the Management Server without setting the Management user account.
- Organization of this subsection
(1) Setting properties of the Management Server
You can specify the port number used by the Management Server and host that allows access to the Management Server in the property file of Management Server (mserver.properties).
The following are the keys specified in mserver.properties. For details on the keys, and the keys that are not described in this sub-section, see 8.2.6 mserver.properties (Management Server environment settings file) in the uCosminexus Application Server Definition Reference Guide.
-
adminagent.connector.comm.state.cache_max_time
Specify the maximum time to cache the status of communication with the Administration Agent.
-
webserver.connector.ajp13.port
Specify the port number for internal communications in the Management Server.
-
webserver.connector.http.port
Specify the HTTP port number for connecting to the Management Server.
-
webserver.shutdown.port
Specify the port number for receiving the Management Server end request.
-
webserver.connector.http.permitted.hosts
Specify the IP address or host name of the host that allows access to the Management Server, and the host on which the Administration Agent operates.
-
mngsvr.myhost.name
Specify the IP address that can be accessed by the host (Application Server) for allocating the Logical Server or the host name that shows the said IP address, in the host for allocating the Management functionality (Management Server). Specify this key, if the host to which the Management functionality (Management Server) is allocated has multiple IP addresses and the host name might not be converted to the intended IP address.
Other than these keys, you can perform the following settings in mserver.properties:
-
You can set the keys for snapshot log collection, and for acquiring data by using commands in case of fault detection. For details on snapshot log collection settings, and the settings to obtain data by using commands in case of fault detection, see the following subsections of the uCosminexus Application Server Maintenance and Migration Guide:
-
3.3.1 Settings for obtaining data with commands in case of fault detection(systems executing J2EE applications)
-
3.3.2 Settings for obtaining data with commands in case of fault detection (systems executing Batch applications)
-
3.3.3 Snapshot log collection settings (Systems executing J2EE applications)
-
3.3.4 Snapshot log collection settings (Systems executing Batch applications)
-
-
You can log in to the Management Server without setting the Management user account. In such cases, omission functionality of the Management user account is enabled. For details on settings of the functionality, see (3) Settings when Management User account is not set.
Also, as and when required, set the environment for execution of the commands used by the Smart Composer functionality in cmxserver.properties (Server Setup Property file).
The keys to be specified in cmxserver.properties are as follows:
-
cmx.max_wait_time
Specify the maximum waiting time when waiting for completion of the already executed command. This maximum waiting time is valid in the command executed by specifying the common option -wait. The default waiting time is set to 180 seconds.
(2) Setting the operating environment of the Management Server
Set the operating environment of the Management Server such as account information of the user using the Management Server, log information output by the Management Server, in the mngsvrctl command, or the Management Server property.
The following table describes the settings of the operating environment of the Management Server.
Settings |
Setting contents |
Necessity of the Settings |
---|---|---|
Management user account settings |
When the Management user account is not set when setting up the Management Server, either set by specifying the argument setup in the mngsvrctl command or set on the Setting Management User Account window of the Management portal. |
Y# |
Log settings |
Specify the log level, number of files, and size of the log output by the Management Server, in the mserver.properties or on the Setting Log window of the Management portal. Specify the following keys:
|
A |
Settings for startup |
Specify whether to run the logical server in a batch when you are starting the Management Server, in the mserver.properties or in the Settings for Startup window of the Management portal. This setting is required for a batch run. |
A |
Trace based performance analysis collection settings |
Set the number of trace based performance analysis files maintained on the Management Server in com.cosminexus.mngsvr.trace key, in the mserver.properties or in the Setting Trace Based Performance Analysis Collection window of the Management portal. |
A |
Setting the JP1 linkage |
Specify whether to publish the Management Server failure information (detected error or the Logical server start notification) as JP1 event in com.cosminexus.mngsvr.jp1event.enabled key, in the mserver.properties or in the Setting the JP1 linkage window of the Management portal. Other than this, perform settings in the keys starting with com.cosminexus.mngsvr.jp1event, to notify the Management Server failure information to JP1. This setting is required when using the functionality to link with JP1. For linkage with JP1, see 12.Operating a JP1 Integrated System in the uCosminexus Application Server Operation, Monitoring, and Linkage Guide. |
A |
(3) Settings when the management user account is not set
A Management user account is the user permission used to login to the Management portal and to execute the commands (Example: mngsvrutil command) for the Management Server. Although you implement the Management user account settings during the setup of the Management Server, you can also use the Management Server without setting the Management user account. If you do not set the Management user account, the following phenomenon might occur when performing management portal operations or executing commands for Management Server.
-
Login window of the Management portal is not displayed. By specifying the URL you can use the Management portal without login.
-
When executing commands for the Management Server, you need not specify -u(Management user ID) and -p (Management user password). You can execute the commands without specifying these options.
When you do not set the Management user account, specify false in com.cosminexus.mngsvr.management_user_account.enabled key of mserver.properties. However, if the Management user account is not set, anyone can operate the Management Server through Management portal and command execution. If the operational environment allows the operations in the Management Server by multiple users we recommend that you set the Management user account.