7.3.4 start
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.
|
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 |
-- |
- Legend:
-
Y: Can be specified.
--: Cannot be specified.
- #
-
displayName indicates the display name of a J2EE application, J2EE resource, or JavaBeans resource.
You can use the start subcommand to execute the following two types of operations:
-
Specify the allServers argument to start the specified logical servers.
Starts the logical servers defined in the management domain in the defined starting order.
When server is specified for the argument, the subcommand starts the logical server specified by the -t option (smart agent, naming service, J2EE server, J2EE server cluster, CTM, CTM domain manager, performance tracer, Web server, Web server cluster, or user server).
-
Specify two arguments for the start subcommand to start the specified J2EE application, J2EE resource adapter, or JavaBeans resource.
When app, resAdapter, or resJavaBeans is specified for the first argument, the subcommand starts the J2EE application, resource adapter, or JavaBeans resource that is specified by displayName (the second argument) and has been imported into the J2EE server specified by the -t option. In the case of a J2EE server cluster, the operation is expanded to its member J2EE servers.
If a logical server that is not a J2EE server (including a J2EE server cluster member) or that is not a J2EE server cluster is specified by the -t option, an error occurs. A host name cannot be specified by the -t option.
- Notes
-
-
If execution of the start or stop subcommand is immediately followed by a similar operation on the same logical server, specify the -s option in the subcommand so that the subsequent command is executed after completion of the subcommand.
-
If the list subcommand is specified, the status existing when the subcommand is invoked is reflected in the information that the command returns, regardless of the execution states of other subcommands (such as start and stop). Therefore, the command might return the status working before the processing of the start subcommand is completed or the status stopped before the processing of the stop subcommand is completed.
-