This section describes the subcommands that can be specified as arguments of the mngsvrutil command.
This subcommand displays a list of values, as specified in the argument. The following table lists and describes the arguments that can be specified for the list subcommand.
Table 7-2 Arguments that can be specified for the list subcommand
Argument | Explanation | Target specification | |
---|---|---|---|
Logical server | Host | ||
Status | Lists the logical servers in the management domain and shows their status. | -- | -- |
appStatus | Lists the J2EE applications that have been imported into the logical server specified by the -t option and shows their status. | Y | -- |
resStatus | Lists the J2EE resources that have been imported into the logical server specified by the -t option and shows their status. | Y | -- |
resJavaBeansStatus | Lists the JavaBeans resources that have been imported into the logical server specified by the -t option and shows their status. | Y | -- |
Queues | Lists the queues belonging to the host specified by the -t option and shows their status. | Y | Y |
You can use the list subcommand to display the following five types of information:
This subcommand acquires the values specified by the argument for the logical server or host specified by the -t option. The arguments listed in Table 7-3 can be specified. Note that arguments other than domainName are referred to as metric category.
When a logical server is specified by the -t option, an error occurs if a logical server (Web server, Naming Service, or smart agent, for example) that is not a logical server that belongs to the metric category (J2EE server, SFO server, or CTM) is specified.
To monitor statistical information at a set interval, you can collect the statistical information on a regular basis by setting the sampling time to be equal to or greater than the interval.
If a J2EE application was started in the test mode, information is output in the format application-name_TEST.
The following table lists and describes the arguments that can be specified for the get subcommand. For details on the arguments that can be specified for the get subcommand, see Appendix A. Extended MIB Object Definition File in the uCosminexus Application Server Definition Reference Guide.
Table 7-3 Arguments that can be specified for the get subcommand
Argument | Explanation | Target specification | |
---|---|---|---|
Logical server | Host | ||
domainName | Acquires the management domain. | -- | -- |
j2eeContainer | Acquires J2EE container information. | Y | Y |
webContainer | Acquires Web container information. | Y | Y |
jvm | Acquires JavaVM information. | Y | Y |
transaction | Acquires transaction information. | Y | Y |
httpServer | Acquires Management Server (simple Web server) information. We recommend that users need not acquire this information because it is management information that is used internally. | Y | Y |
httpSvrConn | Acquires Web server and Web container connection information. | Y | Y |
inprocHttpSvr | Acquires in-process HTTP server information. | Y | Y |
dataSource | Acquires data source (JDBC) information. | Y | Y |
dataSrcFull | Acquires data source (OTS 1.2-compatible JTA) information. | Y | Y |
resAdapter | Acquires resource adapter information. | Y | Y |
j2eeApps | Acquires J2EE application information. | Y | Y |
ejbApps | Acquires EJB application (EJB-JARs) information. | Y | Y |
statelessBean | Acquires Stateless Session Bean information. | Y | Y |
statelessBeanHome | Acquires Stateless Session Bean remote home interface information. | Y | Y |
statelessBeanHomeMethod | Acquires information on the Stateless Session Bean remote home interface method. | Y | Y |
statelessBeanLocalHome | Acquires Stateless Session Bean local home interface information. | Y | Y |
statelessBeanLocalHomeMethod | Acquires information on the Stateless Session Bean local home interface method. | Y | Y |
statelessBeanRemote | Acquires Stateless Session Bean remote component interface information. | Y | Y |
statelessBeanRemoteMethod | Acquires information on the Stateless Session Bean remote component interface method. | Y | Y |
statelessBeanLocalComponent | Acquires Stateless Session Bean local component interface information. | Y | Y |
statelessBeanLocalComponentMethod | Acquires information on the Stateless Session Bean local component interface method. | Y | Y |
statefulBean | Acquires Stateful Session Bean information. | Y | Y |
statefulBeanHome | Acquires Stateful Session Bean remote home interface information. | Y | Y |
statefulBeanHomeMethod | Acquires information on the Stateful Session Bean remote home interface method. | Y | Y |
statefulBeanLocalHome | Acquires Stateful Session Bean local home interface information. | Y | Y |
statefulBeanLocalHomeMethod | Acquires information on the Stateful Session Bean local home interface method. | Y | Y |
statefulBeanRemote | Acquires Stateful Session Bean remote component interface information. | Y | Y |
statefulBeanRemoteMethod | Acquires information on the Stateful Session Bean remote component interface method. | Y | Y |
statefulBeanLocalComponent | Acquires Stateful Session Bean local component interface information. | Y | Y |
statefulBeanLocalComponentMethod | Acquires information on the Stateful Session Bean local component interface method. | Y | Y |
entityBean | Acquires Entity Bean information. | Y | Y |
entityBeanHome | Acquires Entity Bean remote home interface information. | Y | Y |
entityBeanLocalHome | Acquires Entity Bean local home interface information. | Y | Y |
entityBeanRemote | Acquires Entity Bean remote component interface information. | Y | Y |
entityBeanLocalComponent | Acquires Entity Bean local component interface information. | Y | Y |
msgDrivenBean | Acquires Message-driven Bean information. | Y | Y |
webApps | Acquires Web application information. | Y | Y |
servlets | Acquires servlet information. | Y | Y |
requestUrl | Acquires information on each requested URL. | Y | Y |
queues | Acquires information about the CTM schedule (queue state). | Y | Y |
queueApps | Acquires information about the J2EE application connected to the CTM queue. | Y | Y |
This subcommand specifies two arguments and sets the value specified in the second argument for the variable specified for the first argument.
If the target logical J2EE server, logical SFO server, or J2EE application is restarted or redeployed after the value is setup , reset the value. If a logical server other than a logical J2EE server, logical SFO server, or logical performance tracer is specified in the -t option, an error occurs.
The following table lists and describes the arguments that can be specified for the set subcommand.
Table 7-4 Arguments that can be specified for the set subcommand
Argument | Explanation | Target specification | |
---|---|---|---|
Logical server | Host | ||
jvmSamplingTime n | Sets the JavaVM sampling time to n seconds.#1 | Y | -- |
webContainerSamplingTime n | Sets the Web container sampling time to n seconds.#1 | Y | -- |
tranSamplingTime n | Sets the transaction sampling time to n seconds.#1, #2 | Y | -- |
httpSvrSamplingTime n | Sets Management Server (simple Web server) sampling time to n seconds.#1 We recommend that users need not acquire this information because it is Management Server information that is used internally. | Y | -- |
httpSvrConnSamplingTime n | Sets the HTTP server connector sampling time to n seconds.#1 | Y | -- |
inprocHttpSvrSamplingTime n | Sets the in-process HTTP server sampling time to n seconds.#1 | Y | -- |
dataSrcFullSamplingTime n | Sets the data source (OTS 1.2-compatible JTA) sampling time to n seconds.#1, #3 | Y | -- |
resAdapterSamplingTime n | Sets the resource adapter sampling time to n seconds.#1, #3 | Y | -- |
ejbSamplingTime n | Sets the EJB sampling time to n seconds.#1, #3 | Y | -- |
webAppSamplingTime n | Sets the Web application sampling time to n seconds.#1, #3 | Y | -- |
servletSamplingTime n | Sets the servlet sampling time to n seconds. #1, #3 | Y | -- |
reqUrlSamplingTime n | Sets the sampling time for each URL requested after setting to n seconds.#1, #3 | Y | -- |
allPrfTraceLevel STANDARD|DETAIL | tracelevel | Sets a PRF trace collection level for all performance tracers within a management domain.#4 | -- | -- |
prfTraceLevel STANDARD|DETAIL | tracelevel | Sets a PRF trace collection level for the specified performance tracer or the performance tracer within the specified host.#4 | Y | Y |
This subcommand specifies a different PRF trace collection level for each functionality layer. A maximum of sixteen hexadecimal numbers of no more than 4 bytes (8 digits) each can be specified, delimited by a comma (,). For details on the specification values, see the explanation of -PrfTraceLevel under cprfstart (start PRF daemon) or the explanation of -PrfTraceLevel under cprflevel (display or change the PRF trace collection level) in 4.2 Details of commands used for performance analysis trace.
This subcommand starts the specified logical server, J2EE application, or J2EE resource.
The following table lists and describes the arguments that can be specified for the start subcommand.
Table 7-5 Arguments that can be specified for the start subcommand
Argument | Explanation | Target specification | |
---|---|---|---|
Logical server | Host | ||
allServers | Starts the logical servers defined in the management domain in the defined starting order. | -- | -- |
server | Starts the logical server specified by the -t option. | Y | Y |
app displayName | Starts the J2EE application specified by displayName that has been imported into the logical server specified by the -t option.# | Y | -- |
resAdapter displayName | Starts the J2EE resource adapter specified by displayName that has been imported into the logical server specified by the -t option.# | Y | -- |
resJavaBeans displayName | Starts the JavaBeans resource specified by displayName that has been imported into the logical server specified by the -t option.# | Y | -- |
You can use the start subcommand to execute the following two types of operations:
This subcommand stops the specified logical servers, J2EE application, or J2EE resources.
The following table shows the arguments that can be specified for the stop subcommand.
Table 7-6 Arguments that can be specified for the stop subcommand
Argument | Explanation | Target specification | |
---|---|---|---|
Logical server | Host | ||
allServers | Stops the logical servers defined in the management domain in reverse order from the defined starting order. | -- | -- |
server [graceful[:waitTime]] | Stops the logical server specified by the -t option. When graceful is specified, planned termination is executed. | Y | Y |
app displayName [force] | Stops the J2EE application specified by displayName that has been started on the logical server specified by the -t option.# When force is specified, the application is stopped forcibly. | Y | -- |
resAdapter displayName | Stops the J2EE resource adapter specified by displayName that has been started on the logical server specified by the -t option.# | Y | -- |
resJavaBeans displayName | Stops the JavaBeans resource specified by displayName that has been started on the logical server specified by the -t option.# | Y | -- |
You can use the stop subcommand to execute the following two types of operations:
This subcommand reloads the configuration file for the component specified in the argument.
The following table lists and describes the argument that can be specified for the reload subcommand.
Table 7-7 Argument that can be specified for the reload subcommand
Argument | Explanation | Target specification | |
---|---|---|---|
Logical server | Host | ||
userAdmin | Reloads the configuration file to be used in integrated user management. If the logical server specified by the -t option does not use integrated user management, an error occurs. If userAdmin is specified in the sub-command reload, or if you specify a logical server other than the logical J2EE server in the -t option, an error occurs. | Y | -- |
This subcommand holds the services of the queue in the arguments.
The following table describes the arguments that can be specified for the subcommand hold:
Table 7-8 Arguments that can be specified for the hold subcommand
Argument | Explanation | Target specification | |
---|---|---|---|
Logical server | Host | ||
queue <queueName> { in[:waitTime] | out | force[:waitTime]} | Locks the queue with the name specified in <queueName> that belong to the CTM specified by the -t option. | Y | -- |
queues { in[:waitTime] | out | force[:waitTime] } | Locks the queues belonging to the CTM or host specified by the -t option. | Y | Y |
allQueues { in[:waitTime] | out | force[:waitTime] } | Locks all CTM queues in the management domain. | -- | -- |
You can use the hold subcommand to lock queues with the following three types of methods:
This subcommand releases the services of the queue specified in the arguments.
The following table describes the arguments that can be specified for the subcommand release:
Table 7-9 Argument that can be specified for the release subcommand
Argument | Explanation | Target specification | |
---|---|---|---|
Logical server | Host | ||
queue <queueName> | Unlocks the queue with the name specified in <queueName> belonging to the CTM specified by the -t option. | Y | -- |
Queues | Unlocks the queues belonging to the CTM or host specified by the -t option. | Y | Y |
allQueues | Unlocks all CTM queues in the management domain. | -- | -- |
You can use the release subcommand to unlock queues with the following three types of methods:
This subcommand collects the files and other items specified in the argument. If a logical server other than a performance tracer or CTM is specified by the -t option, an error occurs.
The following table lists and describes the argument that can be specified for the collect subcommand.
Table 7-10 Argument that can be specified for the collect subcommand
Argument | Explanation | Target specification | |
---|---|---|---|
Logical server | Host | ||
allPrfTraces | Collects performance analysis traces for all performance tracers in the management domain. | -- | -- |
prfTrace | Collects a performance analysis trace for the specified performance tracer or for the performance tracer at the specified host. | Y | Y |
allCtmStatistics | Collects the statistics of all CTMs in the management domain. | -- | -- |
ctmStatistics | Collects the statistics of the specified CTM, or a CTM in the specified host. | Y | Y |
snapshot [n]# | Collects a snapshot log at the specified host. | -- | Y |
You can use the collect subcommand to execute the following three types of operations:
This subcommand changes the value set for the number of concurrently executable threads, as specified by the arguments. A J2EE server must be specified by the -t option.
The following table lists and describes the argument that can be specified for the change subcommand.
Table 7-11 Argument that can be specified for the change subcommand
Argument | Explanation | Target specification | |
---|---|---|---|
Logical server | Host | ||
webAppThreadCtrl webApplicationContextRoot,maxThreads,exclusiveThreads,queueSize | Manages dynamically the number of threads that can be executed concurrently by the Web applications specified in the J2EE server specified by the -t option. This argument cannot be omitted. | Y | -- |
When webAppThreadCtrl is specified for the argument, the subcommand manages dynamically the number of threads that can be executed concurrently by the Web applications belonging to the J2EE server specified by the -t option.
For the argument webApplicationContextRoot, specify a Web application (J2EE application WAR) context root and the number of concurrently executable threads. You can use the get webApps subcommand to obtain the Web application context root value. If no context root has been set, specify a slash (/).
For the number of concurrently executing threads, specify the maximum number of threads, the number of dedicated threads, and the size of the pending queue for Web applications, in that order, delimited by a comma (,).
If any of the values for the arguments maxThreads (maximum number of threads), exclusiveThreads (number of dedicated threads), and queueSize (size of the pending queue for Web applications) is not to be changed, its specification might be omitted. However, you cannot omit all three items.
Example: To change only the number of dedicated threads: ,20,
Specify the various concurrent thread values within the ranges described below.
This subcommand checks whether Management Server and Administration Agent are active.
The following table lists and describes the arguments that can be specified for the check subcommand.
Table 7-12 Arguments that can be specified for the check subcommand
Argument | Explanation | Target specification | |
---|---|---|---|
Logical server | Host | ||
Mngsvr | Checks whether or not Management Server is active. If a target is specified by the -t option, it is ignored. | -- | -- |
adminAgent | Checks whether or not the Administration Agent is active at the host specified by the -t option. An error occurs when a value other than host is specified by the -k option, a value other than a host name is specified by the -t option, or the -t option is not specified. | -- | Y |
The check subcommand returns one of the following values:
This subcommand outputs the javacore of an active logical server.
The following table lists and describes the argument that can be specified for the dump subcommand.
Table 7-13 Argument that can be specified for the dump subcommand
Argument | Explanation | Target specification | |
---|---|---|---|
Logical server | Host | ||
server [addition]# | Outputs the javacore (active time information) for the logical server specified by the -t option. Only a J2EE server (including a J2EE cluster member), a J2EE server cluster, an SFO server, CTM, or the naming service can be specified as the logical server. When addition is specified, a core or memory dump is collected for the logical server specified by the -t option. | Y | -- |
The commands that are executed to output the javacore and the javacore file output destinations are described for each OS type.
The table below shows the commands that are executed to output the javacore and the javacore file output destinations for each logical server type in Windows.
Logical server | addition specified | Command to be executed | Output information | javacore file output destination directory |
---|---|---|---|---|
J2EE server (including server cluster) or SFO server | Specified | cjdumpsv, userdump#1 | javacore, memory dump | j2ee-server-work-directory\ejb\executing-server-name\ |
Not specified | cjdumpsv | javacore | j2ee-server-work-directory\ejb\real-server-name\ | |
CTM | Specified or not specified#2 | hdumpns | javacore#3 | cosminexus-installation-directory\TPB\logj\ |
Naming service | Specified or not specified#2 | hdumpns | javacore | cosminexus-installation-directory\TPB\logj\ |
The table below shows the commands that are executed to output the javacore and the javacore file output destinations for each logical server type in UNIX.
Logical server | addition specified | Command to be executed | Output information | javacore file output destination directory |
---|---|---|---|---|
J2EE server (including cluster) or SFO server | Specified | javacore -f -p#1 | javacore, core | j2ee-server-work-directory/ejb/real-server-name/ |
Not specified | cjdumpsv | javacore | j2ee-server-work-directory/ejb/real-server-name/ | |
CTM | Specified or not specified#2 | kill -3 | javacore#3 | /opt/Cosminexus/TPB/logj/ |
Naming service | Specified or not specified#2 | kill -3 | javacore | /opt/Cosminexus/TPB/logj/ |
This subcommand adds logical user servers.
The following table lists and describes the arguments that can be specified for the add subcommand.
Table 7-14 Arguments that can be specified for the add subcommand
Argument | Explanation | Target specification | |
---|---|---|---|
Logical server | Host | ||
userserver userServiceDefinitionFile | Adds logical user servers based on the content of the logical user server definition file specified in userServiceDefinitionFile. To change the logical user server definition file contents, first delete the logical user servers and then add the new set of logical user servers. | -- | -- |
If multiple logical user servers are specified, they are added in the order they are defined. The addition processing continues even if an error occurs midway. In such case, the return value is 1 (execution error). An error is caused by one of the following reasons:
This subcommand deletes a logical user server.
The following table lists and describes the arguments that can be specified for the delete subcommand.
Table 7-15 Arguments that can be specified for the delete subcommand
Argument | Explanation | Target specification | |
---|---|---|---|
Logical server | Host | ||
userserver logicalServerName | Deletes the logical user server whose name is specified in logicalServerName. | -- | -- |