The contents of automatic start specified in Administration Agent when executing the mngautorun command are described here for each OS.
Reference note
With the automatic start process, before starting Administration Agent, the Administration Agent automatic start configuration file (/opt/Cosminexus/manager/config/AdminAgentrc) is read. You can code the following settings in this file, so that the logical server which starts from Administration Agent inherits the settings:
• Control settings of resources (ulimit)
• Permissions at the time of file creation (umask)
• Environment variables
Do not code the settings other than the settings mentioned in this subsection, in the Administration Agent automatic start configuration file. If you code other settings in the Administration Agent automatic start configuration file, operations are not guaranteed.
The Administration Agent automatic start configuration file is executed as Shell Script. Therefore, if you change the contents coded in the Administration Agent automatic start configuration file, adequately check the operations. • In Windows
In the Administration Agent service, the following contents are set up to start the service, when the host starts: • Type of startup: Automatic
Also, if you start both Management Server and Administration Agent on the same host, a dependency relationship is set up such that Administration Agent starts first.
• In UNIX
The entry of once is registered in the /etc/inittab file. However, in the case of Red Hat Enterprise Linux Server 6 or later, jobs are registered using upstart. Also, if you start both Management Server and
Administration Agent on the same host, a dependency relationship is set up such that Administration Agent starts first. The following examples illustrate the respective setup contents:
Example inittab file setup
CoAA:3:once:/opt/Cosminexus/manager/bin/adminagentctl start
Example of job registration
# Register CoAA.conf in which the following contents are coded under the /etc/ init directory:
start on runlevel [3]
exec /opt/Cosminexus/manager/bin/adminagentctl start
2.6.4 Settings for automatic restart
When a failure occurs, the stopped Management Server and Administration Agent can restart automatically. If you set up automatic restart, the settings for automatic start are also valid. You use the mngautorun command to specify the automatic restart settings of Management Server and Administration Agent. For details on the mngautorun
command, see mngautorun (Set up/canceling the set up of autostart and autorestart) in the uCosminexus Application Server Command Reference Guide.
We recommend that in Windows, you make the automatic restart processing of Management Server and
Administration Agent set up with the mngautorun command to execute synchronously. In such cases, you specify the synchronous execution option (-sync option) when executing the command. If you specify this option, during the automatic restart, the starting of Management Server and Administration Agent is executed synchronously. Also, during the automatic restart, you can specify the waiting time until the starting of Management Server and
Administration Agent is executed synchronously (the timeout time of synchronous execution), with the -timeout
option.
In UNIX, the synchronous execution option cannot be specified for the automatic restart processing. ! Important note
When executing operations by specifying the automatic start settings of a version earlier than 09-00
If you are executing operations by specifying the automatic start settings of a version earlier than 09-00, when enabling the settings described in this subsection, you are required to cancel the automatic start settings of the version earlier than 09-00. For details on how to change the settings, see10.4 Checking the specification changes from previous versions in the uCosminexus Application Server Maintenance and Migration Guide.
Settings for automatic restart when JavaVM is terminated abnormally (In Windows Server 2008, Windows 7, or Windows Vista)
We recommend that when JavaVM terminates abnormally, after you acquire the user dump, for the correct operations of automatic restart of Application Server, you specify the registry value (DontShowUI : 1) in one of the following registry keys, and control response requests when acquiring the user dump:
\\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting \\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\Windows Error Reporting (to be used when the above mentioned registry key is not present)
The execution format and execution example of the mngautorun command are as follows: Execution format
mngautorun respawn {server|agent|both} [-runlevel run-level]#1 [-sync#2 [-timeout timeout-
time-of-synchronous-execution#2]]
#1
The run level can be specified in UNIX. In Windows, the run level cannot be specified. #2
The synchronous execution option and the timeout time of the synchronous execution can be specified in Windows. In UNIX, synchronous execution option and the timeout time of the synchronous execution cannot be specified. Example of execution
• When restarting Management Server automatically
mngautorun respawn server
• When restartingAdministration Agent automatically
mngautorun respawn agent
• When restarting Management Server and Administration Agentautomatically
mngautorun respawn both
• When synchronously executing the automatic restart of Management Server and Administration Agent# mngautorun respawn both -sync
#: The synchronous execution of the automatic restart can be specified in Windows. In UNIX, the synchronous execution of the automatic restart cannot be specified.
The following subsection describes the contents of an automatic restart, set up in Management Server and Administration Agent, when executing the mngautorun command: