2.6.1 Starting the system
For the normal operations, we recommend that you use the automatic start method for starting Administration Agent and Management Server. If you specify automatic restart of Administration Agent and Management Server, the series of operations from the starting of Administration Agent up to the starting of Management Server can be executed simultaneously with the starting of the host. For details on how to specify the automatic start, see 2.6.3 Settings for automatic start.
The following are the start procedures for programs and servers:
-
Start Administration Agent
-
Start Management Server
-
Start the system
To start programs and servers:
- Organization of this subsection
(1) Start Administration Agent
If you start Administration Agent manually, you start it by using the adminagentctl command for each host of Application Server.
We recommend that you synchronize the state of the command processing and start processing of Administration Agent. In such cases, you specify the synchronous execution option (-sync option) when executing the command. If you specify this option, when the command processing ends, Administration Agent becomes in the operational state. Also, during the synchronous execution, you can specify the waiting time from when the command is executed until Administration Agent is in the operational state (the timeout time of synchronous execution), with the -timeout option.
The start method is shown for each OS.
- In Windows
Installation-directory-of-Cosminexus(1)\manager\bin\adminagentctl start -sync -timeout timeout-time-of-synchronous-execution
- Reference note
-
Note that in Windows, you can also use services to start Administration Agent.
- In UNIX
# /opt/Cosminexus/manager/bin/adminagentctl start -sync -timeout timeout-time-of-synchronous-execution
- Reference note
-
Note that in UNIX, if you specify the -daemon option with the adminagentctl command or if you use the daemon command, you can start Administration Agent as the daemon process. When you use the daemon command, the state of the command processing and start processing of Administration Agent cannot be synchronized.
(2) Start Management Server
If you start Management Server manually, you start it by specifying the start argument in the mngsvrctl command on the host on which Management Server is set up.
- Important note
-
When you define a host by specifying a host name that cannot be resolved or an IP address that does not exist, the starting of Management Server takes time.
We recommend that you synchronize the state of the command processing and start processing of Management Server. In such cases, you specify the synchronous execution option (-sync option) when executing the command. If you specify this option, when the command processing ends Management Server is in the operational state. Also, during the synchronous execution, you can specify the waiting time from when the command is executed until Management Server is in the operational state (the timeout time of synchronous execution), with the -timeout option.
The start method is shown for each OS.
- In Windows
Installation-directory-of-Cosminexus\manager\bin\mngsvrctl start -sync -timeout timeout-time-of-synchronous-execution
- Reference note
-
Note that in Windows, you can also use services to start Management Server.
- In UNIX
# /opt/Cosminexus/manager/bin/mngsvrctl start -sync -timeout timeout-time-of-synchronous-execution
- Reference note
-
Note that in UNIX, if you specify the -daemon option using the mngsvrctl command or if you use the daemon command, you can start Management Server as the daemon process. When you use the daemon command, the state of the command processing and start processing of Management Server cannot be synchronized.
(3) Start the system
You can start the Web system or service units in a batch using the Smart Composer functionality commands. If the system is started in each Web system, all the logical servers in all the service units that exist in the Web system will start.
- Reference note
-
We recommend that you use the default settings for the starting order of logical servers. You can specify the starting order of logical servers with the mstartup.no parameter of the <configuration> tag for each logical server, in the Easy Setup definition file.